On the 404 page, the status check services give the code 200, but the logs show 404. How to make the SEO specialist happy?

M

Mikhail2018-05-10 10:54:58

Search Engine Optimization

Mikhail, 2018-05-10 10:54:58

На 404 страницу сервисы проверки статуса отдают код 200, но логи показывают 404. На неизвестную страницу тоже отдает (в сервисах) 200, хотя в логах и по факту 301й редирект на 404, т.к. сделано в виде заглушки. Пересмотрели и проверили всё, но ничего не понятно. Робот будет тоже видеть 200, что плохо для seo. Заранее спасибо.
P.S. сайт на bitrix.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

H

hOtRush, 2018-05-10
@hOtRush

I don't know what you're talking about, 200 is given

curl https://grandmanor.ru/404.php -v
*   Trying 87.236.16.121...
* TCP_NODELAY set
* Connected to grandmanor.ru (87.236.16.121) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=grandmanor.ru
*  start date: Apr 26 02:58:15 2018 GMT
*  expire date: Jul 25 02:58:15 2018 GMT
*  subjectAltName: host "grandmanor.ru" matched cert's "grandmanor.ru"
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x557028b87da0)
> GET /404.php HTTP/1.1
> Host: grandmanor.ru
> User-Agent: curl/7.52.1
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200 
< server: nginx-reuseport/1.13.4
< date: Thu, 10 May 2018 08:17:30 GMT
< content-type: text/html
< content-length: 274
< last-modified: Wed, 09 Mar 2016 20:03:59 GMT
< etag: "56e081af-112"
< accept-ranges: bytes
< 
<html><head><script>function set_cookie(){var now = new Date();var time = now.getTime();time += 19360000 * 1000;now.setTime(time);document.cookie='beget=begetok'+'; expires='+now.toGMTString()+'; path=/';}set_cookie();location.reload();;</script></head><body></body></html>
* Curl_http_done: called premature == 0
* Connection #0 to host grandmanor.ru left intact

S

synapse_people, 2018-05-10
@synapse_people

look towards nginx configs, apparently it caches the response incorrectly

M

Mikhail, 2018-05-28
@Bearatol

In general, the problem was in the hosting itself.