How to fix “Server error (5xx)” on Magento
If Search Console shows “Server error (5xx)” on your Magento 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 Magento. A powerful e-commerce platform (Adobe Commerce) for large catalogs. Layered navigation filters create many parametrised URLs.
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 Magento
- 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.
- Magento note: Enable full page cache and Varnish and turn on JS and CSS merge/minify. Slow catalog pages reduce crawl frequency.
Step-by-step fix on Magento
- In your Magento admin go to: Stores > Configuration > Catalog > Catalog > Search Engine Optimization and Marketing > SEO & Search.
- Enable full page cache and Varnish and turn on JS and CSS merge/minify. Slow catalog pages reduce crawl frequency.
- 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 Magento
- sitemap: Create the sitemap under Marketing > SEO & Search > Site Map and add it to robots.txt. Tie generation to cron to keep it current.
- noindex and visibility: Under Stores > Configuration > General > Design > Search Engine Robots the default should be INDEX,FOLLOW. A NOINDEX,NOFOLLOW value left over from development is a common live mistake.
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 Magento?
Stores > Configuration > Catalog > Catalog > Search Engine Optimization and Marketing > SEO & Search.