Owner, trigger and scope
The web publisher owns the procedure: they control the content management system or the redirect rules and run every step that touches the site. The SEO lead approves the decision and the new address, and signs off the tests. Each channel owner (paid media, email, social, local listings, print) replaces the old address in their own channel when the web publisher asks, and confirms when it is done.
The trigger is any change to the address of a live, indexed page: a product or service renamed, a section restructured, a slug corrected, or two pages that compete for the same searches merged into one. The site architecture guide recommends changing URLs only with a reason and a redirect mapThe table of every old URL and its new destination, one row per address, from which a site migration or URL change is built and then checked., and this procedure is how that advice is carried out one page at a time.
Three neighbouring jobs are out of scope and have their own pages:
| Situation | Where it is handled |
|---|---|
| Many addresses change at once: a new domain, platform, protocol or URL pattern | SEO for site migrations and the website migration checklist |
| A page with an end date (a listing, an event, an offer) expires | Expired listings, events and offers |
| A new page is published for the first time | Publishing a web page SOP |
If a single change grows into a pattern, such as renaming every product page in a range, stop and treat it as a migration: the inventory, staging tests and monitoring that a project needs are beyond a per-page routine. A page that is being retired with no true equivalent to move to follows the SOP for removing a web page instead. The SOP library routes the other recurring web tasks, from publishing to error triage.
Before you start: inputs and access
| Input | Owner | Notes |
|---|---|---|
| The approved reason and the new address | SEO lead | A written sentence on why, and the final slug |
| A row in the redirect map | Web publisher | Old address, new address, match type and test result, as in the redirect map template |
| The list of places the old address is used | Web publisher, with channel owners | From a site crawl, the ad accounts, the email tool, profiles and print |
| Access to redirects | Web publisher | The CMS redirect manager or the server configuration |
| Search Console access | SEO lead | For the property that holds the page |
| The link register and change log | Marketing operations | Where tagged links and measurement changes are recorded |
Keep the guide to permanent redirects open. Its rules (permanent, one hop, to the true equivalent, kept in place) are the standard every test in this procedure checks against. If both addresses must stay reachable, this is not a move at all: the comparison of canonical tags and permanent redirects explains when a canonical is the right tool instead.
The procedure
Confirm the change is worth making and approve the new address
Write down why the address must change and what the new one will be. A renamed product or a merged page is a reason; a slightly better keyword in the slug usually is not. The one-way and two-way doors framework is a useful lens: once external links, printed material and the index point at the new address, changing it again means a second redirect and a risk of chains, so this is closer to a one-way door than it looks. The SEO lead approves the address before anyone builds anything, and checks it follows the site's URL conventions.
Find every place the old address is used
Crawl the site for internal links to the old address, then ask each channel owner to search their own tools. The method is the same one the tutorial on withdrawing an asset from every channel uses for a claim or an image: list the places, then confirm each. For a page that runs in advertising, the Google Ads website migration guide lists where addresses hide in an account: final URLs of enabled and paused ads, link assets, Performance Max settings, tracking templates, the product feed and the thank-you addresses used in conversion triggers. Add email templates and automated journeys, social profile links, the business profile's website link, QR codes on print and any partner pages.
Write the redirect row: one hop, permanent, to the true equivalent
Add the row to the redirect map. The migrations guide sets the rules: a permanent redirectA permanent server redirect telling browsers and search engines a URL has moved for good., server-side or in the CMS, straight to the page that serves the same purpose. If the old address already receives redirects from earlier changes, update those rows to point at the new address directly, so nothing chains. When two pages merge, both old addresses point at the surviving page, and that page must actually answer what each of them answered.
Publish the page at the new address and switch on the redirect
Publish the page at its new address through the publishing SOP, which sets the title, structured data, canonical and tracking. Switch on the redirect at the same moment, not before, so the old address never points at a page that does not exist yet and the new page never sits live without the old one sending visitors to it.
Update internal links, the canonical tag and the sitemap
Change every internal link found in step two so that it points straight at the new address. The permanent redirect entry is explicit that a redirect protects the links a site does not control, while the links it does control should be fixed at source; the internal linking guide explains why those links matter. Confirm the new page's Canonical TagTells search engines the preferred URL. refers to itself, that the sitemapA file listing the URLs a site wants search engines to discover and crawl. lists the new address and not the old, and that navigation, breadcrumbs and related-page modules have updated.
Update ad destinations, feeds and URL-based conversion rules
The paid media owner replaces the old address in ads, link assets and the feed, choosing the best new destination for each ad rather than relying on the redirect. Then check anything that recognises a page by its address. The conversions not tracking diagnosis names a changed thank-you address as a classic cause of silent loss, and the Meta website migration tutorial warns that custom conversions and audiences built on URL rules stop matching when paths change. Rewrite rules so that they match the new path, or both paths during the switch.
Update emails, automations, profiles, social bios and the link register
Channel owners replace the old address in email templates, automated journeys, social profiles, pinned posts and partner pages. If the page is a location page, the listings owner updates the website link on the business profile, which the business profile tutorial points at the location's own page. Tagged links that carried the old address are reissued through the UTM link request SOP and the register is updated, so nobody copies an outdated link from it later. Printed material cannot be recalled, which is one more reason the redirect stays.
Test the old address, the new page and the tracking
Request the old address and confirm it returns a permanent redirect straight to the new page, with no chain or loop. Request the new address and confirm a normal response; the SEO page checker reads the head and directives of a single live address quickly. Click through from an ad preview, a test email and the profile. Complete the page's main conversion and confirm it records once. The website migration checklist holds the launch-day checks for a whole site; pick the ones that apply to a single page rather than inventing new ones.
Watch Search Console and log the change
Watch the page in Search ConsoleGoogle's search performance and indexing tool.: the Search Console tutorial shows how to inspect the new address and read clicks by page, so you can see the new address take over from the old. If the page indexing report starts showing the old address as a soft 404A page that returns a success status code but shows an error, empty or not-found message. or another error, the Search Console error triage SOP takes over, and the soft 404 diagnosis explains the usual cause: a redirect target that does not answer what the old page answered. If the old address shows up as not found instead, the redirect is missing or broken, and the page on not-found errors in Search Console covers that case. Finally, add the change to the measurement change log, so anyone reading a report later knows why one page's history stops and another's starts.
A music publisher renames its catalogue pages (illustrative)
Three catalogue pages renamed to match how teachers search
Vaskrell Music Editions, an invented sheet-music publisher with an online shop, renamed three catalogue pages so their addresses matched the grade names teachers use. The SEO lead approved the new slugs after checking that the pages had earned 41 external links between them. The search for the old addresses found them in 2 search ads, 1 sitelink, the welcome email, a QR code on 3,000 printed catalogues and a conversion rule that counted sample downloads by path. The web publisher added 3 redirect rows, one of which replaced an older redirect that would have created a chain, published the pages and switched the redirects on together. Paid media changed the ads and the sitelink the same morning; the email owner updated the welcome email template; the conversion rule was rewritten to match both paths. Testing showed every old address answering with a single permanent redirect. In Search Console the new addresses took over the old ones' clicks within the month, with no fall the team could not explain, and the change log entry let the analyst read the break in the page report correctly.
QA checks
Before the change is closed, the SEO lead confirms each check below. If one fails, fix it at source and test again rather than adding another redirect on top.
- The old address returns a permanent redirect straight to the new page, with no chain or loop.
- The new page returns a normal response, carries a self-referencing canonical and appears in the sitemap.
- No internal link, ad destination, email template or profile still points at the old address.
- Conversion triggers and audiences that used the old path still match.
- The change log has the date, both addresses and the reason.
Hand-offs and records
The procedure hands three things on. Paid media receives the new destination for every ad and asset, and is asked to read the next few weeks of results with the change in mind. The email, social and local owners receive the new address with a request to confirm the replacement in their channel. The SEO lead receives the watch on Search Console until the new address has clearly replaced the old one.
The lasting record is a dated row in the redirect map and an entry in the measurement change log naming the old and new address, the reason, who approved it and the result of the tests. The redirect map is also the place the next person looks before changing the same page again; a page that has moved twice should never send visitors through both moves.
Common mistakes
Each of these turns a simple rename into lost visitors or broken reporting.
- Changing the address for cosmetic reasons. Every change is a small migration. Change only with a reason.
- Redirecting to the home page. A redirect to an irrelevant page is commonly treated as a soft not-found. Redirect to the true equivalent or remove the page deliberately.
- Leaving internal links on the redirect. Fix the links you control at source; keep the redirect for the ones you do not.
- Forgetting the ads and the feed. A paid click that bounces through a redirect, or lands on a page that no longer matches the ad, wastes the click.
- Breaking the conversion rule. Thank-you paths and URL-rule audiences stop matching silently.
- Building chains. A page renamed twice should redirect from both old addresses straight to the newest one.
- Removing the redirect later. Links on other sites, bookmarks and print never update. The redirect stays.
