What Does This Status Mean?
When you check the Page Indexing report in Google Search Console, you might encounter a status that says "Indexed, not submitted in sitemap".
This message is very literal. It means that Google has found the page (perhaps by following a link from another site, or through your internal navigation), crawled it, and successfully added it to the Google Search Index. However, this specific URL was not found inside the XML sitemap you submitted.
Is This a Bad Thing?
Not necessarily, but it depends on the context.
The good news is that your page is indexed! It can show up in Google search results and drive traffic. However, from a technical SEO perspective, it indicates a disconnect between your actual site structure and your XML sitemap.
If the page is important, it should be in your sitemap. If the page is a low-quality archive page or a paginated URL that you didn't want in the sitemap, it might be fine.
How to Fix the Issue
Fixing this warning requires you to sync your XML sitemap with your website's actual content. Here are the steps:
- Identify the URLs: Click on the "Indexed, not submitted in sitemap" row in GSC to see the full list of affected URLs.
- Assess Importance: Determine if these pages are actually valuable. If they are junk pages (like tag archives or author pages), you might want to add a
noindextag to them so they drop out of the index entirely. - Generate a New Sitemap: If the pages are valuable, your current sitemap is outdated. Use a tool like our Free Sitemap Generator to crawl your site again. The new crawl will detect these missing pages and add them to the new XML file.
- Resubmit to Google: Upload the new sitemap to your server and click "Submit" again in Google Search Console. Over the next few weeks, the warning will disappear as Google processes the new file.
Automating Your Sitemap
If you see this error frequently, it means you are manually managing a static sitemap file and forgetting to update it when you publish new content.
To prevent this permanently, consider using a dynamic sitemap generator that automatically updates the XML file every time you hit "Publish" in your CMS. Most modern platforms like WordPress, Next.js, and Shopify support dynamic XML sitemaps out of the box.
The Role of Canonicalization
Often, the "Indexed, not submitted in sitemap" error is a direct symptom of poor canonicalization strategy.
For instance, if your sitemap contains https://example.com/shoes, but Google indexed https://example.com/shoes?color=red because it was heavily linked internally, GSC will throw this error because the parameterized URL is missing from the sitemap.
To resolve this, ensure that your parameterized URLs contain a strict rel="canonical" tag pointing back to the clean URL that actually exists within the sitemap. This forces Google to consolidate the signals and respect your intended architecture.
Long-Term Prevention Strategies
Preventing this discrepancy requires aligning your content creation workflow with your technical SEO protocols.
Whenever you execute a bulk import of new products or publish a batch of programmatic SEO pages, verifying that they hit the sitemap should be a mandatory QA step. Furthermore, utilize internal linking plugins that only link to canonical versions of URLs. By tightly controlling how URLs are generated and linked within the site's DOM, you naturally ensure that Google only discovers the pages you intentionally place in your XML sitemap.