Someone opens a link they saved last month. The offer has ended. What should they understand next?
That question matters even when you have stopped promoting the page. An old email, bookmark or printed handout can still bring someone to it. Your new campaign does not explain what happened to the old one.
Prepare one retirement record: the promise being withdrawn, the visitor's remaining question and the destination that honestly answers it. This is a content and routing brief for a ClickFunnels AI project. It does not delete a page, configure a redirect or change anyone's access.
Confirm what is ending
Retiring a page and ending an offer are different decisions. An offer may continue at a new address. A completed workshop may still need a useful information page. A discontinued service may have no replacement.
Write the exact decision and who supplied it. “The spring workshop has finished; no new date is confirmed” is different from “The same workshop now uses a new booking page.” Avoid treating an internal discussion as a public closure date.
If the business only needs to pause new enquiries until capacity returns, use the pause-and-reopen plan. This exercise concerns retiring an old invitation or address, not managing a temporary intake limit.
Record existing commitments separately. Closing a page does not cancel an accepted job, settle a refund or establish that an earlier request was received. Those decisions belong to their responsible owners and existing processes.
Ask whether the proposed replacement keeps the promise
Before choosing a destination, compare the old invitation with the new one. Does the visitor still reach the same offer, with the same essential scope and next action? If the price, audience, service or commitment changes, record that difference.
A different offer may be worth showing as an optional choice. It is not automatically a replacement for the thing the visitor requested. A general homepage may make them search for an answer that the old link should have explained.
Google's URL-move guidance recommends mapping old addresses to relevant destinations and warns against sending unrelated old pages to one generic homepage. Use that narrow relevance principle here. It does not establish that any proposed destination is suitable or promise that search visibility will be retained.
Work through four fictional decisions
Imagine Willow Lettering Studio is reviewing several old offer pages. The business, paths and facts below are invented. The paths are labels for this exercise, not live CFAI routes. No page or response has been changed.
Scroll horizontally to compare all columns.
| Case | Confirmed facts in the example | Decision to prepare |
|---|---|---|
| E01 — Finished workshop | The spring workshop is over. The studio still maintains useful information for its participants. No next workshop is confirmed. | Replace the invitation with an accurate ended-workshop explanation and the existing participant-information route, if that route is confirmed. Do not advertise another date. |
| E02 — Same offer, new address | The current lettering-kit offer has moved from /sample/old-kit to /sample/current-kit. Its scope and next action are unchanged. |
Ask the implementation owner to evaluate a permanent move to the verified equivalent destination. Check both addresses after any authorized change. |
| E03 — No equivalent offer | The studio has stopped offering custom chalkboard lettering. Its current greeting-card workshop is a different task. No useful historical service page is being maintained. | Plan an honest no-longer-available response. Do not silently redirect to the unrelated workshop as though the original service continued. |
| E04 — Decision missing | Someone suggests retiring a private-coaching page, but the offer owner has not decided whether coaching is ending or moving. | Keep the retirement change unresolved and assign that decision. Do not invent an ending, replacement or reopening date. |
E01 preserves useful context. E02 preserves a genuinely equivalent journey. E03 admits there is no equivalent. E04 identifies a missing business decision. These are different outcomes, not four versions of “send everyone somewhere new.”
Write the explanation before choosing the mechanism
For E01, a proposed message is:
The spring lettering workshop has finished. No next workshop date is confirmed. Existing participants can use the participant information page.
That last sentence belongs only if the studio has confirmed the route and its intended access. The example supplies no real link. If the route is unknown, omit the invitation and resolve it with the owner.
For E03, start with the changed fact: “Custom chalkboard lettering is no longer offered.” If you include the greeting-card workshop, label it as a different current option and let the visitor choose it. Do not rename it “your replacement booking.”
Keep a useful explanation separate from its technical response. Google distinguishes successful responses, redirects and not-found responses in its HTTP-status guidance. A page can display a friendly error message while sending an inappropriate success status. Ask the implementation owner to choose and verify the response for the actual content; editing the heading cannot establish it.
For a confirmed permanent move, Google's move guidance discusses permanent redirects. For removed content without a replacement, it discusses not-found or gone responses. Neither instruction means every ended offer must disappear: E01 retains meaningful information. An HTTP success also does not guarantee indexing.
Include the routes people already use
List controlled links to the old page: navigation, related guides, prepared messages and active campaign destinations. Record which owner can update each one. An already-sent email or someone else's saved bookmark cannot be repaired by editing a new message draft.
Give each old address its own planned outcome. Do not apply a broad redirect rule just because several pages share a folder. Keep unrelated services, existing-customer destinations and intentional CF2 journeys outside the change.
If an old form could remain open during retirement, ask the receiving owner how that boundary will be handled. Removing its invitation does not establish whether an already-loaded form still accepts a request. Preserve unknown request state rather than declaring a submission cancelled or saved.
Close the plan with observable checks
After authorized implementation, open the exact old address in a fresh anonymous visit and follow the intended path. Record the page wording, final destination and technical response separately. Check that any existing-customer route still serves its intended audience without exposing private material.
Inspect the new destination's actual offer, not only its title. Recheck controlled links and any permitted transition case. Leave unperformed checks NOT RUN. A working redirect is not evidence of retained rankings, customer understanding or completed obligations.
Use the offer-page retirement worksheet to prepare E01–E04 and your own decision record. Bring the approved scope into the current ClickFunnels AI workflow at /agents. This grants no redirect feature, deletion authority, builder admission or product cutover. Start with the old link whose visitor question you cannot yet answer honestly.