Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Both numbers can be accurate at the same time. The sitemap figure and the URL Inspection result are built from different data, measured at different scopes, and updated on different schedules. A gap between them is common and is partly documented by Google, but the numbers alone cannot tell you which URLs are affected or why. The steps below show how to find the cause for your property.
Why the two reports can disagree
The figures you reported come from two different views in Google Search Console. The Page indexing report is an aggregate view of the URLs Google has tried to crawl for the property, grouped by status. URL Inspection reports Google’s status for one specific URL at a time. A count of zero in one view and a count of 23 in the other do not have to contradict each other, because they are not answering the same question.
As an Amazon Associate I earn from qualifying purchases.
The table below sets out the four signals people usually compare.
| Signal | What it answers | Scope | Time basis |
|---|---|---|---|
| Page indexing report | How many crawled URLs fall into each indexing status for the property | Aggregate, whole property or sitemap-related grouping | Tied to the report’s latest chart date; not stated as real-time |
| URL Inspection, Google Index result | Whether Google’s index holds this URL and, if not, a descriptive reason | One URL | The indexed information Google holds for that URL; the exact refresh time is not stated |
| URL Inspection, Test live URL | How Google fetches and renders the page right now | One URL | Current fetch at the moment of the test |
| Sitemaps report | What a submitted sitemap contains and how many of its URLs are reported as indexed | One sitemap | Reflects Google’s processing of that sitemap; the exact lag is not stated |
The Sitemaps report and the Page indexing report are related but not equivalent. A sitemap can list URLs that Google has not yet processed into the same grouping, and an indexed URL can exist without being tied to the sitemap you are looking at.
#1 Best Overall
What Google documents about this gap
Google’s Page indexing report help page explains the specific case where a URL is indexed according to URL Inspection but missing from the Page indexing report:
“If the page is not in the Page indexing report but it is listed as indexed in the URL Inspection report, it was probably indexed recently, and will appear in the Page indexing report soon.” (Google Search Central Help, “Page indexing report”)
This is a documented possible explanation, not a diagnosis of your property. It fits a recently indexed site, but it does not confirm that timing is the only cause.
Google’s help page on sitemap statistics adds a separate point:
“Google doesn’t guarantee that our system will index all the URLs in a Sitemap, for many reasons.” (Google Search Central Help, “Sitemap stats don’t look accurate”)
A sitemap’s URL count is therefore a list of what you asked Google to consider, not a forecast of what will be indexed.
Rank #4
URL Inspection also reports which sitemaps are associated with a URL. According to Google, this field covers sitemaps submitted in the Sitemaps report or listed in robots.txt. Google also acknowledges that an association may occasionally go unreported even when the URL was submitted, so a blank sitemap field is a reason to check, not proof that the URL is missing from your sitemap.
Free tools Windows power users keep installed
One-click scans. No signup required.
Step-by-step: find out which URLs are actually indexed
- Pick the 23 URLs that URL Inspection reported as indexed, and the exact sitemap they belong to. If you do not have the list, export the URLs from your sitemap file and compare them with the URLs you inspected.
- For each URL, open URL Inspection and read the Google Index result. Use this verdict, not the live test, to decide whether Google holds the URL in its index.
- Open the Page indexing report and note the latest chart date. Compare it with the date you ran URL Inspection. If the inspection is newer, the report may not yet reflect the URL.
- For any URL the Page indexing report does not show, record its exact indexing status and the reason given in URL Inspection. Keep a short log with the URL, the date, and the result so you can compare later checks.
- Check the sitemap itself: confirm that it is the one submitted in the Sitemaps report or declared in robots.txt, and that each inspected URL appears in it.
- Wait for Google’s processing, then re-inspect a sample of the same URLs and compare the results with your log.
Troubleshooting branches
If the Google Index result says indexed but the Page indexing report still omits the URL
This matches the recent-indexing case Google describes. Re-check the Page indexing report after the next processing cycle. If the chart date has moved and the URL still does not appear, record that observation with dates and the inspected URL.
If the Google Index result says not indexed
Use the reason shown in URL Inspection as the starting point. Do not assume the URL is indexed just because the live test succeeds. A live test checks whether Google can fetch and render the page now; it does not check sitemap membership and does not test every indexing condition.
If the live test passes but the index result does not
This is the most common source of confusion. The page is reachable now, but the index record reflects Google’s stored state for the URL. Compare the two results side by side for a few URLs before drawing a conclusion about the whole property.
If the sitemap field is empty for an indexed URL
Confirm that the URL is in the sitemap you think it is in. Because Google acknowledges occasional gaps in sitemap association reporting, an empty field alone does not establish that the URL was never submitted.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat to do with the sitemap count
- Treat the number of URLs listed in the sitemap as the number you submitted, not the number Google will index.
- Look for patterns in the URLs that are not indexed, such as a shared template, a directory, or a recent batch of new pages.
- If the sitemap is much larger than the indexed set, review whether the extra URLs are useful to searchers before submitting more of the same kind.
What the figures cannot establish
The 0 and the 23 are the counts you reported. Neither can be checked independently from this description. To identify the cause for your property, you would need the individual URLs, their Google Index results, the Page indexing report’s latest chart date, the sitemap file and the sitemap you submitted, and whether each inspection was a Google Index check or a live test. Google’s documentation explains how each report works and why timing can produce a gap, but it does not diagnose a specific property.
Most of these gaps resolve as processing catches up with the sitemap. If the discrepancy persists across several re-checks, use the logged URLs and dates to narrow the problem to a template, a directory, or a sitemap submission rather than the whole property.
Quick Recap
“
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
