Indexed, Not Submitted in Sitemap in Google Search Console: What It Means and What to Fix First

A URL shows up as indexed not submitted in your sitemap, and you need to know what that means. The page is in Google's index. It's ranking (or at least eligible to). Google just found it through a link or another discovery method rather than from a sitemap you submitted through Search Console.

That distinction matters more than it sounds.

Pages Google discovers on its own can signal gaps in your sitemap strategy, or they can reveal URLs you never wanted indexed in the first place. Either way, sort one from the other before you touch anything.

What "indexed not submitted" actually means

"Indexed not submitted" was a status label in Search Console's older Index Coverage report. It no longer appears as a named row in the current Page indexing report.

Today, the same situation surfaces through the sitemap filter above the chart in the Page indexing report.

That filter gives you four options:

• All known pages (default)
• All submitted pages
• Unsubmitted pages only
• A specific sitemap URL

Any indexed URL that appears under "Unsubmitted pages only" is the modern equivalent of the old label.

Google crawled and indexed it, but it doesn't appear in any sitemap you've submitted via the Sitemaps report or a robots.txt Sitemap: directive.

This is informational, and plenty of healthy sites have indexed pages that aren't in a sitemap.

Google confirms a URL counts as "submitted" if it's listed in a sitemap filed through either of those methods, even if Google also found the page by following links. So the real question is whether this URL should be in your sitemap, or whether it should be indexed at all.

How to confirm unsubmitted indexed URLs

Open Google Search Console and go to the Page indexing report under the Indexing section in the left sidebar.

You'll see the sitemap filter above the chart.

Filter and export the list

Select "Unsubmitted pages only" from the dropdown.

The chart and table below it will update to show only indexed URLs that don't appear in any submitted sitemap.

Click the export button (top right of the table) and download the full list as a CSV or Google Sheet. On large sites, this list can run into the thousands, so having it in a spreadsheet makes triage realistic.

Spot-check with URL inspection

Pick a few representative URLs from your export and run them through the URL Inspection tool.

Expand the Page indexing details and look at the Discovery section. The Sitemaps field lists any sitemap that refers to the URL. If it reads "No referring sitemap", Google couldn't match the URL to any sitemap it knows about.

This step catches edge cases. Sometimes a URL looks unsubmitted because the sitemap lists a slightly different version of it. URL Inspection tells you exactly what Google sees.

Triage your unsubmitted URLs into three buckets

Not every unsubmitted URL needs the same fix.

Sort your exported list into these three categories before changing anything.

Bucket A: Pages you want ranking that are missing from the sitemap

These are legitimate, high-value pages that should be in your sitemap but aren't.

Common causes include sitemap generator gaps, CMS plugins that exclude certain post types, new templates your dev team built outside the CMS, and paginated series that the sitemap plugin ignores.

The fix is straightforward: add them to your sitemap.

But first, confirm each URL is the canonical version. There's no point adding a URL to a sitemap if Google has chosen a different canonical for it.

Bucket B: URLs that should not be indexed at all

This bucket is often the largest and most valuable to clean up.

Parameter URLs, internal search result pages, tag and filter pages, staging paths, and duplicate content all show up here.

Do not add these to your sitemap.

Instead, fix them at the source with one of these methods:

• Add a noindex meta tag or X-Robots-Tag header
• Set the correct rel="canonical" pointing to the preferred version
• Redirect duplicates to the canonical URL

If you've encountered duplicate pages without a user-selected canonical, this bucket is where those problems often surface first.

Cleaning up Bucket B reduces index bloat and concentrates your crawl budget on pages that matter.

Bucket C: Sitemap pointing at the wrong URL version

This one is sneaky.

Your sitemap might list http://example.com/page while Google indexes https://example.com/page. Or your sitemap uses the www version while the canonical resolves to non-www. Same story with trailing slashes.

The indexed canonical looks "unsubmitted" because the sitemap URL doesn't match it exactly.

The fix: update your sitemap URLs to match the canonical version Google has chosen. URL Inspection confirms which version Google treats as canonical.

