How to Set Up Google Ads Match Types for Ecommerce

Set up ecommerce Google Ads match types by mapping product intent, checking the product page and feed, choosing broad, phrase, or exact as a deliberate reach policy, reviewing negative overlap, and validating orders and contribution after the normal lag. Keep Shopping and product-feed controls separate from Search keyword match types.

Start with Google’s keyword matching guide, add-keywords guide, and negative keyword guide.

1. Define the product and purchase intent

Write the product, customer, commercial stage, location, and page that the keyword should serve. Separate brand, category, model, comparison, purchase, replacement, gift, subscription, and support searches. Mark related searches that should be discovered and categories that clearly do not belong.

Choose the primary outcome: order, contribution after shipping and fees, new-customer value, retained subscription, or another financial measure. Record the event, value, counting rule, product group, conversion window, return period, and owner. Gross revenue and clicks are not a substitute for margin or qualified order quality.

2. Check product page, feed, and availability

Confirm that the product, size, color, market, price, stock, shipping promise, and landing page are available. The page should answer the query and the ad should set a matching expectation. The feed or catalog should represent the same product and offer.

If the page cannot satisfy a query, fix the page or use a carefully scoped negative when the intent is genuinely outside the catalog. If the problem is stock or product eligibility, use feed, inventory, product group, or campaign controls instead of forcing a keyword match type to solve it.

3. Choose broad, phrase, or exact

Select the initial type as a reach policy:

Broad: useful when the store can evaluate related searches, the product context is clear, purchase or value signals are reliable, and Search terms review is staffed.
Phrase: useful when an ordered product concept matters while additional words around it can still be relevant.
Exact: useful when a known product intent needs a distinct page, message, budget, or close query inspection.

Google’s current matching documentation describes broad matching as related to context such as landing page and ad-group signals, and explains that phrase and exact are not literal-only guarantees. Validate actual queries instead of promising a text boundary.

Do not add all three types automatically. Keep more than one only when each has a distinct routing, message, budget, measurement, or reach purpose.

4. Enter and verify the keyword

In the correct campaign and ad group, record the keyword text and intended type. For Search keyword syntax, the current interface uses plain text for broad, quotation marks for phrase, and square brackets for exact. Use Google’s add-keywords guide for the current entry flow.

After saving, reopen the keyword table and verify campaign, ad group, keyword, and Match type. Do not treat an accepted entry as proof that the right row was created. Check paused, duplicate, rejected, or mislocated keywords.

5. Align ad group and landing page

Keep the ad group around one coherent product theme. The ad should make product, availability, offer, and next step clear. The page should answer the product query and expose purchase information without a mismatch.

Before blaming a match type, ask:

Does the page sell the exact product or a relevant category?
Is price, stock, market, size, and shipping accurate?
Does the purchase conversion capture meaningful order value?
Are brand, product, support, comparison, and employment themes mixed?
Are returns, refunds, and contribution available for evaluation?

If the query is relevant but the page is weak, improve the message. If the query is outside the catalog, use a scoped negative. If two campaigns sell different offers for the same word, define routing before changing match types.

6. Check negative and campaign overlap

Review ad-group, campaign, shared-list, and account-level negatives. Google’s negative keyword guide explains that negative matching differs from positive matching and does not automatically cover close variants in the same way.

For each high-impact negative, write one blocked and one preserved query. Check overlap with product names, locations, brands, positive keywords, and sibling campaigns. A negative can block a valuable product query even when the positive keyword is correct.

Do not use a negative list to repair a feed, product, stock, checkout, or page problem. Keep the exclusion policy separate from product availability policy.

7. Use order and value signals

Compare impressions, clicks, spend, orders, conversion value, contribution, average order value, new-customer share, product, stock, returns, refunds, and subscription quality. Let the normal order and return lag mature.

A broad type may produce more orders but lower contribution. Exact may protect a model term while missing useful category discovery. Phrase may balance a known product concept and related additions. Judge the type against the financial objective, not CPC or CTR alone.

Annotate promotions, price, stock, feed, landing page, checkout, shipping, creative, and influencer changes. A match type should not take credit for a promotion or blame for an inventory outage.

8. Test one reach policy

Write a hypothesis such as: “Move this non-brand product theme from phrase to broad because the page and feed are specific, purchase value is reliable, and Search terms review can run weekly; preserve contribution and return-rate guardrails.” Or: “Use exact for this model query because it needs a distinct page and controlled message.”

Preserve the old keyword and settings. Keep budget, locations, product page, feed, conversion action, and major creative stable where practical. If several changes must happen together, call it a combined intervention. Allow weekly patterns and conversion or return lag.

Review new Search terms by intent. Add precise negatives for clear mismatches, then check they do not block a product the campaign should sell. For low-volume stores, treat short-term changes as directional and avoid overfitting one order.

9. Validate and roll back deliberately

Check that the keyword is eligible and that new queries reflect the intended product theme. Then compare qualified orders, contribution, new-customer value, returns, product coverage, search themes, and negative additions.

Set a rollback threshold. Restore the previous type when qualified orders or contribution fall below the guardrail, useful product coverage disappears, or the test cannot be interpreted because feed, price, stock, or page changes dominated the period.

Keep the saved keyword, ad group, page, conversion, and negative configuration available so a reversal does not depend on memory.

Common ecommerce setup mistakes

Choosing broad without reliable product context and purchase signals.
Choosing exact because it sounds safe while losing profitable discovery.
Treating phrase and exact as literal-only guarantees.
Mixing product, support, comparison, and employment intent in one ad group.
Ignoring feed, stock, price, landing page, checkout, shipping, and returns.
Treating Search match types as Shopping or product-feed controls.
Using negatives as a replacement for product structure.
Changing match type, budget, feed, page, bid strategy, and conversion together.
Measuring CTR or CPC without orders, contribution, and product coverage.

The setup is complete when keyword, product context, purchase signal, negative policy, and review process agree.

Ecommerce match-type checklist

Confirm product intent, customer stage, product page, feed, stock, campaign and ad group, match-type rationale, syntax, negative overlap, conversion and return lag, order and contribution metrics, owner, guardrails, and rollback. Use the ecommerce match-type framework and match types checklist for companion reviews.

Start with one product theme and one reach-versus-control question. Review orders and contribution after the normal lag before changing the policy again.