How to fix “Server error (5xx)” on Next.js
If Search Console shows “Server error (5xx)” on your Next.js site, you are in the right place. The server returned a 5xx error to Googlebot. This page covers the causes and a step-by-step fix for Next.js. A React framework. Server-side and static generation hand Googlebot ready-made HTML; metadata is managed with the Metadata API.
Contents
What does this status mean?
The server answered Googlebot with 500, 502, 503 or a similar error. If errors persist Google slows crawling and may start dropping URLs from the index.
Likely causes on Next.js
- The server is overloaded or hit a resource limit.
- A bug in application code crashes on specific URLs.
- A firewall, rate limit or bot protection blocks Googlebot.
- A temporary outage during maintenance or deployment.
- Next.js note: Render pages statically or with ISR where possible, split heavy client bundles and use next/image. Slow server responses reduce crawl rate.
Step-by-step fix on Next.js
- In your Next.js admin go to: The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.
- Render pages statically or with ISR where possible, split heavy client bundles and use next/image. Slow server responses reduce crawl rate.
- Find the 5xx entries from Googlebot request times in your server error logs and fix the cause.
- Verify that firewall and CDN rules do not block Googlebot.
- Use 503 with a Retry-After header for planned maintenance rather than a blank page with 200.
- Increase server capacity and caching, and watch the server error rate in Search Console crawl stats.
- When fixed, start validation and resend important URLs.
Extra checks for Next.js
- robots.txt: Check app/robots.ts or public/robots.txt. If you disallow preview environments, confirm the same rule does not ship to production.
- canonical and duplicate URLs: Give every page an absolute canonical with metadata.alternates.canonical and set metadataBase. On dynamic routes make sure parametrised URLs do not repeat content.
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 a brief 5xx matter?
Google tolerates a brief outage. Errors lasting days can cause index loss.
How do I know if my server blocks Googlebot?
Run a live test in URL inspection; if it errors while the site opens in a browser, blocking is likely.
Where are these settings on Next.js?
The metadata object in app/layout.tsx and page files, app/robots.ts, app/sitemap.ts and next.config.js.