Change a destination without changing the published link
A link already printed, emailed, or posted is difficult to recall. If that public URL points to a redirect you control, you can revise the redirect's destination while keeping the public address intact. You must continue to own the hostname and operate the route.
General educationKeep identity separate from destination
Suppose https://go.example.com/spring appears on posters and social posts. It first redirects to https://example.com/spring. When inventory changes, its target can become https://example.com/spring-clearance. The audience still scans or types the same public URL. The managed address is an asset with a lifecycle of its own; the target is a changeable relationship.
Published: https://go.example.com/spring
Before: → https://example.com/spring
After: → https://example.com/spring-clearanceA safe change is a small release
Check that you control the new destination and that it is suitable for the original audience and promise. Record the old URL, proposed new URL, reason, owner, and time. If a campaign has UTM parameters, decide whether to keep, replace, or remove them deliberately. Check for an unsafe or unrelated target before changing a trusted short link.
Update the managed link only after the new landing page is available. Test the public link from a fresh session, follow all redirects, inspect the final page on mobile, and confirm campaign parameters. Retain a revision record so a sudden change in traffic or customer experience can be explained. A permanently cached redirect may continue to point some clients at the old destination; status and cache controls are operational choices.
- Campaign: replace an expired offer with a current offer, while respecting the original promise.
- Social profile: update one bio link when the featured landing page changes.
- Email: correct a wrong landing path after a message was sent.
- Print: keep a packaging or vehicle URL useful across site redesigns.
When a destination edit is the wrong repair
Do not silently repurpose a published link to unrelated content, especially where a reader has a specific expectation or a prior transaction. Preserve an archived explanation, a dedicated error page, or a new route when that is more honest. A redirect cannot rescue a domain you no longer own, a provider account you cannot access, or a code that encodes an unrelated address.
Pause and expiry can be useful controls, but their exact behavior must be verified in the production application. The current public Sites interface shows example control states; it should not be treated as proof of a live production redirect policy.
Maintenance continues after the edit
Document the domain renewal owner, review important published links periodically, and retest after site migrations. If a destination goes away, a stable public URL gives you a recovery point only while the managed route still works. It is continuity infrastructure, not a guarantee that all future targets will be healthy.
Decide who may make a change
For high-value placements, a destination edit can affect thousands of people immediately. Assign an owner, a reviewer where warranted, and a rollback target. Keep the public URL in an inventory with the physical or digital placements that use it. A history entry should answer what changed and why, rather than merely showing two addresses.