Retire Old Website Pages Without Breaking Links

When an old website page stops matching the business, hiding it from the menu is not enough. Customers can still arrive from Search, bookmarks, email campaigns, QR codes, review sites, social bios, or a Google Business Profile link. The job is to decide where that old URL should lead without sending people to a dead end or an unrelated page.

The clean answer is not to redirect everything. Retiring a page means choosing the smallest honest treatment: keep it, merge it, redirect it, deindex it, or let it return a real not-found response.

Quick Decision: 301, 302, 404, 410, or Noindex?

Situation	Use	Why
The old page has a clear current replacement	301 or 308	The move is permanent and the destination answers the same visitor intent.[1]
The old offer is paused, seasonal, or temporarily unavailable	302 or 307	The change is temporary and the original URL may become useful again.[1]
The page is gone and no fair substitute exists	404	A useful not-found page is better than pushing visitors to an unrelated page.[2]
The page is intentionally gone for good	410	A gone response is appropriate when removal is deliberate and permanent.[2]
The page should stay live but not appear in Search	noindex	Use only for accessible pages that should stay available. Sensitive content needs authentication or restricted access, not just deindexing.[3]

A good redirect target passes one plain-language test: a visitor who wanted the old page can understand why they landed on the new one. If an old wedding catering page points to a current private-events page, that may be fair. If it points to a generic homepage with no catering information, it creates confusion.

Start With a URL Retirement Map

Before deleting anything, make a small URL retirement map. It does not need to be elaborate. For each old URL, record the page purpose, current replacement, traffic or lead value, internal links, external links, campaign links, and the final action you plan to take.

• Use Search Console link data to find pages that still attract internal or external links.^[4]
• Check GA4 campaign links for old URLs with utm_source, utm_medium, and utm_campaign parameters.^[5]
• Check Google Business Profile, social bios, review sites, email templates, QR codes, PDFs, and booking or ordering tools.^[6]
• Mark each URL as keep, merge, redirect, noindex, 404, or 410 before touching the CMS.

The practical insight is to map by customer question, not by page title. An old page called Services may really be answering emergency plumbing, wedding photography, lunch catering, or pricing. The redirect should preserve that question as closely as possible.

Example: Retiring a Seasonal Restaurant Page

Suppose a restaurant has an old holiday ordering page from last year. It still gets clicks from a newsletter, a QR code on printed catering cards, and a few branded searches. The wrong move is to delete it and let visitors hit a bare 404. The second-worst move is to redirect it to the homepage, where the visitor has to hunt for catering.

A cleaner workflow looks like this: keep the useful menu notes and pickup details, move current catering information onto the live catering page, redirect the old holiday URL to that page while the next holiday menu is not available, and update the newsletter template, QR destination, Google Business Profile links, and social bio. When the new holiday menu is ready, publish it at a stable seasonal URL instead of creating another year-stamped dead end.

If the restaurant will never offer holiday ordering again, do not fake relevance. Let the old page return a useful 404 or 410, and make the not-found page point visitors to current catering, reservations, menus, and contact options.

Example: Merging a Renamed Service Page

Now imagine a service business that used to sell a branding package but now sells broader design services. The old page has two testimonials, a useful FAQ, and a handful of links from older blog posts. In that case, the old URL should usually be merged and redirected, not erased.

Move the durable proof into the new design-services page: the testimonial, the before-and-after explanation, the FAQ that still answers a buyer objection, and any pricing language that remains true. Then add a permanent redirect from the old package URL to the current service page. Finally, update the internal blog calls to action so the site links directly to the current service page instead of relying on the redirect.

Preserve the Parts That Still Help

Old pages often contain proof that should survive the migration. Save service explanations, project notes, testimonials, menu descriptions, FAQs, refund terms, parking details, accessibility notes, and event recaps before deleting the source page.

Move content only when it helps the destination page satisfy the same need. A testimonial about wedding photography belongs on the current wedding-photography page. A three-year-old discount code does not. This is also where the work becomes more than technical cleanup: strong destination pages should answer the visitor directly, not just collect redirected traffic.^[7]

Fix the Links You Control

Redirects protect old entry points, but they should not become the site architecture. Update the links you control so current pages point directly to current pages.

