Fix guides · SEO
How to fix “Page has unsuccessful HTTP status code” (404 and 500 errors)
The page you audited answered with an error code, so search engines may drop it. How to find out why and fix it on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- Time to fix
- 10–30 minutes
- Skill needed
- No code
- Who notices
- Search visitors and anyone following an old link
Why it matters
Every page response starts with a status code. 200 means OK; 301 means moved; 404 means not found; 500 and up mean the server failed.
A page that shows content but returns 404 or 500 tells search engines it's broken, so they may not index it. A page that really is gone should redirect visitors to the closest replacement.
“If a search engine encounters a status code error when it's crawling a web page, it may not index that page properly.”
Before you start
- Check the exact address you audited. A typo, an old product URL or a missing trailing slash may simply not exist.
- 404 for a page that moved: add a 301 redirect to its new address. 404 for a page that should exist: republish it or fix its address.
- 5xx errors are server problems; if they persist, contact your host or platform.
Fix it on your platform
Shopify
- Deleted or renamed products, collections and pages return 404. Create a URL redirect from the old address to the new one (search your admin for "URL redirects"). Shopify can create one automatically when you change a handle.
- Check the product or page is published to the Online Store sales channel.
WordPress
- If many pages return 404, go to Settings → Permalinks and click Save Changes; this rebuilds WordPress's address rules.
- For moved pages, add 301 redirects with a redirection plugin or your host's redirect tool.
- 500 errors often come from a plugin or theme conflict: check your host's error log, or deactivate recently added plugins.
Webflow
- Make sure the page is published and isn't a draft. For pages that moved, add a 301 redirect in Site settings → Publishing → 301 redirects.
Wix
- Check the page is published and its URL slug matches the link. For moved pages, add a 301 redirect with the URL Redirect Manager in your SEO tools.
Squarespace
- Check the page is enabled and its URL slug matches the link. For moved pages, add a 301 redirect in the URL Mappings panel.
Next.js
- A 404 usually means no route matches, or notFound() was called because data wasn't found. A 500 means rendering threw an error; check your logs.
- Add redirects for moved pages in next.config.
Any other site
- Make sure the file exists at that path, and configure 301 redirects on the server for pages that moved.
Check that it's fixed
- In Chrome DevTools → Network, reload and check the page request's status column shows 200.
- Re-run your StudioLNC audit: the issue should be gone.
Find every issue like this on your site
Free audit of performance, accessibility, SEO and security, with fixes for your platform.