indexpulseapi.com

The evidence layer for technical SEO in the AI era.

Index Pulse API turns crawls, Google Search Console, sitemaps, schema, and entity data into prioritized, AI-ready evidence: crawl waste scores, indexation contradictions, structured-data coverage, and recommended actions ready for reports, webhooks, dashboards, APIs, and MCP agents.

Stop raw crawl dumps from becoming expensive AI context Turn 200 issues into prioritized evidence with GSC proof Feed agents and reports small, structured, observable JSON
GSC
Crawl
Crawl Waste
Sitemap
Schema
Entity
Reports
API
MCP

Audit The Basics

Capture the crawl checkpoints users already expect, then store them as stable evidence instead of one-off exports.

  • Status, redirects, canonicals, robots
  • Titles, descriptions, headings, links
  • Images, hreflang, schema presence

Explain The Cause

Translate raw signals into issue reasons, priority, crawl waste score, GSC contradictions, and the exact evidence behind the recommendation.

  • Risk scoring by blocker type
  • GSC verdict plus crawl facts
  • Suggested next actions

Ship The Output

Return data shapes that can power dashboards, client reports, product widgets, webhooks, and MCP tools.

  • Client report exports
  • Webhook-ready event shapes
  • Evidence-backed action lists

From raw crawl checks to a reportable answer.

Index Pulse does not stop at "title too long" or "link broken." It keeps those checks, then joins them with GSC, schema, entity, sitemap, history, and crawl waste context so teams can explain what happened and what to do next.

1. IngestSitemaps, watchlists, HTML crawl results, redirect outcomes, robots, manual or future live GSC inspection data.
2. NormalizeConvert raw signals into page records, issue IDs, crawl waste types, schema types, entities, and history.
3. PrioritizeScore URL risk and crawl waste by business priority, redirects, indexability blockers, GSC state, schema gaps, and entity evidence.
4. DeliverSend API responses, client report sections, alert events, or MCP-ready answers to downstream tools.

Classic technical SEO checks are included.

The basics still matter because they are facts about the page. Index Pulse records them as evidence fields, but the product is built around the connected layer that older checklist reports usually leave for the user to assemble by hand.

Crawl accessibilityHTTP status, fetch errors, redirects, canonical targets, robots rules, noindex, and X-Robots-Tag evidence.
Page HTML checksTitle, meta description, headings, internal links, outgoing links, images, and basic page structure facts.
Technical relationshipsSitemap membership, duplicate canonical clusters, redirect chains, broken targets, hreflang evidence, and crawl depth signals.
Modern evidence layerGSC verdicts, crawl waste reasons, schema graph, entity coverage, history, API outputs, reports, and MCP-ready answers.

Run an analysis. Get the first answer fast. Keep crawling intelligently.

Customers should not have to wonder what a queue means. Index Pulse starts with the highest-value URL inventory, returns fresh evidence as each analysis finishes, and keeps rotating through remaining known URL candidates so large sites do not block the whole workspace.

Fast first answerStart with the base URL, saved sitemaps, robots sitemap hints, known priority URLs, and older evidence first so a user sees current findings quickly.
Progressive coverageLarge sites run in capped batches. Later runs prefer never-crawled or oldest-crawled URLs, so coverage expands without freezing the app.
Scale-ready workersHosted workers can raise URL caps, run more jobs, and fetch several URLs in parallel while keeping per-site limits and robots checks visible.

Built for the gap between SEO crawlers, SEO suites, and raw APIs.

Large SEO suites are broad, desktop crawlers are great at one-off audits, and raw APIs are low-level. Index Pulse focuses on the missing layer: explain which owned-site URLs need technical SEO attention, why they need it, and what evidence supports the next action.

For agenciesRecurring client evidence, URL risk queues, crawl waste cleanup, schema/entity coverage, and report sections your account team can explain.
For developersStable JSON, API spec docs, scoped API keys, webhook-ready events, and plan-aware usage records for internal tools or customer portals.
For MCP workflowsGrounded page evidence agents can use to answer what changed, which URLs are blocked, and which schema or entity signals are missing.

Why not just use the Google Search Console API?

GSC is an essential source of truth, but it is not a complete search-evidence layer. Index Pulse sits above GSC and connects Google's verdicts to crawl, sitemap, schema, entity, and reporting context teams need before they can act.

