A Performance Max page feed is an uploaded list of the specific URLs you will let the campaign promote, and when you pair it with Final URL Expansion set to "only send traffic to the URLs in your page feed," it becomes the single most effective guardrail against PMax spending your budget on docs, login, support, and blog pages. For B2B SaaS, this is not an optimisation nicety — it is the difference between Performance Max feeding your demo funnel and quietly burning spend on a changelog article that will never produce pipeline.
This is the setup most SaaS accounts skip because the default behaviour looks harmless until you read the landing-page report. Below is what the control does, why it matters more for SaaS than for retail, and the exact configuration path.
Why PMax sends SaaS spend to the wrong pages
Performance Max's Final URL Expansion feature lets the campaign pick its own landing page for a given auction by scanning your site and choosing whatever indexable URL it predicts will convert. On an e-commerce catalogue that is often fine — most pages are product pages that can transact. On a B2B SaaS site it is a structural mismatch, because the majority of your indexable URLs are documentation, help-center articles, blog posts, changelogs, and login screens. None of those are built to convert a cold paid click into a demo, and several of them (login, docs) actively signal "existing customer" rather than "prospect."
The result shows up in the landing-page report as spend scattered across dozens of low-intent URLs you never chose. Benchmark data from GrowthSpree (Page Feeds for PMax in B2B SaaS, 2026) attributes 15–30% of typical B2B SaaS Performance Max waste to exactly this: traffic routed to thin or off-funnel pages. Trying to fix it with bidding after the fact does not work, because the algorithm has already been told those pages are valid destinations. You have to remove them from the eligible set.
What a page feed actually controls
A page feed is a curated allow-list of URLs. When attached to a PMax campaign with Final URL Expansion restricted to it, you are telling Google: these are the only destinations this campaign may use. PMax keeps all of its automation — asset generation, channel mixing, audience signals, Smart Bidding — but its landing-page choice is constrained to the pages you know convert.
This matters because it changes the control surface from reactive to preventive. Placement exclusions and the tactics in our guide to PMax channel reporting and placement exclusions let you remove bad inventory after you see it. A page feed removes bad destinations before a single click is spent. For a SaaS site with hundreds of indexable but non-commercial URLs, prevention is the only approach that scales.
The setup: step by step
The whole configuration lives in two places — the Business data section where the feed is stored, and the campaign settings where Final URL Expansion is toggled.
- Build the URL list. Export your highest-intent pages only: demo request, free-trial signup, pricing, and the product or solution pages that map to your top campaigns. For most B2B SaaS accounts this is 10–40 URLs, not hundreds. If a page would not be a good manual Search landing page, it does not belong in the feed.
- Upload it as a page feed. Go to Tools and Settings → Business data → Page feeds and create a new page feed asset list. Each row is a final URL plus an optional custom label you can use to group pages (for example
demo,pricing,product). - Attach the feed to the PMax campaign. In the campaign's settings, associate the page feed under the campaign's URL options / Final URL Expansion controls.
- Restrict Final URL Expansion. Set it to only send traffic to the URLs in your page feed. This is the toggle that turns the feed from a suggestion into a hard boundary. Left at the default, PMax treats the feed as a hint and still expands elsewhere.
- Verify in the landing-page report. After a week, pull the landing-page / final-URL report and confirm spend is concentrated on feed URLs. Any off-feed URL appearing means the restriction is not applied correctly.
Using labels to align feeds with campaign structure
Custom labels on page-feed rows let you point different campaigns or asset groups at different subsets of the same feed. If you run separate PMax campaigns for distinct product lines — a pattern we cover in Performance Max for SaaS — label each URL by product and attach only the relevant label to each campaign. This keeps a single maintained feed as the source of truth while still enforcing that your security-product campaign cannot land a click on your analytics-product pricing page.
Labels also make the feed auditable. When a new high-intent page ships, you add one row with the right label rather than rebuilding campaign-level URL rules, and the change propagates to every campaign pointed at that label.
Page feeds vs. negative keywords: both, not either
Page feeds and campaign-level negative keywords are complementary controls that B2B SaaS accounts frequently confuse. Negative keywords — now supported up to 10,000 per PMax campaign — shape the demand PMax matches to, keeping it off irrelevant or competitor-adjacent search terms. A page feed shapes the destination that matched traffic lands on. You can have perfect negatives and still waste budget if clicks land on a docs page, and you can have a tight page feed and still waste budget if PMax is matching junk queries.
The two together form the inbound and outbound boundaries of the campaign. If you are still deciding whether Performance Max belongs in your account at all, start with should B2B SaaS run Performance Max before investing in either control.
When a page feed is not enough
A page feed fixes where clicks land; it does not fix what PMax optimises toward. If your conversion tracking counts low-intent events — newsletter signups, ungated content downloads — restricting the landing page still leaves the campaign chasing the wrong outcome. Pair the page feed with clean conversion goals, as covered in optimising for SQLs, not leads, so the automation is both landing and bidding against pipeline-grade signals.
Equally, a page feed cannot rescue a campaign that is structurally too broad. If one PMax campaign is trying to cover unrelated products or wildly different ACVs, no destination control will clean up the blended reporting — you need to split it first.
Locking down your PMax spend
For most B2B SaaS accounts, adding a curated page feed and restricting Final URL Expansion is a same-day change that removes a measurable chunk of wasted spend — often the 15–30% leaking onto off-funnel pages. It is one of the first things we check when a B2B SaaS Google Ads audit turns up PMax spend scattered across documentation and blog URLs, and one of the fastest fixes we apply inside ongoing management. If you want to self-diagnose first, the free 10-point Google Ads audit flags whether your Performance Max destinations and conversion goals are pointed at pipeline or at noise.