AI Search Visibility Platform
RankX AI changes your WordPress site and proves the change landed.
RankX AI connects to WordPress and WooCommerce with an application password and no plugin, reads every change back to confirm it landed, and refuses the pages it cannot safely touch.
7-day free trial. No credit card required.
2of 4 changes confirmed in the site’s own database
One could not be read back and is reported as unconfirmed, never as success. One never happened at all, because RankX AI worked out beforehand that the write would have returned a perfectly good success and changed nothing.
A change RankX AI cannot confirm is never reported as one that landed.
- verifiedDelivery and returnsRead back and compared. Your page cache may serve the old one for a while.
- verifiedShaker cabinet doorsRead back and compared. Price unchanged, before and after, and no input exists to change it.
- unverifiedWorktop care guideThe site did not answer the read back, so this is unconfirmed rather than failed. It may well have landed.
- refusedAbout the practiceBuilt with a page builder that keeps its content in its own tables. A write here would report success and change nothing.
Written through the site’s own REST API with an application password, with no plugin installed. The site, its pages and its figures are invented.
Three questions
A WordPress site raises three questions, and this page answers the hardest one.
What should be written, what happens when RankX AI writes it, and whether an assistant recommends what you sell. They are three different jobs and they have three different pages.
What to write
What is worth publishing, and what should the page say?
The brief, the draft, the internal links and the schema. RankX AI works that out from what the assistants are already answering about your market and what your own site is missing.
A page nobody asked for ranks for nothing, however cleanly it was published.
This page
Can it change my live site without breaking it?
What RankX AI can read, what it can change, what it refuses before you start, and how it proves a change landed. It connects with your site’s own REST API and an application password, and installs nothing.
This is the question people actually hesitate on, and most tools answer it by not mentioning it.
The WordPress connection in full, including what it will not do
Your products
Do assistants recommend what my shop sells?
A different measurement with a different unit: the product card rather than a mention of your name. A connected WooCommerce store is the only thing that keeps that product list current on its own.
Switched on per website, so a site that sells nothing never carries the screen.
What it reaches
19 tools reach your WordPress site, and most of them only look.
RankX AI connects with your site’s own REST API and an application password you create in your profile. There is no plugin to install, and it acts as the account you connected, so it can never do more than that account could.
What it reads first
Through your site's own REST API, as the account you connected, before RankX AI offers to change anything. It acts as that user and can never do more than that user could.
What your site actually supports
Which content types exist and are editable, which taxonomies exist, whether your SEO fields are writable, whether WooCommerce is present and whether a page builder is in use. A WordPress site only exposes what its plugins and the connected account allow, so nothing about it is assumed.
Posts, pages and every custom type
Listed, read and searched, with each row carrying whether its body can be rewritten at all. That answer travels on the listing rather than arriving as a failure after somebody has written the copy.
The blocks a page is built from
A free outline action lists every block on a page before anything is inserted, removed or reordered, so an edit names a block rather than guessing at a position.
Revisions, media and taxonomies
The revision list is what an edit can be rolled back to, and it answers plainly when a content type has none. Media comes with alt text, captions and titles; categories, tags and custom terms come as lists.
What it changes, on approval
Every write defaults to a dry run that uses the identical conversion pipeline as the real thing, so the warnings the preview produces are the warnings the write will produce. Applying is a second, explicit step.
A whole page, or one paragraph inside it
RankX AI replaces a body, or patches specific text inside a long page without rewriting the rest of it. The targeted edit leaves every other byte, every delimiter and every builder block id alone, which is why it reaches pages a full replacement is refused on.
SEO titles and meta descriptions
Where your plugin exposes them, and it tells you plainly which of the possible reasons applies when it does not. A write that could only land some of the fields you asked for is refused whole rather than sent half.
Blocks, media, alt text and terms
Blocks added, placed or removed by id. Images uploaded and alt text set. Categories and tags created and assigned. Alt text is the only description of an image an assistant or a screen reader can read.
One change across an explicit list
A bulk update runs against ids you named, never a query that might match more tomorrow, and it dry runs first like everything else. Nothing a converter cannot map to a native block is discarded: it is preserved verbatim and reported.
All of this is reachable from an AI assistant too, through 19 WordPress tools on the RankX AI MCP server, and the permissions are not one switch. The 3 product tools sit behind commerce, separately from the rest, because they return prices and stock for a whole catalogue using your stored credential. A token’s scopes are fixed when it is issued and can never be widened, and a tool outside them is not merely refused, it is not listed.
What it writes
A change to your site is read back and compared, and refused before it is attempted.
Writing to WordPress is no longer unusual. Checking that the write landed still is, and the check is the reason a page RankX AI cannot safely change is one it declines rather than one it breaks.
Refuse before the form, not after submit
RankX AI works out whether a page's body can be rewritten at all before offering to rewrite it, and reports that on every listing row rather than only on failure. A refusal that arrives after somebody has written the copy has already wasted the work it was meant to prevent.
Show the before and after first
Every change starts as a dry run, and the dry run is the same code with a flag rather than a second implementation of it. A preview that skipped the step most likely to fail would be the confident green light that causes the loss.
Read it back, past your cache, and compare
Not the timestamp on its own. WordPress does not move a page's modified time when a save changes nothing, so an unmoved timestamp means either that the content was already identical or that a page builder swallowed the write, and those are not the same event. RankX AI plants markers in what it sends and counts how many come back, which is the only signal that tells the two apart.
Say unverified when it cannot be confirmed
A change RankX AI could not read back is reported as unverified, never as success, and a read-back that failed is never filled in with a timestamp RankX AI invented. Unverified does not mean the change failed: it may well have landed, and saying so is more useful than a status code that proves nothing.
The undo is WordPress’s own, and some things have none
RankX AI builds no undo of its own for WordPress, and that is the right answer rather than a gap: WordPress creates a revision on every update where the content type supports them, so the rollback is the one already sitting in your editor, and RankX AI lists those revisions for you. The half nobody mentions is that several types have no revisions at all, including WooCommerce products, attachments and menu items. RankX AI tells you which before the change rather than after it, because an assistant about to propose an edit needs to be able to say there is no undo for this one.
A verified change is verified in your site’s database, and the read back deliberately goes past your page cache to get there. That is the right thing to check, because it is what catches a plugin returning success while persisting nothing. It does not mean your visitors see the change yet: a cache in front of your site can serve the old version for as long as its own rules say, and RankX AI appends a note saying so to every successful write rather than letting you find out on the live URL.
The honest edges
Two things depend on your plugins, and one of them cannot be fixed.
Your SEO plugin decides whether RankX AI can write a meta description, and your page builder decides whether it can touch a body at all. RankX AI probes both when you connect and tells you the answer per page, not per site.
SEO titles and meta descriptions, by plugin
| SEO plugin | Writable | What that means |
|---|---|---|
| Yoast SEO | Usually | Yoast registers its title and description for the API itself, and it does so per content type rather than per site. Measured on a real site: registered on posts and not on pages. RankX AI resolves it per type, so it will write your posts and tell you that your pages are not available rather than accepting both and dropping one. |
| Rank Math | One snippet | Rank Math stores its fields the right way and simply does not expose them to the API. Nothing about RankX AI or your account is the obstacle, and it is one registration snippet away: RankX AI detects the case, says so, and gives you the snippet with your own site's field names already in it, in the form that will parse wherever you paste it. |
| SEOPress | One snippet | The same shape as Rank Math, and the same remedy, supplied the same way. The snippet travels with the refusal, on the thing that hit the wall, rather than sitting on a different screen: the caller who hits the wall is not the one who has already been shown the door. |
| All in One SEO | No | All in One SEO keeps its data in its own database tables rather than in post meta, so no amount of registering anything helps and a write would return success while persisting nothing. RankX AI refuses instead, which is the whole difference between a limit you know about and a field you think you changed. |
Page bodies, by where the builder keeps the content
| How the page is built | Writable | What that means |
|---|---|---|
| Plain WordPress blocks | Yes | The content lives in the page body as core blocks, so RankX AI can replace the whole body or patch specific text inside it. This is the common case and the unrestricted one. |
| A block-based builder | Patches only | The content is still in the page body, in the builder's own block namespace, so a targeted text patch is possible and a whole-body replacement is not. It has to be asked for explicitly on the change, because WordPress re-validates a block when the editor next opens it and a patch that upsets that check can be rebuilt out from under you. |
| A builder with its own tables | Refused | Elementor, Divi and WPBakery are the common case: the page you see is rendered from the builder's own storage, so a write to the page body returns a perfectly good success and changes nothing a visitor sees. RankX AI lists the page as not writable and refuses, and there is no override. A builder it has never met is put in this tier too, by shape rather than by name. |
RankX AI classifies a page by where its content is stored rather than by the builder’s name, so a builder it has never met is put in the most restrictive tier by shape. That is a guarantee rather than a limitation to work around: the alternative is a page that keeps every word and silently loses its layout. RankX AI also writes no redirects on WordPress, because no common SEO plugin exposes a redirect list it can read back, and it does not ship a change it cannot check.
WooCommerce
A WooCommerce store is the same connection, with the catalogue on top of it.
There is no second setup and no API key. RankX AI probes for WooCommerce when you connect WordPress, and the product tools appear if it is there, covering 100 to 1,000 products monitored per website by plan.
What a shop gets on top
The 3 product tools, behind their own permission, plus the catalogue link into AI Shopping. Everything above still applies: the same dry run, the same read back, the same refusals.
The products too thin to sell or rank
The catalogue read comes with prices, stock status and how much description each product carries. That last column is the useful one: a product with two lines of description gives an AI shopping surface almost nothing to recommend it on, and RankX AI flags those rather than making you scan the list.
A product list that keeps itself current
A connected WooCommerce store is the only source that fills the AI Shopping product list on its own. Every other shop uploads a file. It matters more than it sounds: a product RankX AI does not hold cannot be matched, so an answer recommending it is recorded as recommending somebody else.
No price, no stock, no status, no URL
Permanent limits rather than a roadmap. The tools are given no input for any of them, so there is nothing to get wrong, and the price is reported before and after so you can confirm it did not move. Orders, customers and refunds are reads only, by construction: no write function exists to call.
A new product arrives as a draft
It cannot publish, so a human checks the price and the details in WooCommerce and publishes there. Publishing makes a product buyable, and that is not a decision to automate. A price is required on creation, because WooCommerce treats a missing price as free.
The same job on the two shop platforms
| Criterion | WooCommerce, through WordPress | Shopify |
|---|---|---|
| How you connect | The WordPress connection you already made: a site address, a username and an application password you create in your own profile. No plugin to install for it, and no second setup for the shop | Six steps in Shopify's own developer dashboard, where you create an app, paste the permissions, release the version, install it in that order and copy two credentials back |
| Tools you get | All 19 WordPress tools, 3 of them the product tools, which sit behind their own permission because they return prices and stock for a whole catalogue | 6: the store description, the product listing, a diagnostic pass, and three writes for search metadata, image alt text and redirects |
| What fills the AI Shopping product list | The connection itself. A connected store keeps the list current on its own, and it is the only source that does | A product export or a Google Merchant Center feed, read as it comes. Connecting the store reads and fixes the store; it does not fill this list |
| What an undo looks like | A WordPress revision on posts and pages. Products have none at all, and RankX AI says so before the write rather than after it | Nothing on the platform side. Shopify keeps no revisions for any object type, so the value RankX AI read immediately beforehand is the whole of the undo |
| Where Shopify is ahead | No SEO plugin on WordPress exposes a redirect list RankX AI can read back, so it writes none. A page cache in front of the site can serve the old version after a verified write | Redirects are a readable object, so RankX AI creates them. And a store publishes enough to anonymous agents that RankX AI can grade it before you connect anything at all |
Both platforms are supported and neither is going anywhere. If you are choosing, the difference is the door rather than the destination: a WooCommerce store is already through the one connection you made, where a Shopify store gets 6 tools behind six steps in a developer dashboard. The Shopify side has its own page, including the two things it does that WordPress cannot: how the Shopify integration reads and writes your store.
Connecting
Connecting a site takes 4 steps, and none of them installs anything.
An application password ships with WordPress and lives in your own profile. Revoking it is the whole of disconnecting, and every call afterwards fails cleanly.
Open your own WordPress profile
In wp-admin, Users, then your own profile. Application passwords are per user rather than per site, so create it on the account you want RankX AI to act as. That account's capabilities are the ceiling on everything below.
Create an application password
Scroll to Application Passwords and give it a name you will recognise later, such as RankX AI. WordPress shows the password once, in groups separated by spaces, and you copy the whole thing including the spaces. Lose it and you revoke that entry and make another.
Paste three fields into RankX AI
The site address, the WordPress username rather than the email address, and the application password. That is the whole credential: there is no plugin to install, no OAuth app to register and nothing for anyone to review.
Let RankX AI describe the site
It immediately probes what your site actually supports: which content types are editable, which taxonomies exist, whether your SEO fields are writable, whether WooCommerce is present and whether a page builder is in use. That probe is why nothing afterwards has to guess.
Two things are worth checking before you start, and both are your site rather than RankX AI. Some security plugins disable the REST API, and some hardening plugins switch application passwords off; both ship enabled in WordPress itself. The full walkthrough, and what to do when a connection stops answering, is in the WordPress integration documentation and the connection troubleshooting guide.
Questions
What people ask before letting software touch a live site.
Direct answers, including the three where the honest answer is no.
Do I have to install a plugin to connect WordPress?
No. RankX AI connects over your site's own REST API with a WordPress application password, which ships with WordPress and is on by default. You create it in your profile, paste it in with your site address and username, and that is the whole credential: no plugin, no OAuth app, nothing for anyone to review and nothing running on your server. Revoking that application password is the whole of disconnecting, and every call afterwards fails cleanly. The one thing worth checking first is whether a security plugin has switched the REST API or application passwords off, because some do.
How do I know a change actually landed on my site?
RankX AI reads the object back and compares it with what it sent, and a change it cannot confirm is reported as unverified rather than as success. The comparison is not just the page's modified time, because WordPress does not move that when a save changes nothing, so an unmoved timestamp means either that the content was already identical or that a page builder quietly swallowed the write. RankX AI plants markers in what it sends and counts how many come back, which is the signal that tells those two apart. Plugins and platforms that return a perfectly good success while persisting nothing are common enough that the check is the point.
Can I undo something RankX AI changed?
On posts and pages, yes, and with WordPress's own revisions rather than anything RankX AI invented: WordPress creates a revision on every update where the content type supports them, so the rollback is the one already in your editor, and RankX AI lists those revisions for you. The honest half is that several types have no revisions at all, including WooCommerce products, attachments and menu items, and RankX AI says which before the write rather than letting you find out after it. Every change and every refusal is also recorded in an append-only log, so what was changed and when always has an answer.
Will it write my SEO title and meta description?
It depends on your SEO plugin, and there are three different answers rather than one. Yoast usually works and it varies by content type, so RankX AI resolves it per type and will write your posts while telling you your pages are unavailable rather than accepting both and dropping one. Rank Math and SEOPress store their fields correctly and simply do not expose them to the API, which is one snippet away: RankX AI detects that, says so, and supplies the snippet with your own field names in it. All in One SEO keeps its data in its own tables and cannot be written at all, so RankX AI refuses rather than returning a success that changed nothing.
What happens to my Elementor or Divi pages?
They are listed as not writable and a body write is refused, with no override. A page built that way renders from the builder's own storage rather than from the page body, so a write to the body returns a perfectly good success and changes nothing a visitor sees, which is the worst outcome this integration can produce. RankX AI classifies a page by where its content is stored rather than by the builder's name, so a builder it has never met is refused too. A builder that keeps its content in the page body is different: targeted text patches work there, asked for explicitly on the change.
My visitors still see the old version. Did the write fail?
Almost certainly not. A verified write means RankX AI confirmed the change in your site's database, reading past your page cache to do it, and that is the right thing to verify because it is what catches a plugin returning success while persisting nothing. It does not mean your visitors see it yet: a cache in front of your site can serve the old version for as long as its own rules say. RankX AI appends a note saying exactly that to every successful content and SEO write rather than letting you discover it on the live URL.
Does my WooCommerce store need anything extra?
No, and that is the part worth knowing before you compare platforms. WooCommerce is reached through the same WordPress connection, so there is no second setup, no second credential and no API key: RankX AI probes for WooCommerce when you connect and the product tools appear if it is there. You get all 19 WordPress tools, 3 of them product tools behind their own permission, and a connected store is the only thing that keeps an AI Shopping product list current on its own. It changes no price, no stock level, no status and no product URL, and it is given no input for any of them.
Which of this can an AI assistant do through MCP?
All of it, through 19 WordPress tools on the RankX AI MCP server, and the permissions are not one switch. The 3 product tools sit behind commerce, separately from everything else, because they return prices and stock for a whole catalogue using your stored credential. A token's scopes are fixed when it is issued and cannot be widened later, and a tool outside them is not merely refused, it is not listed. Eleven tools across the product are also permanently out of the in-app assistant's reach at any approval level, including every WordPress body write.
Is a WooCommerce store better served than a Shopify store?
On this integration, yes, and the difference is worth stating plainly rather than selling. A WooCommerce store connects once through WordPress and gets 19 tools; a Shopify store takes six steps in Shopify's developer dashboard and gets 6. Shopify is ahead in two places that matter: RankX AI creates redirects there and cannot on WordPress, because no WordPress SEO plugin exposes a redirect list it can read back, and a Shopify store publishes enough to anonymous agents that RankX AI can grade it before you connect anything at all. Neither platform is abandoned and both are supported. If you are choosing, the table above is the difference.
More detail in the WordPress documentation, the catalogue half in WooCommerce, and the other shop platform in Shopify.
Start here
See where you show up in AI answers today.
Add your site and RankX AI suggests the prompts to track, monitors the keywords that matter and audits your pages, with your first results minutes after you finish setup.
7-day free trial. No credit card required. Cancel anytime.