Short answer: If the same plan still exists, update its stable page. If the old plan has a clear replacement at a new URL, redirect the old URL to that relevant replacement. If no replacement exists, explain the retirement where users need it and return a real error status for a removed page. Do not leave an obsolete price live simply because a new pricing page has been published.

The immediate risk is a buyer arriving from a saved link and believing a retired plan can still be purchased. A second risk is that search or an AI answer uses the old page as source material. Google says its AI search features rely on indexed content and links to supporting web pages; it does not guarantee that a recently updated page will immediately replace an old answer. Google's AI optimization guide makes the indexing connection clear.

Match the old URL to the correct fate

Use a URL inventory rather than a blanket redirect rule:

  1. Same plan, same URL: revise the visible price, billing unit, eligibility, and structured data if present. Check the purchase flow against the page.
  2. Equivalent plan moved: use a permanent server-side redirect from the old URL to the specific current plan page. Google's redirect guidance treats permanent redirects as a signal that the destination should be canonical.
  3. Plan retired, no equivalent: make a clear retirement explanation available for people who need it, but do not pretend an unrelated homepage is the old plan's successor. For a page that is truly removed, use the correct HTTP 404 or 410 response rather than a success page that merely says “not found.” Google's status-code guidance explains how error responses are processed.
  4. Multiple live URLs with substantially the same current terms: choose one preferred version and use consistent canonical, internal-link, and sitemap signals. Google's canonicalization documentation explains that a canonical is a strong hint, not a command.

The right fate depends on what the old page meant. A historical release note that explains a past offer can remain useful if it is unmistakably historical and does not present a purchase action for a retired plan. A transactional pricing URL generally needs a current route. Record the decision for each URL and test the destination, rather than guessing from the slug alone.

Test the answer after the change

Open old URLs directly on mobile and desktop. Check the page title, visible price, plan name, currency, billing period, tax or fee qualifier, and final checkout total. Inspect the HTTP response and follow the redirect to its final destination. Update internal links and any sales or support messages that still use old URLs. Search Console can help inspect how Google sees a URL, but changes may take time to be recrawled and indexed; do not claim an instant AI-answer correction.

This is a product-content maintenance task, distinct from a whole-site redesign migration. ARCHV's website service page lists content migration and technical changes as separately scoped work. Bring a list of old and current plan URLs to a website estimate so the content, redirects, QA, and ongoing owner can be agreed before launch.