• Main navigation and footer links
• Service cards, booking buttons, shop links, menu links, and portfolio calls to action
• Older blog posts and case studies that still get traffic
• PDFs, email signatures, QR codes, automations, and downloadable resources
• Google Business Profile, social profiles, review-site profiles, reservation links, and ordering links

For a small site, fix global navigation first, then high-traffic pages, then older resources. Keep redirects as a safety net for bookmarks, outside links, and campaign links you cannot edit.

Common Mistakes That Break Trust

• Redirecting everything to the homepage. This hides the problem from crawl tools but leaves visitors without the answer they clicked for.
• Deleting before exporting evidence. Once a page is gone, it is harder to see old copy, calls to action, metadata, and proof worth preserving.
• Creating redirect chains. Old URL to newer URL to newest URL is slower and messier than pointing the old URL straight to the final page.
• Using noindex as privacy. A deindexed page can still be opened by anyone with the URL. Sensitive client, pricing, medical, legal, or account information needs access control.
• Changing URLs for neatness alone. A cleaner slug is not worth losing signals, links, and customer bookmarks unless the page structure is genuinely improving.
• Redirecting unrelated pages to a money page. Irrelevant redirects are bad for visitors and can become a search-quality risk when used manipulatively.^[9]

Use Platform Notes Only After the Map Is Clear

Builder controls, redirect limits, and plan features change. Do not let platform documentation drive the strategy. First decide what each old URL deserves. Then check whether your CMS, builder, host, or ecommerce platform can implement those decisions cleanly.

If your current plan cannot create the redirect you need, keep the old page live with updated copy and a clear link to the current page until you can implement the redirect properly. A clear temporary page is better than a silent deletion.

Launch and Monitor

• Test every important old URL and confirm the intended result: 301, 302, 404, 410, or live page with noindex.
• Confirm the redirect destination is live, mobile-friendly, and not redirected again.
• Complete the customer action from the destination page: form, booking, phone link, order, reservation, download, or contact path.
• Watch GA4 for campaign traffic still hitting retired URLs.
• Review Search Console performance and link data for the destination pages after recrawling.
• Track lead quality, booking quality, phone calls, and orders, not just traffic.

The best retirement plan is answer-first: clear decisions for humans, clean signals for crawlers, and destination pages that explain the current offer without forcing visitors to reconstruct your old site. That structure also makes the page easier for search systems and AI features to interpret when they summarize or surface information from the web.^[8]

Retirement Rule

If the old page has a current equivalent, use a targeted permanent redirect. If the page may return soon, use a temporary treatment or keep it live with current next steps. If the offer is gone and no current page answers the same need, return a real 404 or 410 with a useful path back into the site.

If the retirement work is part of replacing a messy site, start by comparing old URLs to the new structure before anything is deleted. Deep Digital Ventures WebsiteBuilder can help turn that structure into a clearer site before the old pages are removed.

FAQ

Should every retired page redirect somewhere?
No. Redirect only when the destination is a fair substitute. If no current page answers the same need, use a useful 404 or 410.

Is a 301 better than a 302?
Neither is universally better. Use a 301 when the move is permanent. Use a 302 when the change is temporary.

Can noindex replace a redirect?
No. Noindex is for a page that remains live but should not appear in Search. It does not move visitors and it does not protect sensitive information.

How long should redirects stay in place?
Keep important redirects as long as old links, bookmarks, campaigns, or listings may still send useful visitors. For high-value service, booking, menu, or product URLs, that often means indefinitely.

Sources

1. Google Search Central, Redirects and Google Search: https://developers.google.com/search/docs/crawling-indexing/301-redirects
2. Google Search Central, HTTP status codes, network errors, and DNS errors: https://developers.google.com/search/docs/crawling-indexing/http-network-errors
3. Google Search Central, Block Search indexing with noindex: https://developers.google.com/search/docs/crawling-indexing/block-indexing
4. Google Search Console Help, Links report: https://support.google.com/webmasters/answer/9049606
5. Google Analytics Help, campaign URL parameters: https://support.google.com/analytics/answer/10917952
6. Google Business Profile Help, edit business information and profile links: https://support.google.com/business/answer/3039617
7. Google Search Central, Creating helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
8. Google Search Central, AI features and your website: https://developers.google.com/search/docs/appearance/ai-features
9. Google Search Central, Spam policies for Google web search: https://developers.google.com/search/docs/essentials/spam-policies

Continue reading→