01 / REVIEW STEP
Start with access
Open the page without signing in. Record its final URL, HTTP status and capture time. A login wall, TLS failure or repeated server error needs attention before you rewrite a headline. A successful browser visit still does not establish that Google can access the page. Compare crawler behavior when the evidence calls for it.
02 / REVIEW STEP
Check the indexing instructions
Inspect the response X-Robots-Tag header and the robots meta tags in the HTML. A noindex or none directive can exclude a page even when another tag says index. Confirm whether exclusion is intentional: staging pages, account screens and private reports should usually remain private. Do not remove a directive just to make an audit look cleaner.
03 / REVIEW STEP
Understand the canonical
A canonical link identifies a preferred version among duplicate or similar URLs. Check where it points, whether that destination works, and whether the intended content matches. Multiple plugins can emit conflicting canonicals. Keep the correct source of metadata rather than adding another tag. Google may select a different canonical; inspect Search Console before asserting which URL is indexed.
04 / REVIEW STEP
Make the page understandable
Use an accurate title, a readable heading hierarchy and an honest description of the page. Look for duplicate title or description tags. A description can help communicate the page, but Google may display different snippet text. A single H1 is a useful house convention, not proof that a page will rank.
05 / REVIEW STEP
Inspect the experience
Check the important action on a real phone-width layout. Give informative images useful alt text and reserve image space where the layout needs it. Test keyboard focus and contrast. Source-code checks cannot establish accessibility conformance, a Core Web Vitals pass or a conversion improvement.
06 / REVIEW STEP
Verify and preserve a rollback
Change one diagnosed problem at a time. Save the original configuration and source. Recapture the same URL, check for new conflicting tags, and confirm that related pages still work. Indexing and search outcomes require later evidence; a corrected HTML tag establishes only that the tag changed.
Your next-step checklist
- The reviewed URL and date are recorded.
- Both page and response directives were inspected.
- Canonical intent and target were reviewed.
- The page works at phone width and with a keyboard.
- The original is preserved and the change can be reversed.
Primary references
These links support the process and policy context. Check the current source before making a time-sensitive decision.
Turn the question into a defined scope.
Agree the page, deliverables and evidence needed before work begins. A useful review should explain what to change and what remains uncertain.
Request a technical review scope