Client Reporting

Monthly Indexation Brief

A concise client-ready report that explains which watched URLs are indexed, blocked, newly risky, or fixed since the last reporting period.

Best for: SEO account managers, agency owners, and client stakeholders.

Try this report API docs All examples

Monthly Indexation Brief Client Reporting

100Tracked URLs

4Critical

7New Alerts

11Resolved

Item	Status	Evidence
/pricing	Critical	Noindex conflicts with expected indexable status.
/services	Review	Indexed but missing schema and entity evidence.
/locations/austin	Ready	Indexed, canonical, schema present.

What It Includes

Tracked URL count, critical blockers, alert events, and resolved issue summary
High-priority URL table with GSC state, crawl evidence, and recommended actions
Plain-English executive summary for client calls or async updates
Credit usage and data freshness notes for delivery confidence

How It Is Generated

GSC URL Inspection imports or live GSC jobs
Watchlist priority and expected indexability
Indexation snapshots, alert events, and daily history metrics
Report governance and delivery policy

API Inputs

/v1/indexation/snapshots/v1/alerts/v1/history/daily-metrics/v1/reports/client-index

MCP Uses

Ask which client URLs need the next account-manager follow-up.
Draft a client-safe explanation for each critical blocker.
Summarize what changed since the last report.

Ways People Use It

Monthly Client Update Agency account manager

Pull critical URL changes before a recurring client call and paste the summary into a client report.

The client sees what changed, which pages matter, and what action the team recommends.

MCP Call Prep SEO consultant

Ask an assistant to explain newly blocked revenue pages using the same endpoint data.

The consultant gets a grounded talk track instead of manually stitching GSC and crawl notes.

Executive Rollup Agency owner

Group all client workspaces by critical blockers and reports due this week.

Leadership can see which accounts need attention before clients ask.

Evidence Contract

The live API returns the issue plus the evidence around it: what happened, where it happened, when it was observed, why it matters, and how to act.

Question	Where It Comes From	Example
What	Issue ID, severity, message, schema, crawl, or GSC state	`jsonld_invalid`, `schema_missing`, `noindex_detected`
Where	URL, site, client, final URL, JSON-LD block index, or endpoint row	`/pricing`, block `0`
When	`generated_at`, `fetched_at`, event timestamps, and history metrics	Last observed during the current refresh.
Why	Evidence fields, parse errors, HTTP status, GSC verdict, and crawl facts	JSON parse error, noindex header, sitemap leak, or canonical conflict.
How	Recommended actions and MCP or report prompts	Fix malformed JSON-LD, remove noindex, update sitemap, or consolidate canonical.

For malformed JSON-LD, the API records the affected page, fetch time, invalid block index, parser error, issue severity, and recommended action. It intentionally avoids storing raw page payloads unless a future redacted evidence store is enabled.

Example API Flow

curl.exe -H "Authorization: Bearer YOUR_API_TOKEN" https://indexpulseapi.com/v1/indexation/snapshots

MCP prompt example:
"Ask which client URLs need the next account-manager follow-up."