How to Set Up Microsoft Ads Negative Keywords

Set up Microsoft Ads negative keywords by defining the unwanted intent, reviewing actual search terms, choosing the narrowest campaign or ad-group scope, selecting exact or phrase negative match, applying the change or list, checking conflicts, and validating both wasted spend and eligible demand after the update. A negative keyword is a routing and eligibility control, not a generic list of bad words.

Microsoft's current keyword match-options guidance says negative keywords use exact and phrase match rather than a broad negative-match setting; its Search terms workflow describes reviewing queries and applying exclusions. This article is educational search-advertising guidance, not account-specific, legal, financial, privacy, or platform-policy advice; the account owner approves exclusions and their business consequences.

What should a Microsoft Ads negative keyword exclude?

Start with the business mismatch, not a word list. Write why a query should not receive this campaign: an unavailable product or service, unsupported market, different customer route, research-only intent, employment search, support request, or another owner-defined boundary.

Define the unwanted intent

Record the candidate query, complete wording, campaign, ad group, product or service, location, page, cost, clicks, conversions, downstream outcome, reason for exclusion, receiving route if one exists, proposed match type, proposed scope, owner, and evidence that would reverse the decision.

Do not exclude a word merely because one query did not convert, has a high cost, or looks unfamiliar. A term can be relevant in another context. “Repair” can be unwanted for a new-product campaign and essential for a repair service. “Free” can be irrelevant for a paid offer and valid for an approved consultation. Read the complete query.

Separate irrelevant intent from low performance

An irrelevant query does not fit the campaign's offer or approved route. A relevant query with low conversion or high cost may need a different bid, page, budget, audience, period, or measurement definition. A negative is not a substitute for improving an eligible route.

Keep unknown intent separate from proven mismatch. If the available evidence cannot show that the query breaks the campaign boundary, report the uncertainty and collect the next evidence rather than blocking it.

Identify the receiving route

If a query belongs to another campaign, product, service, market, support path, or landing page, record the intended receiving route before excluding it. A negative that removes the current ad without a real destination can reduce eligible demand rather than improve routing.

Do not use a negative to hide a broken page, unavailable inventory, unanswered phone, weak offer, duplicate conversion, or missing CRM handoff. Fix or assign the underlying issue separately.

Which Microsoft Ads negative match type should you use?

Choose the narrowest supported match type that expresses the proven exclusion. Microsoft documents exact and phrase negative match; do not look for a broad negative-match control that the platform does not provide.

Use negative exact match for one specific query

Use negative exact when the evidence supports blocking one complete query and its exact form at the selected scope. Record the exact query, punctuation or normalization as shown by the account, campaign or ad group, reason, and receiving route. Confirm that close or related queries remain available when they may be eligible.

Exact is useful when a single query is clearly outside the offer but its individual words also appear in relevant searches. It is not a guarantee that every semantic equivalent will be blocked, so review later search-term evidence.

Use negative phrase match for a recurring phrase

Use negative phrase when the complete phrase represents a recurring unwanted intent and the owner has reviewed the variants it will block. Record example queries that should be excluded and examples that must remain eligible. A phrase at campaign or shared-list scope can affect more traffic than the candidate query that prompted it.

Do not use phrase match merely because it is shorter to maintain. Check word order, surrounding terms, product or service routes, languages, and market exceptions before applying it.

Do not use a broad negative-match assumption

Microsoft's negative behavior differs from positive keyword matching and does not provide a broad negative option in the way some account owners expect. Translate an intended broad exclusion into a narrower set of proven exact or phrase rules, or leave it unblocked until the business boundary is clear.

If a requester asks for a broad negative list, report the platform limitation and the eligible-intent risk. Do not simulate broad blocking with a word list without reviewing the complete queries and affected routes.

Compare the negative with positive keyword and product routes

Before saving, inspect positive keywords, search terms, product titles, product groups, landing pages, locations, languages, and campaign overlap. A negative can block a route that another campaign was supposed to receive, or it can create a gap where no campaign is eligible.

