Push a finished cluster into WordPress, write schema into a Shopify store, export it as Markdown for the repo, or let an agent drive the whole thing over MCP. Six real routes, one deployment spine — and Inciteful checks the published page itself before it calls it live.
7-day trial, no card. No connector is required to start — exports work on every plan.
WordPressDiscontinued 11 September 2026. The WordPress connector is no longer offered or supported. Pages are built by your own LLM from the action plan and reported back over MCP, the CLI or a link.
The Inciteful Connector plugin registers a client site against your account. Pushing a cluster nudges the site to pull it, so pages arrive as native Gutenberg blocks with the meta title, description and JSON-LD already attached.
How the push works
ShopifyDiscontinued 11 September 2026. The Shopify app is no longer offered or supported. AI Shopping, the module that tracks product-level answers, continues.
Listed on the Shopify App Store. Optimising a product or collection writes Inciteful’s JSON-LD into metafields, rendered server-side by a theme app extension — so AI crawlers, which do not run JavaScript, read it in the raw HTML.
That catalog workflow is AI Shopping. Content v2 separately publishes approved web-content clusters as generic Shopify Pages; it does not mutate Product or Collection resources.
See AI ShoppingMarkdown, standalone HTML, a WordPress WXR import file, or the full implementation pack with per-page schema — from the app, the API or the CLI.
Every formatA Bearer-key REST surface over the same engine: list clusters, pull pages, run exports and publish — everything the app does, scriptable.
API referenceOne zero-dependency file you curl onto your PATH: list clusters, sync content into a directory, read Site Health findings, run the audit.
CommandsA Model Context Protocol server, so an agent in the client’s own repo can pull a cluster as Markdown, push it live and read the citation evidence afterwards.
The tool listNo Zapier, no analytics importer, no logo wall of things we have not built. This list is the whole list, and every cell on it is running today.
Connect Inciteful as an MCP server with a key from Account, and the agent working in the client’s repository can read the measurement and ship against it.
claude mcp add --transport http inciteful \
https://tryinciteful.com/api/mcp \
--header "Authorization: Bearer inc_live_YOUR_KEY"The CLI is a single file over the same API. There is no install step beyond downloading it, and no runtime to keep current.
curl -fsSL https://tryinciteful.com/inciteful -o inciteful
chmod +x inciteful
./inciteful login
./inciteful sync --out ./contentNothing generated here is locked in a dashboard. Every cluster leaves in the shape your client’s stack actually wants, unbranded, on every plan — including the plan you are trialling.
If a client has no plugin access at all, the WXR file imports through WordPress’s own Tools menu. The plugin route is still better: it keeps the schema and re-syncs by slug.
| markdown | One .md per page with frontmatter, plus llms.txt, a linking map and an index — built for static-site generators. |
|---|---|
| html | Standalone styled pages with the JSON-LD embedded, paste-ready for any builder. |
| wordpress | A WXR import file for Tools, then Import. |
| full | The implementation pack: every format above plus per-page meta, Gutenberg blocks and schema files. |
WordPress, Shopify, the CLI, the API, MCP and a manual export all record the same thing: which cluster went live, where, and by which route. That is what makes the loop measurable rather than anecdotal.
And Inciteful does not take your word for the URL. A connector reports candidate addresses; a read-only verifier fetches each one and checks the content is genuinely there before the deployment advances to live and its questions join tracking. A URL that fails stays visibly recorded with its evidence, ready to retry.
No. Tracking, reporting and generation all work with nothing connected — you can export the pages and hand them to whoever builds the site. The connectors exist to remove the copy-and-paste step, not to gate the product.
Export or the API. Markdown plus llms.txt and a linking map drops into any static-site generator; the HTML export is paste-ready; the full pack carries the schema files. Then record where it went live and tracking picks it up like any other route.
No, and deliberately not. Hosting client content on tryinciteful.com was retired: pages that should build the client’s authority belong on the client’s domain. Our own answer library stays our own product identity, and client content can never redefine it.
You do. Exports are unbranded on every plan, the files are yours to edit, and there is no Inciteful attribution requirement on published pages.
One inc_live_… key, minted by the account owner and shown once. It is stored hashed, can be revoked at any time, and is sent as a Bearer token. MCP accepts only that key — never a browser session.
Yes. Inciteful writes only into its own metafields and keeps a ledger of exactly what it wrote. Revert removes those and nothing else — no other store data is touched, and a write only ever happens on an explicit action.
Start a 7-day trial, no card. Connect one site and push a cluster the same afternoon.