After a redesign, all old service pages lead to the homepage. The redirect map looks complete because every URL has been assigned 301 — a permanent redirect. But visitors looking for a specific service lose the answer they need. For each old service page, find a new page about the same service, or return 404 or 410 — a response indicating that the page is unavailable — if the service is no longer offered.
Find out what was on the old page
Google recommends redirecting moved pages to relevant new destinations. Official documentation.
For each old URL, find its title, main answer, and the reason visitors used to visit it. Use a verified old version, a content management system (CMS) export, or saved text, if available. Don’t make up the content based on part of the URL. The page /repair/ may have described repairs for one model, while the new /services/ page may cover the full range of services. The homepage can help visitors find their way around, but that does not make it an automatic replacement. In the old-and-new URL table, put the service name beside each URL. For a discontinued service with no replacement, leave a clear “removed” note so the developer doesn’t automatically redirect it to the homepage.
Move, consolidate, and remove
| Old content | Is there a suitable replacement? | What response to configure | What the visitor sees |
|---|---|---|---|
| Old service A | New A exists | Permanent redirect | A matching service |
| Old service B | No longer offered | 404 or 410 | A useful error |
| Old product C | There is a direct equivalent | Check the replacement | Not an unrelated category |
| Any old URL | Previously led to the homepage | Remove the blanket rule | Check the exceptions |
Open the page after the redirect
Request the old page using a standard GET request, record the redirect address from Location, and note the final URL. On the destination page, check the title, main text, availability of the relevant action, and that it doesn’t unexpectedly open an account login page. If all old URLs end up at the homepage, find the layer with the blanket rule: content delivery network (CDN), web server, CMS, or browser-side URL handler. Check a URL that never existed. Its behavior shows whether a universal handler is turning any error into a successful redirect. Record the status and the title of the returned page separately. This way, a response of 301 won’t look successful if the visitor has landed on the general homepage.
Give the developer this terminal command for an old service page:
curl -sS -L --max-redirs 10 -D headers.txt -o response.html 'https://example.com/old-service/'In headers.txt, find the full redirect path for the old service page. Then open response.html: the new page should address the same need. A general homepage with status 200 does not prove that there is a suitable replacement. Replace example.com with your domain; this GET request does not change the site settings. curl help.
Replace the blanket rule with exact redirects
Ask the developer to add exact “old URL → new URL” pairs and check that they take priority over the server’s blanket rule. It is better to have an explicit map of important pages than a rule that removes the old path and sends everything to the root. Keep technical redirects for protocol and domain changes, but don’t mix them with content migration. Check that the old URL doesn’t first pass through the homepage and then undergo a client-side redirect. Fix the menus, breadcrumbs, and cards: new links should go directly to the relevant service.
Return 404 for URLs with no replacement
For a removed URL with no suitable replacement, choose 404 or 410 in the CMS’s deletion settings. The error page can include search, links to sections, and an explanation. These elements help visitors, but don’t require returning 200. If a resource is temporarily unavailable, that’s a different situation and requires its own response. Don’t treat every absence as permanent removal. Also check the sitemap and current links: they shouldn’t present a missing URL as a current page. A link may remain in an old overview for historical context, but the text should explain that the service is no longer offered.
Check the service page and an unknown URL
The old service page leads to content about the same service, not to the general homepage. A discontinued service with no equivalent returns 404 or 410, while an unknown URL returns 404. Both pages explain that the requested content isn’t available. The new page doesn’t send the visitor back.
Read also: Checking redirects during a domain migration and Soft 404 with a server response of 200. Site checks are available on the reChecker technical audit page.