Raw GSC APIIndex Pulse API
Returns Google's indexing verdict
Useful, but often not enough to explain the cause.
Combines verdict plus page evidence
Connects GSC states with redirects, robots, noindex, canonicals, sitemaps, HTTP status, schema, entities, and watchlist priority.
URL-by-URL inspection
Your team still has to decide which URLs to inspect, store, compare, and report on.
Monitored URL inventory
Maintains priority watchlists, history, client summaries, alert events, and API-ready snapshots.
Raw data shape
Good for developers, less useful for account managers, automation agents, or recurring operations.
Operational answer
Returns risk, crawl waste, issue taxonomy, recommended action, schema evidence, report context, and governance status.

Why not just use a desktop crawler or SEO suite?

Desktop crawlers and SEO suites are useful, and Index Pulse should not force users to abandon the checks they understand. The difference is that Index Pulse turns those checks into hosted, recurring, GSC-aware, schema-aware, API-ready evidence.

Desktop crawler workflowIndex Pulse API workflow
Manual run on one machine
Someone starts the crawl, waits, exports files, and explains the results later.
Hosted analysis runs
Workspaces can start analyses from the app, API, or scheduled workers, then store the evidence for every customer-facing surface.
Crawl data first
The crawl tells you what the crawler saw, but GSC, schema, entities, history, and client context often live elsewhere.
Evidence graph first
Index Pulse joins crawl facts, GSC verdicts, sitemap source, schema parsing, entity evidence, history, usage, and next actions.
Report assembly is extra work
Teams still need to package the findings for clients, account managers, developers, or automation tools.
Reports and APIs are the product
Use the same evidence in client reports, issue queues, platform widgets, webhooks, OpenAPI clients, and MCP assistants.

SEO Agencies

Show clients which money pages are blocked, why they are blocked, and what changed since the last run.

  • Monthly indexation brief
  • Critical URL queue
  • Schema and entity coverage

Client Portals

Add owned-site evidence widgets to your own portal without building GSC normalization, crawl checks, schema extraction, or report logic.

  • Client rollups
  • Action tables
  • Usage and status feeds

SEO Products

Enrich your app, CMS plugin, or website-builder workflow with risk scoring, entity coverage, schema extraction, and page-level issue taxonomy.

  • API-first data model
  • Webhook events
  • Plan-aware usage

MCP And Agents

Give agents a grounded source for answering which URLs need attention and what evidence supports the fix.

  • URL triage tools
  • Entity gap checks
  • Report draft inputs

Monthly Indexation Brief

Client snapshot: URLs monitored, critical blockers, high-risk pages, alerts, and recommended next actions.

URL Risk Queue

Prioritized URL table with GSC state, crawl status, canonical/noindex/robots evidence, issue IDs, and fix guidance.

Crawl Waste Optimizer

Redirects, non-200s, robots blocks, noindex waste, sitemap leaks, canonical clusters, and queue skips with fix recommendations.

Schema And Entity Coverage

Page-by-page schema types, JSON-LD validity, sameAs evidence, extracted entities, and coverage score.

Platform Feed

API payloads for dashboards, MCP tools, account managers, webhook alerts, or custom client portals.

Built API-first

Turn page evidence into product features.

Power an internal SEO command center, a client-facing reporting portal, an MCP tool, or an SEO product feature without stitching together GSC, crawling, schema parsing, entity extraction, and report logic yourself.

/v1/healthService status for uptime and deploy checks.
/v1/indexation/snapshotsURL-level snapshots with risk scores and issue reasons.
/v1/crawl/wasteCrawl waste score, redirect evidence, sitemap leaks, canonical conflicts, soft 404 exposure, and fix recommendations.
/v1/crawl/soft-404Generated unknown-URL probes that catch frameworks returning 200 OK for missing routes.
/v1/redirects/chainsObserved redirect candidates and final URL recommendations.
/v1/schema/auditStructured-data, entity, sameAs, and schema coverage evidence by page.
/v1/entities/mapEntity graph for client portals, SEO products, CMS plugins, and agent workflows.
/v1/ai/visibilityBing AI Performance citations joined to crawl, indexation, schema, and entity evidence.
/v1/alertsCritical indexation events ready for notifications.
/v1/reportsClient report index, governance, and delivery planning.