Average CPC can rise even when the cost of every comparable search stays unchanged. An account that buys more expensive commercial terms and fewer cheap informational clicks will show a higher blended average. Before changing bids, reconstruct the mix. This investigation is for a marketer deciding what to change, rather than a benchmark chart declaring one CPC good or bad.
Make this useful for your client. Follow the worksheet, or use the ready-to-copy task with your connected data.
Try this task in 1ClickReport → · See the product workflow →Evidence → Decision → Review
How to run the investigation
Match the comparison
Choose equal weekday windows, the same currency and the same Search campaigns. Keep brand, non-brand, network and geography visible. Exclude a newly launched campaign from a like-for-like comparison and explain it separately.
Split price from allocation
For each meaningful search-term or keyword group, record clicks, cost, CPC and share of clicks in both periods. Look for groups whose own CPC increased and groups whose share increased. Small samples stay marked as uncertain.
Check the change timeline
Review bids, targets, match coverage, negatives, landing pages and account changes around the inflection. Consult auction insights when available. A simultaneous competitor change is context, not proof that it caused your CPC increase.
Choose the smallest response
If irrelevant query groups took more spend, review intent and exclusions. If valuable searches became more expensive but qualified economics remain sound, a lower CPC is not automatically the right objective. Set the next review around qualified outcomes.
Decision worksheet
Use these rows to turn the investigation into an action. Add the actual account, date range, evidence and owner before sharing it with a client.
| What you find | Interpretation | Next move |
|---|---|---|
| Within-group CPC flat | Click share moved to expensive searches | Investigate allocation before blaming auctions. |
| Within-group CPC rises | Comparable intent and geography | Review auction context and bid changes. |
| CPC up, qualified CPA down | More valuable traffic may explain it | Keep the business outcome in the recommendation. |
Download this worksheet (CSV) ↓
Worked example: an illustration, not a customer result
Imagine two query groups at $1 and $4 CPC. Moving from an 80/20 click split to 50/50 lifts average CPC from $1.60 to $2.50 without either group becoming more expensive. Cutting every bid would respond to a price increase that did not happen. Check whether the new mix produces better customers before reversing it.
MAKE THIS YOUR NEXT CLIENT TASK
Run the review on your own data.
Start with one client in 1ClickReport. Connect Google Ads, select the correct client and use the task below. The analyst keeps client-specific context as you work.
Read the ready-to-use task
Explain this client’s Google Ads CPC change using matched periods. Separate within-group CPC changes from shifts in brand, non-brand, device, geography and search intent. Include clicks, cost, conversions and uncertainty. List recent account changes and give one recommendation with a validation date. Do not change bids.
3-day free trial · No credit card required.
- Copy the task, then create your account in the new tab.
- Finish setup and connect the relevant client data.
- Return to this page and open the task in AI Analyst ↗. Review the prompt before sending.
Read-only analysis is available from Solo. Campaign execution requires Team or Agency and approval.
A question worth asking
Does rising CPC mean my ads have stopped working?
No. Evaluate conversion rate and the value of the outcomes alongside CPC. A higher click price may still be acceptable if the same cohort produces more qualified customers; a cheaper click can be poor value if intent is wrong.
References and method
Reviewed November 12, 2026. The decision process and worksheets are 1ClickReport’s editorial recommendations. Examples are hypothetical, not customer results. Platform behavior and access can vary; use the current native account view to verify settings.