A missing page usually should not redirect automatically to the homepage. Use a 301 or 308 when the content has a genuinely relevant permanent replacement. If it has been removed and there is no replacement, return 404 or 410 with a useful error page. Temporary stock shortages, planned maintenance and a permanent move are different situations and need different handling.
Choose the response from the actual page state
| What happened? | Suitable direction | What to verify |
|---|---|---|
| The content moved permanently | 301 or 308 to the matching replacement | The destination works and serves the original purpose |
| The content was deleted without a replacement | 404 or 410 | The error page still offers useful navigation |
| A product is temporarily unavailable | Keep a useful product page and show accurate availability | Being unable to buy today does not necessarily make the information obsolete |
| Several resources were genuinely consolidated | Consider permanent redirects after mapping their content | The new resource covers what each old URL was intended to provide |
| The move is temporary | 302 or 307 where appropriate | The implementation matches the intended duration |
| The service is temporarily unavailable | Fix the fault; use an appropriate maintenance response such as 503 | Do not disguise an outage as a successful page or permanent deletion |
Google distinguishes permanent and temporary redirects. A homepage is not forbidden as a destination if the old content genuinely moved there. The problem is a catch-all rule that sends unrelated missing URLs to the same page regardless of what the visitor wanted.
A soft 404 is not a manual-action notice
An HTTP 404 is a server response. A soft 404 is Google's assessment of content that behaves like an error, such as a page returning 200 while showing only a missing-content message. Google's status-code documentation explains that 200 does not guarantee indexing. URLs returning 404 are not indexed, previously indexed URLs are removed, and crawling of those addresses gradually decreases. There is no fixed three-day deadline after which they can never be requested again.
The site-move guide warns that redirecting many old URLs to one irrelevant destination, such as the homepage, may be treated as a soft 404. It does not define a twenty-error penalty threshold. “Discovered—currently not indexed” is a different report status and cannot be used as proof of a soft 404.
Server errors and 429 responses also need separate attention. They can slow crawling, and persistent server errors can eventually affect indexed URLs. That is different from correctly returning 404 for a removed article; a single site-wide “404 rate” cannot describe both problems.
Find the layer that is redirecting missing URLs
- Prepare a small test list: a known working page, a deliberately removed page, an old URL with a genuine replacement and a path that never existed. Include relevant parameter and trailing-slash variants.
- Inspect every response: preserve the browser's network log and record the first status, Location header, intermediate hops and final page. A final 200 alone hides the earlier redirects.
- Check each configuration layer: CMS plugins, theme 404 logic, server rewrite rules and CDN rules can all affect the result.
- Repair the mapping: retain legitimate moves and remove inappropriate catch-all redirects. Test any directory-wide rule against actual content destinations.
- Clear affected caches and retest: compare the origin with the public response. Use a clean browser session when a permanent redirect may have been cached locally.
For a command-line inspection, curl -sS -D - -o /dev/null 'URL-to-check' shows headers from a GET request. Add -L to follow the chain. curl -I sends HEAD, which some systems handle differently. Read the status codes and inspect the page content as well; a successful command exit does not itself mean the HTTP response was successful.
Judge replacement relevance by the reader's task
In a hypothetical example, a rewritten installation guide might completely replace an older guide while serving the same task. An obsolete product model might instead still need a live manual, spare-parts information and a link to the current model. Automatically sending both URLs to a broad product directory would ignore that difference.
A 70% or 80% text-similarity score does not decide whether a redirect is appropriate. Check purpose, information and user expectations. Prefer a direct redirect to the final relevant destination and remove loops; that recommendation is not a claim that Google follows only one hop.
Keep a useful 404 page and verify the release
Explain that the requested page was not found and offer relevant navigation or a working search function while preserving the 404 response. There is no mandatory quota of six or eight recommended links. Avoid unrelated suggestions that merely fill the page.
After deployment, confirm that working URLs still work, removed URLs return 404, mapped URLs reach the right destination, and internal links and sitemaps use current addresses. A Screaming Frog crawl checks reachable internal paths; logs, old URL inventories and customer-facing material help find other entry points. The Page indexing report can then show Google's later processing, which is separate from local repair completion.
For an existing installation, use the five-step homepage-redirect repair checklist to organize response checks, URL mapping and release verification. Do not recreate every random 404 just to reduce a report count, and do not promise a specific ranking recovery from correcting the responses.