Record the expected blocked variants and the intended remaining variants. If the business rule is about a product, service, market, or customer type rather than a phrase, consider a campaign, page, location, or product-group boundary instead of a broad exclusion.

At what level should you apply a Microsoft Ads negative?

Apply the rule at the narrowest level that expresses the business decision. A wider scope is a separate claim and needs evidence that the boundary is global.

Use ad-group negatives for local routing decisions

Use ad-group scope when the query is irrelevant to one product, service, offer, or page but may be eligible in another ad group within the campaign. Map the excluded query to the receiving ad group or product route and check that the negative does not block the desired destination.

Ad-group scope can help route similar terms between tightly separated themes, but it cannot solve overlapping campaign structure by itself. Review campaign-level and shared exclusions that may still block the route.

Use campaign negatives for a campaign-wide boundary

Use campaign scope when every ad group in the campaign must exclude the same proven intent, market, product, service, or customer route. Record all ad groups, product groups, locations, pages, and conversion goals affected. Do not use campaign scope for a term that only one ad group cannot serve.

After a campaign-level phrase negative, run a conflict check and inspect search terms for related eligible queries. Keep a before-state so the owner can see what changed.

Use shared or account-level lists for stable global rules

Use a shared negative list or account-level rule only when the exclusion is stable across every current and future consumer within its scope. List every campaign, market, product, service, brand, language, and support route that consumes it, plus the owner and review condition.

Do not place a local service, product, campaign, or temporary promotion exclusion in a global list. Shared scope can turn a valid local decision into account-wide lost demand.

Check negative conflicts after a scope change

Use Microsoft's conflict-report or equivalent account workflow where available, and inspect the affected positive terms, products, campaigns, and search terms. A conflict is a signal to investigate, not proof that either the positive or negative should be removed.

Record the conflict, expected route, owner, decision, and proof condition. If the conflict cannot be resolved from the available data, keep the claim open and avoid a destructive change.

How should you find negative-keyword candidates in Microsoft Ads?

Use actual search-term evidence and the account's business boundary. Microsoft's Search terms documentation and report-field guidance can help locate the query, campaign, ad group, keyword, match type, spend, and conversion fields needed for review.

Read the complete query in context

Review query, keyword, match type, campaign, ad group, product or service, market, page, device or network where relevant, cost, clicks, conversions, calls or forms, and downstream outcome. Ask whether the query is outside the offer, outside the market, a different customer route, an existing-customer need, or simply an eligible route with insufficient evidence.

Words such as “cheap,” “free,” “repair,” “used,” “near me,” “jobs,” “training,” “support,” “wholesale,” “subscription,” and “DIY” are not universal exclusions. Their meaning depends on the full query and the account's product, service, market, and customer route.

Use a candidate register before applying rules

Create a candidate register with query, evidence, proposed type, proposed scope, blocked variants, protected variants, receiving route, owner, reason, date, approval, and reversal condition. Group candidates only when the business rule and affected intent are genuinely the same.

Keep one-off observations separate from recurring patterns. A candidate that appears once may need review, while a recurring phrase with a clear mismatch may justify a phrase negative after conflict checks.

Check conflicts before applying the exclusion

Search for the candidate phrase in positive keywords, search terms, product titles, pages, locations, ad copy, and other campaigns. Read both clearly irrelevant and clearly eligible examples. If the rule would remove an eligible route, narrow it or use a different control such as campaign structure, product group, location, schedule, page, or offer.

Do not make an account-wide change from a single campaign's evidence. Preserve the query sample and owner decision.

How should you apply a Microsoft Ads negative keyword?

Apply one approved change through the account's current workflow, then record the resulting scope and status. The user must authorize live account edits separately; this article describes the setup decision and QA, not permission to change an account.

Add an ad-group or campaign negative with explicit scope

Select the exact campaign or ad group, add the approved negative text and match type, and record the reason, owner, source query, date, expected effect, and proof condition. Review existing negatives at that scope before saving so a duplicate or conflicting rule does not obscure the decision.

After saving, verify the negative appears at the intended scope and did not change another campaign or list. Confirm the destination page or receiving campaign still has an intentional route.

