Final URL Expansion in PMax and AI Max 2026

You gave the campaign one final URL: your running shoes category. A week later the landing page report shows twenty-three addresses — product pages, a brand hub, three blog posts, the shipping policy and, for good measure, a promo lander that expired in March. Nobody added them. Google did. That is final URL expansion doing exactly what it was designed to do, and it is the least examined setting in Performance Max and AI Max.

The feature is not something you switch on by accident. It ships enabled in Performance Max, and after Search campaigns were upgraded into AI Max the same mechanism arrived there too. The difference between an account that profits from it and an account that quietly bleeds into it comes down to three controls: the page feed, URL contains rules and exact exclusions. Here is what expansion actually changes, where its blind spots are in 2026, how to audit it, and which guardrails to install instead of switching it off.

What final URL expansion changes

In a classic Search campaign the chain is rigid: keyword → ad → the final URL you typed. Expansion breaks that rigidity in two separate places.

Targeting. Google crawls your site and builds a keywordless demand model from the content itself. Your pages become the signal. The system works out that you sell trail shoes in wide fittings and starts matching queries that appear in none of your keyword lists and none of your search themes. On a deep, well-structured site that is a genuine source of cheap long tail. On a site where half the pages are administrative, it is a source of expensive noise.

Landing page selection. The system replaces the final URL you supplied with a page it considers more relevant to the query and intent, then generates a headline to match that page. In other words, the auction decides not only what you pay but what the user reads and where they land.

Final URL expansion is not extra targeting. It is handing Google the right to choose the landing page. While the site is clean, that choice is usually better than yours. The moment the site contains clutter, the automation will confidently route paid traffic into the clutter.

Where the setting lives

Performance Max: campaign → Settings → Asset optimization → Final URL expansion. URL exclusions and rules sit in the same panel.
AI Max for Search: campaign settings → AI Max block → a dedicated toggle next to automatically created assets. For what the upgrade changed overall, see our breakdown of AI Max in Google Ads Search campaigns.
Campaigns inherited from DSA: expansion is the direct descendant of dynamic search ads, and page feed logic carried over almost intact. The migration traps are covered in the DSA to AI Max migration playbook.

Three levers: page feed, rules, exclusions

The common mistake is treating expansion as an on/off switch. You actually have three layers of control, and for most advertisers the right configuration is “on and fenced”, not “off”.

1. Page feed — your priority whitelist

A page feed is a plain sheet: one column of URLs, one column of custom labels. You upload the addresses you genuinely want to send paid traffic to, and the system leans on them first.

A workable structure is one row per URL plus a label such as category, clearance, brand_x, high_margin. The labels then act as filters, so one campaign can work only on high-margin pages while another covers the rest of the catalogue. It is the same segmentation logic used on the product side with custom labels in Merchant Center, applied to content pages.

Belongs in a page feed:

category and subcategory pages with real, in-stock inventory;
hero product pages you are happy to promote individually;
service landers that end in a form or a buy button;
brand pages — but only brands you are authorised to advertise.

Never belongs in a page feed: blog posts, About Us, careers, privacy policy, internal search results, cart, account pages, and pagination URLs such as ?page=7.

2. URL contains rules — section-level control

Rules match on a substring in the address, so a single line can open or close an entire section of the site.

Goal	Rule	Effect
Catalogue only	URL contains `/shop/`	Cuts blog, help centre and admin pages in one move
Kill content traffic	Exclude URL contains `/blog/`	Stops clicks landing on articles that never convert
Retire an old promo	Exclude URL contains `/sale-`	Prevents traffic to expired landers
Separate a market	URL contains `/uk/`	Keeps a regional campaign on regional pages
Drop parameter junk	Exclude URL contains `?sort=`, `?utm_`	Removes duplicate address variants

Rules combine well: allow /shop/ and exclude /shop/archive/. That “broad allow plus narrow deny” pair beats listing a hundred exact URLs almost every time.

3. Exact URL exclusions — surgical work

Exact exclusions close individual pages: shipping information, contact, a discontinued product, a lander with legal restrictions. Two constraints trip people up constantly.

You cannot exclude the campaign’s own final URL. If the campaign points at example.com/shop/, that page keeps receiving traffic no matter what you add to the exclusion list. To remove it, change the campaign’s final URL instead.

Exclusions only exist while expansion is on. Turn expansion off and you lose the list of pages you spent months curating. “I’ll switch it off just in case” is therefore not a safe default.

When to run expansion and when to genuinely turn it off

Run it when

