How to Set Up Google Ads PMax Final URL Expansion

To set up Google Ads PMax Final URL expansion safely, first decide which pages are suitable for paid traffic, test their conversion paths, then enable the campaign control and add precise URL rules or exclusions. Finish by verifying the saved setting, checking selected destinations, and recording a rollback trigger. The setup is not complete simply because the feature is switched on.

Google’s About Final URL expansion documentation is the authority for current behavior and interface labels. Its URL exclusion guide explains the current exclusion flow, while Final URL expansion and asset optimization covers URL controls and page feeds. For the decision framework behind the setup, see PMax Final URL expansion best practices.

Decide whether the campaign should expand

Expansion can replace the supplied asset-group URL with a more relevant page from the site and can use that page’s content in related ad optimization. That can be helpful for a clean catalog or a service site with distinct, current pages. It is risky when the domain contains obsolete offers, internal pages, unsupported locations, or content that has no measurable next step.

Before opening Google Ads, answer:

What business outcome is this campaign optimizing for?
Which page families can deliver that outcome today?
Which page families must never receive acquisition traffic?
Can the team review the selected pages and fix a problem quickly?
What spend, quality, or policy signal would cause a pause or narrowing?

If the answer is “only these few URLs,” prepare a controlled page set and exclusions before enabling broader discovery. If the site is a structured, current catalog, expansion may provide useful coverage, but it still needs page governance and measurement.

Audit the pages before changing settings

Create a short page inventory for the domain connected to the campaign. Mark each family as approved, needs review, or protected. Include more than the homepage and the URL currently entered in the asset group:

products, categories, services, locations, languages, and pricing;
blog, guides, comparisons, support, and other informational content;
account, login, checkout, cart, internal search, and redirect paths;
careers, investor, legal, privacy, contact-only, and obsolete pages;
out-of-stock products, expired promotions, duplicate pages, and unsupported locations.

Open representative pages on mobile and desktop. Confirm the offer, headline, qualification, price or availability, service area, primary action, consent flow, and conversion event. Test forms, calls, booking, checkout, and analytics. A page that loads successfully can still be an unsuitable destination if the business cannot fulfill what it promises there.

Prepare measurement and page controls

Record the current campaign state before editing: asset-group final URL, primary conversion actions, bidding strategy, budget, tracking template or suffix, page feed, existing exclusions, and text or asset customization settings. This gives the team a before state and prevents a page-selection change from being confused with an unrelated optimization.

Test the conversion path

Complete a real test from an approved page. Verify that the intended action records once, values and currency are correct, consent behavior is respected, and the result can be traced to the CRM, order system, call record, or booking queue. Test more than the initial final URL if expansion will expose different product, service, or location families.

Define protected URL families

List paths that should not receive ads, such as careers, login, support-only, internal search, obsolete offers, or products the business cannot supply. Use stable path patterns where possible, but test every rule against an allowed page, an excluded page, and a near-match. Do not block a whole folder because one page in it is weak without checking what else the rule would remove.

Prepare a page feed when useful

A page feed can supply a curated set of important URLs and custom labels for page controls. Keep it current and document whether it is intended to prioritize key pages, restrict a campaign, or support exclusions. Confirm the current behavior before promising that pages outside the feed cannot serve; the official documentation explains how page feeds and custom labels work in the current configuration.

Open the Performance Max settings

Google’s navigation and labels can change, so use the current help page beside the account rather than following an old screenshot. The current URL-exclusion flow starts in Campaigns: find the Performance Max campaign, open its Settings from the gear control, and expand Asset optimization. The Google Ads URL exclusion instructions describe the current path and the controls available after expansion is on.

Before saving, confirm the campaign name and read the surrounding settings. A common setup error is editing a similarly named campaign or changing a budget, target, or conversion action while trying to edit a URL control. Take a record of the current state first.

Enable Final URL expansion

In the campaign’s current Asset optimization or URL settings, locate the Final URL expansion control and select the option that allows the campaign to use more relevant pages from the site. The exact label or placement may vary with the Google Ads experience. If the account presents text customization or automatically created asset choices nearby, read those choices separately: Final URL expansion controls page selection, while text customization affects how page content can contribute to ad messaging.