Create and apply a shared negative list deliberately

Name the list for its business boundary, not a vague label such as “bad words.” Record owner, purpose, match types, entries, exceptions, campaigns, markets, products or services, review cadence set by the owner, and removal condition. Apply it only to campaigns that share the same exclusion.

Before applying, compare every consumer's positive routes and search-term evidence. After applying, check conflicts and campaign-level overrides or duplicates. A shared list is a reusable control, not a substitute for campaign ownership.

Keep account-level changes exceptional

Use an account-level exclusion only when the rule is proven to apply to every current and future campaign within the account's scope. Record the account boundary, business rule, affected consumers, owner, approval, and rollback. If any market, product, service, support, or brand route is an exception, keep the rule narrower or manage the exception explicitly.

How should you maintain Microsoft Ads negative-keyword lists?

Negatives need ownership and change control because products, services, markets, inventory, and query meaning change over time.

Give every rule a reason and owner

For each entry, keep source query or pattern, match type, scope, reason, receiving route, owner, date, evidence, and removal or review condition. A list without a reason is difficult to audit and easy to over-apply.

Do not treat a negative list as permanent merely because it has existed for a long time. Recheck it when the offer, page, market, language, product catalog, service coverage, or campaign structure changes.

Remove duplicates without losing scope information

Duplicate text can have different effects at ad-group, campaign, shared-list, and account levels. Consolidate only after recording the original scope, owner, reason, and affected campaigns. Removing a duplicate from one list may not remove the same exclusion elsewhere.

Use the narrowest clear list structure and make exceptions visible. Do not move local rules into a global list to reduce the number of rows.

Treat imports and scheduled jobs as change sources

Review Google Ads imports, recurring imports, scripts, rules, API updates, shared lists, feed logic, and management tools that can create, overwrite, pause, or remove negatives. Microsoft and Google negative behavior can differ, so translate the business rule rather than copying syntax blindly.

Record what a future import may overwrite and how an intentional Microsoft-specific change is protected. If a recurring job reintroduces an unsafe negative, assign the finding to its owner before changing the schedule.

Use change history for accountability

Record who added, edited, moved, applied, removed, or imported a negative and when. Link the action to the candidate register, approval, query evidence, conflict check, and post-change result. If the account cannot identify the source of a negative, treat that lack of ownership as a finding.

How do negatives interact with positive match and automation?

Negative keywords filter eligibility; they do not fix positive keyword quality, campaign overlap, bid strategy, conversion measurement, page fit, product availability, or capacity.

Keep exclusion rules narrower than the business problem

Use a phrase negative only when the phrase itself represents the proven boundary. If the issue is a location, product type, service, customer stage, or page route, use the corresponding campaign or business control when possible. A word-level exclusion can block many valid combinations.

Do not use negatives as a substitute for routing

If a query belongs in another campaign, build or verify that receiving campaign before excluding the current one. If no route exists, state that the business has an unmet demand-handling decision rather than disguising it as search-term cleanup.

Treat automated suggestions as candidates

An automated recommendation can surface a query or pattern, but it cannot know the full product, service, market, customer, support, or fulfillment boundary. Review the complete query and protected examples before approving it. A suggestion is evidence to inspect, not account authorization.

How should you handle imports and non-Search exclusions?

Do not assume a Search negative is a universal control for every Microsoft Ads surface. Import, Shopping, Audience, Performance Max, and other campaign types can have different settings, product or feed logic, and context exclusions.

Review Google Ads imports as translations

Before importing, map source negative text, match type, list, campaign or ad-group scope, positive route, receiving campaign, and owner to the Microsoft destination. Microsoft's import guidance and import-field documentation can identify the process, but post-import conflict QA remains necessary.

Do not copy Google negative broad, phrase, or exact assumptions into Microsoft without checking the destination behavior. Preserve source and destination rules separately, record unsupported mappings, and review any recurring import that can overwrite a deliberate Microsoft change.

Separate Search exclusions from other campaign controls

