WordPress
Connect WordPress to RankX AI in one click or with an Application Password, add the optional free plugin, and see what RankX AI can write and how it checks.
RankX AI connects to WordPress through the site's own REST API and a WordPress Application Password. In one click, you type your site's address, approve RankX AI on WordPress's own approval screen and come back connected, with nothing to copy or paste. Creating an Application Password by hand works too.
Once connected, RankX AI reads your content, proposes changes and applies them, and verifies every write by reading the object back. No edit is applied without a dry run first, and no article is published without being approved first. For what RankX AI does for a WordPress site before you sign up, see RankX AI for WordPress.
What is a WordPress Application Password?
A WordPress Application Password is a separate password that lets a third-party app authenticate REST API requests as one user, without your main login. WordPress core has included them since version 5.6.
Each one is unique to the app it was created for, has the access of the user who created it, and can be managed and revoked on its own in the user's profile. WordPress states that Application Passwords cannot be used for traditional logins, so a third-party app holding one cannot sign in to wp-admin. That is why RankX AI uses Application Passwords: it is the secure way for a site owner to grant access to a third-party app without sharing an admin login.
What do I need before connecting WordPress?
- A WordPress site served over HTTPS, with the REST API reachable. The REST API is on by default; some security plugins block it.
- Application Passwords enabled. They are on by default over HTTPS, but some security plugins disable them; enable them again in that plugin's settings. Both ways of connecting rely on them.
- An account on the site with the capabilities you want RankX AI to have. RankX AI acts as that user and can never do more than that user could.
How do I connect WordPress in one click?
Enter your site's address
In RankX AI, open Settings, then Integrations, and choose to connect WordPress. Type the address and press Check. RankX AI asks the site what it supports, so the next screen shows what is true for that site.
Approve RankX AI on WordPress's own screen
Press Approve in WordPress. Your own wp-admin opens (sign in if WordPress asks), and WordPress asks whether to approve the connection. Approve it on the account you want RankX AI to act as.
Come back connected
WordPress returns you to RankX AI with the connection made, and RankX AI tests it and
checks what the site supports. The approval appears in your WordPress profile under
Application Passwords, named RankX AI, which is also where you revoke it.
One-click approval is WordPress's own authorisation screen, so RankX AI never sees your WordPress login. WordPress generates the Application Password when you approve and hands it to RankX AI directly.
A host or security plugin can switch the screen off; RankX AI then says so and the manual route below works instead. The manual route also suits an agency that holds a credential for a client's site without a wp-admin session there.
How do I connect with an Application Password instead?
Open your WordPress profile
In wp-admin, go to Users, then Profile. Application Passwords belong to a user, so create it on the account you want RankX AI to act as.
Create a new Application Password
In the Application Passwords section, type a descriptive name you will recognise
later, such as RankX AI, and press Add Application Password.
Copy the password straight away
WordPress shows the new password once, in groups of four characters separated by spaces. Copy all of it; it works with or without the spaces. If you lose it, revoke that entry and generate another.
Paste it into RankX AI
In RankX AI, open Settings, then Integrations, choose to connect WordPress, and choose Enter an Application Password instead. Fill in a connection name, the site URL, the WordPress username and the Application Password, then press Test on the new connection to verify it. If the test fails, the error message names the cause; see troubleshooting connections.
What does RankX AI check when it connects?
RankX AI probes what your site actually supports as soon as the connection is tested: which content types exist and are editable, which taxonomies exist, whether SEO fields are writable for each content type, whether WooCommerce is present, whether a page builder is in use, and whether the RankX AI plugin is installed.
That probe is why nothing later has to guess. A WordPress site only exposes what its plugins and the connected account allow, so nothing about it can be assumed.
What can RankX AI do once WordPress is connected?
| Area | What it does |
|---|---|
| Content | List, read and create posts, pages and custom post types. Update title, body, excerpt, slug, categories, tags and featured image |
| Targeted edits | Change specific text inside an existing page without rewriting the rest of it |
| Blocks | Add, place or remove whole blocks, with a free outline that lists every block first |
| SEO metadata | Set the SEO title and meta description, where your SEO plugin exposes them or on any site with the RankX AI plugin |
| Media | List images, upload new ones, and set alt text, caption and title |
| Taxonomies | List and create categories, tags and custom terms |
| Bulk | Apply one change across an explicit list of IDs, dry run first |
| Structured data | Read every schema a page carries, and add, replace or remove one through your SEO plugin, dry run first |
| Redirects | Read your redirects and 404 log, and redirect a genuinely missing address through the Redirection plugin, Rank Math or the RankX AI plugin, dry run first |
| SEO coverage | Check which SEO features the site actually prints, as a visitor sees them, whatever SEO plugin it runs |
| Publishing articles | Send an approved Content Studio article to the site as a draft, scheduled or live, with every field verified |
| Site settings | Read settings, menus, users, comments, widgets, templates, plugins and themes. Change a small set of site settings and moderate comments |
| Revisions | List a page's WordPress revisions, which is what an edit can be rolled back to |
Every one of those is also an MCP tool, and that is how most of it gets used: you ask an assistant, it dry runs (or, for an article, you approve it), you look, and it applies.
What rules does every WordPress write follow?
- Every write is verified by reading the object back. RankX AI writes, re-reads and compares. A write it cannot confirm is reported as unverified, never as success, because plugins that return HTTP 200 while saving nothing are common. The read-back bypasses your page cache, without which a good write would look failed on most managed hosts.
- A write can be refused before it is attempted. RankX AI checks whether a page's body can be rewritten at all before offering to, and shows that on every listing row rather than only on failure.
- Nothing you send is discarded. Content the converter cannot map to native blocks is kept verbatim in a raw HTML block and reported.
- Every edit defaults to a dry run. The dry run uses the same conversion as the real write, so its warnings are the warnings the write will produce. Applying is a second, explicit call. Publishing a Content Studio article needs the article approved instead.
How does RankX AI handle page builders?
RankX AI sorts every page into one of three tiers by how its content is stored, and tells you which.
| The page is | Where its layout lives | What RankX AI can do |
|---|---|---|
| Plain block editor (Gutenberg) | The page body, in core blocks | Replace the whole body, or patch specific text |
| A block-based builder | The page body, in the builder's own blocks | Targeted text patches, and adding or removing a block, each asked for explicitly |
| A protected builder | Builder data that plain blocks cannot represent | Protected. Edit it in the builder itself; every body write from a tool is refused, so the layout stays intact |
Elementor, Divi and WPBakery are the common protected builders. A page built with one of them is listed as not writable and refuses a body write, with no override from MCP. That protects the page from keeping every word and silently losing its layout.
An unrecognised builder is treated as protected rather than plain, deliberately, so the guard keeps working for a builder RankX AI has never seen.
Editing a block-based builder page has to be asked for explicitly on the change. It is never automatic, because WordPress re-validates a block when the editor next opens it. Protected builder pages are refused whatever you ask for.
Which SEO plugins can RankX AI write to?
With the RankX AI plugin installed, RankX AI writes the SEO title and meta description whatever SEO plugin you run. Without it, writability depends on how your SEO plugin stores those fields and whether it exposes them to the WordPress REST API, and RankX AI checks that for you per content type.
| SEO plugin | Writable without the RankX AI plugin? |
|---|---|
| Yoast SEO | Usually, and it varies per content type. RankX AI resolves it per type, because a site can be writable on posts and not on pages |
| Rank Math | Not by default, because its fields are not exposed to the WordPress REST API. A short registration snippet makes them fully writable |
| SEOPress | Same as Rank Math |
| All in One SEO | No. It keeps its fields in its own database tables rather than post meta, so RankX AI writes them through the RankX AI plugin and refuses without it rather than appearing to succeed |
| Any of them, with the RankX AI plugin | Yes, on Yoast, Rank Math, SEOPress, All in One SEO, The SEO Framework, or a site with no SEO plugin, with no snippet to add. RankX AI still reads every value back |
When fields are not writable, RankX AI tells you which reason applies. Where the fix is a registration snippet, it gives you the snippet with your site's own field names in it, on the tool that met the refusal. If a site that was writable stops being writable, RankX AI names that as a regression rather than asking you to apply a snippet you already applied.
The snippet deliberately leaves out two fields. It does not expose the robots field, because declaring the wrong type for it can stop a post opening in the editor. And it does not expose the focus keyword, because a field readable over the REST API is publicly readable, which would publish every page's target keyword.
What does the optional RankX AI plugin add?
The RankX AI plugin is a free, optional companion plugin that runs beside your SEO plugin and extends what the connection can do. Every feature above works without it. Installed, it adds:
- SEO title and meta description through every major SEO plugin, or on a site with none, with no registration snippet. It also writes the Open Graph and Twitter title and description, which the WordPress REST API cannot write on any site.
- Redirects with Rank Math, or with no redirect plugin. It adds redirects to Rank Math's own Redirections list, or keeps them itself and answers only for addresses that would otherwise show "page not found". With the Redirection plugin, no RankX AI plugin is needed for redirects.
llms.txt,agents.mdandai.txtserved from your site's root, published from RankX AI in one click. A file or plugin that already serves one of those addresses keeps it, and RankX AI tells you which.- A Markdown copy of each page for AI assistants, off until you switch it on, kept
out of search results, and never made for a page marked
noindex. - A count of the AI crawler visits that reach WordPress, switched on by the site's administrator in the plugin's own screen. RankX AI shows the counts on AI Readiness beside which assistants cite your pages. A page cache or firewall that answers a crawler first serves visits WordPress never sees, so treat the counts as a floor.
- Site checks and View as AI in the plugin's own RankX AI menu in wp-admin, including what an assistant is given for each post and page.
How do I install the RankX AI plugin?
The plugin is a free download from inside RankX AI, installed with WordPress's own upload screen.
- In RankX AI, open the Website's WordPress settings and the Connection tab. On a connected site without the plugin, choose Download the plugin.
- In wp-admin, go to Plugins, then Add Plugin (Add New Plugin before WordPress 6.8), then Upload Plugin.
- Choose the file, press Install Now, then Activate Plugin.
- Back in RankX AI, press Test to confirm RankX AI can see it.
New versions then appear on your Plugins screen with the usual update link.
What does a verified write mean?
A verified write means RankX AI confirmed the change in the WordPress database, through the REST API. That is the check that catches a plugin returning success while saving nothing.
It does not mean your visitors see the change yet. A page cache in front of your site can serve the old version for as long as its own rules say, and RankX AI adds a note saying so to every successful content or SEO write.
How do I disconnect WordPress?
Revoke RankX AI's entry under Application Passwords in your WordPress profile.
One-click approval names that entry RankX AI; on the manual route it carries the
name you gave it. RankX AI holds no other credential for your site, so every later
call fails cleanly.
Remove the connection in RankX AI too, on the Connection tab of the Website's WordPress settings, so the Website stops offering publishing actions that can no longer work.
Where to go next
- WooCommerce, which uses the same connection.
- The WordPress MCP tools, for driving all of this from an assistant.
- Publishing to WordPress, for the content workflow.
- Troubleshooting connections, when something stops answering.
Questions
Is it safe to give RankX AI a WordPress Application Password?
An Application Password only works for API requests such as the REST API, never for logging in to wp-admin, and you can revoke it at any time. RankX AI acts as that one user and can never do more than the user could.
Why is the Application Passwords section missing from my profile?
WordPress offers Application Passwords on sites served over HTTPS, and some security plugins switch them off. Check the site loads over HTTPS, then check your security plugin's settings.
Do WordPress Application Passwords expire?
No. An Application Password works until you revoke it in your WordPress profile, which is also how you disconnect RankX AI.
Do I need the RankX AI plugin to connect WordPress?
No. The connection uses WordPress's own REST API and an Application Password. The free RankX AI plugin is optional and adds SEO fields for every major SEO plugin, redirects and llms.txt.
Which WordPress user should I connect as?
One with the capabilities you want RankX AI to have, usually an Editor or Administrator. RankX AI can never do more than that user could.
Last updated