Methodology and data limits
How GSC Pulse compares periods, estimates loss, diagnoses likely causes, and communicates uncertainty.
Data sources
The extension uses the Google Search Console APIs through the read-only webmasters.readonly scope. It may request property lists, daily Search Analytics rows, pages, queries, query-page pairs, devices, countries, Search Appearance categories, sitemaps, and permission levels.
Period comparison
The selected 7, 28, or 90-day finalized period is compared with the immediately preceding period of equal length. The interface displays the common finalized data date so properties with different freshness are not silently treated as identical.
Estimated click loss
Estimated loss is the positive difference between previous-period and current-period clicks. It is used to rank attention and describe exposure; it is not a causal, revenue, or forecast guarantee.
Likely-cause model
- CTR / SERP: clicks and CTR fall while impressions and average position remain comparatively stable.
- Rankings / visibility: average position worsens and impressions decline.
- Demand / query mix: impressions decline while position remains relatively stable.
- Device or country concentration: a single segment accounts for a material share of listed loss.
- Page concentration: a small number of landing pages account for most listed page loss.
The labels are directional hypotheses. The evidence panel shows the underlying metrics and direct native links.
Portfolio scope
A portfolio-wide label requires enough properties with comparable volume, finalized dates, and complete period data. When the eligible set is too small, GSC Pulse explicitly says that a portfolio conclusion cannot be made.
Confidence
Confidence increases with sufficient clicks and impressions, comparable dates, complete periods, and consistent supporting dimensions. Low-volume or incomplete properties remain visible but are labeled as low data.
Page and query limits
Search Analytics does not guarantee a complete export of all page and query rows. It returns top rows and applies aggregation and privacy behavior. GSC Pulse therefore calls these lists directional evidence and does not present the row count as a complete site total.
Hourly data
Hourly data is requested only as an optional pulse. It may be partial and is never used as a substitute for finalized daily comparisons.
AI and Search Appearance
Search Appearance or AI-related cards are shown only when the API returns a relevant category. GSC Pulse does not create an artificial AI visibility score.
Sitemap limits
The Sitemaps API provides processing status, error and warning counts, type, submitted URL counts, and timing fields. It does not expose every detailed native issue label or sample URL. GSC Pulse distinguishes confirmed API evidence from likely checks and sends the user to native GSC for the exact detail.
Brand classification
The extension does not claim to reproduce Google's branded-query classifier through a simple domain-name regex. A brand filter is not presented unless it can be supported by explicit user configuration or documented API data.
SEO, GEO, and AEO approach
This website uses crawlable HTML, clear page hierarchy, visible product facts, internal links, structured data, descriptive answers, and fast static delivery. It does not rely on nonstandard AI markup or claim that a special file guarantees inclusion in generative search.