404 and Redirect Configuration Review
Key takeawayAfter a redesign, product removal or domain change, how old URLs are handled decides whether past equity is wasted and whether visitors hit a dead end. This sheet reviews redirect types, chains, 404 pages and parameter retention.
Industries and use cases
- After a site redesign or domain change
- After bulk product removal or category restructuring
- When Search Console reports a wave of 404s
- When campaign links change but tracking parameters must survive
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| Redirect type | 301 for permanent moves, 302 for temporary campaign pages, never mixed | High | The wrong type breaks signal transfer; use 301 for every migration. |
| Chain length | Any old URL reaches its final target in one hop with no A to B to C chain | High | Point straight at the final URL, since chains confuse crawling and reporting alike. |
| Target status | Every redirect target returns 200 and never another redirect or a 404 | High | After bulk configuration, crawl the site and confirm each target individually. |
| No home page fallback | Deleted pages with no replacement return 404 rather than redirecting to home | High | Blanket home redirects are read as soft 404s and leave visitors without the answer they wanted. |
| True 404 status | Missing pages return a 404 status code, not 200 with an error message | High | Soft 404s keep dead URLs in the index, so fix the status at server level. |
| 404 page content | The custom 404 page offers search, main category entry points and a contact route | Medium | Guide visitors onward instead of showing a single line of apology. |
| Case and trailing slash | URLs are lowercase with one trailing slash convention, and variants 301 to the canonical form | Medium | Normalise at server level so one page cannot exist at four addresses. |
| Old URL map | Before migration a full list of old URLs is mapped with 100% coverage | High | Crawl the old site completely, build the map, then switch traffic. |
| HTTPS chain merge | HTTP to HTTPS is merged with other redirects into a single step | Medium | Stacked hops slow the first screen, so configure the final URL directly. |
| Parameter retention | Tracking parameters on old URLs remain readable by analytics after the redirect | Low | Preserve the query string in the rule or use a common landing page with separate source tracking. |
| Redirect monitoring | 404 and 301 reports are reviewed weekly after launch | Medium | Increase to twice weekly for the first two weeks after a migration. |
| Cache purge | CDN cache is purged after redirect changes and external access is confirmed | Medium | Stale CDN rules keep serving the old page to part of your audience. |
Common misjudgements
- Seeing a page open and assuming the redirect works: 200 with a notice is a soft 404 and does nothing for indexing.
- Pointing every dead URL at the home page, which looks clean short term but loads the home page with unrelated queries.
- Ignoring case variants so one product page exists under several addresses while only one is redirected.
How to use this checklist
- Pair with the duplicate content sheet, since redirects are the first deduplication tool.
- Run before and after a migration and review reports monthly in normal operation.
- Link with sitemap validation so URLs are updated once redirects are in place.
FAQ
Do 301 and 302 differ for indexing?
Yes. A 301 signals a permanent move and passes signals to the new URL, while a 302 is temporary only.
What should a deleted product page return?
404 or 410 when there is no replacement; a 301 to a similar product is acceptable when one exists.
How long do redirects take effect?
Server configuration applies immediately, while search engines update stored URLs over days to weeks.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
hreflang Configuration Review for Multilingual Sitesrobots.txt Configuration Checks and Common MistakesXML Sitemap Creation, Submission and ValidationCrawl Budget and Index Permission Review for New SitesDuplicate Content Risk ReviewNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.