Compare the response, the rendered page and navigation
Use three views during diagnosis: the server response, the page after scripts run and the routes reached through internal navigation. Each can fail independently. A static export might contain correct metadata on direct load while client navigation restores older metadata. A client-rendered article might look complete after an API call while its initial response contains little useful information. Record which behavior you observed rather than calling the whole site crawlable.
Worked example
Illustrative scenario; not a claim of measured client results.
Imagine a new Insights library replacing an old application route. Direct loading shows the new articles, but clicking Insights from the homepage opens the old collection. Test that exact journey and inspect whether the application intercepts the link. The remedy may involve rebuilding the route or using a normal navigation to the deployed document. Do not infer correctness from a screenshot of the destination alone.
Checks, limitations and next decisions
For failures, identify the first missing resource or incorrect response rather than changing all scripts. Check blocked requests, error messages and delayed content on representative templates. Verify canonical and indexing directives after rendering as well as before it. Finish with a fresh browser session and a direct URL inspection so cached state does not conceal a navigation regression.
A practical starting point
Work through these checks in order. Use the results to decide what needs to change in your own workflow.
- Inspect the raw HTML for the main heading, useful content and canonical.
- Open the page with its scripts running and compare the content and links.
- Use URL inspection where available to identify rendering or resource errors.
A mistake to avoid
Do not assume that a successful homepage render proves every template works.
How to check progress
Track rendering differences across homepage, service, category and article templates.
Your action checklist
Use this checklist while reviewing your own setup. Checkmarks are temporary and stay in this open page.
For the wider decision process, read Diagnosing a page that Google has not indexed.
Further reading
Official background resources for this topic. The workflow above is general guidance, not a guarantee of a particular result.
AI-assisted editorial content. Examples are illustrative, not client case studies. Read our editorial policy or report a correction.
