Setup guides, troubleshooting, and common issues.
Roborank connects to your WordPress site via the REST API using an Application Password.
Your site must use HTTPS. Application Passwords are disabled on plain HTTP sites. Some security plugins (Wordfence, iThemes) can also disable them.
The plugin registers SEO meta fields (Yoast and RankMath) so Roborank can read and update them via the REST API. Without it, WordPress silently ignores meta writes.
Current version: 1.3 — Download the plugin (.zip), or grab it from Settings when testing the WordPress connection.
.zip (or get it from Roborank Settings)yoursite.com/wp-json/content-agent/v1/status — should show "version": "1.3"_yoast_wpseo_metadesc, rank_math_description, etc.)/wp-json/content-agent/v1/statusRoborank automatically discovers and fetches custom post types (e.g. WooCommerce products, destinations, portfolios). For meta editing to work on CPTs, you need:
True in your CPT settingsmeta field from the REST API entirelypost — otherwise WordPress returns "not allowed to edit this post"TrueIf you use the CPTUI plugin, check these settings for each custom post type:
post (not blank, not the CPT name)"Sorry, you are not allowed to edit this post"
The Capability Type is wrong. Change it to post in CPTUI. This tells WordPress to reuse standard post editing permissions.
Meta writes succeed but nothing changes
The CPT is missing Custom Fields in its Supports setting. Without it, WordPress accepts the POST but silently drops the meta data. Enable Custom Fields in CPTUI and try again.
CPT not showing up in Roborank
Either Public or Show in REST API is set to False. Both must be True. After fixing, hit Refetch Site in Roborank.
Plugin v1.1 or v1.2 doesn't register meta for CPTs
A timing issue: the plugin ran before CPTUI registered the post type. Update to v1.3 which runs at priority 99.
Roborank works with WordPress Multisite, but there are a few gotchas:
On multisite, super admin is a network-level privilege. The REST API checks per-site roles. If your user has no role on the specific subsite, API writes will fail with "not allowed to edit". Fix: assign your user the Administrator role on the subsite (Users → your profile → Role).
rest_not_logged_in errors, check Jetpack's security settings.If the agent says it updated the meta but nothing changed, work through this checklist:
yoursite.com/wp-json/content-agent/v1/status. Should return "active": true and "version": "1.3"."seo": "yoast" or "seo": "rankmath". If it says "unknown", neither is active.yoursite.com/wp-json/wp/v2/users/me with your credentials. Should return your user info, not an error."roles": ["administrator"]. If it shows "roles": [] or null, your user has no role on this site (common on multisite).yoursite.com/wp-json/wp/v2/posts/ID. The meta object should contain _yoast_wpseo_metadesc. If meta is empty or missing, the plugin isn't working.post.Roborank supports two AI providers. Your API key stays in your browser and is never stored on our server.
If you have both keys configured, Anthropic takes priority. To use OpenAI, remove the Anthropic key.
Connect GSC to give the agent real search performance data (clicks, impressions, position, CTR). Without it, the agent can still analyze content and structure but can't identify keyword opportunities.
Google OAuth verification is pending. Until approved, new users must be manually added to the test users list. Contact us if you see an "access denied" error during GSC connection.