HTTP 200, but the page is essentially missing: how to check for soft 404
We examine how to distinguish a soft 404 from a standard error, verify the exact URL in Google and Yandex, and select the correct response: 200, 301, 404, or 410.
Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в личном кабинете.
Страны не найдены. Попробуйте другое название или код.

One point for every published article.

We examine how to distinguish a soft 404 from a standard error, verify the exact URL in Google and Yandex, and select the correct response: 200, 301, 404, or 410.


The October 26–27 incident affected part of the Cloudflare Workers schedules: jobs could be delayed, skipped, or launched again. We examine how to perform a safe reconciliation without a mass restart.


A Brotli decompression error can cause application crashes, disclosure of data from memory, or code execution. We list the fixed Node.js versions and the procedure for checking servers, containers, and integrations. Separate section: important update for Windows PHP builds.


We examine five distinct page states—Sitemap entry, current response, crawling, indexing, and impressions—and compile a separate checklist for Google and Yandex.


We explain why free gigabytes do not rule out file limits: where to check File Usage and inode, what to request from support, and when cleanup or a different plan is needed.


We analyze SPEED, PMEM, IO, IOPS, EP, and NPROC in CloudLinux: what data to request from support, how peaks differ from faults, and when upgrading a plan is truly justified.


On October 24, Oracle issued a critical warning, CVE-2026-114820. The new Java patch removes root certificates: who should verify their runtime environment, TLS trust, and API connections.


On October 23, Yandex Cloud announced a new location for ru-central1-a resources. Access is being rolled out in stages; virtual machines and some databases remain stopped. We examine what to verify before restoring traffic.


I explain why a green lab score can differ from field metrics, how to compare like-for-like conditions, and how to find the cause without guesswork.


On October 23, Ruby versions 4.0.9, 3.4.12, and 3.3.13 were released. We explain which applications are affected, why the GitLab package requires separate verification, and what to ask the server administrator.


On October 23, a network incident affected some Cloudflare customers in North America. The provider reported the issue was resolved. We explain who should check task queues and incomplete operations.


Fixes for two critical PHP vulnerabilities were released on 21 October, and on 23 October the developers clarified an additional rare risk. We explain the fixed versions and what to ask the administrator of a 1C-Bitrix website or another PHP-based system.

Public pages use basic statistics. Our recording and Yandex Webvisor require your permission. You can keep basic statistics or disable all analytics.
Operator: General IT Rus LLC, INN 2310208877. Statistics and recording help improve the website. Basic statistics: pageviews, a random daily ID, a public URL and time. The ID lasts until Moscow midnight. Original records: up to 48 hours; totals: up to 7 years. Campaign tags and a technical identifier are sent by our server to the existing Yandex tag. Visitor IP, User-Agent and cookies are not included in this transfer. If selected, its browser code collects technical data, cookies, actions and masked page snapshots; recordings last 15 days. Inputs, chat and account areas are hidden. Interaction recording requires permission: clicks, scrolling, technical information and filtered public-page snapshots. Events: up to 7 years; IP and snapshots: up to 90 days. Permission is remembered for up to 365 days; full opt-out remains until changed. Basic statistics only disables recording; Disable all analytics stops new analytics. Previously sent data is not automatically deleted. Withdrawal and requests: support@git.ru. Full terms are linked below.
Your browser requests no tracking: analytics is off.