Landing page change and conversion rate: how to measure the impact and prove the cause
A landing page change can raise or lower conversion rate through its content, form, speed, URL or tracking. To measure it, compare equal full weeks by traffic source in GA4 or split traffic with a Google Ads ad variation, and line up every other change from the same days so you can prove the page moved the rate.
How does a landing page change affect conversion rate?
A landing page change affects conversion rate when it changes what visitors see, how fast the page loads, how much effort the form asks for, or whether the conversion is still measured. The last one is the most common surprise: a release that moves the thank-you page or drops a tag looks like a conversion rate drop even when visitors behaved exactly as before.
Count all of these as landing page changes, because each one can move the rate on its own:
- Content: headline, offer, price display, proof, call to action.
- Form and flow: number of fields, required fields, steps, booking widgets, checkout.
- Layout and speed: a new template, heavier images, extra scripts, a cookie banner, mobile rendering.
- URL and routing: a new URL, redirects, final URLs in your ads pointing to a different page, URL parameters.
- Measurement: the thank-you page URL, Google Tag Manager triggers, key event definitions, consent settings.
Measuring a landing page change means answering one question with evidence: did the new page change how many visitors convert, or did something else change in the same days? The sections below show how to answer it with GA4, Google Ads and a plain record of what changed and when.
How do I measure a landing page change with a before/after comparison?
Compare the same page, the same traffic sources and the same number of full weeks before and after the change, and read key events per session rather than totals. A before/after comparison is the fastest method, but it only holds when nothing else changed in the window.
- Write down the date and time the new page went live, and the date your ads started pointing to it.
- In GA4, open Reports > Engagement > Landing page. The Landing page dimension is the path and query string of the first page view in a session, so filter the report to the page you changed.
- Add Session source / medium as a secondary dimension and read each source on its own. A shift from paid search to social traffic can move the blended rate with no change to the page at all.
- Use equal windows of full weeks, for example 14 days before and 14 days after, so weekdays are balanced.
- Divide key events by sessions for each window and each source, and compare like with like.
| Check | Why it matters |
|---|---|
| Same source/medium mix | Channels convert at different rates |
| Same key event definition | A renamed or re-triggered event breaks the comparison |
| Equal full weeks | Weekday patterns differ |
| No other big changes in the window | Bids, budgets or offers can move the rate on their own |
If the URL changed, compare the old path before the switch with the new path after it, and confirm both are tracked the same way. For a broader method, see how to measure the impact of marketing changes.
Read also: Site speed and a conversion rate drop: how to find the change that slowed you down · Marketing change log: what it is and how to keep one
How do I test a new landing page in Google Ads instead of comparing weeks?
Run the old and the new page at the same time on split traffic. In Google Ads, ad variations can change the final URLs of responsive search ads, and custom experiments test a modified copy of a campaign against the original.
Ad variations with new final URLs
Go to Campaigns > Experiments > Ad variations, choose the campaign, set the ad type to Responsive search ads and pick Update URLs as the variation type to send the variation to the new page. Under Experiment split, enter the share of the campaign budget the variation gets, set the start and end dates and select Create variation. Google assigns users with cookies, so one person tends to see only one version. Performance data covers only the modified ads.
Custom experiments
For larger changes, a custom experiment runs a treatment campaign next to the original. Search campaigns can use a cookie-based or a search-based split. Google warns that changing the original campaign or the experiment during the run makes results harder to read, so freeze other edits until it ends.
| Method | Good for | Main risk |
|---|---|---|
| Before/after in GA4 | A quick read on any traffic source | Other changes in the same weeks |
| Ad variation (Update URLs) | Old page vs new page for responsive search ads | Covers only the modified ads |
| Custom experiment | Page and campaign changes together | Edits during the run blur the result |
| On-site A/B testing tool | Every channel, page-level variants | Needs enough traffic and a clean setup |
Why can conversion rate move after a landing page change when the page isn't the cause?
Because the same days often hold other changes: a broken tag, a redirect, a new traffic mix or edits in the ad account. Check these before you judge the page itself.
- Tracking moved with the page: a new thank-you URL or form plugin can stop the trigger your key event depends on. Compare form submissions in your CRM or inbox with key events in GA4 and conversions in Google Ads.
- The URL chain changed: Google Ads has a landing page test (the Test button next to the URL fields) that flags messages such as "Landing page has URL mismatch", "Final URL mismatch" and redirects in the tracking chain.
- Mobile experience: in Google Ads, Insights & reports > Landing pages shows the Mobile-friendly click rate for each page. A value below 100% means the page did not always pass Google's mobile-friendly test.
- Traffic mix: new campaigns, broader match types or a new audience send different visitors to the same page.
- Account edits: bids, budgets and ad text changed in the same week. Google Ads Change history shows the past 2 years; the Google Ads change history guide explains how to read it.
If the conversion rate also fell on pages nobody touched, the cause probably sits outside the page. The article on why a conversion rate drops covers those wider checks.
How do I prove which change caused the conversion rate shift?
Put every change from the 7 to 14 days before the shift on one timeline, rule out tracking first, then test one hypothesis at a time. The cause is usually the change that sits just before the move and explains it on the affected pages and sources only.
- Rule out tracking
- Check the traffic mix
- Line up the changes
- Test one hypothesis
Example: on Monday a B2B client asks why demo requests fell about 30% from Friday. The landing page had just been redesigned, so the easy answer was that the new page converts worse. Lining up the changes from the days before showed three: the new page went live on Wednesday, the final URLs moved to it on Thursday, and the same release renamed the thank-you page that the key event used as its trigger. Form submissions in the CRM were flat. Most of the drop was tracking; once the trigger was fixed, the remaining gap was small enough to settle with an ad variation.
- WedWebsiteNew page /demo-v2 live
- ThuGoogle AdsFinal URLs moved to /demo-v2
- ThuTrackingThank-you URL renamed
- FriDemo requests drop 30%
Demo requests per dayFri: −30%
With every change on one timeline, the thank-you URL rename shows up next to the final URL switch, a day before the drop, instead of hiding in a developer ticket. In Changeline, Google Ads edits are imported through a read-only connection and the team logs site and tracking releases next to them, so the question "what changed before Friday?" has one place to look.
How do I log landing page changes so the next comparison is easy?
Record each landing page change on the day it ships, with the URL, what changed, who changed it and why. A two-minute entry now saves hours of reconstruction when the next client asks why the rate moved.
Checklist
- Date and time the change went live
- Page URL, old and new
- What changed: copy, form, layout, speed or tracking
- Who made it and the hypothesis behind it
- Ads and final URLs that point to the page
- Result after two full weeks
Keep landing page entries in the same log as ad, tracking and CRM changes, so they are read together. The marketing change log template gives you the columns, and the website change log article covers site releases in more detail. When you present the result, the guide to explaining a conversion drop to a client shows how to lay out the cause and the evidence.
Put every site release next to your traffic drop
Changeline puts your team’s changes, imported Google Ads changes and site, tracking and CRM edits on one timeline per client.
Free plan: 1 project, 2 editors, 15 days of history. No card.
FAQ
How long should I wait before judging a new landing page?
Wait for at least two full weeks of traffic after the change, longer for low-volume pages, so weekday patterns even out. If the switch also involved new ads or bids, give those time to settle as well. With small volumes, a split test such as a Google Ads ad variation gives a clearer answer than a before/after comparison.
Can I test two landing pages in Google Ads without building a new campaign?
Yes. Ad variations let you pick Update URLs for responsive search ads and send part of the traffic to a different final URL. You set the share of budget in Experiment split, users are assigned with cookies, and the performance data covers only the ads you modified.
Why did conversions drop after I moved my landing page to a new URL?
Check measurement first. A new URL often comes with a new thank-you page or form, which can stop the trigger your key event relies on. Then check redirects and the Google Ads landing page test for URL mismatch messages, and compare CRM form submissions with reported conversions.
Which GA4 report shows conversions by landing page?
Reports > Engagement > Landing page lists sessions, key events and revenue for the first page of each session. Filter it to your page, add Session source / medium as a secondary dimension and divide key events by sessions to get a conversion rate per source.
Should I change the landing page and the ads at the same time?
Not if you want to measure either one. Changing both in the same days makes it impossible to say which moved the rate. Ship one change, wait for a clean read, then the next, and log each with its date and reason.