Why it matters
It supports portfolio-level technical triage and tells users which sitemap deserves native inspection.
How to use it
Show confirmed API fields first, then label likely causes as checks, provide safe repair steps, and link to the native sitemap detail.
Limits and interpretation
The API does not return every detailed issue name or affected sample URL. Deprecated indexed-count fields should not be treated as coverage truth.
Common mistakes
Saying “sitemap error” without evidence; guessing an exact cause; using submitted versus indexed counts as a complete index report; applying sitemap checks to platform properties.
Questions people also ask
Where GSC Pulse fits
GSC Pulse uses this concept inside a decision workflow and links to the underlying evidence instead of presenting the term as a decorative metric.
Primary documentationSource
Use the concept in a real portfolio review
Install GSC Pulse or continue with the related methodology and guides.
Add to Chrome Methodology