What did Google Ads Editor 2.11 add for Performance Max?

Google Ads Editor 2.11 added two Performance Max controls that previously only lived in the web UI: a search term report showing which queries triggered your PMax ads, and the ability to attach negative keyword lists directly to Performance Max campaigns offline. Together they let you review PMax search terms and stage negatives across many campaigns in one desktop pass, then post the changes in a single upload. Search Engine Land described the release as adding campaign-level negatives and smarter automation controls to the desktop tool. Version 2.11 shipped in late 2025; if your Editor predates it, download the current build before you try this workflow.

Why use Editor instead of the web UI to review PMax search terms?

The web UI shows the Performance Max search terms report one campaign at a time, and adding negatives there is a per-campaign, click-heavy job. Editor lets you pull the report for many campaigns at once, sort and filter the whole set in one grid, and stage negative keyword lists against multiple campaigns before a single upload. For an account with several PMax campaigns, that collapses an afternoon of clicking into one review-and-post pass. It also gives you an offline working copy you can filter aggressively without waiting on the UI to reload, which is the real speed win when you are scanning thousands of query rows.

Does the PMax search terms report show every query?

No. The Performance Max search terms report shows the queries that met Google's volume threshold, the same way the standard Search report does, so a share of low-volume terms stays hidden regardless of whether you read it in Editor or the UI. Editor changes how efficiently you can work the terms you can see; it does not unlock terms Google withholds. It also only covers the Search and Shopping surfaces where a query exists — PMax spend on Display, Discover, YouTube, and Gmail has no search term to report, so the report is a view into part of PMax traffic, not all of it.

Can I add negative keyword lists to Performance Max in Editor 2.11?

Yes. Editor 2.11 lets you attach existing shared negative keyword lists to Performance Max campaigns offline, so you can apply the same list to several PMax campaigns and post them together. This is the bulk counterpart to the in-UI control. Note the distinction between a shared list and campaign-level negatives: a shared list is one object applied to many campaigns and maintained once, which is what you want for account-wide junk. Build the list from the terms the search term report surfaces, attach it across your PMax campaigns in Editor, and maintain it in one place from then on.

How often should I mine PMax search terms this way?

Run the Editor mining pass on the same cadence you use for the rest of your search terms hygiene — weekly for high-spend accounts, at minimum monthly for everything else. Performance Max keeps discovering new queries as its matching widens, so a single cleanup decays; the value is in the repeated pass, not the one-time export. Because Editor makes the pass fast, there is little excuse to stretch the interval. Pull the report, sort by cost against zero or thin conversions, stage the new negatives onto your shared list, and post. The whole loop is minutes once the list structure exists.

Mine Performance Max Search Terms in Ads Editor 2.11

For most of Performance Max's life the search terms were the part you could not get at. The campaign type spent your money across Search, Shopping, Display, YouTube, and more, and the one report that would tell you which queries it bought was either absent or so thin it was closer to a gesture than a tool. That has been changing in stages, and the latest step is a practical one: Google Ads Editor 2.11 brings the Performance Max search term report — and the ability to attach negative keyword lists to PMax campaigns — into the desktop tool. PPC Land noted the release adds Performance Max search term reports to Editor, and Search Engine Land framed the same build as campaign-level negatives and smarter automation for the desktop app.

The reason this matters is not that the data is new — the in-UI Performance Max search terms report already showed you the queries. It is that Editor changes the economics of acting on them. Reviewing PMax terms in the web UI is a one-campaign-at-a-time job, and applying negatives there is a slow, click-heavy loop. Editor lets you pull the report across every PMax campaign at once, work the whole set in a single grid, stage negatives against many campaigns, and post it all in one upload. That is the difference between a workflow you run weekly and one you keep meaning to. This post is about that workflow: how to mine the PMax search terms in Editor and turn them into negatives at scale.

What Editor 2.11 actually changed

Two capabilities landed together, and they are complementary. The first is the Performance Max search term report inside Editor — the list of queries that triggered your PMax ads, pulled into the desktop grid instead of the browser. The second is the ability to attach negative keyword lists directly to Performance Max campaigns offline. On their own each is useful; together they close the loop, because you can find the wasteful query and stage the block against it without leaving the tool. Before this, the report and the negative control lived in separate parts of the web UI, and neither scaled across campaigns without a lot of clicking.

Two caveats keep this honest. First, the report obeys the same volume threshold as the standard Search terms report, so a slice of low-volume queries stays hidden no matter which tool you open it in — Editor makes you faster on the terms you can see, it does not reveal the ones Google withholds, which is the same visibility ceiling covered in the visibility-ratio audit. Second, version 2.11 shipped in late 2025; if your Editor install is older, none of this appears until you update. Download the current build first, then re-download your account so the PMax campaigns arrive with their search term data attached.

Pulling the report across every PMax campaign

Start by downloading a fresh copy of the account in Editor, then narrow to Performance Max so you are not scrolling past Search and Shopping campaigns you are not working on. The point of doing this in Editor rather than the UI is that the search terms from all of your PMax campaigns land in one grid you can sort and filter as a single dataset, instead of paging through each campaign's report in a browser tab. For an account with one PMax campaign the advantage is marginal; for an account with five or ten it is the whole game, because the wasteful patterns you are hunting usually repeat across campaigns and are far easier to spot when the terms sit side by side.

