Roborank Help v1.0

Setup guides, troubleshooting, and common issues.

WordPress Setup

Roborank connects to your WordPress site via the REST API using an Application Password.

Creating an Application Password

Go to WP Admin → Users → Profile
Scroll to Application Passwords
Enter a name (e.g. "Roborank") and click Add New Application Password
Copy the generated password (spaces are normal) and paste it in Roborank Settings

Application Passwords not showing?

Your site must use HTTPS. Application Passwords are disabled on plain HTTP sites. Some security plugins (Wordfence, iThemes) can also disable them.

Content Agent Connector Plugin

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.

Installation

Download the .zip (or get it from Roborank Settings)
Go to WP Admin → Plugins → Add New → Upload Plugin
Upload the zip and activate
Verify: visit yoursite.com/wp-json/content-agent/v1/status — should show "version": "1.3"

Updating from an older version

Deactivate and delete the old plugin
Upload and activate the new zip

What the plugin does

Registers Yoast and RankMath meta fields as writable via REST API (_yoast_wpseo_metadesc, rank_math_description, etc.)
Exposes ACF fields in the REST API if ACF is installed
Adds a health check endpoint at /wp-json/content-agent/v1/status

Custom Post Types

Roborank automatically discovers and fetches custom post types (e.g. WooCommerce products, destinations, portfolios). For meta editing to work on CPTs, you need:

Checklist for CPT support

Required Plugin v1.3 installed (uses priority 99 to run after CPT registration)
Required Show in REST API set to True in your CPT settings
Required Custom Fields checked under Supports — without this, WordPress hides the meta field from the REST API entirely
Required Capability Type set to post — otherwise WordPress returns "not allowed to edit this post"
Required Public set to True

Using Custom Post Type UI (CPTUI)

If you use the CPTUI plugin, check these settings for each custom post type:

Public: True
Show in REST API: True
Capability Type: post (not blank, not the CPT name)
Supports: check Title, Editor, Custom Fields, and any others you need

Troubleshooting CPTs

"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.

WordPress Multisite

Roborank works with WordPress Multisite, but there are a few gotchas:

Super Admin with no site role

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).

Application Passwords are per-user, not per-site. The same password works across all subsites.
The Content Agent Connector plugin should be network activated or activated on each subsite individually.
Jetpack can interfere with REST API authentication. If you see rest_not_logged_in errors, check Jetpack's security settings.

Meta Descriptions Not Saving

If the agent says it updated the meta but nothing changed, work through this checklist:

Plugin installed? Check yoursite.com/wp-json/content-agent/v1/status. Should return "active": true and "version": "1.3".
Right SEO plugin? The status endpoint shows "seo": "yoast" or "seo": "rankmath". If it says "unknown", neither is active.
Application Password working? Check yoursite.com/wp-json/wp/v2/users/me with your credentials. Should return your user info, not an error.
User has a role? The response should show "roles": ["administrator"]. If it shows "roles": [] or null, your user has no role on this site (common on multisite).
Meta fields registered? Check a post at 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.
Custom post type? See the CPT section above. CPTs need Custom Fields support and Capability Type set to post.

AI Providers

Roborank supports two AI providers. Your API key stays in your browser and is never stored on our server.

Anthropic (Claude) — Sonnet for chat and strategy, Haiku for content drafting. Recommended.
OpenAI — GPT-4.1-mini for chat and drafting. Works but less capable for SEO tasks.

If you have both keys configured, Anthropic takes priority. To use OpenAI, remove the Anthropic key.

Google Search Console

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.

OAuth is in testing mode

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.

The GSC connection uses OAuth 2.0 — your tokens stay in your browser.
Make sure you select the correct property (domain or URL prefix) that matches your site.
GSC data can take 2-3 days to appear for new pages.