Diagram the full search process for one of your target pages and identify where it might break.
Choosing a target page: Pick a page that already gets some impressions in Search Console but ranks below position 10 — this gives you data to work with and a realistic gap to analyze.
Diagnosing the crawl stage: The URL Inspection tool in Search Console shows you the last crawl date, the user-agent used, and the rendered HTML Google saw. Compare that rendered HTML to your browser's view source to detect rendering failures.
Diagnosing the index stage: The same URL Inspection tool shows Google's indexing decision and the canonical URL Google selected — if it differs from your intended canonical, that is an indexing-layer problem, not a crawl problem.
Diagnosing the rank stage: If the page is indexed but ranks poorly, the failure is in relevance, authority, or experience signals — compare directly to the top three results using the framework from the Core Ranking Signals task.
Target page: /blog/what-is-compound-interest
Process diagram: Discovery → Sitemap (submitted, no errors) → Crawl → Render (JavaScript delayed: 1.2s Googlebot render lag) → Index (indexed, canonical confirmed) → Rank (position 14, relevance strong, authority gap)
Failure points identified:
Top intervention: Add three contextual internal links from high-traffic calculators that already rank on page 1 — estimated 2 hours, highest equity transfer with no engineering dependency.