you are ecommerce with hundreds or thousands of SKUs and no chance of covering that demand by hand;
your URL structure is predictable and administrative pages are clearly separated;
product pages work as landing pages on their own — price, availability, an obvious call to action;
you are willing to review actual landing pages weekly and extend the exclusion list.

Fence it hard or disable it when

you run a single-page site or five service landers — there is nothing to expand into;
a large share of pages should never carry ads: stale promos, partner pages, duplicated regional content;
you operate in a regulated vertical where every landing page is legally reviewed;
your conversion depends on one specific form with a specific field set;
expanded URLs have produced clicks and zero conversions for two to three consecutive weeks at meaningful volume.

Cannibalisation deserves its own mention. Expansion happily takes traffic your Search campaigns were already winning, and the dashboard reads as “PMax is growing, Search is shrinking”. The mechanics and the fix are in campaign cannibalization between PMax, Search and Shopping.

How to find out where the traffic actually went

In-campaign URL report. Performance Max exposes landing pages under Insights; AI Max reports final URLs at campaign level. This is the list of addresses the system chose, with clicks and conversions attached.
Channel split. To separate search volume from everything else, use the channel breakdown — how to read it is covered in Performance Max channel reporting.
Your own analytics. The most honest source. Filter paid sessions by campaign and build a landing page report. If the top entries are pages you never promoted and never added to a feed, expansion is running wider than you assumed.
A weekly diff. Export the actual landing pages and compare against the whitelist. Every new address goes either into the page feed or into exclusions. There is no third state.

Landing page health checklist

Check	Benchmark (directional)	Why it matters
Crawlable by AdsBot	200 OK, not blocked in robots.txt	A page Google cannot read cannot be expanded into
In stock	No out-of-stock URLs in the page feed	A click on an unavailable product is pure waste
Load speed	LCP under 2.5s on mobile	Expansion tends to select heavy product pages
Policy compliance	No destination policy conflicts	One disapproval can take the campaign down
Clicks outside the whitelist	below 10–15%	Higher means your fences are too loose

The crawl check is not bureaucracy. If AdsBot cannot fetch a page it drops out of the model, and the system compensates with neighbouring sections. Diagnostics are in AdsBot and landing page crawlability, and the formal rules for the page itself are in Google Ads destination requirements.

Five failure patterns and what they cost

1. Enabling expansion on a site with an active blog

Articles answer long queries better than product pages — which is precisely why the automation picks them. Sessions rise, revenue does not. Fix: add “exclude URL contains /blog/” before the campaign accumulates history, not after.

2. Assuming the page feed is a boundary

A page feed sets priority, not limits. If you need a hard boundary, pair the feed with URL contains rules; otherwise the system is still free to step outside the list.

3. Trying to exclude the campaign’s final URL

It will never work. Narrow the campaign’s final URL instead.

4. Not revisiting rules after a site release

A replatform or redesign changes URL patterns, and every /shop/ rule silently stops matching. Audit rules the same day the release ships.

5. Switching expansion off instead of fencing it

Disabling removes the entire long tail and deletes your exclusion list with it. In most accounts “page feed + two or three rules + a dozen exact exclusions” outperforms a blanket off.

A special case: feed-driven campaigns

When a product feed is attached, the logic splits in two. The shopping side sends traffic to the URLs in the feed — expansion plays no part there, the address comes from the product link attribute. The non-shopping side (Search, YouTube, Display, Gmail) keeps using expansion and can send a user anywhere on the domain.

Three practical consequences:

turning expansion off in such a campaign does not “switch everything off” — shopping inventory continues unchanged;
conflicts between the feed link and an expanded landing page are possible: the same product may open from its own page in one session and from a category page in another, and conversion reporting starts to diverge;
URL exclusions apply to the expanded portion only; broken links inside the feed are fixed in the feed.

If your reports show both the expected product pages and unexpected sections, check the channel split first — things usually make sense once you can see how much of the volume is search at all.

What diagnosis looks like in practice

A common scenario: a campaign runs steadily for three months, then conversion rate drops by a third in September at unchanged click volume. Work it in this order.

Change history. Were settings, assets or the final URL edited? If nothing changed in the account, the cause is almost certainly on the site.
Landing page lists for two periods. Export addresses before and after the drop and diff them. New sections appearing in the top clicks is your answer.
Site releases. Ask the team whether URLs changed, new sections launched, or an archive was opened to crawling.
Stock status. If the system shifted onto out-of-stock product pages, conversion falls while CTR stays flat.
Rules. Confirm your URL contains rules still match the current address structure.

