Content revised 20 October 2026.
You can't reproduce Google’s complete ranking process in a browser. You can inspect access, rendered content and indexing signals to find specific problems with a page.
Begin with the public request
Open the intended URL while signed out and record its response. Check whether it redirects, fails or requires a login. Confirm that the main information is available without a private session. A page that looks fine to an administrator may behave differently for a visitor.
Inspect the content and instructions
Review the visible answer, title, heading, canonical and robots directives. Check whether important text depends on an interaction that makes it difficult to discover. Compare the HTML source and rendered page when JavaScript changes the content.
Use the relevant inspection evidence
- Review the URL in Search Console when you have verified access.
- Distinguish the indexed report from a live test.
- Check reported access or rendering problems.
- Compare the reported canonical with your intended version.
Check media and internal links
Make sure relevant images load, alternatives describe their role and links lead to accessible destinations. Avoid reducing this review to a fixed title or description character count. Display length varies, and a short field can still be inaccurate or unhelpful.
Turn findings into a repair list
Record the affected URL, observed fault, proposed fix and test. A successful fetch doesn't guarantee indexing, and indexing doesn't guarantee a particular position. The useful outcome of this inspection is evidence you can act on, such as an accidental noindex instruction or missing content, rather than a claim that a tool sees every ranking signal.
Official guidance: Google’s URL Inspection guide.