Ad Settings Verdict / Google Ads

Google Ads Final URL expansion: on or off?

The community's evidence-backed call on Final URL expansion, the reasoning behind it, and, because it is not the same for everyone, when the call flips.

The verdict

Disable

Disable 72%Enable 28%
StrongEvidence
MediumConfidence
19Sources weighed

Score reflects weighted evidence consensus across web and practitioner sources, not a statistical calculation.

Read this first

Your account can land differently.

This is the community's default call, weighed across the general evidence. Whether Final URL expansion helps or hurts still varies from account to account: your business type, budget, vertical, goals, and how your conversion tracking is set up all move the answer. Plenty of accounts get the opposite result from the default and are right to.

Treat the verdict as a strong starting position, not a universal rule. The when to disable and when to enable split further down is exactly where that variation lives: find your situation there, then confirm it on your own account before you commit. The most reliable answer is always the one your own test gives you.

What it does

Final URL expansion is a campaign-level setting available in Performance Max and AI Max for Search campaigns. When enabled, Google's AI can override your specified final URL and redirect traffic to any page on your domain it deems more relevant to the user's query. This means ads may land on product pages, category pages, the homepage, or other URLs never explicitly added to your campaign, based on Google's interpretation of intent match.

The recommendation

Disable Final URL expansion unless you are running a large ecommerce PMax campaign with a fully indexed, conversion-ready site and have the time to monitor and exclude pages actively. For most accounts, especially those built around specific conversion funnels, the setting introduces uncontrolled landing page variation that undermines performance rather than improving it.

If you want to test whether expansion helps, the right approach is to enable it with a strict URL exclusion list in place first, blocking the homepage and any non-conversion pages before the campaign goes live. Monitor the URL report (available in the asset performance breakdown) weekly for the first three to four weeks, looking for declines in conversion rate or increases in bounce-related signals at the landing page level.

For accounts where landing pages have been deliberately built and tested for conversion, disabling this setting and maintaining full URL control is the lower-risk default. Google's recommendation to enable it reflects its broader interest in traffic volume, not necessarily your specific conversion architecture.

Weighing it up

Reasons to enable

  • Google's AI can surface deeper catalog pages that may convert better for specific long-tail queries you haven't explicitly mapped to URLs.
  • Reduces the manual overhead of maintaining exhaustive asset group URL lists, useful in large ecommerce accounts with hundreds of SKUs.

Reasons to disable

  • Google frequently sends traffic to the homepage or low-intent pages, diluting conversion rates and wasting budget on poor landing page matches.
  • You lose control over message-to-landing-page continuity, which is critical for accounts with CRO-optimised pages or compliance-sensitive copy.
  • Any page on your domain, including outdated, untested, or irrelevant pages, becomes eligible for ad traffic without your explicit approval.
  • Diagnosing performance issues becomes harder because the landing page variable is no longer controlled, making it difficult to isolate what is driving or hurting conversions.

When the call flips

This is where your account fits in.

Disable when

  • Lead generation accounts where specific landing pages have been CRO-tested and conversion lift is tied to message match with the ad creative.
  • Accounts where compliance or legal requires exact control over which page is shown alongside which ad copy.
  • Any campaign where Google has been observed routing traffic to the homepage or irrelevant pages, a common and well-documented failure mode.
  • Smaller accounts without sufficient conversion data to guide the AI toward meaningful landing page selections, where random page selection is more likely.

Consider enabling when

  • Large ecommerce accounts with a deep, well-structured product catalog where Google can genuinely match queries to relevant category or product pages.
  • Campaigns where your domain architecture is clean, every indexed page is conversion-ready, and you have enough conversion volume to let the AI optimise landing page selection meaningfully.
  • You have excluded low-quality or irrelevant pages (homepage, blog, careers) via the URL exclusion list and have verified Google's selections in the asset report.

What this looks like in an account

  • PMax asset group targets /running-shoes but expansion redirects a 'trail shoe' query to /hiking-boots instead of your intended landing page.
  • A lead gen campaign with a tailored conversion-optimised landing page gets bypassed; Google sends traffic to a generic /services page it deems relevant.
  • A deleted or redirected page still receives ad traffic via URL expansion because Google cached it as relevant before the change.

How we reached this

This verdict is produced by the Shared Learnings engine, which weighs live web evidence and practitioner discussion against real A/B tests from the community, scored by source authority and recency. This run drew on 19 sources. As the community logs first-party tests on this setting, the verdict updates to reflect what those tests actually found. More on the methodology.

More settings verdicts

Start a 7-day free trial

Check this on your own account.

Run a verdict on any setting across Google, Meta, TikTok, Microsoft, Snapchat, and Pinterest, filtered to your situation, then test it on your account to see what your data says.

Start 7-day free trial Card required · Full plan access for 7 days · Cancel any time