Once the terms are in the grid, sort by cost descending and read from the top. High-cost queries with zero or thin conversions are the fastest waste to confirm, and they are where the money actually leaks, so working cost-down means every minute you spend is aimed at the biggest holes first. Keep in mind the report only covers the Search and Shopping surfaces where a query exists — a Performance Max campaign also spends on Display, Discover, YouTube, and Gmail, and that spend has no search term to show. So treat this report as a clear window into part of PMax traffic, not a full accounting of where the budget went. It is the part you can negate against, which is what makes it worth the pass.

Reading the grid for the waste worth blocking

The same three patterns that plague broad-match Search show up in the PMax report, and the grid makes them easy to see when the campaigns are pooled. The first is branded cannibalization: your own brand terms, or a partner's, showing up as cheap converters that PMax is claiming credit for rather than driving incremental sales. The second is research-intent traffic — "how to," "vs," "reviews," "free" — that clicks and rarely buys. The third is adjacent-product or wrong-audience queries that share a word with your offer but not the intent. Each is a different decision, and the grid view helps because a pattern spread thinly across five campaigns is invisible one report at a time but obvious when the terms are stacked together.

This is where an n-gram pass over the export pays off. Rather than judging each query in isolation, break the terms into their component words and phrases and look at which fragments carry cost without conversions across the whole set. A recurring token — a competitor name, a "jobs" or "salary" modifier, a category you do not sell — is a candidate for a single grouped negative that catches every current and future variant, which is far more durable than negating the specific strings you happened to see this week. The difference between one-off blocks and grouped patterns is covered in the pattern-grouping guide; the Editor grid is simply the fastest place to spot which patterns have grown big enough to be worth a grouped block.

Staging negatives in bulk, then posting once

Here is the payoff of doing both halves in Editor: once you have identified the wasteful terms and patterns, you attach a negative keyword list to your Performance Max campaigns without ever opening the browser. Build or extend a shared negative list, add the terms and grouped patterns you found, attach the list to every relevant PMax campaign, and post the whole thing in one upload. What was a per-campaign click marathon in the UI becomes a single staged change set you review before it goes live. That review step — seeing every pending negative and every campaign it will hit in one place before you commit — is itself worth the switch, because it is where you catch the block that is too broad before it costs you conversions.

Prefer a shared list over one-off campaign negatives for anything that is not campaign-specific. A shared list is one object you attach to many campaigns and maintain in a single place, so account-wide junk gets blocked everywhere and updated once — the structure argument laid out in the negative list structure guide. Reserve campaign-level negatives for genuinely campaign-specific exclusions. Editor 2.11 supports attaching those shared lists to PMax offline, which is exactly what lets you apply one well-maintained list across your whole PMax footprint in a single pass rather than rebuilding the same blocks campaign by campaign.

Brand terms, exclusions, and what not to negate

Brand traffic in Performance Max needs a decision, not a reflex negative. If PMax is scooping up your own brand searches, a negative keyword may not be the right instrument — Performance Max has a separate brand exclusions control, and the two behave differently, which is the whole subject of the brand exclusions versus negative keywords comparison. Decide whether you want brand queries handled by a dedicated brand campaign and excluded from PMax, or left in and accepted, before you start blocking brand strings, because a blunt brand negative can suppress traffic you meant to keep and hand it to no one.

The general guardrail against over-blocking applies here as much as anywhere. A query that looks adjacent but occasionally converts is not automatically waste, and the fast bulk workflow Editor enables makes it easier to negate in haste across many campaigns at once — which means a mistake propagates just as fast. Before you post a grouped negative, sanity-check that the pattern is not catching a term that pays off, the same discipline as avoiding over-negation. Speed is the benefit of this workflow and also its trap: review the staged change set with the same skepticism you would apply to a single manual negative, because you are about to apply it many times over.

Folding it into a repeatable routine

The Editor workflow is worth setting up as a fixed routine rather than a one-time cleanup, because Performance Max keeps finding new queries as its matching widens and a single pass decays within weeks. Run it weekly for high-spend accounts and at least monthly for everything else: download the account, filter to PMax, sort the search terms by cost, mine the new waste, stage it onto the shared list, and post. Once the list structure exists, each subsequent pass is a matter of minutes, which is the entire reason the desktop tool changes the calculus — the friction that used to make PMax term review something you skipped is largely gone.

Treat this as one instrument in the broader Performance Max hygiene set rather than the whole of it. The Performance Max negative keywords overview covers the limits and mechanics of PMax negatives, and the channel-split report guide covers reading the Search-versus-Shopping breakdown the report exposes. Editor 2.11 does not replace either; it makes the acting-on-what-you-find step fast enough to actually do on schedule. That is the quiet upgrade here — not new data, but a workflow where the report and the block finally live in the same place, so mining PMax waste stops being a chore you postpone.

For the in-UI counterpart to this desktop workflow, see the Performance Max search terms report guide. For the mechanics and limits of PMax negatives themselves, see Performance Max negative keywords, and for deciding brand handling before you block brand strings, see brand exclusions versus negative keywords.