Why a migration is a Google Ads event
The SEO site migrations guide plans the organic side of a migration, and the redirect map template holds the old-to-new URL mapping. Neither covers the paid account, which depends on the site in four ways that organic search does not.
- Destinations. Ads, link assets and Performance Max asset groups send clicks to specific addresses. A page that moves without the account being updated sends paid clicks to a redirect, a not-found page or the wrong page.
- Policy. The Google Ads pillar states that policy is enforced at the landing page level as well as the ad, and that destination requirements cover broken pages, misleading claims and pages that do not match the ad. A migration can disapprove ads nobody in the account touched.
- Measurement. Conversion actions depend on the Google tag and the conversion event being present on the new templates, and often on the address of a thank-you page. A migration is the commonest day for tracking to break.
- Products. For Shopping and Performance Max, the feed's links, prices and availability have to match the new product pages, or products are disapproved.
The consequences arrive together. A broken tag means automated bidding sees fewer conversions and bids down while ads are being disapproved and clicks are landing on the wrong pages. Planned in advance, each is a short checklist item.
Inventory every URL the account uses
Before mapping anything, list every address the account and the feed point at. The SEO guide builds its inventory from crawls, sitemaps, logs and Search Console; the paid inventory comes from the account itself.
| Where the URL lives | What to export or list | Why it matters |
|---|---|---|
| Ads | Final URLs of every enabled and paused ad | The main destinations of paid clicks |
| Link assets | Sitelinks and any other assets that carry a URL, at account, campaign and ad group level | Easy to miss, because they sit outside the ads |
| Performance Max | Asset group final URLs, URL exclusions and the final URL expansion setting | Expansion can send clicks to other pages on the site |
| Tracking settings | Tracking templates and final URL suffixes at any level | They can carry parameters or redirects of their own |
| Merchant Center | The link attribute of every product, and canonical_link where used | Product ads send clicks to the feed's links |
| Conversion tracking | Thank-you and confirmation addresses used in conversion triggers | A changed address leaves the trigger firing on nothing |
Paused ads and assets belong in the inventory too: they are often re-enabled months later, by someone who assumes the address still works. The Performance Max structure guide explains final URL expansion and URL exclusions: with expansion on, the campaign may send clicks to pages other than the final URL supplied, so the new site's careers, support and account pages need excluding again under their new addresses.
Map old destinations to new ones
Add the paid inventory to the project's 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., rather than keeping a separate one, so that the web team sees every address the advertising depends on. For each row, record the new destination the ad should use, not just the redirect target: the best new page for a paid click is sometimes more specific than the page a 301 RedirectA permanent server redirect telling browsers and search engines a URL has moved for good. sends organic traffic to.
Check each new destination against the ad that will use it. The price, the offer and the claim in the ad should be what the visitor sees on arrival, which is the message match the landing page entry treats as the first test of a page. Where the migration changes product names, prices or offers, the ads change with them. Where a page disappears with no equivalent, decide whether the ad pauses or moves to a broader page, and record the decision.
Tracking: tags, conversion actions and click identifiers
Three links in the tracking chain can break in a migration, and each is checked before launch on the staging site and again on launch day.
The tag and the event. Google's help page on setting up conversion tracking for a website describes the Google tag across the site and an event for the conversion itself; the conversions not tracking diagnosis notes that both have to be present. New templates often ship without the container or with the event wired to the old confirmation step.
The trigger address. Where a conversion fires on a thank-you page, its trigger names the address. The conversion tracking setup tutorial lists "Tag inactive after working before" among its failure patterns, with a site redesign that removed the container or changed the thank-you URL as the cause. Update the trigger to the new address and test a real conversion end to end.
The click identifier. Auto-TaggingA Google Ads setting that adds a click identifier (GCLID) to every ad click's landing URL. appends a click identifier to landing URLs, and Google Ads uses it to connect a conversion to the click. The conversions not tracking diagnosis states the risk plainly: if a redirect, a link shortener or a server rule drops query parameters, the conversion may still fire but cannot be credited to the click. Every redirect the migration adds is a place this can happen. Test with a URL carrying a click identifier parameter through every redirect pattern on the new site, and confirm the parameter is still in the address bar on arrival.
The same move usually affects Meta's pixel, Conversions API route, URL-rule audiences and catalog, and the tutorial on moving a website without breaking Meta Ads carries that side of the migration.
Affiliate partners' links, the click identifier those links carry and the postback that pays partners go through the same move, and the tutorial on protecting affiliate tracking through a website migration plans that part.
Feeds and product links
For product campaigns the feed is part of the migration. Merchant Center's product data specification makes
link, price and availability required attributes, and the product feeds guide
spells out what follows: the link must match the product and be crawlable, and a price or availability that does not
match the landing page is a cause of disapproval. A Product FeedA structured file of a store's products, prices and availability used to build shopping and catalogue ads. exported from a new platform can
change product IDs, titles, image links and category values as well as addresses.
Before launch, compare a sample of the new platform's feed against the old one: the same products, the same IDs
where possible, links pointing at the new pages, prices and currencies matching what those pages show. Product IDs
deserve particular care: supplemental feeds and their overrides are keyed on id, as the feed guide describes, so
a product whose ID changes loses the titles, labels and corrections they supplied. The feed guide
also describes structured data on the product page, which lets Merchant Center check prices and availability
against the page; confirm the new templates carry it.
Launch day: update, review and watch
Launch day in the account follows the site going live, in this order:
- Update destinations. Final URLs, link assets, Performance Max final URLs and URL exclusions, and tracking templates move to the new addresses from the map.
- Confirm the feed has fetched from the new platform and that items are being processed, then read the Merchant Center diagnostics for new disapprovals.
- Watch the review. Edited ads go back under review, as the ads not showing diagnosis notes, and some may be disapproved for destination problems the migration created. The ad policies and disapprovals guide covers the response: read the reason, fix the page or the ad, resubmit.
- Test conversions. Complete a real conversion for each primary action on the live site and watch the tag fire, then check the action statuses the following morning.
- Test the click path. Click a live ad, or use a test URL with a click identifier, and follow it through every redirect to the landing page.
Keep budgets, targets and structure unchanged on launch day. The fewer things that change at once, the easier it is to see which one went wrong.
The weeks after: bidding, quality and reporting
Protect bidding during a tracking gap. If conversions stop recording, automated bidding treats the gap as a fall in results. The tracking outage response SOP sets out the protective options: hold budgets and targets steady, avoid structural edits, and, where the platform documents it, use a data exclusion for the outage windowA period when conversion or analytics tracking stops recording, or records wrongly, while sales carry on; its start and end are marked as the outage window.. Pausing is a last resort. Fix the tracking first, then annotate the affected dates so later reports do not read the gap as a real change.
Watch conversions against the business's own records. For several weeks, compare daily conversions with orders or leads from the shop system or CRM. A widening gap means a link in the tracking chain is still broken for some pages or some visitors.
Watch landing page quality. Quality ScoreGoogle's 1–10 keyword diagnostic. includes a landing page experience component, and the Quality Score guide treats it as a diagnostic pointer. A component that drops after migration points to slower, less relevant or less usable new pages, which is a matter for the web team.
Watch where Performance Max sends clicks. With final URL expansion on, the new site's pages are new candidates; check the landing pages it uses and add URL exclusions for any that should never receive paid traffic.
Reconcile reporting. Note the launch date in reports and dashboards. Comparisons across the migration need the caveat that destinations, tracking and possibly conversion definitions changed on that day.
A store relaunch, step by step (illustrative)
Quiltferry Bedding moves to a new e-commerce platform
Quiltferry Bedding, an invented bedding shop, moves from an old e-commerce platform to a new one, and every product and category address changes. It runs three search campaigns, a Performance Max campaign on a feed of 410 products and two conversion actions: purchase and newsletter sign-up. The paid inventory finds 96 ad final URLs, 34 sitelinks, 5 asset group final URLs, 3 URL exclusions, 410 feed links and 2 conversion triggers.
| Item | Old site | New site | Plan |
|---|---|---|---|
| Category pages | /shop/duvets and similar | /collections/duvets and similar | Final URLs and sitelinks updated on launch; 301 redirects as a safety net |
| Purchase confirmation | /checkout/thank-you | /order/confirmed | Trigger updated and tested on staging |
| Newsletter confirmation | /subscribe/done | Inline message, no new page | New trigger on the form success event |
| Feed | Old platform export | New platform export, same product IDs | Sample of 40 products compared before launch |
| URL exclusions | /careers, /help, /account | /pages/careers, /help-centre, /account | Updated on launch day |
On launch day the account edits go in within two hours of the site going live, and the feed fetches cleanly. The click-path test fails on one pattern: old sale links ending in /sale-items redirect through a rule that rewrites the address and drops everything after the question mark, so clicks on the sale campaign's ads arrive without their identifier. The sale ads are pointed straight at the new sale page that afternoon, and the rule is fixed the next morning.
| Period | Purchases in Google Ads | Orders from paid search in the shop system |
|---|---|---|
| Week before launch | 212 | 220 |
| Launch week | 171 | 214 |
| Week after the fix | 208 | 216 |
The gap in launch week matches the sale campaign's clicks during the day and a half the rule was live. The paid media manager holds targets steady for the week, records the dates in the decision log and notes the launch in the monthly report.
Common mistakes
- Leaving the account out of the migration plan. The web team maps organic URLs and nobody updates the sitelinks, feed links or conversion triggers.
- Relying on redirects alone. Each redirect is a chance to drop the click identifier and slow the page; update destinations directly.
- Forgetting paused ads and assets. They are re-enabled later, pointing at addresses that no longer exist.
- Not testing the click identifier. Conversions still fire but cannot be credited, and the account looks as though results fell.
- Letting product IDs change without a reason. Supplemental feeds keyed on them stop applying.
- Changing budgets and targets in launch week. Several changes at once make every problem harder to trace.
- Reacting to a tracking gap with new targets. Hold steady, fix the tracking and protect bidding as the outage SOP describes.
- Judging the new site on the first days. Late conversions distort them; compare full weeks against the business's own records.
