Indexing via API/IDE: submit URLs and get per-URL status

Extend the Cromojo MCP connector (currently read-only, Page Performance tools) to cover Indexing, so developers and agencies can act on specific pages directly from their IDE or AI agent (Claude Code, Cursor, Codex, ChatGPT, etc.).

What's being asked

1. Submit URLs for indexing from the IDE/agent (write access)

A new MCP tool like submit-urls-for-indexing that respects the account's daily quota.
Return which URLs were accepted vs. rejected (quota exhausted, invalid, etc.).

2. Per-URL indexing status (read access, more granular than bulk)

Not just "X indexed / Y pending / Z not indexed" counters, but a URL-by-URL view returning for each URL: current indexing status, reason if not indexed, when last checked.
Matches what the September 2026 Google Indexing rebuild already shows in the dashboard — just surfaced through the MCP so IDE workflows can read it.

Why this matters

Developers and agencies working on specific pages (new product launches, blog posts, pages fixed after a redirect) need to confirm indexing one URL at a time, inside their coding workflow — not by context-switching to the Cromojo dashboard. Bulk counters don't answer "is the page I just shipped actually indexed yet?"

From a customer conversation (2026-10-09)

"Feature request on this — be great if we can submit pages (within quota) via the IDE/agent."
"Oh and URL by URL visibility of what's indexed and what isn't. That would make page work far more targeted and accurate rather than bulk numbers."

Related existing work

MCP Integration with Analytics — In Progress. The Indexing side is a parallel ask on the same MCP surface.
Graph showing indexed/deindexed pages — In Progress, 39 upvotes. Overlaps on "better visibility into indexing state", but focuses on trend charting in the dashboard rather than per-URL + programmatic access.
Google Indexing: rebuilt with per-page diagnostics (shipped Sept 2026) — already delivered per-URL visibility in the dashboard UI. This request extends the same data model to the MCP/API surface.

Suggested scope

Phase 1 (read): add get-url-indexing-status (single URL) and list-urls-indexing-status (per site, filtered) MCP tools.
Phase 2 (write): add submit-urls-for-indexing MCP tool, quota-aware, with clear accept/reject feedback per URL.