AI4Ranks SEO

AI4Ranks SEO manages local metadata safely and can link your site to AI4Ranks Cloud after you explicitly connect your account.

Features include:

• SEO audits for posts, pages, and WooCommerce products.
• AI-assisted meta title and meta description generation.
• Local SEO title, description, canonical, and robots fields that work while disconnected.
• Safe connector-only mode when another known SEO engine is active.
• Metadata revision history, audit events, optimistic conflict checks, and rollback APIs.
• Content scoring with actionable checks.
• Keyword suggestions and keyword workflow statuses.
• Content sync to the AI4RANKS dashboard.
• SEO score columns in WordPress content lists.
• Shortcodes for displaying generated SEO fields where you choose.
• Bulk sync for published content.

This plugin is a connector for the AI4RANKS software-as-a-service platform. It ships its public JavaScript and CSS locally, does not add public credit links, and keeps Visitor Intelligence off until an administrator enables it. A connected AI4RANKS workflow can request the plugin’s authenticated, published-resource endpoint; it does not expose drafts, private posts, pending posts, or scheduled posts.

External services

The plugin uses the AI4RANKS service only after an administrator connects the site or uses a connected feature. The following describes each connection and the data involved.

Account connection and workspace requests

When an administrator connects in AI4RANKS > Settings, the plugin sends the administrator’s email and password, site URL, site name, and WordPress version to AI4RANKS to authenticate and link the site. The password is used for that request only and is not stored by WordPress. AI4RANKS returns a site token, which the plugin stores locally to make authenticated service requests.

After connection, the plugin may send the site token with a capability manifest (plugin, WordPress and PHP versions; installation ID; enabled modules; and WooCommerce availability), account-status requests, dashboard-overview requests, Visitor Intelligence configuration, and integration-status requests. These requests occur when the corresponding administrator screen or control is used, or when a connected administrator saves Visitor Intelligence settings.

SEO, content, and AI requests

When an administrator explicitly starts a sync, audit, score, keyword, metadata, editor-AI, or optimization action, the plugin sends only the data needed for that action. This can include site token, post ID, post type/status, title, URL, excerpt, post content or plain-text content, categories, tags, SEO fields, and requested settings. AI4RANKS may also use the authenticated WordPress optimization endpoint to read published posts, pages, products, categories, and product categories for a connected workflow. That endpoint does not return drafts, private posts, pending posts, or scheduled posts.

The legacy connected content-creation endpoint can create a WordPress draft only; it cannot publish, schedule, or make a post private. Review and publish the resulting draft in WordPress.

Cloud-originated changes require a separate approval in WordPress. A signed cloud request only saves a private, expiring proposal in AI4Ranks > Cloud proposals; it does not create a content draft, edit live content, publish a post, or change a redirect. The administrator reviews the exact proposed values and chooses Approve and apply or Reject. Applying requires a WordPress login, an action nonce, manage_options, edit_post for the target, and the post type’s publish capability when publication is requested. Creation requests remain draft-only. A pending proposal is not reported as a successful write. Proposals are single-use, expire after one hour, and are invalidated when the service is disconnected or reconnected. Local connection credentials are revoked before the best-effort disconnect notification to the platform.

Visitor Intelligence

Visitor Intelligence is off by default. If an administrator enables it, the plugin serves its reviewed JavaScript files from this plugin’s own assets/ directory. No executable visitor-tracking code is loaded from AI4RANKS. The local script contacts the AI4RANKS HTTPS analytics API only after the site has obtained affirmative visitor consent by calling window.ai4ranks.consent('grant') (or dispatching the documented consent event).

After consent, the feature sends a site key, anonymous visitor and session identifiers, page URL and referrer with ordinary query values removed (attribution parameters may be retained), event timestamps, page/scroll/click/form/video interaction summaries, browser/operating-system/device category, viewport/screen size, language, web-vital measurements, and limited error diagnostics. It stores its anonymous visitor ID in local storage and session IDs/activity in session storage only after consent. As with any HTTPS request, AI4RANKS also receives standard network metadata such as the visitor IP address.

Optional replay is separately controlled by the administrator’s replay setting and sample rate, and starts only after visitor consent. It sends structural selectors, element geometry, pointer/click and scroll events; it does not collect input values, DOM text, clipboard content, audio, video, passwords, payment data, or raw identity data. Site owners are responsible for connecting this feature to their consent-management and privacy workflow and for configuring excluded, masked, blocked, and ignored selectors appropriately.

Personal AI provider keys

If an administrator chooses “Your API keys” under AI4RANKS > Settings > Integrations, the selected provider, model, and API key are sent to AI4RANKS over HTTPS so AI4RANKS can store the key encrypted for that account and use it for future AI requests. The key is not stored in WordPress or shown again. The administrator is responsible for reviewing the selected provider’s terms and privacy policy.

The service is provided by AI4RANKS.

• Service website: https://ai4ranks.com
• Terms of service: https://ai4ranks.com/terms
• Privacy policy: https://ai4ranks.com/privacy

Source code

The plugin includes readable PHP, JavaScript, and CSS. The readable inputs for assets/solutions.js are included as assets/source/solution-engine.js and assets/source/solutions-browser.js. The runtime combines these two files in an immediately invoked function, replacing the engine’s export function declarations with local function declarations. Development tools and duplicate development copies are excluded from the installable ZIP.

Uninstall

Deactivation preserves local data. The explicit Disconnect action asks AI4RANKS to disconnect the site and removes the local connection credentials and Visitor Intelligence keys. If the Delete local Visitor Intelligence settings on uninstall checkbox is selected before uninstalling, the plugin deletes only its local Visitor Intelligence settings and keys; it does not delete cloud analytics data. Manage cloud analytics deletion separately in AI4RANKS Settings & Privacy.