Publishing articles
Taking a RankX AI article live on WordPress or a Shopify blog. What publishing writes, how every field is verified, and how edits stay safe.
Publishing takes a reviewed article from Content Studio to a connected WordPress site or a Shopify blog. RankX AI writes the post, writes its SEO title and meta description through the site's SEO plugin, and then reads every field back, so the result names exactly what landed.
A person decides when an article goes live. An article publishes when someone asks for it from its own screen, or on a schedule when a Website runs Content Autopilot in publish mode. A staff member's Publish approves and publishes in one action unless the Website requires approval first, and an edit to an existing page shows you exactly what it will do before it runs.
Before you publish
Three checks, in order, and the first one saves the most time:
Can this page be written at all? RankX AI probes what your site supports and reports whether each content type is editable, whether SEO fields are writable and whether a page builder is in use. Ask for that first; everything below reads differently once you know.
Is the draft reviewed? The quality and GEO gates tell you what to fix, and they are cheaper to act on before the page exists. See content quality scores.
Where does this site keep its SEO fields? The answer depends on your SEO plugin, and RankX AI tells you which case you are in and how to make the fields writable. See the WordPress integration.
What publishing writes
RankX AI's publish sheet asks where, when and as whom. Publish now is the first choice, Schedule for later sets a time in the Website's own time zone, and Save as a draft puts the post on the site without making it live.
One publish sets the whole post: title, body, excerpt, slug, categories and tags, featured image and author, then the SEO fields and, on WordPress, the article's structured data. A term the site does not have yet is offered as "Create", and only your click creates it.
The SEO title and meta description go through your SEO plugin. RankX AI writes them through Yoast, Rank Math or SEOPress where the plugin exposes them, and through any SEO plugin, All in One SEO included, on a site running the optional RankX AI plugin. On a site with no SEO plugin, the meta description is saved as the post excerpt, and the RankX AI plugin can print it as the meta description.
The body is converted faithfully. Canonical block markup is passed through untouched. Plain semantic HTML is converted to blocks. Anything the converter cannot map is preserved verbatim in a raw HTML block and reported, never dropped with a warning.
Every field is verified by reading the object back, not by a success response. Plugins that return success while persisting nothing are common enough that a status code proves nothing. The result lists each field (body, SEO title, meta description, schema, featured image, categories and tags, author, slug) as verified, written, not writable, failed or skipped, and a write RankX AI cannot confirm is reported as unverified rather than as success.
Publishing to a Shopify blog
RankX AI publishes to a Shopify blog through the same engine and the same read-back. The sheet picks the blog (the one this store last published to, or its only blog), takes tags as words and the author as a name, and writes the SEO title and description to the article's own search fields. Your Shopify theme prints the article's structured data itself.
On Shopify an article is published now or saved hidden on the store. Scheduling for a later time is offered on WordPress sites.
After an article is live
From the article's own screen you can update the live post with your latest edits, unpublish it, cancel a schedule, or publish a scheduled article now. An update on Shopify checks first for an edit made in Shopify admin since RankX AI's last write, and asks before overwriting it.
Publishing twice by accident
Content Studio publishing guards against duplicates itself. Each publish is claimed once, the create is keyed to the article and the site, and a create whose outcome was uncertain is looked up on the site before anything is sent again. A second press of Publish cannot create a second post.
The raw MCP tool wp_create_content is different. It creates a post directly,
outside Content Studio, and it is idempotent only when asked. Pass an idempotency
key and a repeat of the same call returns the original post, creating nothing.
Without one, two calls create two posts. So if you are driving wp_create_content
from a script or an assistant and you are ever unsure whether a call landed,
list the content and look before retrying.
Updating an existing page
Different tool, different risk, and getting this wrong is the expensive mistake.
Prefer a targeted patch for any edit to an existing page. It changes exact text inside existing blocks and nothing else, so it is safe on a long page and far cheaper than resending the whole body. If any of its edits fails to match, nothing is written at all.
A whole-body update replaces the body. That makes it unsafe after a truncated read: a very long body comes back truncated and says so, and sending that back would delete the part you did not see.
Adding, moving or removing a whole block is a third operation, with a free outline action that lists every block first. A text patch cannot do it and refuses rather than trying.
Pages built with a page builder
RankX AI protects every page's layout, and there are three tiers:
| The page is | What is possible |
|---|---|
| Plain Gutenberg | Replace the body, or patch specific text |
| A block-based builder | Targeted text patches, and adding or removing a block, each asked for explicitly |
| A meta-based builder (Elementor, Divi and similar) | Protected. Edit the body in the builder itself; every body write from a tool is refused |
An unrecognised builder is treated as the most restrictive tier deliberately, so the guard keeps working for a builder RankX AI has never seen.
After the write
A verified write means RankX AI confirmed the change in the database through the REST API. It does not mean your visitors see it yet: a page cache in front of your site can serve the old version, and RankX AI appends a note saying exactly that to every successful content and SEO write.
If a write reports as unverified, check the object in wp-admin. It may have landed and been unreadable behind a cache, or the plugin may have accepted and discarded it, which is the case this check exists to catch.
Driving this from an assistant
Publishing a Content Studio article over MCP takes two tools, and the order is
the safeguard. approve_content_item records the person's sign-off, which is free
and changes nothing on the site. publish_content_item then sends the approved
article to a WordPress site as a draft, scheduled for a later time, or
published now, and it refuses an article nobody has approved. A Shopify blog
is published from the article's screen in Content Studio.
"Show me content item X. If I approve it, publish it to my site as a draft and tell me which fields were verified."
Publishing spends no credits. It returns straight away and carries on in the
background, and get_publication_status reports each field as verified, written,
not writable, failed or skipped. An unconfirmed state means the write may have
landed and could not be read back: check the site, and do not publish again.
Edits to pages that already exist are different: every one of those dry-runs by default, and the dry run runs the identical pipeline as the real write, so its warnings are the warnings the write will produce. See the WordPress tool reference.
Where to go next
- The WordPress integration, for connecting and for the SEO plugin detail.
- The Shopify integration, for connecting a store.
- Writing articles, for what gets published.
- Troubleshooting connections, when a write is refused.
Last updated
Content quality scores
The two scores RankX AI puts on a generated article. What each gate checks, why they are pass or fail rather than weighted, and what a null score means.
Tasks
The prioritised board RankX AI builds from everything it finds. How tasks are created, why they are deduplicated, and what a task carries with it.