What is it?
HTTP Status Codes explains every common status code in plain words. Type a code (404, 5xx) or a word (redirect, timeout) to Find a status code.
Who is it for?
Website and blog owners fixing errors from Search Console, developers debugging APIs, and support staff explaining errors to users.
How to use it
- Type a code like 404 or a word like redirect in the search box.
- Read the explanation and common fixes.
- Tap Copy to share it.
The groups
- 2xx success (200 OK). 3xx redirects. 4xx problems with the request (often the visitor’s link). 5xx problems on the server.
Codes site owners meet most
- 301 vs 302: 301 is a permanent move and passes search ranking to the new address; 302 is temporary. Use 301 when you change URLs (the .htaccess Redirect Generator helps).
- 404 Not Found: the page doesn’t exist. Fix broken links or redirect the old address. A few 404s are normal.
- 403 Forbidden: the server refuses access; often file permissions (see the chmod Calculator) or a security rule.
- 500 Internal Server Error: a bug or a broken .htaccess file; check the server error log.
- 502 / 504: a gateway or CDN couldn’t get a reply from your server in time.
- 503 Service Unavailable: the server is overloaded or in maintenance. Search engines retry later.
Checking a page’s code
In Chrome, open Developer Tools (F12) → Network, reload the page and look at the Status column. Google Search Console also reports pages with errors.
Example: moving a blog post
You change /2024/05/old-title.html to /2024/05/new-title.html. Without a redirect, the old link gives 404 and loses its Google ranking. A 301 from the old to the new address keeps visitors and ranking. On Blogger, add it under Settings → Errors and redirects.
Errors and how to fix them
- No match for a code: uncommon or custom codes (like 520–527 from Cloudflare) are server-specific; check your host’s documentation.
Open the tool: HTTP Status Codes
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.
Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.