Fix: Performance Max Final URL Expansion unrestricted

Final URL Expansion is ON by default in Performance Max campaigns post-2024. Without URL exclusion rules, Google can dynamically swap your declared final URL for any other crawlable page on your domain — including support articles, blog posts, careers pages, or expired campaign landing pages — based on the user's query. For regulated verticals, that can route paid clicks to pages that lack jurisdictional compliance copy, creating both spend waste and liability exposure.

Why this matters

Final URL Expansion was repositioned from an opt-in beta to a default-on feature for PMax during the 2024 rollout. Google's product framing is that expansion lets the system "send ad traffic to what it considers to be the most relevant URLs" on your domain — but the implicit contract is that the entire domain is auction-ready.[1][4] Most domains are not. Support articles, careers pages, legal disclosures, archived offers, and out-of-stock product pages all sit alongside the URLs you actually want PMax bidding on, and expansion treats them as eligible unless you exclude them.

Three concrete failure modes drive the severity:

1. Non-product spend leakage. When >15% of PMax cost lands on non-product pages (blog, support, legal, careers), you are paying auction prices to send paid clicks to pages that were never built to convert. The leakage compounds because PMax's bidding signal degrades — Smart Bidding learns from non-converting traffic and recalibrates downward.
2. Regulated-niche liability. In finance, healthcare, gambling, pharma, legal, insurance, CBD, crypto, and adult verticals, every served URL must carry jurisdiction-appropriate disclosures. Expansion routing a UK gambling click to a US-style landing page without GamCare references, or a pharma click to a US-only safety-info page, is a compliance event independent of ad spend.
3. Search-themes interplay (2025). Google now treats search themes as intent signals that direct queries into PMax, while expansion still chooses the landing page Google judges relevant.[2][3] Themes can pull in a query that expansion then routes to a thin support page — a configuration most operators do not realize they have until they audit landing-page reports.

The fix is not "turn expansion off." Used with proper exclusions and a curated page feed, expansion can lift conversions ~9% according to Google's own 2024 beta data.[3] The fix is "do not run it unmanaged."

How to verify

🔴 Detection note. This check must currently be performed manually in the Google Ads UI. Programmatic detection is currently blocked at the Google Ads API level — v23 removed the url_expansion_opt_out proto field, so the underlying campaign setting cannot be read via GAQL. When the SDK restores the field (drift-guarded by an internal test), a new rule story will be opened to automate this finding.

