Before retiring a service page, identify why people still arrive there. A prospective customer may be trying to make a booking, while an existing customer may need instructions for an order or appointment. Those tasks can require different destinations. Confirm what the business can still do, then choose whether the old URL should explain the change, redirect to a useful successor or return a clear unavailable response.
Treat retirement as a customer handoff. Turning off a service and removing its page are separate decisions. Keep the information people can still act on, assign its owner and verify the old routes after the change. The work is complete when someone following an old link can understand what happened and find a valid next step where one exists.
Disclosure. AI Visibility is published by Lunasol, which offers GEO and AEO services. The UAE service example below is fictional. The public retirement and social examples are used within their dated scope. No live site was changed or transaction performed for this guide. About AI Visibility
List the tasks that survive the service
Ask the service owner to confirm the effective end date, whether the decision is permanent and what happens to existing customers. A business may stop taking new bookings while continuing work already agreed. A paid service may end while its documentation stays useful. A renamed service may continue with narrower terms. Record those distinctions before the web team decides what to do with the old page.
List the routes customers could take into the page. Include search, the site's navigation, partner links, saved emails and campaign or social links. Check which of those routes still receive attention or support important tasks. Traffic can help set priorities. The presence of a high-impact task matters even when only a few people use it. An old appointment reminder can be more consequential than a widely shared link to a former campaign.
Microsoft's public Skype retirement documentation illustrates this separation. It describes a transition to Teams Free and gives separate information about data, existing invite links and paid services. The document also describes differences in what transfers. An editor can take from this example the practice of giving each surviving task its own answer and date. It does not establish that those transition options are still available today or that every retired service needs a migration path. Microsoft's Skype retirement guidance
Decide what the old URL should do
Keep a useful closure or transition page when existing customers need an explanation that is specific to the retired service. Lead with what changed and when. Follow with the approved routes for existing orders, bookings or support. If an alternative serves new customers, describe how its scope differs and link to it. Remove sales copy that still implies the former service can be booked. Keep the notice in the language the customer used to arrive where possible.
Use a permanent redirect when the service page moved or there is a clear successor that answers the old question. Open the proposed destination and ask whether a reader can understand the relationship and complete the same task. If the new offer only partly replaces the old one, a notice linking to several verified actions may help more than a redirect to one of them. Sending someone to a homepage can force them to reconstruct the decision the old page used to answer.
When the page has been removed and there is no similar replacement, Google Search guidance describes returning a 404 or 410 response. It also describes a permanent redirect for content that moved or has a clear replacement. A useful error page can offer navigation while returning the correct status. A real closure page with useful guidance is a separate option because the page still has a purpose. Agree the intended status and destination with the web owner, then verify the live result. Google Search guidance on removed pages and replacements
GOV.UK distinguishes keeping withdrawn content available with explanatory context from unpublishing it, depending on content type and policy. That public workflow illustrates a decision any editor can ask in their own context. Does leaving the old text as it is help the reader, or does it get in the way of completing today's task? Use your publishing system's own status and release process to implement the answer. GOV.UK guidance on retiring outdated content
If the service is suspended temporarily, set a separate review. Publish the current status and the next confirmed step, such as a date for checking availability or a contact path for existing bookings. Avoid describing an unconfirmed reopening as a commitment. Where operations has no reopening date, say how the team will handle enquiries now and who will decide whether the page should change again. Recheck scheduled campaigns and automated booking messages so they do not keep taking new customers into a paused process.
Decide whether a successor is equivalent from the customer's point of view. Compare the audience, fulfilment method, eligibility and next action. A service that used to include collection and now requires a workshop visit may address the same general need while changing a material condition. The new page can explain that difference, or the old page can provide a short bridge to it. Ask the service owner to verify the wording before the route goes live.
Preserve history without carrying forward an obsolete action
Separate instructions that still apply from material that explains the earlier offer. A checklist can remain useful if its steps work for the current service. A past promotion or event can still be worth describing if its period and purpose are clear. A registration button or reservation instruction has a different role. Review whether it still has a valid destination and whether readers could mistake it for an open offer.
The official Dubai Fitness Challenge Instagram reel dated 2 November 2026 is a recap of Dubai Ride. It illustrates a social asset that remains useful in an account of a past edition. The organiser's event page also presents 2026 highlights. An editor retiring an old signup article could keep the recap as historical context, provided the article clearly explains its purpose. A future registration guide needs its own current source. No registration availability or event performance is inferred from the reel. Official Dubai Fitness Challenge Instagram recap · Dubai Ride event page
Inspect the short forms of the old page too. A social caption may still direct people to book, a pinned highlight may show a former price and a downloadable PDF may contain a contact route that no longer works. Give each important copy an owner. Update a controlled link or caption where appropriate, and request changes to partner copies that still create a material risk. Keep historical credits and source dates with any retained asset.
Work through a fictional service retirement
Imagine a Dubai bicycle workshop ending a weekend pickup service. Previously arranged collections still have a support route, and the company continues to accept workshop appointments. The operations owner confirms that the workshop booking form cannot check a previous pickup. The editor keeps the former service URL as a transition page with separate instructions for each task. This example is fictional and describes no real workshop or booking policy.
| Reader arriving from an old link | What the replacement needs to say | Owner and check |
|---|---|---|
| Someone checking a previous pickup | The service has ended for new customers and previous collections use the approved support channel | Operations verifies the policy and the web editor checks the live link |
| Someone seeking a new repair | The workshop still offers in-person appointments under its current terms | Service owner checks availability wording and booking path |
| Someone reading an old campaign | The offer applied to a dated period and the former pickup action is closed | Campaign owner verifies public copy and destination |
| A partner linking from an old directory | Use the closure notice or the current service page according to what the listing promises | Partnerships owner requests the appropriate change and checks the public result |
| A reader using the Arabic route | Explain the same service boundary and provide a usable handoff | Locale owner checks wording and the destination |
The publisher can decide how long to keep the transition page after observing which tasks still depend on it. Give that decision a review date and owner. If previous customers still need help, keep the relevant instructions easy to find. If that need has ended and another page offers a clear replacement, consider changing the old route after checking links and approvals. Preserve the original policy reference in the internal record so staff can explain the earlier service if a question returns.
Test from the old routes and hand off what remains
Open the former URL as a visitor and check the final destination and visible information. Follow important links from navigation, customer emails and campaign pages where you have access. Verify the correct service name, language and next action. For a redirect, have the web owner record its status and final location. For a notice, verify that the old booking option cannot still be selected from another active route. Stop before sending a real request unless an authorised test has been arranged.
Use a short record the next reviewer can take over.
Service page retirement
Service, old URL and effective end date
Customer tasks that still need support
Approved notice, redirect or removal decision
Related links, assets and channel owners
Public verification and unresolved destinations
Next check and the person who can change the route
Include the person who owns the booking system in the release check. The page may be gone while a saved booking form still offers the former service. Verify that the form shows the intended options and that any permitted request for existing support reaches the team named on the notice. If the old link has been shared with partners, record which links you checked directly and which owners still need to respond. Review the transition again if support enquiries show that visitors are reaching the wrong destination.
If an assistant or search result continues to present the old offer, capture the date and the route it gives. Open the destination and verify that the current handoff still works. If it cites a partner page presenting the old service as live, assign that copy for correction. If the page is accurate and the answer repeats outdated wording, keep the observation separate from the website task. An old answer may recur even after the business has verified the current customer guidance.
The broader AI Visibility guides cover initial search and content work. This playbook covers the end of a specific offer and the tasks that remain. Retain the approved decision, the public checks and the next review date so a colleague can explain the retirement without having to reconstruct it from the old campaign. AI Visibility guides and 90-day plan



