Indexing API restricted to JobPosting/BroadcastEvent + putting JobPosting schema on non-job pages is a manual-action catalyst — Splitt: "Pushing it to the API doesn't mean indexed right away or indexed at all"; Mueller: "Search is never guaranteed"

Claim: Three layered facts that together kill the "use the Indexing API for general content" pitch:

1. Scope restriction: Google's Indexing API is officially restricted to JobPosting and BroadcastEvent content (Google's Indexing API is restricted to JobPosting and BroadcastEvent content — Mueller has warned against using it for ordinary pages). Using it for general content violates policy. The API now requires approval.

2. The schema-cheat backfires: Putting JobPosting schema on non-job pages to qualify for the Indexing API is a documented manual-action catalyst — Google has applied manual structured-data spam actions against this pattern.

3. Even legitimate use doesn't guarantee indexing. Martin Splitt: "Pushing it to the API doesn't mean indexed right away or indexed at all." John Mueller: "Search is never guaranteed."

Practical bottom line for Candid: there is no legitimate Indexing API path for marketing-site content, and the workaround (schema-faking) is actively dangerous.

Source: Google Search Central documentation; Martin Splitt + John Mueller on-record statements.

Confidence: Verified.

Caveat: The IndexCheckr submission-tool test (Benchmark #11 (Single-source): IndexCheckr submission-tool test 2025 — 33,930 previously-unindexed pages submitted to indexing tools, 29.37% indexed / 70.63% remained unindexed) provides the independent-test number — 29.37% indexed even when submission tools are used — for clients who want a hard number alongside the policy reasoning. Cross-link: Rule: you cannot reliably force Google to index a page — submission tools AID discovery but do not guarantee inclusion or ranking; "Search is never guaranteed" (Mueller).