Why a sitemap URL can be discovered but not indexed
A sitemap helps Google discover a canonical URL, but it does not require Google to crawl or index it. Diagnose access, duplication, page value, and internal links separately.
Written for a small-site owner who submitted a valid XML sitemap and sees a URL reported as discovered but currently not indexed.
Key facts
- Google states that submitting a sitemap is a hint and does not guarantee crawling or indexing.
- A sitemap should list fully qualified canonical URLs that return useful public content.
- Internal links explain priority and context in ways a sitemap entry cannot provide by itself.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
What does discovered but not indexed tell you?
The status tells you that Google knows the URL but has not added the inspected version to the index at the time of the report. Discovery may come from the sitemap, an internal link, an external link, or a previous crawl. It does not identify one cause. Google may delay a crawl, crawl and later consolidate the URL, or decide that another page is the representative version. Start by separating what the report proves from what it does not. It proves awareness of the URL. It does not prove that the sitemap is broken, that crawl budget is the limiting factor, or that resubmitting the same file will change the decision.
- Inspect one representative URL instead of treating every discovered URL as the same problem.
- Compare the report date with server logs or hosting analytics to see whether Googlebot requested the URL.
- Check whether another canonical URL already appears for the same content or intent.
Verify the sitemap entry before changing the page
Open the generated sitemap and verify the exact string Google receives. The entry should use an absolute HTTPS URL, the production hostname, the stable canonical path, and an accurate `lastmod` value when you include one. Remove redirects, tracking parameters, preview hosts, search-result filters, and URLs that intentionally use `noindex`. A valid XML file can still carry the wrong inventory. Google also ignores sitemap `priority` and `changefreq` values, so changing those fields will not solve selection. Once the file is correct, submit it once and use the Sitemaps report to check retrieval and parsing. Repeated submissions do not turn a hint into a command.
- Fetch the sitemap as an unauthenticated user and require a successful response with XML content.
- Compare every listed host with the canonical host used in page metadata and internal links.
- Set `lastmod` from the last significant content change, not the deployment or request time.
Sources: 1
Check the URL response and canonical signals
Fetch the listed URL and follow its response without relying on the browser address bar. A sitemap URL that redirects wastes the clean inventory signal and can expose a migration mistake. The final page should return `200`, allow crawling, permit indexing, and declare a canonical that agrees with the final URL. Inspect the rendered page for a real title, main heading, answer, and links. If the page is an app shell that depends on a failed API call, Google may receive little usable content even though the route itself responds. If several URLs show the same main content, align redirects, canonicals, sitemap entries, and internal links on one preferred version.
- Test HTTP status, redirect target, robots controls, and canonical as four independent checks.
- Compare raw HTML and rendered HTML when JavaScript supplies any part of the main answer.
- Do not block a duplicate in robots.txt before Google can read the canonical signal on that duplicate.
Sources: 2
Give the page a reason to be selected
An eligible URL still needs a distinct purpose and enough content to satisfy it. Compare the page with other URLs on your site before comparing competitors. Generated tag pages, nearly empty tool states, and city pages with swapped place names often repeat an existing intent without adding a new decision, example, or dataset. Write the primary question and confirm that no stronger internal page already answers it. Then make the opening answer concrete, show conditions or examples that change the answer, and attach primary sources to material claims. The goal is not a word threshold. The goal is a page whose useful content cannot be replaced by a short label and a link elsewhere.
- Merge two pages when the same reader would choose either result for the same decision.
- Add an example, calculation, diagnostic sequence, or original dataset only when it helps complete the task.
- Return a genuine 404 for absent resources instead of publishing an empty template for every possible slug.
Sources: 2
Connect the URL to the site and monitor one change
A sitemap is an inventory file; internal links show how the page belongs to the site. Link from a relevant hub, tool result, or adjacent guide using anchor text that names the destination. Avoid placing every new article in a generic footer because that provides weak topical context and poor reader value. After correcting the strongest issue, request inspection for a small sample and wait for processing. Track whether Google crawls the page, selects the expected canonical, records impressions, or changes the exclusion reason. If nothing changes, reassess intent and duplication before adding more technical signals. The evidence should decide the next edit, not the discomfort of seeing an exclusion count.
- Add at least one contextual link from an already discovered page that a reader would use next.
- Monitor a representative sample rather than resubmitting dozens of unchanged URLs.
- Keep a dated log of the issue, the single change, and the later inspection result.
Put it to work
Find the highest-impact fix on your site.
Verify response status, crawl controls, canonical alignment, visible content, and internal links before resubmitting anything.
Audit the sitemap URLSources
- 1.Google Search Central: Build and submit a sitemapChecked 2026-07-26
- 2.Google Search Central: Troubleshoot crawling errorsChecked 2026-07-26