Fixes

How to fix “Indexed, not submitted in sitemap” on Laravel

If Search Console shows “Indexed, not submitted in sitemap” on your Laravel site, you are in the right place. The page is indexed but not in your sitemap. This page covers the causes and a step-by-step fix for Laravel. A PHP framework. SEO behaviour is entirely in your code; meta tags live in Blade templates and the sitemap comes from a package or a custom command.

Updated: 05.11.2026 · 2 min read · Türkçe

Contents
  1. What does this status mean?
  2. Likely causes on Laravel
  3. Step-by-step fix on Laravel
  4. Extra checks for Laravel
  5. After fixing
  6. More information

What does this status mean?

Google found the URL through a link and indexed it, but it is not in your sitemap. Usually harmless; it can show an incomplete sitemap or unwanted URLs being indexed.

Likely causes on Laravel

  • The sitemap is old or does not update automatically.
  • Parametrised, paginated or archive URLs got indexed.
  • Some content types were left out of the sitemap.
  • Test or legacy URLs are still reachable.
  • Laravel note: Generate the sitemap with a package such as spatie/laravel-sitemap or a custom Artisan command and refresh it with a scheduled task. Include only published, canonical URLs.

Step-by-step fix on Laravel

  1. In your Laravel admin go to: The Blade layout (head section), public/robots.txt, routes/web.php and the sitemap package configuration.
  2. Generate the sitemap with a package such as spatie/laravel-sitemap or a custom Artisan command and refresh it with a scheduled task. Include only published, canonical URLs.
  3. Add important URLs to the sitemap and make sure it updates automatically with new content.
  4. Set unwanted URLs to noindex or canonicalise them to the main address.
  5. Remove legacy and test URLs with 301 or 404.
  6. Resubmit the sitemap in Search Console.
  7. Compare the list of indexed URLs with the sitemap regularly.

Extra checks for Laravel

  • speed and crawling: Cache routes, config and views in production (artisan optimize), cut database queries with eager loading and use OPcache.
  • noindex and visibility: Check the robots meta tag in the layout and any middleware adding an X-Robots-Tag header. If noindex depends on the environment, make sure APP_ENV is production live.

After fixing

In Search Console start "Validate fix" for this status and resubmit the page with URL inspection. First confirm the blocker is gone with the free Free indexability checker tool; for many URLs follow Bulk URL indexing: how to send thousands of pages to Google. Google makes the indexing decision itself and timing ranges from days to weeks.

More information

Frequently asked questions

Is this a problem?

Mostly not. Act only if you see URLs that should not be indexed.

Does a sitemap boost rankings?

Not directly; it makes discovery and crawling easier.

Where are these settings on Laravel?

The Blade layout (head section), public/robots.txt, routes/web.php and the sitemap package configuration.

Related pages