The weekly search terms report habit

1. Review buying intent, not just expensive rows

A keyword is targeting input; a search term is the query someone actually entered. The weekly habit is to inspect available query evidence and decide whether the traffic belongs, whether the destination serves it, and whether more evidence is needed. This guide focuses on paid search, particularly Google Ads.

Start with a written boundary: what you sell, where you serve, who qualifies and which outcomes matter. Without that boundary, reviewers can confuse unfamiliar language with irrelevant demand. Every example below is hypothetical.

For an emergency plumber, ‘burst pipe help tonight’ could be valuable despite not naming the service formally. ‘Plumbing apprenticeship wages’ is a different intent. The first needs a relevant booking experience; the second may warrant exclusion. Neither decision requires waiting for an arbitrary spend threshold.

• Keep a short reference list of offered services, excluded services and service locations.
• Separate clear commercial mismatch from relevant traffic with uncertain performance.
• Give each reviewed theme a decision: exclude, improve, investigate or retain.

2. Prepare a repeatable evidence pack

Use a consistent reporting window, account timezone and currency. Review the latest complete week alongside a longer context window chosen for your conversion cycle. A business with lengthy quote approval needs more maturity than an immediate online purchase. Record the extraction date because attributed outcomes can arrive later.

Include search term, campaign, ad group, matched keyword where available, cost, clicks, conversion action and conversion value where meaningful. Keep campaign types separate when their reporting or targeting differs. Privacy protections and reporting rules mean visible terms are not a complete ledger of every search.

Do not substitute Search Console queries for paid search terms. Search Console reports organic search performance, with its own aggregation and average-position rules. Its query language may inform research, but it does not establish which paid queries consumed budget.

• Check active filters and whether the export omits low-volume rows.
• Compare visible-term cost with relevant campaign totals without assuming any gap is waste.
• Save the original export before adding classifications.

3. Check the outcome before judging the query

Confirm what the conversion columns count. Google distinguishes GA4 key events from Google Ads conversions; do not assume similarly named figures are interchangeable. Check the selected actions, counting settings and reporting context before treating a query as profitable or unproductive.

A conveyancing firm might count both enquiry submissions and brochure downloads. A term producing downloads is not necessarily generating qualified matters. Where lawful and available, inspect qualified-lead or completed-sale feedback rather than optimising solely towards the easiest recorded action.

Mark recent terms as immature when outcomes usually arrive after the reporting window. A tracking outage, changed form or missing value should create an investigation task, not a wave of exclusions. Cost per acquisition is meaningful only against a defined acquisition and the business economics behind it.

• Name the decision-driving conversion action.
• Check outcome delay and known measurement incidents.
• Separate lead quantity, lead quality and revenue evidence.

4. Group intent before sorting by cost

Classify terms into practical themes: clearly irrelevant, relevant but poorly served, relevant with weak evidence, and promising. Grouping exposes repeated intent that individual rows can hide. Then use cost to prioritise attention within each group.

For a furniture retailer, ‘oak dining table assembly instructions’ may be existing-customer support intent, while ‘extendable oak table for small apartment’ signals a product requirement. Treating both as generic furniture traffic misses the operational distinction.

Avoid labelling every zero-conversion row as waste. A relevant theme with limited observations may deserve monitoring. Conversely, an obviously unsupported service does not become appropriate because it has only spent a little. Set account-specific review triggers around commercial risk and evidence, not a universal target CPA multiple.

• Inspect high-cost mismatches first.
• Group repeated modifiers such as hire, repair, wholesale or replacement.
• Preserve the original query wording beside each theme label.

5. Apply negatives at the narrowest useful scope

An exclusion should solve a defined mismatch without blocking legitimate demand elsewhere. Choose scope deliberately: ad group, campaign or a shared list where supported. Check the platform’s negative matching behaviour rather than assuming it mirrors positive keywords or covers every variant.

A retailer selling coffee machines but not repairing them might exclude repair-service intent from sales campaigns. Blocking ‘replacement’ broadly could also remove valuable searches for replacement machines. An exact negative for a specific unwanted query may be safer while the wider theme is investigated.

Keep exclusions reversible. Record the term, proposed negative, match type, scope, reason and approver. Shared lists deserve extra scrutiny because one mistaken exclusion can affect unrelated campaigns.

• Test proposed exclusions against known valuable query wording.
• Check whether another campaign legitimately serves the intent.
• After application, verify the correct list and scope, then set a review date.

6. Turn relevant queries into destination decisions

Not every useful finding belongs in a negative list. Queries can reveal missing specifications, weak service explanations or a mismatch between advertising and the landing page. Decide whether the business can genuinely satisfy the request before proposing new targeting or copy.

For a commercial cleaning business, ‘office cleaning after 6 pm’ might justify clearer after-hours availability if that service exists. If it does not, promising it in an advert would create a misleading acquisition path. The task may instead be exclusion or commercial review.

Promising terms can inform keyword and message tests, but adding every converting query as an exact keyword creates maintenance work without guaranteed benefit. Prefer changes that offer a clear routing, relevance or control advantage.

• Write the customer need in one sentence.
• Verify availability, margin and operational fit.
• Assign the appropriate fix: targeting, advert, destination or offer clarification.

7. Separate housekeeping from experiments

Removing clearly unrelated recruitment searches from a customer-acquisition campaign is housekeeping. Changing match strategy, landing pages and bidding together is a broader intervention. Mixing them makes interpretation difficult.

For a software provider attracting ‘free invoice template’ searches, distinguish an unsupported free-template audience from a deliberate acquisition strategy. If the team wants to test a template-led offer, define the hypothesis, qualified outcome and budget exposure before proceeding.

Google Ads experiments can compare supported campaign changes against an original campaign. Check eligibility and available controls in the account. Low-volume campaigns may not yield a useful answer quickly, so avoid forcing a short deadline into a confident conclusion.

Log promotions, budget shifts and site changes alongside the review. Better CPA after exclusions is an observation, not proof that the exclusions caused the improvement.

• State what will change and what should remain stable.
• Choose a primary outcome and a downside guardrail.
• Review when evidence is sufficiently mature, not merely next Monday.

8. Measure the effort of the habit itself

Close the review with a small decision register, not another slide deck. Each action needs evidence, scope, an owner, an approver where required, and a follow-up date. Keep deferred decisions visible so the same ambiguous query does not trigger a fresh debate every week.

Measure preparation, classification, approval and implementation minutes separately. Also track rework, erroneous exclusions and the time between decision and verified implementation. Faster reviewing is not an improvement if it increases mistakes.

Hypothetically, reducing total weekly handling from 80 to 55 minutes saves 25 minutes per comparable review. Include approval and correction time in both measurements. Over four equivalent reviews that is 100 minutes released, not automatically a cash saving or evidence of better advertising performance.

• Use a stable template and compare similar account workloads.
• Record accepted, deferred and reversed decisions.
• Audit a sample of classifications to protect review quality.

9. Keep the provider report and the work connected

Its stated Google Ads integration includes reading campaign performance and budget recommendations. This does not establish native search-term ingestion or negative-keyword editing. Use the advertising provider’s report and controls for those steps unless support is explicitly confirmed.

RiseProjects is designed to hold manual tasks and accepted DailyRise opportunities with owners, dates and context. RiseInsights is designed to compare named sources and reporting windows. These can support an accountable review workflow, but period comparisons do not prove incremental impact.

Review the relevant product pages and /the-solution before planning implementation. Connected capabilities depend on provider access, permissions and supported reporting. Keep human approval attached to exclusions, tests and spending decisions.