The evidence layer for search
See what is blocking visibility, why it matters, and what to fix next. Index Pulse connects page facts with search evidence so people and agents can reach the same answer.
Use cases
Index Pulse gives each team the same verified page evidence, shaped for the decision they need to make.
Start with Search Console, then check the page evidence that can explain Google's verdict instead of guessing from a status label.
Verify redirects, status codes, canonicals, robots, sitemap membership, and indexability across old and new URL inventories.
Check titles, headings, schema, entities, internal links, and the GSC queries already earning impressions. Keep editorial judgment with the editor.
Use the same evidence in client reports, issue queues, portal widgets, webhooks, API responses, and MCP tools without rewriting the analysis.
Evidence in, evidence out
The public audit starts with one URL. A workspace adds recurring crawling, GSC and Bing evidence, history, reports, and automation.
{
"url": "https://example.com/service",
"facts": {
"http_status": 200,
"indexable": true,
"canonical": "self",
"schema_types": ["Service"]
},
"findings": ["internal_link_support_low"],
"provenance": ["direct_http", "robots_txt"]
}Evidence rules
Trust comes from being explicit about the line between a fact, a calculation, and an inference.
Intent and funnel labels need observed query, page, or first-party behavior evidence. Missing evidence stays missing.
Index Pulse shows what the page contains, what search data supports, and where evidence is weak. Your editor or agent decides what to write.
Direct HTTP remains authoritative. Optional rendered evidence is labeled as a secondary source with its own observation time.
Reports people can actually use
Use a focused report instead of sending a client or developer a wall of crawler rows.
Audit a URL now, or create a workspace for recurring site evidence.