Connect the analytics and CMS tools you already run

Google Analytics 4 and Search Console for traffic, CMS publishing to WordPress, Webflow, Contentful and Framer, and a generic webhook alongside Zapier and Make for automation. The developer surfaces sit next to them: a REST API, the airankly CLI, a hosted MCP server and a Looker Studio connector. Which you can use depends on tier. CMS publishing, webhooks and MCP are on every plan; the API, CLI, Looker connector and GA4 traffic views are Professional and Enterprise.

No. Integrations carry no separate fee and no per-connection charge, and seats are unlimited on every plan, so connecting a tool never adds a line to your bill. What varies by tier is which surfaces exist on your plan at all, not what they cost once they do. No integration carries a minimum term either: cancellation follows the normal terms, taking effect at the end of your billing period.

Most do not. GA4, Search Console and the supported CMSes are authenticated connections you set up once from the dashboard. Webhooks need something on your side to accept a payload, which is a small job, and Zapier or Make will do it without code. The REST API and CLI are for building a pipeline rather than making a connection, and those genuinely are developer work, which is why they sit on Professional and Enterprise.

Yes, tell us. The roadmap is shaped by what teams actually need to connect to, and Support@airankly.io reaches us Monday to Friday, 8:00 AM to 6:00 PM CT. In the meantime the webhook plus the REST API covers most cases, since anything that can receive a payload or call an endpoint can be wired up today. We will not promise a date for something that does not exist yet, and would rather say so plainly.

Your AI Rankly data stays. Visibility, rankings, citations and sentiment are measured by us directly and do not depend on any integration, so disconnecting GA4 empties the traffic views and leaves everything else intact. Exports in CSV, Excel and JSON are available at any time while your account is active, and for thirty days after termination on request, so there is no point at which your history is trapped.

Only when you approve it. Content generated in the studio arrives in your CMS as a draft for review rather than as a live page, and the agent that proposed the work is supervised throughout, so nothing publishes to your site without your say-so. Webhooks fire on events you choose, which is how most teams route an alert into Slack or a task into their tracker without granting anything permission to change their site.