Read a site's search performance
The baseline read - what a site is doing now, what it was doing before, and which named question to ask next.
Use this when you want the current picture of a site and have no particular suspicion yet. Everything else in the cookbook starts from somewhere in this sequence.
list_sites - the sites in your
workspaces, with the search engines attached to each. It is also how you
learn the exact domain string the other tools want.
get_connection_status -
whether Google and Bing are actually connected and how fresh their data
is. Worth checking before concluding that a site has no traffic.
get_site_snapshot or
get_performance_trend -
the overall picture. The snapshot compares a window against the one
immediately before it; the trend gives the daily, weekly or monthly
series, which is what tells you when something changed.
A named question -
find_low_hanging_keywords,
find_content_decay,
find_ctr_opportunities,
find_content_gaps and the rest
each answer one thing and explain their rows. Prefer them over the
generic
get_advanced_search_analytics,
which only groups and counts.
score_seo_opportunities
ranks several of those into one queue priced in clicks, and
generate_search_performance_report
assembles them into a report.
Where it goes next
- Clicks are down and you want the cause → Diagnose a traffic drop.
- Nothing is obviously wrong and you want a work list → Turn findings into one work queue.
- You need to drill from a query to its pages or back -
get_query_pagesandget_page_queriesare the two directions.
Both engines, read differently
Google reports daily and Bing largely weekly, and position especially so. A figure that is null for one engine means not measurable there, not zero - so a Google-only number is a Google finding, not a site finding. The per-engine values are always in the response; prefer them to a combined average when the answer turns on position.