How to fix server error on WooCommerce
Identify and fix every page returning an HTTP 5xx server error so search engines can crawl and index those URLs again.
Steps for WooCommerce
- Enable WordPress debug logging: in wp-config.php set define('WP_DEBUG', true); and define('WP_DEBUG_LOG', true); — errors are written to /wp-content/debug.log.
- In your hosting control panel (cPanel, Kinsta, etc.) open the Error Logs section to read PHP fatal errors and the exact stack trace.
- Deactivate plugins one by one via Plugins > Installed Plugins (start with recently updated ones) until the 500 disappears, then reactivate them to identify the culprit.
- Switch temporarily to a default WordPress theme (Twenty Twenty-Four) via Appearance > Themes to rule out a theme-level error.
- Fix the identified cause (update the plugin, contact its support, increase PHP memory in php.ini or wp-config.php with define('WP_MEMORY_LIMIT', '256M');), then re-enable debug mode off in production.
- Submit the repaired URL in Google Search Console > URL Inspection > Request Indexing.
What is server error?
An HTTP 500 (or any 5xx) response means your web server encountered an error and could not deliver the page — instead of your store content, visitors and search-engine crawlers receive an error message. Common culprits include broken app/plugin code, a crashed database connection, exhausted server memory, a misconfigured hosting environment, or a recent theme/code change that introduced a bug. Unlike a 404 ("page not found"), a 5xx error tells crawlers the page should exist but the server failed to produce it.
Google explicitly drops URLs from its index when they persistently return 5xx errors — your products, categories, and blog posts simply disappear from search results, costing you organic traffic and revenue. Even intermittent 5xx errors waste your crawl budget: Googlebot retries and eventually de-prioritises your site, slowing the indexing of new and updated pages. Shoppers who land on a broken page immediately leave, driving up bounce rates and signalling poor quality to both users and search engines. If high-revenue pages stay broken long enough, recovering their rankings can take weeks or months even after the fix.
See the complete Server error guide for every platform and the full background.
Not sure if your WooCommerce store has this?
Run a free SEOLZ scan — we’ll find server error and every other issue across your whole site.
Scan my site free