Skip to main content
RankAI only asks for what it needs to publish articles and read your search data. Use this page to answer a security or IT review, or to pick the right user and permissions before you connect.
Good to know: give RankAI its own user or token where your platform allows it. You can remove that access later without affecting anyone else.
In RankAI: Settings → Integrations · rankai.ai/dashboard/<project>/settings/integrations

Google Search Console

See Connect Google Search Console.

Your CMS

RankAI uses your CMS access to create, update and unpublish the articles it writes. It only changes posts it created itself. RankAI never shows a saved password, token or secret back to you after you save it.

Technical SEO & AEO script

The script is one line you add to your site. On each page, it asks RankAI which fixes are enabled for that page and applies them in the visitor’s browser: titles, meta descriptions, canonical links, social sharing tags, image alt text, headings, structured data and internal links. Disabled fixes leave the page as it was. The script sends RankAI only the address of the page being viewed, including any query string. It doesn’t send cookies or store anything in the visitor’s browser. Fixes stop when the project has no active trial or plan.

Remove access

RankAI doesn’t have a disconnect button for CMS logins, so remove access on your platform:
  • WordPress: delete the application password in Users → Profile.
  • Webflow: delete the API token in your site settings.
  • Shopify: uninstall or delete the app you created for RankAI.
  • Wix: delete the API key.
  • Sanity: delete the API token in your Sanity project.
  • Framer: remove the plugin.
  • Script: remove the script line from your site.
Removing access stops publishing. Articles already on your site stay there. Need this for a security review, or something isn’t listed? Contact support.
Last reviewed: November 13, 2026.