Skip to content
Guides

Changing a page URL? A practical redirect checklist for OffPress

You have renamed a service, reorganized your workshops, or found a clearer title for an old article. Changing the page address feels like a small finishing touch. But that address may already be in a customer's bookmark, an email campaign, or a link on someone else's website. Before replacing it, decide what should happen when someone follows the old link.

This checklist is for a page move within your existing website, not a domain change. The aim is simple: keep useful links working and help visitors reach the right content. It is not a promise that search rankings will stay unchanged.

1. Decide whether the address needs to change

A new headline does not automatically require a new URL. If the page still serves the same purpose and its address is useful, keeping it avoids a move you do not need. You can improve the copy, page title, and SEO description without treating every edit as a relocation.

For example, changing a workshop page's heading from “Our workshops” to “Practical workshops for small teams” does not by itself make /workshops a poor address. A move makes more sense when the old path is misleading or the site structure genuinely needs to change. Do not rename working URLs simply to fit more keywords into them.

2. Confirm the real current route

Open the published page and copy its address. Do not assume the slug shown in the editor tells the whole story. OffPress documentation notes that imported pages may retain their original paths, so changing a slug may not change the public address. If the two do not match, ask OffPress to check the current route before making changes.

For each planned move, write down the old path, intended destination, reason for moving, and places where you control links to it. Start with navigation, buttons, related articles, and reusable email templates. Keep this short list as your test plan.

3. Choose a destination that answers the same need

Imagine someone opening the old link without knowing that anything changed. Would the destination still help them? A renamed workshop page should lead to the replacement workshop page, not automatically to the homepage. If there is no equivalent, decide what explanation or alternative the visitor needs rather than hiding every retired page behind the same redirect.

In this fictional example, /old-workshops is moving permanently to /workshops. Check that the destination opens and contains the intended information before switching visitors to it. These example paths are not links to actual OffPress pages.

4. Add the redirect in OffPress

In Content Admin, open Settings → Redirects. Create a record with the old path in From and the destination in To. Choose 301 Permanent for a lasting move or 302 Temporary for a temporary one. Turn on Active and save. The search settings and redirects guide has the current instructions, including how to review the page's SEO fields.

Do not point an address back to itself or create a loop between two pages. If a destination has moved more than once, ask for the old addresses to lead directly to the final page rather than deliberately adding more intermediate stops.

5. Update the links you control

A redirect supports people using the old address; it is not a reason to keep publishing that address everywhere. Update your menu, page buttons, and relevant article links to the final destination. Review recurring email templates and profile links too. You cannot edit messages already in someone's inbox, which is one reason the redirect still matters.

Keep the requested work narrow. If you are moving one service page, do not bundle in a site-wide URL cleanup unless you have a separate reason and a plan for each move.

6. Test the live journey, not just the saved record

Open the old address on your live domain in a fresh browser tab. Confirm that it reaches the intended final address, then read the page and try its main next step. Also open the destination directly and follow an updated internal link. Check on a phone if the moved page is part of an important enquiry or purchase journey.

If the work includes site code or design changes, follow the publishing guide to release those changes. Do not treat the main site Publish control as a second approval gate for edits to already-published CMS content: saving those edits can affect the live site immediately. Coordinate the work accordingly.

A focused AI brief you can reuse

“Check the current public route for [page]. I want to move it from [old path] to [new path] because [reason]. Confirm whether an imported path affects routing. Prepare the destination, add the appropriate redirect, and update the internal links you find. Preserve unrelated pages and metadata. Tell me which changes need a site publish, then test the old and new addresses on the live domain.”

Replace the brackets with real details before using the brief. The best outcome may be a decision to keep the existing URL. When a move is necessary, a clear destination, a working redirect, and a completed live test are more useful than a tidier-looking slug alone.

← All articlesRebuild my site — free →