Loading page
This may take a few seconds.
Loading page
This may take a few seconds.
If reChecker is not working correctly, describe the problem and the page where it happened. Leave an email or phone number; we will reply after checking.
Сохранённые факты, точный охват и разрешение владельца: объясняем, как формируется публичная версия проверки и когда она может попасть в поиск.
The breakdown is based on the saved results of a successful check in reChecker. After a preview and the owner’s approval, we save a separate public version with approved metrics, issues, page examples, and recommendations. Viewing the page again doesn’t run a new audit or rewrite the text.
A registered account does not make checks public by itself. A new private check does not automatically replace published data. To update the report, the owner opens the new result, reviews the preview, and publishes it.
The start of the analysis specifies a particular URL and the scope of the check. A single-page result applies to that page, even if the report’s permanent URL contains the domain name. This result does not confirm the status of all pages and subdomains.
We report the number of pages checked during a site crawl. Published examples may be part of this set. A limited crawl doesn’t mean we checked every URL on the site; limitations are listed in the report itself.
The check date shows when the source data was collected. Publication may happen later. The public content modification date is updated when the published version or its visible history changes, not every time it’s viewed.
If the next check doesn’t provide sufficiently reliable data, the previous available version may remain accessible with its original date. It is not presented as a fresh check.
The technical score summarizes the checks performed. It doesn't measure rankings on Yandex or Google, demand, revenue, or the likelihood of site growth. A high score doesn't guarantee that there are no vulnerabilities or issues outside the scope of the checks.
For each issue, we show what the check found, what impact it may have, what action to consider, and how to check the result again. These recommendations are based on specific data; they are not a confirmed explanation for a drop in search traffic.
“Could not check” and “No data” mean there is no reliable result. They should not be read as a confirmed website issue. We show “0” separately from a missing measurement.
History uses published versions from the same owner with compatible conditions: matching checked page addresses and methodology version. If the scope changes, we explain why comparison isn’t available.
If the new run checked fewer pages or the methodology changed, a missing issue does not count as fixed. For compatible checks, we distinguish between new, ongoing, and no longer detected issues.
Before publication, the owner can see exactly what will be visible to visitors. The public version does not include raw results from all checks, account data, private search queries, questions for AI, or integration data. URLs with parameters and sensitive URLs are excluded from examples.
You can revoke permission in the publishing settings for a specific result. We will stop access to this version and remove it from the current catalog and sitemap. Search engines and third-party visitors control when their saved copies are updated.
Consent to publication and indexing, an active saved source, enough reliable measurements, and a substantive analysis are required. In addition, the same owner must have at least three distinct successful runs under compatible conditions. Saving the same run again doesn’t increase this count.
An editor can approve a high-quality, independent analysis after a single review. Moderation does not replace the owner's permission or data quality checks. A public summary without detailed measurements or recommendations remains available at the old address with noindex.
A large HTML document may exceed the amount of data available to the built-in validator. If the other checks produced reliable data, this analysis may be allowed with a separate explanation: HTML validation was not performed. An absent result is not treated as confirmation that the markup is valid.
We include only approved permanent pages in the sitemap. The lastmod value reflects a significant change to public content. A page’s presence in the sitemap does not guarantee indexing; this follows from Google sitemap recommendations.
The overall structure of audits may be similar; their value should come from specific measurements, evidence, and recommendations. Generating many pages without adding value runs counter to Google's rules on scaled low-value content. We don't add made-up errors or text just to increase volume.