Nine times out of ten this turns up one of two things: a new section appeared on the site and expansion enthusiastically adopted it, or the URL structure changed and your old fences stopped matching anything.

Expansion and your brand terms

Expansion is drawn to brand queries: they convert, so the model learns they are “good” clicks fast. The campaign reports beautifully while re-buying traffic you would have received anyway.

The workable arrangement is to keep brand in a dedicated Search campaign and constrain it inside PMax and AI Max with brand lists — mechanics in brand lists and brand exclusions. If your site hosts other companies’ brand pages, close that section with a rule too: expansion will happily advertise a brand you have no authorisation to bid on.

Why the headline suddenly is not yours

When expansion swaps the landing page it writes a headline to match. Hence the recurring complaint: “the ad contains copy I never wrote.” You cannot edit those headlines directly, but you can narrow the corridor:

clean up title and h1 tags — generation leans on them first;
set text guidelines for AI assets so the automation keeps your tone and terminology, as described in text guidelines for AI-written ad copy;
watch asset reporting: if generated headlines consistently beat yours, rewrite yours rather than resent them — see Ad Strength and RSA asset reporting.

A one-evening setup

Export your sitemap and sort every URL into three buckets: promote, neutral, never.
Build the page feed from bucket one, with labels for margin, season and market.
Add one allow rule for the main catalogue path.
Add deny rules for blog, admin pages, promo archives, internal search and parameterised URLs.
Add exact exclusions for the specific pages in bucket three.
Check the campaign’s final URL — make it as narrow as the campaign allows, because you cannot exclude it later.
After 7 days export actual landing pages and file every new address into the feed or the exclusions.
After 30 days compare conversion rate inside and outside the whitelist. A gap of 2–3× means tighten the rules.

Running this across dozens of accounts hits a manual ceiling quickly; that is where a proper agency setup with a single MCC and clean access separation pays for itself — see Google Ads agency account rental. The rest of our paid traffic material sits in the PPC Rebels blog.

Where this fits with price and trust

Expansion decides where a click lands. Two other things decide whether the click happens and whether it pays. Price is the first: the most relevant page in the world cannot rescue a product priced above the market, and the gap is measurable — see price competitiveness and best sellers in Merchant Center. Trust in the SERP is the second: star ratings lift the click-through rate of the same ad without raising a bid, covered in seller ratings and product ratings in Google Ads.

FAQ

Can final URL expansion be turned off completely?

In Performance Max, yes, via the asset optimization panel; in feed-driven campaigns it only affects the non-feed portion. In AI Max it toggles separately from automatically created assets. Remember that switching it off also removes your URL exclusion list.

How is a page feed different from URL contains rules?

A page feed is a priority list telling the system where to send traffic first. Rules are boundaries that open or close whole sections by substring. Strict control needs both.

Why does an excluded page still get clicks?

Three usual causes: it is the campaign’s own final URL, the served address differs from your exclusion by a parameter or a trailing slash, or the traffic is coming from the product feed rather than from expansion.

How many exclusions can I add?

Google does not publish a practical limit, and most advertisers never approach one. The better guidance: if you are past a few dozen exact exclusions, the job belongs to a single section rule instead.

Does expansion affect Quality Score?

Keyword-level Quality Score does not apply to these campaign types in the familiar form, but landing page relevance still feeds the auction. An irrelevant page costs more per result than a relevant one.

What if expansion sends traffic to competitor brand pages?

Close the section with a rule and reinforce it with brand lists. This is not only an efficiency question — advertising on a brand you are not authorised to use invites a trademark complaint.

Do I need to change anything for seasonal sales?

Yes. Before the event, add the promo landers to the page feed and lift the exclusion on the sale path; afterwards, put the exclusion back. Otherwise the system will keep routing shoppers to a dead page for years.

How do I know expansion is adding demand rather than re-buying it?

Compare the account before and after, not campaign to campaign: total conversions and the brand share of traffic. Flat volume with a rising brand share means you are paying for traffic you already had.

Does expansion work across multiple domains?

No. It stays within the domain of the campaign’s final URL. Another domain needs its own campaign.

What should I do after a site redesign?

Same day: rebuild the page feed, re-check every URL contains rule against the new structure, and confirm redirects return a single 301 rather than a chain.

How often should I review landing pages?

Weekly for the first month after launch, then every two to three weeks, and always after a site release or a major promotion.

Is expansion usable for lead generation?

Yes, if you have more than five or six substantive landing pages that all end in a form. With a single form there is nothing to gain — restrict the feed to that one page or disable expansion.