CitationBench provides a REST API to bulk-publish programmatic content directly to WordPress and auto-indexes every page via GSC and IndexNow on publish.
# Publish a landing page to WordPress via REST APIPOST /v1/produce/publish/send> { "content_id": "lp_9xk3m", "platform": "wordpress",> "workspace_id": "ws_acme", "auto_index": true }✓ Published · post_id: 4821 · url: acme.com/landing/seo-tools# Auto-indexing fires immediately on publish✓ GSC submission queued · url: acme.com/landing/seo-tools✓ IndexNow submitted · engines: bing, yandexPublishing programmatic content manually across client sites creates bottlenecks, indexing delays, and consistency failures that compound at scale.
Pages go live but never get submitted to Google, leaving newly published content invisible in search for days or weeks.
WordPress plugins and manual dashboards cap throughput at dozens of pages, not thousands needed for programmatic SEO campaigns.
Managing separate WordPress credentials, staging environments, and publish workflows across ten or more client sites consumes the entire team.
The fix
CitationBench exposes a REST API and hosted MCP server to publish to WordPress, Ghost, or custom webhooks via produce.publish.send, then automatically fires GSC and IndexNow submissions so every page is crawlable the moment it goes live.
Five purpose-built capabilities covering content generation, multi-platform publishing, auto-indexing, and scale operations for programmatic SEO workflows.
Publishing API
Send content to WordPress, Ghost, Wisp, or custom REST webhooks from a single produce.publish.send call. Per-workspace platform credentials, test-connection endpoint, and depublish supported.
Indexing
Every produce.publish call automatically triggers Google Search Console URL submission and IndexNow simultaneously. No manual step, no page left waiting to be discovered.
Content at Scale
Programmatically generate landing pages from keyword and pillar schema via produce.landing_page.create. Scales from 1 to 10,000 pages and feeds directly into the publishing pipeline.
Agency Architecture
One master API key scopes all publish calls per client via the X-Workspace-Id header. Workspace-level WordPress credentials, campaign isolation, and bulk actions across all client sites.
Search Console
Submit any URL to Google Search Console programmatically via indexing.gsc.submit. Manage GSC connection and config per workspace. Returns submission status and full history.
How it works
An `sk_test_*` key lands in your dashboard instantly. No demo gate — start calling real endpoints with shape-complete responses.
`claude mcp add citationbench https://mcp.citationbench.com/mcp` from Claude Code, Cursor, or any MCP client. Or `curl` against `api.citationbench.com/v1/*` directly.
Every tool returns shape-complete demo data without auth, so your agent works before the user signs up. Tools across research, production, indexing, link-building, and agents.
Add `X-Workspace-Id: ws_***` to scope per client. Switch to a live `sk_live_*` key when you're ready. Same API surface, same SDK.
Why CitationBench
Hosted at mcp.citationbench.com/mcp. Works with Claude Code, Cursor, Claude Desktop, Windsurf, and ChatGPT Apps. No self-hosting required.
Every long-running call runs on Cyclonic workers — survives restarts, cancellable, resumable, streams via SSE. Production-safe by default.
One master API key, N client workspaces. Switch with a single `X-Workspace-Id` header. Per-client data isolation, bulk ops across all of them.
Every endpoint responds in shape-complete demo mode without auth, so you can build the agent before the user signs up.
FAQ
Automate bulk WordPress publishing with auto-indexing built in, so every page you publish gets discovered immediately.
Start Free