Diagnosing a page that Google has not indexed

Identify which stage has failed

This workflow is for a public page that you genuinely want people to find. Before changing anything, record its exact URL, purpose and publication date. A service page, a filtered listing and a private customer portal should not have the same indexing goal. Check the URL in Search Console rather than relying on a search for the page title.

Google's URL Inspection documentation distinguishes its stored index information from a live test. A successful live test does not promise indexing or predict the canonical Google will choose. Keep those two kinds of evidence separate in your notes.

Build a small evidence record

Use one row per affected URL with columns for expected status, observed response, declared canonical, Google-selected canonical, robots state, discovery source and next action. Include the date of Google's last crawl. If that date precedes your deployment, the report may describe an older page. Record the change and wait for fresh evidence before declaring that it failed.

Open the page on a phone as well as a desktop. Confirm that the main answer exists in the initial HTML and remains available after scripts load. A polished screenshot can hide an empty response, a broken application state or a login dependency. Check the destination after every redirect, because a working homepage does not prove that the article URL works.

Worked example: a new AI service guide

Imagine a business publishes a guide about preparing documents for an AI assistant. The URL returns 200 and has no noindex directive, but its canonical points to the general AI services page. The library also links to a tracking version of the URL. In this hypothetical case, start by making the guide's self-canonical, internal links and sitemap agree. Do not add hundreds of links or rewrite the entire article before correcting the contradictory signals.

Now consider a different guide with correct technical signals but only a definition and three generic sentences. Expand it with a document-selection example, failure cases and a useful checklist. If another page already answers the same question better, consolidation may be more useful than keeping both. The decision is about reader value, not meeting a universal word count.

Define completion realistically

Separate implementation completion from search outcomes. You can verify that a fix is deployed, the URL is accessible and links are consistent. Only later can you observe whether Google recrawls, indexes and sends relevant visits. Submit a recrawl request for a materially improved priority page once; repeated requests are not a monitoring strategy. Track the category of failure across several pages so that one template repair can address a pattern.

Continue with canonical selection if duplicate signals are involved, or orphan-page discovery if the page lacks internal links.

A practical starting point

Work through these checks in order. Use the results to decide what needs to change in your own workflow.

1. Inspect the exact canonical URL in Search Console and record its reported status.
2. Check the live HTTP response, robots rules and page-level indexing instructions.
3. Compare the rendered page with the intended content, then check internal links from relevant indexed pages.

A mistake to avoid

Repeated indexing requests do not repair a blocked page or weak content.

How to check progress

Track status changes for the same URL, keeping the inspection date beside the result.