Skip to main content
Glama

SEO GSC Wizard MCP

Find page poaching opportunities

find_page_poaching_opportunities
Read-only

Finds queries ranking just outside the top positions (between minPosition and maxPosition) and estimates the click upside of pushing them to a target position. The upside is computed from the property's OWN CTR at the target position (measured over every query in the window on the warehouse), not a broad industry benchmark, so the estimate reflects how this site actually converts impressions at that position. When the property has no queries at the target position, or fewer than 100 impressions there, it falls back to the industry benchmark named by fallbackBenchmark: awr (Advanced Web Ranking 2026, default), awr2026 (AWR 2026 CTR study, organic), awrAio (same study, SERPs with an AI Overview), firstPageSage (First Page Sage 2026), sistrix (Sistrix 2024), or backlinko (Backlinko 2019). The response reports targetCtr (the expected CTR used), ctrSource ("own" or the benchmark key) and ctrSourceNote (why). Sorted by potential click gain. Scans up to 25,000 queries: on the warehouse the ones with the most impressions; on the live API its click order. truncated: true means the scan hit that cap (scanNote says what that left out). Served from the GSC Wizard ClickHouse warehouse when available, otherwise the live Search Console API (see dataSource). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
endDateNoOptional. Window end as YYYY-MM-DD (e.g. 2026-05-31). You do NOT need to know today's date or the latest available date: omit this and the server uses the latest settled Search Console date (data lags ~2-3 days behind today). Never pass null or the string "null".
siteUrlYes
startDateNoOptional. Window start as YYYY-MM-DD (e.g. 2026-05-03). You do NOT need to know today's date. Omit BOTH startDate and endDate to analyze the last 28 settled days automatically (Search Console data lags ~2-3 days). Never pass null or the string "null".
searchTypeNoweb
maxPositionNo
minPositionNo
minImpressionsNo
targetPositionNo
fallbackBenchmarkNoawr

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
rangeNo
paramsNo
siteUrlNo
scanNoteNo
ctrSourceNo
scanLimitNo
targetCtrNo
truncatedNo
dataSourceNo
dataMaturityNo
ctrSourceNoteNo
opportunitiesNo
settledThroughNo
warehouseLatestDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / ctrSourceNote
      Added value: +{
      +  "$ref": "#/properties/siteUrl"
      +}
    • addedOutput schema / properties / scanLimit
      Added value: +{
      +  "$ref": "#/properties/range/anyOf/0/properties/days"
      +}
    • addedOutput schema / properties / scanNote
      Added value: +{
      +  "$ref": "#/properties/siteUrl"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / warehouseLatestDate
      Added value: +{
      +  "$ref": "#/properties/siteUrl"
      +}
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources