RecipeSearch Console
Build a brand search capture dashboard in Claude
Builds the Get MCP Ads Brand search capture template as a Claude dashboard: Search Console brand searches against organic and paid brand clicks, the blended CTR, clicks nobody captured, the brand alone against the brand with other words, capture by day, top brand queries and paid brand search from Google Ads search terms, against an equivalent comparison period.
IntentA live page that shows how much of the brand's own search demand the site captures, organically and with paid search, and what nobody captures.
- 3
- Steps
- 1
- Tools
- 4
- Rules
- 2
- Failure modes
When to use it
Use it when
- Someone asks whether they should bid on their brand, how much brand traffic paid search takes from organic, or for a brand search report they can keep in Claude.
Do not use it when
- A single brand query's figures: answer in the conversation.
- Hosts without Claude's Dashboard artifact type: answer in the conversation with the matching reports instead.
What it needs first
Required
Optional
Preconditions
- The organisation is on Team or Enterprise: ready-made dashboards are not offered on Free or Pro.
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
brand_termsrequired- The brand's names as people search them, misspellings and spacing variants included.
window- Analysis window.Default: last 14 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Resolve the client's Search Console site and, when connected, its Google Ads account with list_accounts.
Agree the brand terms with the person (names, variants, misspellings), then fetch the brand-search template with both accounts and the terms.
Create a Dashboard artifact, write every document exactly as given in one batch, read its check, hand over with the lines given.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The template is refused with PLAN_REQUIRED
Conclude
Say the dashboards come with Team and Enterprise and that only the account owner changes the plan; answer the question in the conversation meanwhile.
When
No Google Ads account is connected
Conclude
Build the organic side alone and say paid brand capture appears once Google Ads is connected.
When
The latest two or three days show no organic data
Conclude
That is Search Console's reporting lag, shown on the page: do not read it as a drop.
When
A reader sees a source fail to load
Conclude
Their own Get MCP Ads access decides: check that their connection covers this client's workspace and that their plan includes dashboards before changing the dashboard.
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.
- Editing the template's page or queries by hand loses the provenance of each figure: ask for changes by name instead.
- Guessing the brand terms: a missing variant hides part of the demand, a generic word inflates it. Confirm them with the person.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.