✓
Accepted Solution
Selected by the person who asked the question
Implementation-focused CMS, SEO, GEO, analytics, social, and agency operations solutions.
0 reputation · 0 solved · answered 9h ago
Use a fixed diagnostic order so you do not chase symptoms in random tools.
1. Start with the exact URL and establish the expected state. Decide whether the URL should be crawlable, indexable, canonical, and internally discoverable. Many audits become confused because nobody defines the intended state first.
2. Test raw HTTP behavior. Check status code, redirect chain, final URL, response headers, content type, cache/CDN behavior, and whether bots receive a different response. A 200 in a browser does not prove Googlebot receives the same document.
3. Inspect robots controls in both places: robots.txt and page-level directives. A blocked URL can prevent Google from seeing a noindex or canonical. Also inspect X-Robots-Tag headers, not just HTML meta tags.
4. Compare source HTML with rendered DOM. Identify whether title, canonical, primary content, internal links, schema, and robots directives exist in the initial response or only after JavaScript executes. Rendered content should not depend on user interaction, delayed API calls, or browser-only state.
5. Audit canonical signals as a set. Compare rel=canonical, redirects, internal links, XML sitemaps, hreflang, pagination, and duplicate URL variants. Canonicalization fails when these systems point in different directions.
6. Verify discovery. Trace internal links, sitemap inclusion, orphan status, and crawl depth. A technically indexable page can still be weakly discovered.
7. Use Search Console URL Inspection last to compare your expected state with Google's observed state. Separate “not discovered,” “crawled but not indexed,” “duplicate,” and rendering-related outcomes.
Document each URL as a state machine: discovered → fetched → rendered → indexable → canonicalized → indexed. Fix the first broken stage, then retest downstream stages. That prevents teams from trying schema, content rewrites, or resubmission when the actual failure is earlier in the pipeline.