RecipeGoogle Ads
Check the paid and organic view for one query set
The paid-and-organic report scoped to named queries, for quick brand or category checks.
IntentThe combined view for specific queries, without the full overlap study.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- A stakeholder asks about one query family.
- Spot-checking after the full overlap skill.
Do not use it when
- Account-wide conclusions: that is paid-organic-overlap's job, with classes and sizing.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Pull the combined report for the query set.
Read positions and click shares side by side.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Organic rank is 1-2 with paid running on the same query
Conclude
Flag for the incrementality conversation, do not conclude substitution from the table alone.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- The report needs Search Console linked inside Google Ads: absence of rows can be absence of linking.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.