04 / Recheck and proof
A fresh recheck answers a narrow question: does this supported condition pass on this page now?
Failure or unknown evidence never confirms a repair.
Fresh evidence
What this does not tell youPassing a technical condition does not establish that Google has indexed the page, selected its canonical or changed its position.
See both outcomes
Illustration with example.com data, not a customer result.
The example page has no canonical tag. First decide which URL should represent this content. A canonical is a preference signal, not a command to Google.
Choose how you edit the page. These are generic steps, not WordPress, Shopify, Wix, Squarespace or Webflow tutorials.
1. Confirm that https://example.com/ is the preferred URL.
2. Add this tag inside the page’s <head>.
3. Save and publish the change.
<link rel="canonical" href="https://example.com/">
An acknowledgement records that you followed a step in this session. It is not evidence that the condition passes, and it is not durable repair history.
The actual guide fetches fresh evidence for one supported condition on one page. This illustration makes no scan request. Choose an outcome to see both paths.
Only the named condition and page are confirmed. Other affected pages still need their own evidence.
Review the current evidence. A failed fetch or an unknown result never becomes a pass.
Wider comparisons
Compare two dated scans of a domain: score movement, check and page changes, readable-content overlay, raw HTML diff and available screenshots. Screenshots have been captured since 7 July 2026. The homepage overlay is free; other pages are paid.
Open the scan comparisonSet a baseline and collect weekly snapshots. The receipt uses stored scans and real Search Console rows only. It needs dated evidence and a valid connection for search metrics.
Understand the connected data