This is a sitemap hygiene issue. If Search Console says the sitemap itself couldn't be fetched, fix that first.

What to fix first

With your URLs sorted into buckets, resist the urge to fix everything at once.

Prioritize by business value.

Start with Bucket A pages that drive revenue or conversions.

Product pages and high-traffic blog posts missing from the sitemap should go in immediately. Google already indexed them, so adding them to the sitemap reinforces the signal that you consider these URLs canonical and important.

Next, tackle Bucket C.

Version mismatches are quick fixes that can move a large batch of URLs from "unsubmitted" to "submitted" in one sitemap update.

Bucket B comes last because those fixes (noindex tags, redirects, canonical updates) carry more risk if done carelessly. Work through them in batches and verify each change with URL Inspection before moving on.

Which pages matter most?

If you're unsure, sort your exported CSV by clicks or impressions from the Performance report. A page getting traffic that isn't in your sitemap deserves attention before an obscure tag page that gets zero clicks.

What not to do

Three mistakes waste the most time with this status.

Don't dump every indexed URL into the sitemap.

Google's sitemap documentation says to include only canonical URLs you want in search results. A bloated sitemap filled with junk URLs dilutes the signal and doesn't help ranking.

Don't spam "Request Indexing" in URL Inspection.

These pages are already indexed. Requesting re-indexing does nothing to change their sitemap status. It only uses up your request quota.

Don't panic.

The goal is to ensure important pages are submitted and junk pages aren't indexed.

Similarly, if you see pages that are discovered but not yet indexed, that's a different problem with a different fix. Don't conflate the two statuses.

How to verify your fixes worked

After updating your sitemap (adding missing pages, fixing URL versions), resubmit it in the Sitemaps report in Search Console.

Google re-reads it on its own schedule, and the Sitemaps report shows when it was last read.

Track the numbers over time

Go back to the Page indexing report and check the sitemap filter.

Over the following weeks, you should see the "All submitted pages" count rise and the "Unsubmitted pages only" count shrink.

Don't expect instant results. Google recrawls and reprocesses at its own pace. If you've added noindex tags to Bucket B URLs, those pages need to be recrawled before they drop out of the index entirely.

Set a recurring audit

New pages get created. Templates change. CMS plugins get updated.

Run this same filter once a month to catch new unsubmitted URLs before they pile up. A five-minute check now prevents an overwhelming triage session later.

Frequently asked questions

Will being unsubmitted in the sitemap hurt my rankings?

Rankings depend on signals like content quality and links. A sitemap mainly helps with discovery and confirmation of preferred URLs. If the page is already indexed, the bigger risk is inconsistency or indexing low-value URLs.

Should I include paginated pages, tag pages, or category pages in my sitemap?

Include them only if they provide unique search value and are part of your intentional SEO strategy (for example, a category page with strong internal linking and curated content). If they mainly replicate other listings or generate endless variants, keep them out of the sitemap and manage indexing intentionally.

How can internal linking cause new URLs to get indexed even if they are not in the sitemap?

Google can discover URLs through navigation, filters, breadcrumbs, and related-content modules. If those elements expose parameterized or duplicate paths, they can expand the number of discovered URLs. Auditing your templates and link patterns is often as important as auditing your sitemap.

How long should I wait before concluding my sitemap changes did not take effect?

Give it enough time for recrawling and reprocessing, which can vary by site size and crawl frequency. If nothing changes after a reasonable window, re-check for blockers like incorrect status codes, inconsistent canonicals, or sitemap formatting issues.

Make your sitemap a true signal

The "indexed not submitted" status is a diagnostic signal.

It tells you where your sitemap and Google's index don't agree, and the right response depends entirely on why they disagree.

Important pages missing from the sitemap need to be added. Junk URLs that slipped into the index need noindex tags or redirects. Version mismatches need a sitemap update.

That's the entire playbook.

The hardest part is maintaining the habit of checking regularly so small gaps don't become large ones. If you want to automate more of your SEO monitoring and content workflows, ClickFlow can help you stay on top of indexing issues and content performance without the manual overhead.