End-to-end, what’s the actual path that a WordPress post takes to become citable by an LLM? This article traces the journey from “Publish” button to “cited in a ChatGPT answer”, through every intermediate hop.
Standard WP workflow. Editor → Publish. The post is now live at a stable URL. WordPress’s built-in stuff fires: sitemap entry created, RSS feed updated, schema.org Article markup emitted by your SEO plugin (Yoast / RankMath / whatever).
The Suite plugin hooks into save_post. On publish, it calls back to app.aioxsuite.com via a signed REST request, telling the dashboard there’s new content to process. The dashboard queues the post for processing (immediately, unless you’ve configured a delay).
The 11-stage pipeline (covered in detail in another article) reads the post, classifies it, extracts entities, infers intent, assembles a schema.org JSON-LD, merges licensing, signs, and pushes the resulting Capsule back to the Suite plugin.
The Capsule is now stored on your WordPress server and served from /aiox-capsule/{slug}/. The site-wide manifest at /aiox.json is updated to list the new Capsule with its modified timestamp.
Concurrently, the Suite plugin updates the rendered HTML of the post itself: enriched schema.org JSON-LD is embedded in the <head>, TDM-REP headers are added to the HTTP response, and a discovery link points to the Capsule URL.
This is the part you don’t control directly. The major AI crawlers operate on their own schedules:
Someone types “What’s the best Y for use case Z?” into ChatGPT, or Gemini, or Perplexity. The LLM either:
If the LLM cited you with a link (Perplexity always does; ChatGPT Search usually does), the user can click through to your site. That’s referral traffic. AIOX tracks it via UTM parameters.
If the LLM only used you to inform the answer without citing — also useful, but harder to measure. The AI Visibility Score is how you measure that less-tangible visibility.