How to fix “Crawled - currently not indexed” on Laravel
If Search Console shows “Crawled - currently not indexed” on your Laravel site, you are in the right place. Google crawled the page but did not add it to the index. 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?
Googlebot visited the page and read its content but decided it was not worth adding to search results for now. This is a decision, not an error; page quality, uniqueness and site-wide signals all play a part.
Likely causes on Laravel
- The content is short, shallow or largely the same as other pages.
- Almost no links from inside the site point to the page.
- The site is new with few trust signals; Google adds new pages cautiously.
- The URL is a template, filter or tag page with little value of its own.
- Laravel note: Cache routes, config and views in production (artisan optimize), cut database queries with eager loading and use OPcache.
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.
- Cache routes, config and views in production (artisan optimize), cut database queries with eager loading and use OPcache.
- 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.
- Make the page truly original and detailed: answer the question completely and add information found nowhere else.
- Link to it from strong pages of the site with relevant anchor text and connect it to a menu or hub page.
- Merge near-identical pages or point them to one address with a canonical.
- Verify the page carries no noindex or robots block and returns 200.
- After improving it, request indexing through URL inspection in Search Console and send the link through an indexing panel; allow a few weeks for the result.
Extra checks for Laravel
- robots.txt: Edit public/robots.txt; if it is missing the framework returns 404. The web server root must be the public folder.
- 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.
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
Does this status mean a penalty?
No. It is an indexing decision, not a penalty. A manual action would appear in its own Search Console section.
How long should I wait?
If you made improvements, wait a few weeks; repeating the request daily does not speed it up.
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: Discovered - currently not indexedFixes
- Laravel: Duplicate without user-selected canonicalFixes
- Laravel: Duplicate, Google chose different canonical than userFixes
- Ghost: Crawled - currently not indexedFixes
- WordPress: Crawled - currently not indexedFixes
- WooCommerce: Crawled - currently not indexedFixes