Connecting RankLantern to your own tools

• Your sites, with the score of the latest audit.
• The problems from the latest audit, with explanation and fix, and the pages for each problem.
• Search Console: clicks, impressions, the main searches and pages, and opportunities.
• Your articles by stage: ideas, to review, drafts and online.
• The status of the weekly Autopilot.
• With a key for reading and approving: put a written article in WordPress as a draft. Never publish.

1. Log in to RankLantern and go to Account, section API keys.
2. Give the key a name (for example the name of your workflow) and choose read only, or read and approve.
3. Choose whether the key may access all your sites or one. Confirm with your password.
4. Copy the key straight away. It starts with rl_ and is shown only once.

A key is valid for a year and works like a password. Don't put it in shared documents, and revoke it when you no longer use it.

Claude Code:

claude mcp add --transport http ranklantern https://app.ranklantern.com/api/mcp --header "Authorization: Bearer YOUR_KEY"

Cursor, in .cursor/mcp.json:

{
  "mcpServers": {
    "ranklantern": {
      "url": "https://app.ranklantern.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:RANKLANTERN_API_KEY}"
      }
    }
  }
}

n8n: use the MCP Client Tool node with transport HTTP Streamable, the URL above and Bearer authentication with your key.

Then you can ask your assistant things like “What technical problems does my site have?” or “Show me the articles waiting for my review”.

Every request sends the key in the Authorization header. Zapier and Make do that with their module for a custom HTTP request.

curl -H "Authorization: Bearer YOUR_KEY" https://app.ranklantern.com/api/v1/sites

Per key: 60 requests a minute for reading, 15 a minute for Search Console, 10 a minute and 50 a day for approving. With too many requests you get status 429 with the waiting time in Retry-After.

Errors always have the same shape, with a fixed code: unauthorized (401), forbidden_scope and plan_required (403), not_found (404), conflict (409), validation (422), rate_limited (429) and unavailable (503).

• A key only sees the sites you have access to, never anyone else's.
• We only store a fingerprint of the key, not the key itself.
• Approving through a connection only makes a draft. Publishing never goes through the API.
• Under Account you see for each key when it was last used, and you revoke it with one click.

Questions about a connection? Email hello@ranklantern.com.