usdigitalmarketingindex.com SEO
Why might Google index a page absent from every submitted XML sitemap?
Updated November 15, 2026
Because a sitemap is one way Google finds URLs, and following links is another. A page that appears in your navigation, in an article’s body, or in a link on someone else’s site can be discovered, crawled, and indexed without ever being listed in a sitemap. Google’s documentation says as much from the other direction: “If your site’s pages are properly linked, Google can usually discover most of your site” (Google’s overview of sitemaps). A sitemap adds URLs to what Google knows about. Leaving a URL out removes nothing, and it is not a way to keep a page out of search.
Internal and external discovery paths
A URL can reach Google by several routes.
| Route | Example |
|---|---|
| Internal links | Navigation, footer, body links, related-content modules, pagination |
| External links | Another site links to the page |
| Redirects | An old URL forwards to it |
| Canonical and alternate references | Another page names it in a canonical or hreflang tag |
| Sitemaps | Listed in a submitted file |
| Previously known | Google crawled it in the past and remembers the address |
Only the fifth route is under the control of the sitemap. A page missing from the file and present in the main menu is discoverable through the first.
Observed versus submitted sitemap state
Work through an example. A company publishes a careers page, links it from the footer of every page, and never adds it to the sitemap, because the sitemap is generated from the blog and product databases only.
Is the URL in a submitted sitemap?
no
|
Is it linked from a page Google crawls?
yes: the footer of every page links to /careers/
|
Can Google fetch it? (not blocked by robots.txt, returns 200)
yes
|
Is it allowed to be indexed? (no noindex, canonical points to itself)
yes
|
Result: eligible to be crawled and indexed through links alone
Decision points for the publisher:
Do you want this page in search?
yes -> add it to the sitemap so your records match reality
no -> add noindex, or restrict access; removing it from the
sitemap, where it never was, changes nothing
In the example, Google finds the careers page on its first crawl of any page, through the footer link. The sitemap’s silence about it is irrelevant to that outcome.
Search Console shows the gap. In the page indexing report, the view for all known pages can be compared with the view filtered to submitted pages. URLs that are indexed and not submitted are pages Google found by other means.
Index inspection
To see how a specific unlisted URL was found, inspect it in Search Console.
- Discovery: the inspection result lists sitemaps that include the URL, if any, and referring pages through which it was found. For the careers page, the sitemap field would be empty and a referring page would be shown.
- Crawl: the last crawl date and whether the fetch succeeded.
- Indexing: whether indexing is allowed, and the canonical Google selected.
Then check the site itself. Crawl it and list every URL reachable by links, and compare that list with the sitemap. Three groups result.
| Group | Meaning | Action |
|---|---|---|
| In sitemap and linked | Normal | None |
| Linked, not in sitemap | The sitemap is incomplete, or these are pages you did not mean to expose | Add wanted pages to the sitemap; deal with unwanted ones properly |
| In sitemap, not linked | Orphans that depend on the sitemap | Add internal links |
The second group is where surprises are found: old landing pages, test pages, filtered listings, staging paths linked by mistake.
Correcting publisher expectations
Three beliefs need correcting.
A page left out of the sitemap will stay out of Google. It will not, if anything links to it. To keep a page out of search, use noindex on a crawlable page, or put it behind authentication. Google’s documentation on noindex says that when Googlebot extracts the rule, it “will drop that page entirely from Google Search results, regardless of whether other sites link to it” (Google’s documentation on blocking indexing with noindex).
Removing a URL from the sitemap removes it from the index. It does not. Sitemap inclusion is described by Google as a weak signal toward canonical selection. Its absence is no instruction at all.
Sitemaps therefore do not matter. They do. On a large site, a new page, or a page with few links, the sitemap may be the fastest or only route to discovery, and it tells Google which URLs you prefer. The finding here is narrower: a sitemap is additive.
What to do with an unexpectedly indexed page:
- Decide whether it should be in search.
- If yes, add it to the sitemap, so that the file reflects the site, and confirm its canonical points to itself.
- If no, apply noindex and keep it crawlable until it drops out, or restrict access, or remove the page and return a not-found status.
- Find and remove the links that exposed it, if it was never meant to be public.
- Check whether similar pages exist. One unexpected URL may be a sample of a pattern.
Keep the sitemap generator honest. If it draws from some content types and not others, as in the example, whole sections of the site are missing from it, and the file gives a false picture of what you have asked Google to consider.
How a sitemap should be built and partitioned to do its real job on a large site is covered in the guide to how an XML sitemap supports URL discovery on a very large website.
The point to keep: a sitemap is a list of what you recommend. Google indexes what it finds and judges worth keeping, whether or not it was on the list.
Add your comment to this answer