How to fix “Soft 404” on Laravel
If Search Console shows “Soft 404” on your Laravel site, you are in the right place. The page looks empty or like an error but returns 200. 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 server says "success" (200) but the content reads to Google like a missing page: an empty list, a "product not found" message or almost no content. Google does not index the URL.
Likely causes on Laravel
- An empty category, empty search result or out-of-stock product page.
- Deleted content shows a custom error page while returning 200.
- JavaScript content fails to load and the page stays empty.
- Template pages with very little text.
- Laravel note: 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.
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.
- 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.
- Cache routes, config and views in production (artisan optimize), cut database queries with eager loading and use OPcache.
- Return 404 for pages that truly do not exist, or 410 if permanently removed.
- If a close replacement exists, redirect to it with a 301.
- Set empty category and search pages to noindex or add content.
- Verify that JavaScript loads the content with "Test live URL" in URL inspection.
- Start validation after fixing.
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.
- sitemap: 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.
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 a soft 404 penalised?
No, but it spends crawl budget and the page is not indexed. Many soft 404s can be a poor quality signal for the site.
What if a real page shows as soft 404?
Enrich the content and confirm it appears in the raw or rendered HTML.
Where are these settings on Laravel?
The Blade layout (head section), public/robots.txt, routes/web.php and the sitemap package configuration.