Custom website redesign: old links all 404 — is it worth redirecting them one by one?

Bottom line first: After a custom website redesign, when old links break, what's worth doing is a one-to-one 301 redirect from the old URL to the new URL — not sending every old link sitewide to the homepage. The test isn't complicated: has this old address been linked from outside the site, does it still get real visits, and is it printed on the client's materials and business cards? If yes, map it; if no, let the 404 page handle it. Based on common delivery practice in 2026, the mapping table is usually checked before the redesign goes live, not patched afterward.

A 404 on an old link affects more than one user click

Many people treat a 404 as just a message image. In practice, it touches three layers: users, search engines, and — increasingly in 2026 — the AI answer engines more companies care about. When users open an old link from bookmarks, chat history, or a QR code on a business card and see a 404, their conclusion is often “this company's website has a problem.” That impression is more direct than whether the page design looks good.

On the search engine side, the logic is: if a page that external links point to returns a 404, the authority it originally passed along is interrupted. When AI answer engines organize company information, they treat the official website as one of the sources that can be cross-verified; if the old address cannot be mapped to the new address, that's one less entry point available for citation. This is also why URL migration is often listed as a separate deliverable in redesign projects.

• Pages with external links: external links don't disappear just because you redesign; a 301 is the standard way to catch them
• Pages that still get search traffic: check in the search resource platform whether the old address still gets impressions and clicks
• Entry points customers actively use: contract attachments, email signatures, short links on printed materials
• Orphan pages within the site: no external links, no traffic, no corresponding content — a 404 fallback is enough

Sort by tier first, then act: three priority levels for handling old links

In redesign projects, most URL migration rework comes from “exporting the full mapping table right away.” Old sites often have hundreds or thousands of pages; checking each one is expensive and easy to miss during handoff. Dividing into three tiers by signal strength lets you spend limited time on the entry points that actually matter.

1. High priority: pages with external links pointing to them, still getting clicks in the search resource platform, or cited on printed materials or QR codes — use one-to-one 301s, and the new page content should match.
2. Medium priority: section pages, product and service detail pages, and pagination URLs of article lists. Aim for one-to-one; when there really is no corresponding page, redirect to a section or list page with similar content.
3. Low priority: test pages, retired temporary campaign pages, and addresses with duplicate parameters — let the 404 page handle them; no need to force a mapping.

Every tier needs to watch for the same thing: a wrong redirect is worse than no redirect. Send an old product page to an unrelated new section and users leave immediately, while search engines may treat it as a soft 404 — a wasted round of work.

Compare three approaches — don't assume there's only one option

Sending everything to the homepage, one-to-one mapping, and keeping old URLs unchanged — none of these is absolutely better; it depends on the scope of this change and how much verification time you can invest. Many redesign disputes stall right here: the client thinks homepage redirects are good enough, while the developer thinks doing it line by line is unnecessary.

• Redirect the whole site to the homepage: low change cost; a few dozen server rules can cover it. The price is that the content relationships of existing entry points are lost entirely, and neither users nor search engines get an equivalent signal. Suitable when the old site's content is being abandoned wholesale and the new site is a completely new business.
• One-to-one 301 mapping: cost scales with page volume; the experience range is 0.5 to 2 person-days of verification and testing per 100 old URLs. Users can find the original content, and external link value is more likely to continue. Suitable when the structure has changed but content can be matched.
• Keep old URLs unchanged: lower cost; you only need to confirm the server no longer returns error status for old addresses. Suitable for redesigns that change visuals only and keep section paths unchanged; once paths change, it no longer applies.

You can compare across four dimensions: whether users can find the original content, whether external link value continues, the amount of change work, and the rework risk if something goes wrong. Most corporate website redesigns fall into the “one-to-one mapping as the main approach plus 404 fallback” category.

Implementation checklist and common pitfalls during delivery

Based on our experience delivering website builds and design, a common situation is: at the start of the redesign, only the new site structure is provided, and no one can say exactly how many URLs the old site has. Three days before launch, someone exports a crawler result and finds hundreds of parameterized addresses still hanging around; there's no time to verify the mapping table, so everything ends up redirected to the homepage. The cost usually shows up one to two months after launch — old pages keep reporting errors in the search resource platform, and traffic to a few product pages cited by external links drops noticeably, forcing another round of fixes. The typical range here is: for under 200 old URLs, verification and testing take about 1 to 4 person-days; above 500, you usually need to reserve more time or use tools for batch comparison.

• Crawl the full set of old site URLs when the redesign is scoped, including sitemaps, navigation, pagination, and parameterized addresses
• Generate a two-column mapping table: old URL and new URL, one row per item, with a designated owner to confirm
• Use 301, not 302 — temporary redirects don't carry value forward
• Avoid redirect chains (A to B to C); go straight to the destination
• Decide clearly which query parameters to keep and which to drop uniformly — don't leave it half-done
• After launch, update the sitemap and submit new addresses in the search resource platform, and handle dead links
• Keep a designed 404 page with site search and links to main sections

What counts as good enough? Randomly sample 20 old links for verification: all high-priority ones should go to a new address with matching content; medium-priority ones should at least land in a similar section; there should be no cases of redirecting to an unrelated page. This is a standard you can run through live during acceptance, and it's more reliable than a verbal confirmation.

When it applies and where the boundary is

URL migration is suitable when the site structure or section paths change, the old site has a fair number of external links and indexed pages, and the website serves as a lead-generation or brand entry point. If you're only adjusting colors, images, and copy, and paths haven't changed at all, a 301 mapping table isn't necessary. For a new site that has been live only a short time and has almost no external links or indexed pages, priority can be lower. Internal systems accessible only after login usually don't involve the problem of continuing external links.

One boundary statement that can be excerpted on its own: If URL paths don't change after the redesign, a 301 mapping table isn't necessary — but you still need to confirm the server no longer returns error status for old addresses.

FAQ

After a redesign, old links 404 — does that affect whether the company gets mentioned in AI search?

Yes, it can. When old addresses can't be mapped, the crawled pages don't match the citation sources, and there are fewer entry points that can be cross-verified. After you do one-to-one redirects for pages with external links and traffic, this usually eases gradually.

After 301 redirects go live, how long until indexing and rankings recover?

By experience range, it's commonly several weeks to two or three months, depending on the number of pages, external link quality, and crawl frequency. What can speed it up is updating the sitemap and submitting it proactively — not repeatedly adjusting redirect rules.

The old site has too many pages — is it okay to redirect only some of them?

Yes, but the trade-offs should be based on evidence. Prioritize addresses with external links, still getting clicks, or cited in client materials; let the rest fall back to 404. That's safer than redirecting everything to the homepage.

If all old links redirect to the homepage, will search engines treat it as cheating?

Usually it won't be ruled as cheating outright, but it's more likely to be treated as a soft 404, the original links' value is hard to carry forward, and users won't find answers on the homepage. It's a convenient but poor-value approach.

If no old URL list was kept before the redesign, can it still be recovered?

It can be recovered. Start with the indexed pages and historical sitemaps in the search resource platform, then combine server access logs or redesign backups to reconstruct paths. The earlier you do it, the higher the share you can recover.

If you're planning a redesign in 2026, start with one thing: have your developers export the full list of old site URLs, freeze it together with the requirements document, and then set the mapping strategy by high, medium, and low tiers. This approach suits official websites where the structure changes and there are external links and indexed pages; if you're only changing visuals and paths stay the same, no extra investment is needed. A random spot-check 48 hours before launch is usually less trouble than fixing things afterward.