Save only the intended change. Do not combine the first URL-expansion change with a new bid target, a large budget increase, a complete asset rewrite, or a new conversion action. If the interface does not show the control, confirm the campaign type, permissions, account configuration, and current Google Ads help before inventing a setting name.

Add URL exclusions and rules

After expansion is enabled, return to Asset optimization and choose Add URL exclusions when that option is available. The current Google Ads flow supports individual URLs, custom labels from a page feed, and rules. Use the narrowest control that solves the problem:

Add an exact URL for one high-consequence page, such as a careers or privacy page that should not receive acquisition traffic.
Use a custom label when the page feed already groups approved or protected destinations intentionally.
Use a URL rule for a stable path family, such as a support or internal-search section, after testing the pattern against allowed and excluded near-matches.
Apply the exclusions, save the campaign, and record the rules and owner.

The official URL exclusion documentation notes an important boundary: excluding the campaign’s supplied Final URL from URL expansion does not necessarily prevent that supplied URL from serving. If the homepage must not serve, choose a more specific campaign Final URL and exclude the homepage where appropriate. Merchant Center campaigns can have additional inventory-specific behavior, so test the actual destination surface.

Do not add a broad rule merely to stop one weak page. A pattern can remove valuable product or service pages and create a low-delivery problem that looks like a bidding failure.

Attach and label a page feed if needed

If the campaign uses a page feed, upload or maintain the curated URLs in the feed and use custom labels to distinguish page groups. In the current Google Ads guidance, a page feed can help the system index and prioritize key pages; it can also support a more controlled page strategy when combined with the relevant campaign and asset-group controls.

Check three test cases before relying on the feed:

a page that is included and correctly labeled;
a page in the feed that has an exclusion label or rule;
a relevant page outside the feed.

Record what the campaign should do in each case and verify the behavior in the current account. Do not promise that a page feed is a strict allowlist unless the current configuration confirms it. Remove expired offers and update labels when the site changes.

Test the saved setup

Reopen the campaign after saving. Confirm that Final URL expansion is in the intended state, the exclusions are present, the page feed or labels are current, and the asset-group URL and conversion settings were not changed. Then test the selected page families directly.

For each representative destination, check:

HTTPS, status code, redirect behavior, and mobile rendering;
product, service, location, language, offer, price, and availability;
form, call, booking, checkout, and consent behavior;
analytics parameters, tracking templates, and one-time conversion recording;
ad claims or page-derived text against the actual page content;
routing to the correct sales, support, fulfillment, or appointment team.

Use a test conversion or controlled visit where the business process permits it. Do not conclude that the setup is healthy from a campaign-level conversion rate; one low-quality page family can be hidden inside the total.

Launch with a review plan

Set the review date before launch and define what would cause a correction. In the first review, check eligibility, selected final URLs, spend, obvious page errors, policy state, and whether conversions arrive plausibly. For later review, compare page families by cost, conversions, value, qualified outcomes, and conversion lag.

Intervene when traffic reaches a protected path, a page breaks, a location is unsupported, a price or claim is stale, tracking disappears, or business quality falls beyond the agreed guardrail. Make the smallest useful response: repair a page, update a feed, narrow a rule, add an exact exclusion, or temporarily turn off expansion while investigating.

Keep a change record with the setting, exclusions, feed revision, page release, budget, target, and conversion state. This makes the next diagnosis possible when page selection and other campaign changes overlap.

Setup checklist

[ ] Page families are classified as approved, review, or protected.
[ ] Representative pages and conversion paths pass mobile and desktop tests.
[ ] Current campaign settings and measurement are recorded.
[ ] Final URL expansion is enabled in the intended campaign.
[ ] Exact exclusions, rules, or custom labels are narrow and tested.
[ ] Page feed behavior is understood rather than assumed.
[ ] Saved settings are reopened and verified.
[ ] Selected destinations and page-derived messaging are reviewed.
[ ] Review date, quality guardrails, and rollback triggers are documented.

For the more detailed settings decision framework, see best Google Ads PMax Final URL expansion settings. If the first review reveals wrong destinations or poor delivery, use how to fix Google Ads Performance Max and review the page controls before changing targets. The adz.so overview is an educational starting point; confirm currently available workflows before promising that the product changes Google Ads settings for an account.