Search Terms Need Device Split Rules Before You Add Negatives

A search term that fails on mobile may still be valuable on desktop. Segment query performance by device before you solve a device-path problem with a permanent negative keyword.

What This Means: The Practical Takeaway

Some search terms are not bad everywhere. They are bad on one device. Google Ads lets teams segment search terms by device, compare performance across computers, mobile phones, tablets, and TV screens, and use device-specific controls before they block demand outright. If a query fails because the mobile path is weak, the better fix may be a landing-page or bid change on that device instead of a permanent negative keyword.

The blended search-term row can hide a device problem.

Teams often review search terms in aggregate. One row shows clicks, cost, conversions, and maybe a rough CPA. If the row looks weak, the query is marked for exclusion and the account moves on.

That workflow is fast, but it can be wrong.

Google says the search terms report can be segmented by device.[Google Ads Help: About the search terms report](https://support.google.com/google-ads/answer/2472708?hl=en-EN) Its general segmentation guide also says the `Device` segment compares computers, mobile phones, tablets, and TV screens.[Google Ads Help: Use segments in your tables](https://support.google.com/google-ads/answer/2454072?hl=en) When a search term looks expensive, the right first question is not "Do we block it?" It is "Which device is creating the loss?"

Device Blending Creates False Negative Decisions

A search term can send useful traffic on desktop and poor traffic on mobile. The reverse can also happen, especially for local-intent terms where mobile calls outperform form fills. When those device behaviors are collapsed into one row, the operator sees one average and makes one permanent decision.

That is where weak cleanup starts.

Good [ppc analysis](/articles/ppc-analysis) separates the diagnostic layers before acting. Search terms are one layer. Device handling is another. If desktop converts and mobile bounces, the problem may be the mobile experience, not the query intent.

Google Ads Already Supports The Better Workflow

Google's search terms report supports device segmentation. Google's table-segmentation guidance lists device as a standard comparison layer. Google also documents device bid adjustments for computers, tablets, and mobile devices.[Google Ads Help: About bid adjustments](https://support.google.com/google-ads/answer/2732132?hl=en)

That matters because it gives teams a practical control path before a negative keyword:

- inspect the query by device - decide whether one device is distorting the total - change bids, routing, or page experience on the weak device - only add the negative if the term fails across the devices that matter

This is not over-analysis. It is basic [sem optimization](/articles/sem-optimization) discipline.

Mobile Weakness Is Often A Landing-Page Or Call-Flow Problem

Google's Landing pages view includes `Mobile-friendly click rate`.[Google Ads Help: Evaluate the performance of your landing pages](https://support.google.com/google-ads/answer/7543502?hl=en-IN) That gives PPC teams a direct way to test whether the bad device result is tied to the page path rather than the query itself.

If a search term drives clicks from mobile but the landing page is not consistently mobile-friendly, the operator should not rush into a negative keyword. The query may be valid. The page may be the failure point.

The same logic applies to lead-generation call flows. A mobile-first query can look weak if the call asset, click-to-call path, or follow-up handling is poor. Removing the query hides the operational issue instead of fixing it.

Device Rules Beat Blanket Exclusions

Device splits usually point to one of four actions:

- keep the query because it works across devices - fix the mobile landing page or call path - lower bids on the weak device - block only after the term fails across the relevant devices

Permanent negatives should come after device review, not before it.

How To Do It

Step 1: Open the search terms report and include query, keyword, match type, clicks, cost, conversions, conversion value, and cost per conversion. Segment the table by `Device` so each search-term pattern can be read across desktop, mobile, and tablet instead of as one blended total.

Step 2: Group terms into query families before you judge the row. Use labels such as pricing, competitor, support, local service, urgent, and research. Device differences are easier to trust when the pattern repeats across a family rather than one isolated search.

Step 3: Mark each family with one of three outcomes: `keep`, `fix device path`, or `block`. `Keep` means the term is healthy across devices. `Fix device path` means one device is dragging the total because the page, call route, or post-click flow is weak. `Block` means the term fails across the devices that matter to the business.

Step 4: For `fix device path`, open the Landing pages report and inspect `Mobile-friendly click rate`, click behavior, and the actual mobile path. If the mobile experience is poor, repair that before changing the query list. If the page is sound but mobile economics are still weak, apply a device bid adjustment or move the query family into a campaign structure that handles devices more cleanly.

Step 5: Download or schedule the segmented report so the same device review can be repeated weekly. Google Ads supports downloading, scheduling, and sharing segmented statistics tables, which makes this a repeatable workflow instead of a one-time cleanup pass.

Final check: Only add the negative after the search term still fails when device effects have been isolated. Record the device split, the action taken, the review date, and why the team concluded the query itself was the problem.

Sources

- [Google Ads Help: About the search terms report](https://support.google.com/google-ads/answer/2472708?hl=en-EN)

- [Google Ads Help: Use segments in your tables](https://support.google.com/google-ads/answer/2454072?hl=en)

- [Google Ads Help: About bid adjustments](https://support.google.com/google-ads/answer/2732132?hl=en)

- [Google Ads Help: Evaluate the performance of your landing pages](https://support.google.com/google-ads/answer/7543502?hl=en-IN)

- [Google Ads Help: Create, save, and schedule reports from your statistics tables](https://support.google.com/google-ads/answer/2404176?hl=en)