

Dashboard — site health, SEO score, and AEO score at a glance.
Ranklance is a WordPress plugin for SEO and Answer Engine Optimization (AEO). It scores your pages for AI answer engines, audits your site for technical SEO issues, and gives you full control over meta tags, schema, sitemaps, and robots directives — for both traditional search engines and AI-powered answer engines.
What the free plugin does
Ranklance Pro
The free edition analyzes; Pro turns that analysis into automatic execution — an AI agent team that generates fixes and an approval queue that applies them to your live site with one click, plus:
Learn more at ranklanceai.com.
External Services This Plugin Connects To
Ranklance connects to external services to provide its features. All connections are initiated by the site administrator and require explicit setup. No data is transmitted without configuration.
Google Search Console
Service: https://search.google.com/search-console — OAuth 2.0 authentication. Data received: impressions, clicks, CTR, position per page, crawl errors. Connection occurs during OAuth setup and on scheduled syncs. Privacy policy: https://policies.google.com/privacy | Terms: https://developers.google.com/terms
Google PageSpeed Insights API (optional)
Service: https://pagespeed.web.dev/ — Public page URLs are submitted for performance analysis during a Technical SEO audit run. Privacy policy: https://policies.google.com/privacy | Terms: https://developers.google.com/terms
Google Rich Results Test API (optional)
Service: https://search.google.com/test/rich-results — JSON-LD markup is submitted for schema validation, on demand from the post editor. Privacy policy: https://policies.google.com/privacy | Terms: https://developers.google.com/terms
Anthropic Claude API (optional, bring-your-own key)
Service: https://www.anthropic.com — Used only for AI-assisted AEO analysis, and only when you supply your own Anthropic API key AND enable the data-sharing consent toggle in Settings Integrations. When enabled, page content (titles and body text) is sent to Anthropic for analysis. Nothing is sent without both the key and explicit consent; with neither, the plugin uses rule-based analysis and contacts no AI service. Privacy policy: https://www.anthropic.com/legal/privacy | Terms: https://www.anthropic.com/legal/consumer-terms
IndexNow — Bing and Yandex (optional, off by default)
Service: https://www.indexnow.org — When you enable IndexNow under Settings Instant Indexing, the URL of a post is sent to https://www.bing.com/indexnow and https://yandex.com/indexnow each time it is published, updated, or removed, together with your site’s IndexNow key. No other content is sent. Bing privacy policy: https://privacy.microsoft.com/privacystatement | Bing terms: https://www.microsoft.com/servicesagreement | Yandex privacy policy: https://yandex.com/legal/confidential/ | Yandex terms: https://yandex.com/legal/rules/
Google Indexing API (optional, off by default)
Service: https://developers.google.com/search/apis/indexing-api — When you enable it under Settings Instant Indexing and provide your own Google Cloud service-account key, the plugin requests an access token from https://oauth2.googleapis.com/token and sends the URL of a post to https://indexing.googleapis.com when it is published, updated, or removed. No other content is sent. The service-account key is stored encrypted. Privacy policy: https://policies.google.com/privacy | Terms: https://developers.google.com/terms
Ranklance is open source (GPLv2+). The complete, human-readable source for every compiled asset is included in the plugin package, and the build is fully reproducible.
Build tooling: @wordpress/scripts (webpack) for the block-editor bundles, and Terser / cssnano for the classic admin assets.
Compiled files and their sources:
assets/build/editorial-sidebar.js is built from assets/js/gutenberg/editorial-sidebar.jsassets/build/meta-editor-sidebar.js is built from assets/js/gutenberg/meta-editor-sidebar.jsassets/js/*.min.js are minified from the matching assets/js/*.js sourcesassets/css/*.min.css are minified from the matching assets/css/*.css sourcesTo regenerate the compiled assets from source:
npm install
npm run build
The webpack entry points are defined in webpack.config.js and the build scripts in package.json (both included in the package), so the compiled assets can be regenerated directly from the included source.