The Sitemap Was Read, but the Page Is Not Indexed: What Do You Check First?

“Sitemap success” means Google could read a file. It does not mean Google crawled or indexed every URL in it. Google says a sitemap helps discovery without guaranteeing crawl or indexing. Diagnose the specific page that matters to the business before treating every “not indexed” URL as an error.

Keep the report dates attached to their numbers

In one November 5 site review, a Pages report showed 83 indexed and 129 not indexed, including 121 marked “Discovered – currently not indexed.” Its last chart point was October 23. The sitemap report showed 252 URLs discovered when it was last read on November 3. Dividing 83 by 252 would look like a coverage rate, but it mixes different dates and different URL sets. Google's Page Indexing explanation says its totals are as of the last date on the chart and omit URLs Google does not know about. The sitemap's discovered number is not a matching denominator for that earlier chart.

For a new service page, record its exact canonical URL, publication date, sitemap lastmod, the sitemap's last-read date, and the Page Indexing chart date. That is an observation log, not an indexing forecast. If the report is older than the page, the report cannot yet describe that page's current state.

Inspect one URL in a useful order

1. Check the public URL and internal path. Does the exact HTTPS URL return the intended page, with a stable canonical and no accidental noindex? Can a visitor reach it from relevant navigation or another page using an ordinary link? Google notes that linked pages are usually easier to discover and a sitemap is especially useful when pages are hard to reach through links. See its sitemap guidance.

2. Use URL Inspection's indexed view. Enter the exact URL in Search Console. Read the current Google index verdict, last crawl if present, crawl/index permission, and Google-selected canonical. This view reflects Google's stored version, not necessarily today's live page. Google's URL Inspection guide distinguishes the indexed view from the live test.

3. Run a live test if the page changed or the indexed verdict needs explanation. Check the current fetch, rendered text, response, and indexability signals. A passing live test shows that the inspection crawler can access the page now; Google explicitly says it cannot guarantee indexing or predict all canonical decisions. Fix a concrete defect if found, then inspect again. If it passes and the indexed report is older, allow time for Google's systems to update rather than treating the mismatch as a new bug. The live-test limits are documented here.

4. Decide whether the page deserves a separate canonical. A near-duplicate landing page, a temporary sort URL, or an obsolete campaign page may be correctly excluded. Google's Page Indexing help says not all non-indexed URLs are problems; prioritize important canonical pages. For an essential page with distinct value and no technical blocker, verify sitemap and internal links, then consider one indexing request. A request is a queue signal, not an acceptance or ranking promise. Google's request guidance says so.

This workflow is narrower than a post-redesign SEO migration investigation: it answers why this URL, now is missing. In an ARCHV website project, the useful handover is a list of important canonical URLs, their link paths, sitemap status, and dated inspection evidence, so a later owner can repeat the check without guessing from headline totals.