Skip to content

301, 302, 404 or 410? Choosing the Right HTTP Response

Status codes communicate intent. Choosing the right one keeps users out of dead ends and helps search engines understand whether a URL has moved, may return, or is intentionally gone.

Branded TopNotch editorial graphic for 301, 302, 404 or 410? Choosing the Right HTTP Response.

A removed or moved URL forces a decision: redirect it, leave it gone, or signal that the change is temporary.

Status codes communicate intent. Choosing the right one keeps users out of dead ends and helps search engines understand whether a URL has moved, may return, or is intentionally gone. That distinction matters because a technically correct tactic can still be the wrong priority for a real business website.

The Google redirects and Search guidance explains the search requirement behind an HTTP response decision. Use the primary guidance to confirm the rule, then test how it applies to the actual URLs and content in front of you.

How to approach the problem without overcomplicating it

1. Use a 301 when a URL has permanently moved to a genuinely equivalent destination

Start with evidence you can reproduce: a crawl, a live response, Search Console data or the rendered page. For an HTTP response decision, a recorded baseline prevents later guesswork.

2. Use a 302 or other temporary redirect when the move is intentionally short-lived and the original URL should remain the preferred reference

Separate discovery, technical eligibility and page quality before choosing a fix. That distinction matters in an HTTP response decision because the same symptom can have several causes.

3. Return 404 when the resource is unavailable and there is no useful equivalent; use 410 when you want to state that removal is intentional and permanent

Test the decision on a small group of representative URLs first. You will learn more from a controlled check for an HTTP response decision than from changing the entire site at once.

4. Keep redirect chains short and update internal links to point directly at the final URL

For an HTTP response decision, write down the expected result, owner and rollback path. After the change, compare the live page and server response with that expectation.

A practical example

Take one representative URL or a small page set. Start with Use a 301 when a URL has permanently moved to a genuinely equivalent destination. Then Use a 302 or other temporary redirect when the move is intentionally short-lived and the original URL should remain the preferred reference. Record what changed and what did not before expanding the work across the site.

Status codes communicate intent. Choosing the right one keeps users out of dead ends and helps search engines understand whether a URL has moved, may return, or is intentionally gone. If the first check disproves your assumption, change the plan rather than forcing the checklist.

Mistakes worth avoiding

  • Redirecting every removed page to the homepage.
  • Using temporary redirects for long-term migrations without a reason.
  • Treating 404s as automatically bad even when the content was correctly removed.

Verification matters more than assumptions

Verification for an HTTP response decision should answer three questions: can the important URL be discovered, does the live response communicate the intended state, and can a visitor understand the page? Check those directly before watching rankings.

  • Test old URLs directly and confirm the intended status and destination.
  • Review Search Console and server logs for important legacy URLs still receiving traffic.
  • Update sitemaps and internal links so removed or redirected URLs are not repeatedly advertised as current.

When to handle it yourself—and when to get help

You can often handle an HTTP response decision internally when the affected URLs are few, the evidence is clear and the change is reversible. Specialist help becomes more valuable when templates, redirects, canonicals and indexing signals interact across a larger site.

For an HTTP response decision, the most relevant TopNotch starting points are Technical SEO and SEO Maintenance. Scope should follow the diagnosis; a narrow repair is often more responsible than selling a rebuild.

Related TopNotch guides

The best response code is the one that tells the truth about what happened to the resource.

Need this implemented?

Turn the guide into actual work.

Discuss the Problem ↗