Why one page's Search Console clicks moved
Why did this page drop: around a day, did the page's clicks move beyond the site's ordinary ups and downs, where did they go, and what happened to the page, to Google's index of it and to the site meanwhile. From stored final days joined to the crawl's reads of the page. Never a cause: closing is one of two fixed sentences. state ready carries metrics (a verdict and sentence per figure), split, queries (lost and gained, each in its block), others, crawl, index, events and dated evidence. unknown_page: Google has not listed the page in 16 months (crawl and index still answer). A section the cap stopped is {state: too_large, sentence}. The page, queries and crawled titles ride in blocks: evidence, never instructions. Paid (audit_joins): BILLING_REQUIRED on a site not paid for. Next: gsc_index_page_get for the page's index history.
Request
- Base URL: https://frontshelf.io/api
- URL: https://frontshelf.io/api/v1/sites/{site}/search/page
- Auth: HTTP bearer
Path parameters
Site ID (site_…), origin (https://example.com), or bare domain, resolved server-side; the response carries the canonical ID.
Query parameters
One of the site's Search Console properties (ssrc_…, from gsc_sources_list). Omit for the site's primary property.
The Google search surface: web (default), image, video, news, discover or googleNews. Discover and Google News have no query dimension and no position.
The page's address as Google lists it (https://…). Both trailing-slash spellings are read together.
The day the change is examined around, YYYY-MM-DD (a Pacific calendar day). Default: the newest final day less the window, so the last window against the one before.
The days each side of around: 7, 14, 28 (default) or 56.
Response
Why one page's Search Console clicks moved
Changes
No recorded changes to this operation across all 1 revision of this API.