The response behind the visible page
An HTTP status code tells the requesting client how a request was handled. The first digit groups responses: 2xx indicates success, 3xx relates to redirection, 4xx covers client-side request problems and 5xx covers server-side failures. The exact code supplies more detail.
Common website examples include 200 for a successful response, 301 for a permanent move and 404 when the requested resource is not found. MDN lists HTTP response status codes. The visible design and the response code need to describe the same outcome.
Example: a deleted service page
Imagine a business removes a service it no longer offers. If there is a genuinely equivalent replacement, a permanent redirect can take visitors there. If there is no replacement, a useful not-found page can explain the situation and provide navigation while returning the appropriate missing-resource status.
Returning an attractive “page not found” screen with a successful 200 response is misleading to software. Redirecting every missing page to the homepage can also be confusing because the visitor’s requested subject has disappeared. Choose the response based on the actual content relationship rather than trying to make an error report look empty.
How to investigate an unexpected response
Check the initial response and any subsequent redirects, not only the final page displayed by the browser. A single visit can pass through several addresses. Record the requested URL, time and response headers when diagnosing an intermittent failure.
After a migration, test old service URLs, image files and enquiry endpoints as well as the homepage. Server errors may require application or hosting logs to identify their cause. Avoid changing status codes merely to hide a failing application. The code should accurately communicate the result while the underlying fault is fixed.
Common questions about http status code
Is every 404 a problem that needs a redirect?
No. A 404 can be correct for a resource that no longer exists. Repair broken internal links, and redirect only when there is a relevant replacement destination.
Does a 200 response mean the whole page works?
No. The initial request may succeed while images, scripts or form requests fail separately. Check the complete customer journey and its supporting requests.
Related definitions
- Redirect — A server or browser instruction that sends a request to another URL. Permanent URL migrations should avoid unnecessary chains and link directly to the intended destination.
- Technical SEO — Improving the technical foundations of search access and understanding, such as crawlability, indexing signals, URL handling, rendering and performance.
- Crawlability — Whether a search engine can discover and request pages and resources. It depends on factors including links, server responses, access restrictions and crawler directives.
- Hosting — The infrastructure and services that make a website accessible online. Capacity, reliability, security, backups and support should match the site’s role in the business.
Related SEO guides
Status codes tell clients whether a resource exists, has moved or cannot currently be served.
For help connecting these decisions with your website, explore our SEO services or start with an SEO audit.
Put it into practice
Explore our technical seo service or talk with Refined IT about applying this to your website or business systems.