Connect WordPress to AltoRank
WordPress authenticates with a application password that you create and can revoke yourself. Connecting it makes WordPress an available destination — it does not give AltoRank permission to publish. That still takes a person approving the draft.
What you will need
Setup
- 1 Create the credential in WordPress
Go to WordPress admin → Users → your profile → Application Passwords. AltoRank never asks for your WordPress login: you create a scoped credential there and paste it here, so revoking our access later is one click on your side and does not change how you sign in.
- 2 Add the connection in AltoRank
In your workspace, open Integrations, choose WordPress, and fill in site url, username, application password. The connection is tested before it saves, so a wrong value fails here rather than silently at publish time.
- 3 Approve an article
Nothing publishes on connection. Open a draft, read the fact-check verdict, and approve it. Only then does AltoRank call WordPress. You can also turn on automatic publishing for the workspace, which ships after a hold you can veto; either way there is no agent route around the approval.
What approving does in WordPress
Worth knowing
- An application password is revocable on its own, so removing AltoRank’s access never means changing your WordPress login.
- The user you name is the post author, so give it a role that can publish posts.
- Self-hosted WordPress and WordPress.com Business both expose the REST API this uses; the cheaper WordPress.com tiers do not.
- The connector does not write into Yoast, Rank Math or other SEO-plugin fields. If your plugin does not read the excerpt, set the SEO title and description in the plugin after publishing.
The adapter behind this page is apps/web/lib/cms/wordpress.ts . If this page and that file disagree, the file is right and the page has a bug.
Common questions
Does AltoRank publish to WordPress automatically?
Only after a person approves the specific draft. Connecting WordPress removes the copy-and-paste step; it does not hand over the decision. The publish path requires an approval recorded under a person, by click or by the rule they set, and the MCP server exposes no publish tool, so this holds even when an AI agent is driving the product.
What WordPress credentials does AltoRank need?
Site URL, Username, Application password. Application password. Nothing else, and never your WordPress account password.
Can I publish to WordPress as a draft instead of live?
Not from AltoRank: the review happens here, before anything is sent, so approving is the act of publishing. On approve, Creates a post through the REST API with status "publish", so it is live at once. The meta description is stored as the post excerpt and the slug is the one you approved. If you want a staging destination, connect Notion as well and approve there first. Unpublishing is available afterwards: Sets the same post back to draft. Nothing is deleted.
Can I revoke access without breaking my site?
Yes. The credential is created in WordPress and revoked there, independently of your login. Revoking it stops AltoRank publishing and changes nothing else. Articles already published stay where they are: they are ordinary content on your platform, not embeds pointed at us.
Can I use WordPress on the self-hosted version?
Yes. Self-hosting is the same product under an open-source licence with no feature gates, so every connector works and your credentials never leave your own infrastructure. The adapter is apps/web/lib/cms/wordpress.ts in the repository.
Be the site the assistant names.
Add a domain and the first draft is written while you watch. Every publish is your decision, a click on the draft or a rule you set and can hold, and you can read the source or self-host it free.
Add a domain, it sets up your workspace