1. Open Campaigns → select the Performance Max campaign → Settings → expand Final URL expansion. Note whether the toggle is On (default) or Off.
2. If On, expand the URL exclusions panel directly below. Count the number of URL or URL-prefix exclusions. Zero exclusions on a domain with non-product subpaths = finding confirmed.
3. Open Insights → Landing pages for the campaign and switch the view to last 30 days. Sort by cost descending. Scan for non-product paths — /blog/*, /support/*, /careers/*, /legal/*, /help/*, /about/*, archived /campaigns/*, expired /promo/*. Sum cost-share for these paths.
4. Cross-check against your domain's page feed (if configured). A page feed plus expansion plus zero exclusions means Google can still pick URLs outside your feed — the feed only adds preferred candidates, it does not constrain expansion.
5. For regulated verticals: spot-check 5-10 served URLs from the Landing pages report. If any served URL lacks the jurisdiction-appropriate disclosure copy required for that vertical (GamCare for UK gambling, FDA black-box for US pharma, FCA risk disclaimers for UK finance, etc.), treat the finding as CRITICAL regardless of cost share.

Severity escalation matrix:

How to fix

Plan a 45-minute working session per PMax campaign — exclusion lists are campaign-scoped, not account-scoped, so you must repeat the work per campaign.

1. Inventory non-product paths. Pull the last 90 days of /sitemap.xml against your Landing pages report. List every URL prefix that should never receive paid traffic: /blog/, /support/, /help/, /careers/, /legal/, /privacy/, /terms/, /about/, /press/, archived /campaigns/, expired /promo/, internal /admin/, /login/. Add /404, /maintenance, and any soft-404 paths your site returns.
2. Add URL exclusions. Settings → Final URL expansion → Add URL exclusions. Paste one URL-prefix exclusion per line. Use the URL-prefix syntax (https://example.com/blog/) rather than wildcards — prefix matching covers all subpaths.
3. Configure a page feed (preferred). For eCom and content-heavy sites, configure a page feed via Tools → Business data → Page feeds, upload your curated product/landing URLs, then link the feed to each PMax asset group via Asset groups → Edit → Page feed. The feed does not replace exclusions, but it tilts expansion toward URLs you have vetted.
4. For regulated verticals, default to opt-out + multiple LPs. Toggle Final URL expansion to Off for regulated PMax. If the campaign currently has a single landing page, build 2-3 jurisdiction-appropriate landing pages and rotate them via asset group → final URL field. Single-LP opt-out is itself a missed exploration opportunity — pair opt-out with LP diversification.
5. Re-verify after 7-14 days. Re-pull Insights → Landing pages. Non-product cost-share should drop below 5%. If a previously excluded subpath still appears, your exclusion syntax was wrong (most common cause: trailing-slash mismatch or wildcard typo).

Edge cases

• eCom with a clean catalog and curated page feed. If your domain is exclusively product pages (no blog, no support, no legal-disclosure surfaces), expansion ON without exclusions is defensible — but you should still add /cart/, /checkout/, /account/, and /404 to the exclusion list. Optmyzr's 2025 data shows 58% of advertisers see flat or slightly better performance with no exclusions at all, but that average hides the regulated-vertical and content-heavy tails.[5]
• Lead-gen with a single conversion-optimized LP. Opt-out is acceptable, but it caps exploration — Whitead flags expansion OFF + single LP + leads goal as MEDIUM because building 2-3 LP variants and re-enabling expansion typically lifts qualified-lead volume without CPA degradation.
• Brand-only PMax campaigns. If the campaign is configured as a brand-only PMax (brand inclusions enabled, brand exclusions disabled on competitor PMax), expansion behavior matters less because the matched queries are brand-anchored. Still exclude /support/ and /careers/ — brand searches frequently route to careers pages.
• Feed-only PMax (no asset groups). Not applicable. Final URL expansion requires asset groups; feed-only PMax campaigns bypass this rule entirely.

Industry benchmarks

• Google's 2024 beta data: advertisers testing Final URL Expansion saw an average ~9% lift in conversions / conversion value at similar CPA / ROAS — conditional on having a page feed or exclusions configured.[3]
• Optmyzr's 2025 24,702-campaign study: 58% of advertisers saw flat or slightly better performance with no exclusions at all; the operative phrase is "precise, purposeful exclusions, not blanket blocks."[5]
• Search Engine Land 2024 playbook (Navah Hopkins): "URL expansion is almost always a bad idea unless you have your exclusion list ready."[4]
• Whitead internal threshold: >15% non-product cost-share is the action trigger for non-regulated verticals; any non-product cost-share is the trigger for regulated verticals.

Related rules + concepts

• Performance Max — the campaign type this finding tunes.
• Asset groups — expansion operates per asset group; exclusions are campaign-scoped above asset groups.
• Fix: PMax search themes missing or misconfigured — themes interact with expansion; pair this fix with theme review.
• PMax brand cannibalization — expansion can route brand queries to non-brand pages; brand exclusions are a separate setting.
• PMax low ROAS diagnostic — non-product spend leakage from expansion is a common root cause.

Sources

[1] Google Ads Help — About Final URL expansion in Performance Max. https://support.google.com/google-ads/answer/14337539 (accessed 2026-05-27)

[2] Adnabu — Final URL Expansion in PMax: What It Is and How It Works (2026). https://blog.adnabu.com/google-ads/pmax-final-url-expansion/ (last updated 2026-05-14)

[3] Search Engine Land — The Performance Max playbook: Best practices and emerging tactics for 2024 (Navah Hopkins, 2024-04-11). https://searchengineland.com/the-performance-max-playbook-best-practices-and-emerging-tactics-for-2024-439585

[4] Search Engine Land — The Performance Max playbook: Best practices and emerging tactics for 2024 (Navah Hopkins, 2024-04-11). https://searchengineland.com/the-performance-max-playbook-best-practices-and-emerging-tactics-for-2024-439585

[5] Optmyzr — Take action on the "PMax Campaigns with Final URL Expansion turned Off" audit. https://updates.optmyzr.com/en/take-action-on-the-pmax-campaigns-with-final-url-expansion-turned-off-audit (2023-09-26)