Title: AI4Ranks SEO Author: ai4ranks Published: November 7, 2026 Last modified: November 7, 2026 --- Search plugins ![](https://ps.w.org/ai4ranks-seo/assets/banner-772x250.png?rev=3789917) ![](https://ps.w.org/ai4ranks-seo/assets/icon-256x256.gif?rev=3791445) # AI4Ranks SEO By [ai4ranks](https://profiles.wordpress.org/ai4ranks/) [Download](https://downloads.wordpress.org/plugin/ai4ranks-seo.4.6.12.zip) * [Details](https://wordpress.org/plugins/ai4ranks-seo/#description) * [Reviews](https://wordpress.org/plugins/ai4ranks-seo/#reviews) * [Installation](https://wordpress.org/plugins/ai4ranks-seo/#installation) * [Development](https://wordpress.org/plugins/ai4ranks-seo/#developers) [Support](https://wordpress.org/support/plugin/ai4ranks-seo/) ## Description Plan better content. Find SEO opportunities. Stay in control. AI4Ranks SEO brings essential SEO controls to WordPress and connects your site to optional AI-assisted content, research and reporting workflows in AI4Ranks Cloud. #### Shape your search appearance Give every important page a clear search identity. Manage SEO titles, meta descriptions, canonical URLs and robots directives locally, including while disconnected. Review AI-assisted metadata proposals before saving, and use metadata history when you need to restore an earlier version. #### Find the gaps in your content Review SEO and content checks for posts, pages and WooCommerce products. Connect your published content to AI4Ranks Cloud to explore primary, secondary, long-tail and related keywords, and identify areas that deserve a closer look before your next update. #### From content idea to reviewed draft Turn research into a clearer content plan. Eligible Cloud plans offer Content Planner, AI-assisted generation, Content Autopilot and Content Evolution workflows. Prepare and refine content with supported scheduling workflows, then review proposed WordPress changes before applying them. Scheduled optimization is in Beta. #### Turn site audits into clear next steps Use Site Audit findings to prioritize technical SEO work. Review affected pages, understand the issue and decide what to address next. Technical URL checks depend on the connected project and configured data sources; recommendations help guide your work rather than promising an automatic fix for every issue. #### Explore your AI search visibility LLM Visibility (Beta) helps you review provider responses, observed mentions and available source references when a supported provider is configured. Combine these observations with keyword tracking, traffic insights and Search & AI Preview where connected data is available. Results can vary between scans. #### Discover relevant link opportunities Research potential sources with Backlink Intelligence (Beta), review backlink opportunities and monitor supported link records. Use internal-link suggestions and Opportunity Intelligence to organize relevant next steps. An opportunity is a research candidate, with no guarantee of placement, indexing, traffic or rankings. #### Bring your SEO work together Organize connected websites and collaborate in a shared workspace. Eligible Cloud plans add team members, SEO reports and export workflows; Agency workspaces can access multi-site management and white-label reporting. Available reporting depends on the connected data sources. #### Your website. Your approval. Cloud-originated changes require a separate approval inside WordPress before they are applied. Review the exact proposal, approve or reject it, and disconnect whenever you choose. Creation requests remain draft-only. Pending proposals expire and are invalidated on disconnect or reconnect; local metadata controls stay available while disconnected. AI4Ranks Cloud is optional and requires an account. Feature availability and usage allowances depend on your plan, connected data sources and provider configuration. Some workflows are Beta. See current plans at https://ai4ranks.com/pricing. The banner includes an illustrative workspace. The gallery contains generated feature illustrations, not screenshots of the live product interface. Example websites, people and observations are fictional. 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. ## Screenshots [⌊Illustration: local SEO metadata controls and a search appearance preview. Connected AI proposals require review.⌉⌊Illustration: local SEO metadata controls and a search appearance preview. Connected AI proposals require review.⌉[ Illustration: local SEO metadata controls and a search appearance preview. Connected AI proposals require review. [⌊Illustration: content checks and keyword hierarchy analysis for connected content. Cloud analysis depends on available content and data.⌉⌊Illustration: content checks and keyword hierarchy analysis for connected content. Cloud analysis depends on available content and data.⌉[ Illustration: content checks and keyword hierarchy analysis for connected content. Cloud analysis depends on available content and data. [⌊Illustration: Cloud content planning and AI-assisted drafting, followed by WordPress review. Supported workflows and scheduling depend on the plan; scheduled optimization is Beta.⌉⌊Illustration: Cloud content planning and AI-assisted drafting, followed by WordPress review. Supported workflows and scheduling depend on the plan; scheduled optimization is Beta.⌉[ Illustration: Cloud content planning and AI-assisted drafting, followed by WordPress review. Supported workflows and scheduling depend on the plan; scheduled optimization is Beta. [⌊Illustration: technical Site Audit findings and recommended next steps. Findings and URL checks depend on the connected project and configuration.⌉⌊Illustration: technical Site Audit findings and recommended next steps. Findings and URL checks depend on the connected project and configuration.⌉[ Illustration: technical Site Audit findings and recommended next steps. Findings and URL checks depend on the connected project and configuration. [⌊Illustration: LLM Visibility (Beta) with a fictional provider response and observed source. Requires a configured provider; example observations are not actual customer results.⌉⌊Illustration: LLM Visibility (Beta) with a fictional provider response and observed source. Requires a configured provider; example observations are not actual customer results.⌉[ Illustration: LLM Visibility (Beta) with a fictional provider response and observed source. Requires a configured provider; example observations are not actual customer results. [⌊Illustration: Backlink Intelligence (Beta) research candidates and an example monitored link. Opportunities do not guarantee backlinks or placements; monitoring depends on the plan and setup.⌉⌊Illustration: Backlink Intelligence (Beta) research candidates and an example monitored link. Opportunities do not guarantee backlinks or placements; monitoring depends on the plan and setup.⌉[ Illustration: Backlink Intelligence (Beta) research candidates and an example monitored link. Opportunities do not guarantee backlinks or placements; monitoring depends on the plan and setup. [⌊Illustration: connected sites, workspace collaborators and an SEO report with fictional data. Team, reporting and multi-site access varies by Cloud plan.⌉⌊Illustration: connected sites, workspace collaborators and an SEO report with fictional data. Team, reporting and multi-site access varies by Cloud plan.⌉[ Illustration: connected sites, workspace collaborators and an SEO report with fictional data. Team, reporting and multi-site access varies by Cloud plan. [⌊Illustration: an exact proposed metadata change awaiting local WordPress administrator approval. No change is applied until approved; the service can be disconnected.⌉⌊ Illustration: an exact proposed metadata change awaiting local WordPress administrator approval. No change is applied until approved; the service can be disconnected.⌉[ Illustration: an exact proposed metadata change awaiting local WordPress administrator approval. No change is applied until approved; the service can be disconnected. ## Installation 1. Upload ZIP via Plugins > Add New > Upload Plugin 2. Activate 3. Go to AI4RANKS menu 4. Enter email + password, click Connect 5. Showing up to 50 recently published items. Click “Sync to AI4RANKS” to send content 6. Use the AI4RANKS dashboard to generate and manage SEO ## FAQ ### Does the plugin send data automatically? Nothing is sent merely because the plugin is activated. Connecting sends account and site-linking information, stores the returned site token locally, provisions an optional Visitor Intelligence site key, and sends a capability manifest. Connected administrator screens may request account status or workspace summaries. Content is sent when an administrator starts a sync or AI-assisted action; a connected AI4RANKS workflow may also request the plugin’s authenticated published-resource endpoint. Visitor data is sent only after an administrator enables Visitor Intelligence and the visitor gives affirmative consent. ### Does the plugin store my AI4RANKS password? No. The password is used only during connection. The plugin stores the site token returned by AI4RANKS. ### Can I disconnect? Yes. Use AI4RANKS > Settings > Disconnect. Deactivation preserves settings and history so reactivation is safe. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “AI4Ranks SEO” is open source software. The following people have contributed to this plugin. Contributors * [ ai4ranks ](https://profiles.wordpress.org/ai4ranks/) [Translate “AI4Ranks SEO” into your language.](https://translate.wordpress.org/projects/wp-plugins/ai4ranks-seo) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/ai4ranks-seo/), check out the [SVN repository](https://plugins.svn.wordpress.org/ai4ranks-seo/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/ai4ranks-seo/) by [RSS](https://plugins.trac.wordpress.org/log/ai4ranks-seo/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 4.6.12 * Require a local WordPress administrator to review and apply each exact cloud- originated write proposal. * Keep automatic cloud writes disabled and invalidate proposals after disconnecting or reconnecting. * Preserve password characters by validating strings and removing WordPress slashes only. * Check the target post’s edit_post capability in both revision route permission and restoration. #### 4.6.11 * Select workspace navigation from the active page callback instead of query input. * Cache immutable revision lookups briefly while checking current edit permissions on every restore. * Report revision lookup database failures without caching them as missing revisions. #### 4.6.10 * Reject malformed REST metadata and invalid setup steps before writing data. * Require successful transaction locks and byte-exact conditional solution updates. * Preserve literal backslashes in metadata and solution titles. * Verify AJAX request shapes, handle revision save failures, and cache revision history by version. * Preserve WordPress 5.3 database-query compatibility and use the supported REST request attribute API. #### 4.6.9 * Exclude Python build tools and duplicate development files from the installable plugin archive. * Sanitize and validate editor optimization plans, local SEO fields, and request paths at their input boundaries. * Validate nested input types before storing metadata or using request values. #### 4.6.8 * Align the release ZIP directory and main plugin file with the `ai4ranks-seo` slug and text domain. * Include the self-contained release builder and its used source inputs in `development/` for transparent review and reproducible packaging. * Require short-lived, body-bound HMAC signatures and single-use nonces for all cloud-originated WordPress writes. * Limit connected content creation to idempotent WordPress drafts and restrict optimization reads to published resources. * Normalize cloud response data before it enters the admin UI and escape rendered values for their output contexts. * Ship Visitor Intelligence browser code locally, require affirmative consent before any identifier or request, and honor excluded pages for analytics and replay. * Document all AI4RANKS cloud and optional Visitor Intelligence connections, including consent, browser storage, and uninstall behavior. #### 4.6.7 * Escape FAQ structured data and visitor goal rules for their script contexts. #### 4.6.6 * Require WordPress 5.3 or later, matching the date functions used in scan history. * Prevent features from loading on unsupported WordPress versions and show an administrator notice. * Correct database table definitions for reliable activation and reactivation. #### 4.6.5 * Removed development-only source files from the distribution archive. * Load all WordPress admin menu styles through the admin enqueue APIs. #### 4.6.4 * Use WordPress enqueue APIs for admin styles and restrict shortcode HTML tags to a fixed allowlist. * Removed the optional image-file optimization feature from the WordPress.org distribution. * Included the maintained source and build script with the release. #### 4.6.3 * Updated WordPress compatibility metadata and aligned the text domain with the directory slug. #### 4.6.2 * Removed the automated linking feature and all automatic outbound-link reporting from the WordPress.org distribution. * Removed automatic post-publication sync; cloud actions require an administrator’s explicit request. #### 4.6.1 * Added exact editorial previews, conditional single-field publication and restore for content, excerpts, focus keywords, schema and image alt text. #### 4.6.0 * Added five-minute HMAC write signatures with nonce replay protection. * Added capability schema v6 for signed, idempotent approved writes. * Cloud execution now uses a durable operation outbox with bounded reconciliation. #### 4.5.0 * Added durable idempotency receipts for approved metadata and canonical writes. * Safe retries return the original verified receipt instead of applying a duplicate revision. * Connector capability schema v5 advertises idempotent write support explicitly. #### 4.4.0 * Added approval-gated self-referencing canonical updates with exact revision checks, receipts, and rollback. * Canonical capability support is advertised explicitly through connector schema v4. #### 4.3.3 * Added exact same-site 301/308 redirects for missing pages, with approval and guarded removal. #### 4.3.2 * Added approval-bound broken-link replacement and removal with exact body revision checks. * Preserves link text, native revisions and public verification through AI4Ranks Optimization. #### 4.3.1 * Added controlled Renovation Estimator rendering with local calculations. * Added authenticated draft-only create/update/rollback with version checks and retry deduplication. * Prevent solution updates from replacing owner content or editing published pages. #### 4.2.0 * Added revision-bound keyword metadata updates and serialized cloud apply operations. * Validate page and metadata versions before content writes; publish capability schema v3. #### 4.1.0 * Added revisioned, version-conflict-safe staged autofix metadata execution. * Added authoritative full-content sync fields and SEO metadata versions. * Added connector responses that confirm rollback support and rendered-output verification. #### 4.0.0 * Added safe SEO output ownership and competing-plugin detection. * Added local Titles & Meta output, canonical AI4Ranks metadata keys, revisions, audit events, and rollback APIs. * Added a versioned cloud capability manifest while preserving legacy connector compatibility. * Changed AI metadata generation to proposal-first behavior. #### 3.0.1 * Hardened WordPress.org submission readiness. * Enabled SSL verification for remote requests. * Added stricter capability checks, sanitization, and escaping. * Added external service and privacy documentation. #### 3.0.0 * Full pages, posts, and products support * Content sync to SaaS (auto + bulk) * Fetch and apply SEO data from SaaS * Keyword Lab integration * WooCommerce product support #### 2.0.0 * SEO audit, meta generation, content scoring * Keyword suggestions #### 1.0.0 * Initial release ## Meta * Version **4.6.12** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 5.3 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Tags * [AI](https://wordpress.org/plugins/tags/ai/)[audit](https://wordpress.org/plugins/tags/audit/) [content](https://wordpress.org/plugins/tags/content/)[keywords](https://wordpress.org/plugins/tags/keywords/) [seo](https://wordpress.org/plugins/tags/seo/) * [Advanced View](https://wordpress.org/plugins/ai4ranks-seo/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/ai4ranks-seo/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/ai4ranks-seo/reviews/) ## Contributors * [ ai4ranks ](https://profiles.wordpress.org/ai4ranks/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/ai4ranks-seo/)