Short answer
A page whose address has changed for good should 301 to its new equivalent; content with no replacement should return 404 or 410. Google treats a 301 as a strong signal and a 302 as a weak one. To avoid soft 404s, an error page must return a real 404 status code.
Picture a shop that deletes last year’s campaign page. The page still receives links from three blog posts and an email archive. A visitor who clicks lands either on a blank error screen or on an unrelated home page. The fix is often a single correct response code: a 301 redirect for a page that moved, and an honest 404 or 410 for a page that is really gone.
This guide shows how to choose between them and how to sort 404 errors, starting in Search Console, in five steps. If you are rebuilding a whole site or changing domain, keeping SEO through a site rebuild and SEO when changing your domain name go further. Here we look at the day-to-day handling of individual pages. There is also a short definition in the glossary.
What is the difference between 301 and 302?
Google’s redirect documentation describes two groups. Permanent redirects lead to the new target being shown in search results. Temporary redirects lead to the source page staying in the results. The document recommends 301 and 308 for a permanent move. According to Google’s status code page, a 301 is a strong signal that the target should be processed, while a 302 is a weak one. 308 is treated as equivalent to 301, and 307 as equivalent to 302.
The same page explains how 4xx codes are handled. The table below summarises the common responses based on those two documents.
| Response | Meaning | How Google handles it | When to use it |
|---|---|---|---|
| 301 or 308 | Moved permanently | Strong signal; the new address is shown in results | The page has a new, permanent address |
| 302 or 307 | Temporarily elsewhere | Weak signal; the source page stays in results | Maintenance or a short-lived redirect |
| 404 | Not found | Not indexed; removed over time if it was indexed | The page is gone and nothing replaces it |
| 410 | Gone for good | 4xx codes are handled alike, so the same outcome as 404 | You are sure the removal is permanent |
| 200 with a “not found” message | Looks like a live page | Search Console may report a “soft 404” | Never |
Using a 302 for a permanent move is a common mistake. According to Google’s documentation, a temporary redirect shows the source page in results, so the old address may stay there. If a page really is elsewhere only for a while, a 302 is the right tool.
Step 1: Find the problem addresses in Search Console
Open the Page indexing report in your Google Search Console account. If the “Why pages aren’t indexed” table has a “Not found (404)” row, click it to see the affected addresses. Look at the “Soft 404” and “Redirect error” rows too; we come back to both below.
Google’s Page indexing report help says two things. First, it recommends fixing only the 404 errors that you link to yourself or list in a sitemap. Second, it says a removed page may keep being crawled for a while, that there is no way to make Googlebot forget an address entirely, and that it crawls it less and less often. So not every address on the list is an alarm.
For each address, note three things:
- Does it receive links from inside your site (menu, posts, product pages)?
- Is it in the sitemap?
- Does it receive links from outside? You can see this in the links report or with a crawling tool.
If the answer to all three is no, the address is probably not a problem. If it receives any link, move to the next step.
Step 2: Decide for each address
Decide according to what happened to the page. The flow below is our suggestion; it ties the response codes in the table to three questions.
The logic is this. If the new address is permanent and the old page has a like-for-like replacement, set up a 301. If there is no exact match, look for a page close in topic: a category page for a withdrawn product, or a current-offers page for a finished campaign. If there is none, the honest answer is 404 or 410. If you know the old address will return and you are sending visitors elsewhere for a while, a 302 or 307 is enough.
Redirecting everything to the home page is not in the flow. It looks like a shortcut but takes the visitor further from what they wanted. A “close page” and the “most general page” are not the same thing.
On 404 versus 410, MDN’s 410 page defines 410 as the resource no longer being available, a condition that is likely to be permanent. The same page says to use 404 if you do not know whether the condition is temporary or permanent. MDN’s 404 page says a 404 only reports that the resource is missing and recommends 410 for a resource that has been removed permanently. Google handles 4xx codes, except 429, alike. In practice, 410 is more accurate when you know the removal is permanent; if your platform makes sending 410 awkward, 404 works too.
Step 3: Set up the redirect and shorten chains
A redirect is set up in the server configuration, in your hosting platform’s redirect file or in a plugin in your content management system. Whichever you choose, three rules stay the same.
- Set it up on the server side. Google ranks redirect types by how likely they are to be interpreted correctly and puts server-side redirects first. Use a JavaScript redirect only when there is no other way; if rendering fails, Google may never see it.
- Redirect in one step. The old address should go straight to the final address. If A goes to B and B goes to C, point A directly at C.
- Update internal links. If menus and posts still link to the old address, every click passes through a needless redirect. Point links at the final address; our internal linking guide covers the detail.
According to Google’s status code page, Googlebot generally follows 10 redirect hops for general web content. In the Page indexing report, “Redirect error” lists four causes: a chain that is too long, a loop, a redirect that exceeds the maximum URL length, and a bad or empty URL in the chain. After setting up a rule, test it with a tool. On the command line, this command shows each hop:
curl -sIL https://example.com/old-address
You should see a single 301 followed by a 200. A second 301 means there is a chain. A “Page with redirect” row in the report is normal: the redirecting address is not indexed, only its target is.
Step 4: Weed out soft 404s
A soft 404 is a server sending its error page with a “success” code. According to Google’s status code page, even when a 2xx code is returned, if the content suggests an error, an empty page or an error message, Search Console reports a soft 404. The Page indexing help describes it as a page that shows a user-friendly “not found” message without returning a 404 code, and recommends returning a 404 code for pages that are truly not found.
Typical sources are listed below. This list is ours, not Google’s:
- A theme or plugin that serves the error page with a 200 code.
- Filter and search pages that return no results and are empty.
- A one-line empty page such as “out of stock” in place of a removed product.
The fix is one of two things. If the page really does not exist, return a real 404 or 410. If it exists and is valuable, complete its content. To see how Google views a page, Google suggests running a live test in URL Inspection and using “View tested page” to see a screenshot.
Step 5: Build a useful 404 page
Every site will produce a 404 somewhere: a mistyped address, an old link on another site. At that moment, show the visitor a way out. MDN considers custom 404 page design a good thing in moderation; it can be humorous, but it should not confuse visitors about why they are seeing something unexpected. Our checklist:
- A clear first sentence. A plain statement of what happened, such as “This page could not be found.”
- The site’s normal header and footer. The visitor should see they are still on your site.
- A search box. So they can type what they were looking for.
- Links to the most visited sections. Services, product categories, the blog.
- A way to get in touch. In case the broken link is on your own site and they want to tell you.
- A real 404 code. However nice the page looks, the response code must be 404; otherwise you produce a soft 404.
The last point is easy to verify. Type an address that does not exist on your site, for example /this-page-does-not-exist-123, and read the response code on the Network tab of your browser’s developer tools.
Common mistakes
- Sending all old addresses to the home page. The visitor does not find what they wanted. Redirect to a page close in topic or give an honest 404.
- Using 302 for a permanent move. Google treats 302 as a weak signal and may keep the old address in results.
- Leaving chains and loops. Each hop adds delay, and a loop makes the page unreachable.
- Serving the error page with a 200. It gets flagged as a soft 404.
- Clearing the report blindly. Google recommends fixing only the 404s you link to or list in a sitemap.
- Leaving 404s and redirecting addresses in the sitemap. The sitemap should hold only addresses that open and do not redirect; the technical SEO checklist has the detail.
- Removing a redirect too early. Old links live on for years on other sites; the day you remove the redirect, those visitors land on a 404.
Common questions
Does a 301 redirect protect my rankings?
A 301 is a signal Google treats as strong that the redirect target should be processed, and the new address is shown in results. Nobody can guarantee rankings stay exactly as they were. If the target page really covers what the old one did, the signal is expected to carry over.
Do 404 errors hurt my site’s rankings?
Google’s Page indexing help says 404 responses are not necessarily a problem if a page has been removed without a replacement. The problem is when pages that receive links, or sit in the sitemap, return 404. Redirect them or remove the link.
Why does a page I deleted still appear in Search Console?
Google keeps crawling known addresses for a while even when they return 4xx, in case the error is temporary. The crawl frequency falls over time. An address sitting on the list does not by itself show an error.
After reading this, here is the one thing you can do today: open the “Not found (404)” row in Search Console, take the first ten addresses and write “301”, “404/410” or “leave alone” next to each. Use the flow above to decide. If you would like these checks tied into a regular technical review, technical SEO auditing is part of our SEO service.
Sources
This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 15 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.