Indexed, Not Submitted in Sitemap: What It Means + How to Fix It

This is one of the more misleading-sounding statuses in Search Console, because it reads like an error and almost never is one. "Indexed, not submitted in sitemap" simply means: Google has this page in its index, and your sitemap didn't tell it to. That's it. Google found the URL some other way — usually an internal link, sometimes an external one — crawled it, and indexed it entirely independent of your sitemap file.

The question worth asking isn't "why isn't this in my sitemap" as an alarm. It's "should this page be indexed at all, and is my sitemap missing something it should actually include."

Why this happens (it's not a bug)

Sitemaps are a discovery aid, not a gate. Google has never required a URL to appear in a sitemap to crawl, index, or rank it — a sitemap just makes discovery faster and more efficient by handing Google a direct list instead of making it find every URL through links alone. Plenty of perfectly legitimate, perfectly fine pages get indexed purely through normal crawling and never touch the sitemap.

Common, harmless reasons a real page ends up here:

• It's linked prominently from your nav or homepage, so Google found and crawled it before your sitemap generator even picked it up.
• Your sitemap is scoped to certain URL patterns (e.g., only blog posts) and this page is a different type — a landing page, a legal page, a one-off.
• The page is new, and your sitemap regenerates on a schedule or build step that hasn't run again yet.
• It's an older page that predates whatever sitemap generation you currently have configured.

None of these are problems. The page is indexed, which is the actual goal — the sitemap not listing it is incidental.

When it's actually worth investigating

1. Check whether the page should be indexed at all

   Pull a few URLs from this list and sanity-check them. If they're real, intended pages — good. If you find URLs that shouldn't really exist as standalone indexed pages (an old tracking-parameter variant, a duplicate from a template bug, a staging leftover that went live), the sitemap gap isn't the issue — the page itself is. Handle that as a canonical or noindex decision, not a sitemap one.

2. Check if your sitemap is systematically missing a page type

   If you notice a pattern — an entire section of your site (say, all your location pages, or everything under /guides/) showing up here — that's worth fixing at the source. It usually means your sitemap generator's rules don't cover that URL pattern, or a specific content type was added to the site after the sitemap logic was last configured.

Fixing a genuine sitemap gap

If you've confirmed real pages are systematically missing from your sitemap, fix the generator, not the individual URLs.

1. WordPress

   If you're using Yoast SEO or Rank Math, sitemaps are auto-generated per post type at /sitemap_index.xml (Yoast) or /sitemap_index.xml (Rank Math). Check Search Appearance → Content Types in the plugin settings — a post type or taxonomy can be toggled out of the sitemap here, which is the most common cause of a systematic gap. If you're not using a plugin, WordPress core generates a basic sitemap automatically since 5.5 at /wp-sitemap.xml, with more limited customization.

2. Shopify

   Shopify auto-generates /sitemap.xml and keeps it updated automatically as products, collections, and pages are published — there's no manual configuration for what's included. If pages are missing here, check that they're actually published (not in draft) and not excluded from search visibility in the page/product's own settings.

3. Next.js / React

   If you're using the App Router's built-in sitemap.ts/sitemap.xml route convention, or the Pages Router equivalent via next-sitemap, the gap is almost always that the route generating the sitemap doesn't query the data source your new page type comes from. Check that your sitemap generation function pulls from every content source the site actually renders pages from — a common bug is a sitemap that only queries one CMS collection while pages are now rendered from two.

4. Webflow

   Webflow auto-generates and auto-updates sitemap.xml for static pages and CMS Collection pages that are set to be indexed. If a Collection is missing entirely, check the Collection's SEO settings — there's a per-Collection toggle for whether its pages are included in the sitemap at all.

How to verify it's fixed

1. Reload and validate the sitemap

   After regenerating, open the sitemap URL directly and confirm the previously-missing URLs now appear. Then resubmit it in Search Console under Sitemaps (only needed if it's not already being auto-fetched from a stable URL).

2. Check the Pages report over the following weeks

   This status isn't urgent to re-check immediately — since the pages are already indexed, there's no ranking impact waiting to be unlocked. Confirm over the next sitemap re-crawl cycle that the count in this bucket has dropped for the pages you fixed.

When to just leave it

If the pages showing up here are legitimate, already ranking fine, and the gap is small or explainable (a handful of older pages, or intentionally excluded page types like legal pages you don't want prioritized), there's no reason to chase every one into the sitemap. This status describes a discovery mechanic, not a ranking problem — spend the effort only where you found an actual systematic gap or a page that shouldn't be indexed at all.