How to Set Up Google Ads Negative Keywords for Enterprise Accounts

Set up enterprise negative keywords by defining the target-account or buying- role mismatch, reviewing Search terms with mature sales evidence, checking positive and account-list overlap, choosing the narrowest match type and scope, and monitoring opportunities and pipeline after saving. Treat “jobs,” “support,” “API,” “pricing,” and “security” as context-dependent research, not automatic exclusions.

Start with Google’s negative keyword guide, Search terms workflow, and list-management guidance.

1. Define the account or buying-role mismatch

Write why the query should not enter this enterprise campaign. It may represent employment, consumer or student research, an unsupported industry or company size, a free or DIY request, existing-customer support, or a market the account team does not serve.

Record one query to block, one similar query to preserve, and one edge case. “Jobs,” “support,” “API,” “pricing,” “security,” “RFP,” and “training” can all be legitimate committee research or a mismatch depending on the offer and buying role.

Separate account-fit mismatch from slow response, weak content, missing offline conversion mapping, or incomplete target-account data. A negative should state a stable boundary, not remove research the enterprise team has not yet qualified.

2. Review Search terms and mature sales data

Open Search terms for the exact campaign and date range. Review clicks, cost, target-account status, qualified leads, meetings, accepted opportunities, buying-committee engagement, pipeline, revenue, and disqualification reason. Allow enterprise sales and procurement lag.

Prioritize repeated mismatches with material spend or clear incompatible intent. One contact from an untargeted company is weak evidence if the campaign can serve that segment. Check campaign, content, landing page, industry, location, account list, and CRM mapping before excluding.

Record query, reason, report window, owner, match type, scope, and application date. A negative added today cannot change historical traffic. Annotate conferences, launches, territory changes, account-list updates, sales coverage, content, and offline imports.

3. Protect buying-committee research

Review positive keywords, ads, content, security and integration pages, account lists, sales routing, and sibling campaigns. Write one blocked query, one preserved query, and one edge case.

An engineer may search an API or integration. Procurement may search pricing or an RFP. A champion may download a template. A support query may be an existing customer or the enterprise service being sold. Read the complete query before choosing a negative.

If an industry, market, or tier is genuinely unsupported, audience, location, account list, or campaign structure may be more precise than a global keyword.

4. Choose negative match type

For Search campaigns, choose negative broad, phrase, or exact from the boundary you need. Google documents:

Negative broad match: all words in the negative keyword must occur in the search, in any order.
Negative phrase match: the complete terms must occur in the same order, with possible extra words before or after.
Negative exact match: the same terms must occur in the same order without extra words.

Use broad when every word in the category should be excluded, phrase when the ordered concept is the mismatch, and exact when one known query is confirmed. Negative keywords do not automatically match close variants, synonyms, or every word form. Add variants only when they represent the same unwanted account intent.

Do not widen a negative because a longer query remained eligible. Review its role in the committee and opportunity journey first.

5. Select the narrowest enterprise scope

Use an ad-group negative for one product or topic, a campaign negative when all ad groups share an account tier, industry, location, or offer rule, and a shared list only when every applied campaign has the same documented policy. Reserve account-level rules for truly global exclusions.

A support rule may be right for new acquisition and wrong for a support offer. An employment rule is wrong for recruiting. An account-tier rule can remove a strategic account. Check positive, account-list, and sibling campaign overlap.

6. Create an owned, approved list

Confirm account, campaign or ad group, keyword text, match type, and scope. For a shared list, record purpose, account tier, owner, review date, source Search terms, blocked and preserved examples, applied campaigns, approver, and rollback.

Google’s negative keyword management guide describes adding negatives and applying lists. Read the saved row back. A list can exist without association, or it can block a buying role another campaign should serve.

Review the list after a new product, market, account tier, security offering, pricing model, content program, or sales qualification rule launches.

7. Check network behavior

Confirm whether the campaign is Search, Display, Video, Shopping, or another type. Search negative broad, phrase, and exact behavior is documented by Google. Display and Video negatives behave differently and are less precise; placement, content, audience, or other controls may be better.

For account-level negatives, verify current campaign and inventory scope. Do not describe a keyword as a universal enterprise exclusion without confirming the current control.

8. Verify the saved configuration

Reopen the negative-keyword view. Confirm text, match type, status, campaign or ad-group scope, list association, and account-level source. Check Change history and retain the previous configuration.

If an excluded query appears, check date range, application date, campaign, network, match type, word order, close variants, list association, and another negative source. Google’s troubleshooting guide supports this sequence.

If a target-account query stops showing, inspect negative overlap before changing the positive keyword. Remove or narrow the negative, verify content and sales routing, and record the rollback reason.

9. Monitor account quality and pipeline

Compare new Search terms, spend, target-account engagement, meetings, accepted opportunities, pipeline, revenue, and response time after the normal lag. Check that the mismatch declined while committee and account activity remained available.

Set guardrails using accepted opportunities, target-account movement, pipeline, or revenue. Lower contact volume is not success if qualified account demand also falls. If the result is inconclusive, stop widening the list.

Common enterprise setup mistakes

Blocking target-account research because it does not look like a form.
Treating “jobs,” “support,” “API,” “pricing,” “security,” or “training” as universal mismatches.
Adding a negative before sales and procurement lag mature.
Applying an industry, market, or account-tier rule at account level.
Ignoring content, account lists, positive keywords, and routing.
Assuming negative keywords match close variants or every word form.
Copying Search behavior to Display, Video, or other inventory.
Using negatives to hide offline-import or qualification gaps.
Measuring fewer contacts while missing qualified pipeline.

Protect legitimate enterprise research while excluding the account or intent the campaign cannot serve.

Enterprise negative-keyword checklist

Confirm target-account and buying-role rule, unwanted intent, blocked and preserved examples, Search terms range, sales and procurement lag, positive and account-list overlap, match type, campaign or list scope, network behavior, owner, approver, review date, application date, monitoring metric, and rollback. Use the enterprise negative-keyword framework and negative keyword checklist for a second review.

Start with one repeated mismatch and the narrowest scope. Recheck accepted opportunities, target-account movement, and pipeline after the normal lag, and revisit the list when the offer or account policy changes.