Skip to main content
Use these tools for stored Google observations within an enabled Search Console property. All Search Console requests are read-only.

​
Inspect one URL

Call inspect_url_enhanced with the exact property and page URL:
The response can include index status, crawl, canonical, robots, and rich-result observations. Interpret the available fields and timestamps; a missing observation should not be turned into a positive or negative verdict. Free includes a limited daily individual-inspection allowance. Read get_usage before repeating requests.

​
Inspect a small batch

Call batch_url_inspection on Starter or higher. Its urls argument is a newline-separated string, with at most ten URLs:
The response preserves successful results and individual errors. Use check_indexing_issues with the same argument shape when you want grouped findings. Unknown or failed inspections remain separate from confirmed issues.

​
Read sitemap processing

Use get_sitemaps to list sitemaps for a property:
Use list_sitemaps_enhanced with an optional sitemap_index to list children, or get_sitemap_details for one sitemap:
These tools require Starter or higher. Processing state, submitted counts, errors, and warnings are observations about the sitemap; they do not establish that every listed URL is indexed.

​
Stored snapshot versus a live page

URL Inspection is not a live crawl or an indexing request. A deployed fix may differ from Google’s stored snapshot. Read the live page separately when you need to compare its current content with the inspection result. HyperGSC does not submit sitemaps or request indexing. Use Google’s own interfaces for those actions. See the indexing workflow for a nontechnical prompt and interpretation guide.