For Shopping or product campaigns, inspect product groups, listing groups, feed eligibility, product exclusions, inventory, market, and page instead of assuming Search negatives control product delivery. For Performance Max, review the current Microsoft controls for negative keywords or context exclusions and their documented scope. Do not call a product or automated campaign corrected because a Search negative was added.

Audit the negative rule after each translation

After an import or cross-campaign change, inspect destination text, type, scope, conflicts, positive keywords, product groups, queries, pages, delivery, and downstream outcomes. Record the source, destination, owner, exception, proof, and rollback condition.

How should you validate a Microsoft Ads negative keyword?

Validate both sides of the change: the unwanted query should be less eligible at the intended scope, and protected eligible demand should remain reachable.

Verify the saved scope and match type

After an authorized change, confirm the negative text, exact or phrase type, campaign, ad group, shared list, account scope, status, owner, and change-history record. Check that a shared list was not applied to an unintended campaign and that a local rule was not moved to account level.

Review conflicts and search terms

Run the available negative-keyword conflict workflow and inspect new search-term data after the account's owner-defined review period. Compare blocked queries with protected queries and the receiving campaign or page. Do not infer success from lower impressions alone; the exclusion may have blocked eligible demand.

Test valid and invalid routes

Use approved test queries, previews, or live evidence to check an unwanted route, an eligible route containing the same word, a query intended for another campaign, a market exception, a product or service exception, and a support or existing-customer route where relevant. Record expected eligibility and observed behavior.

Do not use a real customer or unnecessary spend to prove a negative. Use the account's approved QA method and state what remains unproven.

Reconcile spend and business outcomes

Compare spend, impressions, clicks, search terms, calls, forms, product interactions, leads, orders, and downstream outcomes before and after the change using the same campaign, market, product or service, period, and conversion definition. Separate reduced irrelevant traffic from reduced eligible traffic and from ordinary demand variation.

If the evidence shows a blocked eligible route, remove or narrow the negative through an approved change and record the correction. If evidence does not prove an effect, keep the claim open rather than adding more exclusions.

Microsoft Ads negative-keyword setup checklist

Before adding a negative

Define the unwanted intent, business boundary, complete query, affected campaign, receiving route, owner, evidence, and reversal condition.
Confirm exact or phrase match is the supported Microsoft behavior for the proposed rule; do not assume broad negative matching.
Check positive keywords, product groups, pages, locations, languages, campaigns, shared lists, imports, and protected eligible examples.

While making the change

Choose the narrowest ad-group, campaign, shared-list, or account scope that the evidence supports.
Record text, match type, scope, reason, owner, approval, expected blocked variants, protected variants, and rollback.
Apply the negative or list only through an authorized account workflow and verify the saved result.
Keep local, campaign-wide, and global business rules separate.

After making the change

Check conflicts, search terms, positive routes, receiving campaigns, product eligibility, and destination pages.
Compare irrelevant and eligible traffic, calls, forms, orders or leads, spend, and downstream outcomes using the same boundary.
Review imports, recurring jobs, scripts, shared lists, and future overwrites.
Narrow, remove, or leave open an exclusion based on evidence; do not add a larger list just because the result is unclear.

The bottom line on setting up Microsoft Ads negative keywords

A safe Microsoft Ads negative-keyword setup starts with a complete query and a proven business mismatch. Find candidates in search-term evidence, identify the receiving route, choose exact or phrase match, apply the narrowest scope, record ownership, check conflicts, account for imports and non-Search controls, and validate both wasted spend and protected eligible demand.

Do not call a negative setup successful because impressions fell, a list was applied, or an automated recommendation was accepted. The result is proven only when the intended irrelevant route is excluded at the intended scope without blocking eligible demand that the business still wants to serve. adz.so provides educational advertising guidance and does not administer accounts, approve exclusions, guarantee traffic quality, or promise performance.

Sources and related reading

The platform details and links above were checked against Microsoft Advertising documentation on 2026-08-15. Negative match behavior, scope, conflict reporting, campaign controls, import mappings, and account interfaces can change; verify the live account and current official documentation before applying an exclusion.