How to fix “Discovered - currently not indexed” on Laravel
If Search Console shows “Discovered - currently not indexed” on your Laravel site, you are in the right place. Google knows the URL but has not crawled it yet. 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.
Contents
What does this status mean?
The URL was discovered from your sitemap or a link, but Googlebot has not visited it yet. It usually comes from crawl budget, server load or the page being treated as low priority.
Likely causes on Laravel
- The site is large and Google cannot get to every URL.
- The server is slow or throws errors and Googlebot slows down to be polite.
- Many low-value URLs (filters, parameters) fill the crawl queue.
- No internal links; an orphan page known only from the sitemap.
- 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
- In your Laravel admin go to: The Blade layout (head section), public/robots.txt, routes/web.php and the sitemap package configuration.
- 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.
- Cache routes, config and views in production (artisan optimize), cut database queries with eager loading and use OPcache.
- Link to important pages directly from the home page and category pages.
- Put only canonical, 200-returning URLs you want indexed in the sitemap.
- Take filter and parameter URLs out of crawling with robots.txt or canonicals.
- Lower server response time and error rate; watch response time in Search Console crawl stats.
- Send priority URLs through an indexing panel and follow progress with URL inspection in Search Console.
Extra checks for Laravel
- canonical and duplicate URLs: Output a canonical in the layout with url()->current() and leave query parameters out. For pagination, each page should carry its own canonical.
- redirects and 404: Define 301s with Route::permanentRedirect in routes/web.php. When an Eloquent model is not found call abort(404); do not return an empty page with 200.
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
What is the difference between "Discovered" and "Crawled"?
"Discovered" means Google knows the URL but has not visited; "Crawled" means it visited but did not index. The first is usually about crawl priority, the second about content quality.
Thousands of my pages have this status. What now?
First decide which ones truly need indexing and remove the rest from the sitemap and internal links. Work in priority order instead of forcing every URL at once.
Where are these settings on Laravel?
The Blade layout (head section), public/robots.txt, routes/web.php and the sitemap package configuration.
Related pages
- Laravel: Duplicate without user-selected canonicalFixes
- Laravel: Duplicate, Google chose different canonical than userFixes
- Laravel: Alternate page with proper canonical tagFixes
- Ghost: Discovered - currently not indexedFixes
- WordPress: Discovered - currently not indexedFixes
- WooCommerce: Discovered - currently not indexedFixes