RecipeSearch Console
List Search Console properties reachable
The property list read at onboarding, ticked scope made explicit.
IntentWhich properties exist and which are ticked.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Onboarding.
- Multi-domain estates.
Do not use it when
- No specific contraindication beyond the preconditions below.
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.
List sites.
Mark ticked scope and property types (domain vs URL-prefix).
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Both domain and URL-prefix properties cover one site
Conclude
Numbers differ by construction between them: name the canonical property before any report.
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.
- Reachable is not ticked: the gateway answers only for ticked properties.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.