List every property the authenticated account can read.
Call this first when a property string fails: it returns the exact `site_url`
values the other tools expect, and whether each one is a domain property
(`sc-domain:example.com`) or a URL-prefix property.
Permission level and property type for one property.
Query the Search Analytics report: clicks, impressions, CTR, position.
This is the general-purpose tool. With no dates it covers the last 28 days
ending today (UTC), with data_state=all so today's partial data is included,
matching what the Search Console UI shows.
Example: site_url="sc-domain:example.com", dimensions="query,page",
period="last_28_days", row_limit=100.
Returns a `# meta ...` line then a TSV table, or JSON with `meta` and `rows`.
The meta names the exact range, the row count, whether more rows exist and
the `start_row` to pass next.
Site totals for a period, compared with the preceding one by default.
Start here: it answers "is the site up or down" in one call, with the
percentage change on every metric. `position_delta` is negative when the
average position improves.
Join two periods on one dimension and rank the rows by click delta.
Answers "what changed" without the model diffing two tables by hand. Rows
present in only one period are kept, with zeros on the missing side; the
biggest movers in both directions are returned, worst first. The meta counts
how many rows gained and how many lost clicks.
Queries close enough to the top that a push would pay off.
Ranked by the clicks each query would gain at `target_position`, not by
impressions: a big query already near its ceiling is not an opportunity.
The meta reports the thresholds that were applied.
Rows that rank well but are clicked far less than their position implies.
The snippet, not the ranking, is the problem, which makes these the
cheapest fixes available. `expected_ctr` is what a result at that position
normally earns.
Queries where several pages of the site compete for the same result.
Reads one page of up to 25,000 query/page pairs; on a very large property
the tail is cut off, and the meta says how many pairs were analysed.
Each row lists the competing pages with their own clicks and positions.
Pages that lost clicks against the baseline, each with a likely cause.
`diagnosis` separates a ranking loss from falling demand, a collapsed CTR
and a page that disappeared: the four need different fixes, and the raw
numbers for both periods are in the row so the call can be checked.
Pages sliding down month after month.
A period comparison hides this: a page that halves over six months never
shows a sharp drop in any single month-on-month check. One query per month
runs in parallel.
What changed sharply enough to be worth a message today.
Compares the last `window_days` against the window before it across both
queries and pages, and returns only movements past the alerting rules:
lost positions, collapsed CTR, dropped or vanished pages.
Every accessible property at a glance, ranked worst first.
One row per property with the current period, the previous one and a health
flag: critical below -30% clicks, warning below -15%. Use it to decide which
property to look at before running anything else.
+5 more tools listed on main page