code
Status Code Check

Frequently Asked Questions

Home All Codes Check URLs

Frequently Asked Questions

Everything you need to know about HTTP status codes, errors, and troubleshooting.

help_outline General Questions

An HTTP status code is a 3-digit number returned by a web server in response to a browser's request. It indicates whether the request was successful, redirected, encountered an error, or requires additional action. Status codes are grouped into five categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Errors), and 5xx (Server Errors).

Status codes directly impact how search engines crawl and index your website. Here's why they matter:

  • 404 errors tell search engines a page doesn't exist, which can hurt rankings if it's a valuable page
  • 301 redirects pass SEO value to the new URL, while 302 redirects don't
  • 500 errors prevent indexing and can cause search engines to remove pages from results
  • 200 OK signals healthy pages that should be indexed normally

You can check status codes several ways:

  • Use URL Status Checker to test up to 100 URLs at once
  • Open browser Developer Tools (F12) → Network tab → reload page → check Status column
  • Use curl command: curl -I https://yoursite.com
  • Use online tools like Redirect Checker or HTTP Status Checker

error_outline 404 Errors

A 404 error means the server cannot find the requested resource. This happens when a page has been deleted, moved without a redirect, the URL is mistyped, or the link is broken. The page never existed at that URL, or it existed but no longer does. Learn more about 404 errors →

Fix 404 errors by:

  1. Check if the page still exists - restore it if it was accidentally deleted
  2. If the page moved, create a 301 redirect to the new location
  3. Fix broken internal links in your navigation, content, and sitemaps
  4. Update external links where possible (contact site owners)
  5. Create a custom 404 page with helpful navigation and search
  6. Monitor 404s in Google Search Console and fix high-traffic ones first

404 errors aren't inherently bad - they're a normal part of the web. However, they can hurt SEO if: (1) important pages with backlinks return 404, (2) you have many 404s from broken internal links, or (3) users land on 404s from search results. A few 404s from old or mistyped URLs won't harm your site. Focus on fixing 404s for pages that receive traffic, have backlinks, or are linked from your site.

sync_alt Redirects (301, 302, 307, 308)

301 (Moved Permanently): Tells search engines the page has permanently moved. Search engines transfer ranking signals to the new URL and update their index.

302 (Found / Temporary Redirect): Indicates a temporary move. Search engines keep the original URL in their index and don't transfer full SEO value.

When to use: Use 301 for permanent URL changes (rebranding, consolidating pages, fixing URL structure). Use 302 for temporary situations (A/B testing, seasonal pages, maintenance).

Best practice is to keep redirect chains to 1-2 hops maximum. Each redirect adds latency, and search engines may stop following after 3-5 redirects. For example, URL-A → URL-B → URL-C → URL-D is problematic. Instead, update all redirects to point directly to the final destination: URL-A → URL-D, URL-B → URL-D, URL-C → URL-D. This improves page speed and ensures search engines can reach your content.

A redirect loop occurs when URL-A redirects to URL-B, which redirects back to URL-A (or through multiple URLs that eventually loop back). Browsers detect this and show an error like "too many redirects."

Common causes:

  • Conflicting redirect rules in .htaccess or nginx config
  • Plugin or CMS settings creating circular redirects
  • HTTP to HTTPS redirect conflicting with HTTPS to HTTP
  • www to non-www redirect conflicting with opposite rule

Fix: Review your redirect rules, disable conflicting plugins, clear server cache, and test redirects with curl or redirect checker tools.

report_problem Server Errors (500, 502, 503, 504)

A 500 error is a generic catch-all for server-side errors. Common causes include:

  • Syntax errors in server-side code (PHP, Python, Node.js, etc.)
  • Database connection failures or query errors
  • Insufficient server resources (memory, CPU, disk space)
  • Incorrect file permissions (chmod issues)
  • Corrupted .htaccess file or configuration errors
  • Plugin or extension conflicts

Check server error logs for specific details about what went wrong.

502 Bad Gateway: Your server (acting as a gateway/proxy) received an invalid response from an upstream server. Common with load balancers, reverse proxies, or when backend application servers are down.
503 Service Unavailable: The server is temporarily unable to handle requests, usually due to maintenance, overload, or resource exhaustion. Often temporary.
504 Gateway Timeout: Your server didn't receive a timely response from an upstream server. The backend server is taking too long (slow queries, processing, or network issues).

Server errors (5xx) prevent visitors from accessing your content entirely. Impact includes:

  • Lost conversions: Visitors can't complete purchases, sign-ups, or other actions
  • Poor user experience: Frustration leads to visitors leaving and not returning
  • SEO damage: If errors persist, search engines may de-index pages or lower rankings
  • Brand reputation: Frequent errors make your site appear unprofessional or unreliable
  • Revenue loss: Downtime directly impacts sales for e-commerce sites

Monitoring tools and quick response times are essential to minimize impact.

lock Authentication & Permissions

401 Unauthorized: You need to authenticate (log in) to access this resource. Your credentials are either missing, invalid, or expired. The server is saying "who are you?"
403 Forbidden: You're authenticated, but you don't have permission to access this resource. Your identity is known, but you're not allowed. The server is saying "I know who you are, but you can't access this."

Think of it like a club: 401 = "Show me your ID" / 403 = "Your ID is valid, but you're not on the VIP list"

Common fixes for 403 errors:

  1. Check file permissions: Ensure files are 644 and directories are 755
  2. Review .htaccess rules: Look for Deny/Allow directives blocking access
  3. Check user roles: Verify the authenticated user has required permissions
  4. IP whitelist/blacklist: Ensure your IP isn't blocked
  5. Firewall/WAF rules: Check if security tools are blocking legitimate requests
  6. Index file: Ensure index.html or index.php exists in the directory

Still Have Questions?

Check your website's status codes now to identify and fix issues.

speed Try URL Status Checker