voxfor

Voxfor Autopilot is a self-contained WordPress plugin that works like an in-house AI SEO team. It handles the full content lifecycle — from keyword research and long-form article generation to intelligent optimization of existing posts — all from your WordPress dashboard, with no external workflow engines, no subscriptions, and no sending your content to third-party platforms. You bring your own API keys; Voxfor does the rest.
<h4>Why Voxfor Autopilot?</h4>
Most AI content tools are one-trick: they either write new content or rewrite what you have. Voxfor Autopilot does both, adds a safety net, and puts you in control at every step. The pre-update Review Agent, budget gates, kill switch, and per-post scheduling mean the plugin will never surprise you with an unreviewed change or an unexpected API bill.
<h4>Resources</h4>
<ul>
<li><a href="https://www.voxfor.com/voxfor-autopilot.php" rel="nofollow ugc">Official Website</a></li>
<li><a href="https://www.voxfor.com/voxfor-autopilot.php#documentation" rel="nofollow ugc">Documentation</a></li>
<li><a href="https://www.youtube.com/watch?v=AqPoe4-AIPg" rel="nofollow ugc">Watch Full Video Guide</a></li>
</ul>
<h4>Core Features</h4>
1. AI-Powered Content Creation
Generate complete, long-form, SEO-ready blog posts in one click:
<ul>
<li>Target a focus keyword and optional secondary keywords.</li>
<li>Choose content length, language, and tone.</li>
<li>Auto-insert internal links to your existing content.</li>
<li>Add author bio, external reference links, and structured FAQs.</li>
<li>Schedule the post to publish now, as draft, or at a future date/time.</li>
<li>Gutenberg-compatible HTML output — no shortcodes required.</li>
<li>Schema markup hints embedded in the generated structure.</li>
</ul>
The AI never adds a duplicate H1 inside the post body — the post title stays the only H1 on the page, keeping your SEO clean.
2. Content Auditor & Deep Optimization
Audit any existing post and let the AI propose surgical improvements:
<ul>
<li>Problem signal detection — identifies thin content, missing focus keyword, poor meta title/description, over-optimized anchor text, missing CTAs, and more.</li>
<li>5-stage Judgment Engine — every proposal goes through Observe → Diagnose → Plan → Simulate → Decide before a single character changes.</li>
<li>Preserve map — shortcodes, Gutenberg blocks, CTAs, internal links, factual claims, and required phrases are locked before any edit begins.</li>
<li>Four editing modes, from the safest to the most comprehensive:
<ul>
<li>Safe Refresh — meta tags, minor phrasing, keyword density only.</li>
<li>Section Improvement — targeted paragraph-level rewrites.</li>
<li>Guided Rewrite — rewrites weak sections and fixes all flagged problem signals.</li>
<li>Full Rewrite — full article rewrite with all problem signals resolved.</li>
</ul>
</li>
</ul>
3. Manual Review Queue
AI proposals that do not meet the confidence threshold, or that you simply want to inspect, are held in a manual review queue:
<ul>
<li>See the proposed changes side-by-side.</li>
<li>Approve & Apply in one click — the post is updated instantly.</li>
<li>Reject with a reason, or delete entries in bulk to keep the queue clean.</li>
<li>Status updates in real-time: pending → approved, so you always know what was actioned.</li>
</ul>
4. Keywords Research
Expand any seed keyword into a researched list of topical variations, questions, and long-tail phrases:
<ul>
<li>Powered by the same AI provider you configure for research tasks.</li>
<li>Save keywords to the internal library for use in content creation or scheduling.</li>
<li>Cluster keywords and track which have been used, are pending, or have been paused.</li>
</ul>
5. Per-Post Scheduling
A metabox on every post lets you configure automation without touching a single setting page:
<ul>
<li>Set optimization frequency (daily, weekly, monthly, or custom interval).</li>
<li>Choose the editing mode and allowed action types per post.</li>
<li>Set a confidence threshold — proposals below it go straight to manual review.</li>
<li>Define a human-edit policy (skip optimization if you recently edited the post manually).</li>
</ul>
6. Cost Controls & Budget Guard
Every single AI API call is tracked, rolled up, and gated:
<ul>
<li>Per-call cost logging with provider, model, task type, token counts, and USD cost.</li>
<li>Daily and monthly budget caps — once reached, no further API calls are made until the period rolls over.</li>
<li>A one-click Kill Switch in the dashboard halts all outbound AI calls site-wide instantly.</li>
<li>30-day cost trend chart, provider breakdown, and task-type breakdown under AI Cost.</li>
</ul>
7. Activity Log
A full audit trail of every action the plugin takes:
<ul>
<li>Filterable by level (Info, Warning, Error) and searchable by keyword.</li>
<li>Bulk-delete selected entries or clear the entire log with one click.</li>
<li>Errors and warnings are highlighted so issues stand out instantly.</li>
</ul>
8. Multi-Provider AI Support
Voxfor Autopilot is provider-agnostic and supports:
<ul>
<li>OpenAI (GPT-5.5, GPT-5 family, GPT-4.1, GPT-4o Mini, and compatible models)</li>
<li>Anthropic (Claude 3.5 Sonnet, Claude 3 Opus, Haiku)</li>
<li>Google Gemini (Gemini 1.5 Pro, Gemini 1.5 Flash, Gemini 2.x)</li>
<li>Perplexity (sonar-pro, sonar — ideal for research with live citations)</li>
</ul>
Each AI task (Research, Content, Optimization, Review, Images) can be routed to a different provider, so you can use the best model for each job while controlling costs.
9. SEO Plugin Compatibility
Works natively with:
<ul>
<li>Rank Math — reads and writes focus keyword, meta title, meta description.</li>
<li>Yoast SEO — reads and writes focus keyword, meta title, meta description.</li>
<li>Standalone mode — when no SEO plugin is active, Voxfor stores everything under <code>_voxfor_*</code> post meta.</li>
</ul>
No hard dependencies. If your SEO plugin is deactivated, the plugin falls back to standalone mode automatically.
10. Multilingual Content
Set any language in Settings and every AI prompt is automatically adjusted to produce content in that language — no WPML or translation plugin required for the AI output itself.
<h4>Privacy & Data</h4>
<ul>
<li>No data leaves your server except for the API calls you explicitly configure to your chosen AI provider(s). See the External services section below for full disclosure of what is sent, when, and to whom.</li>
<li>API keys are stored in your own <code>wp_options</code> table and are never sent to Voxfor or any third party — only to the provider whose key it is.</li>
<li>No telemetry, no usage pings, no licensing servers, no analytics, no user tracking.</li>
<li>Voxfor Autopilot does not load any third-party scripts or fonts on the front end of your site.</li>
</ul>
<h4>Minimum Requirements</h4>
<ul>
<li>WordPress 6.2 or higher</li>
<li>PHP 7.4 or higher (PHP 8.x recommended for best performance)</li>
<li>At least one API key from a supported AI provider</li>
<li>cURL enabled in PHP</li>
</ul>
<h3>External services</h3>
Voxfor Autopilot is a “bring your own API key” plugin. It does not include or require any service operated by Voxfor. The plugin only contacts an external service when the site administrator explicitly configures an API key for that provider in Settings → API Keys AND assigns that provider to a task in Settings → Task Routing, and then triggers an action that uses that task (e.g. Create Content, Run Auditor, Expand Keywords, Approve Manual Review).
No data is sent to any third party on plugin activation, page loads, cron ticks, or front-end visits. No data is sent to Voxfor itself — there is no Voxfor server.
For every provider listed below, the data transmitted is the same general shape: the prompt the plugin builds for the requested task (which may include the focus keyword, secondary keywords, post title, post excerpt, the existing post content when optimizing an existing post, the target language and tone, and your API key in the request header for authentication). The provider’s response (the generated/optimized text, research results, or image URL) is then stored in your own WordPress database. The plugin does not send any visitor data, IP addresses, or analytics.
<h4>OpenAI (api.openai.com)</h4>
<ul>
<li>What it is: OpenAI’s GPT and DALL-E APIs.</li>
<li>What it is used for: Generating new article drafts, expanding keyword seeds, optimizing existing posts, generating featured images (DALL-E / gpt-image), and pre-update review of AI proposals — but only for the tasks you assign to “OpenAI” in Task Routing.</li>
<li>What is sent and when: The prompt for the requested task and your OpenAI API key, sent only when an administrator triggers an action in the admin UI (or when a per-post / per-keyword schedule the administrator configured fires). Endpoint: <code>https://api.openai.com/v1</code>.</li>
<li>Terms of service: https://openai.com/policies/terms-of-use</li>
<li>Privacy policy: https://openai.com/policies/privacy-policy</li>
</ul>
<h4>Anthropic Claude (api.anthropic.com)</h4>
<ul>
<li>What it is: Anthropic’s Claude API.</li>
<li>What it is used for: Article generation, keyword expansion, post optimization, and pre-update review — but only for the tasks you assign to “Anthropic” in Task Routing.</li>
<li>What is sent and when: The prompt for the requested task and your Anthropic API key, sent only when an administrator triggers an action or a configured schedule fires. Endpoint: <code>https://api.anthropic.com/v1</code>.</li>
<li>Terms of service: https://www.anthropic.com/legal/consumer-terms</li>
<li>Privacy policy: https://www.anthropic.com/legal/privacy</li>
</ul>
<h4>Google Gemini (generativelanguage.googleapis.com)</h4>
<ul>
<li>What it is: Google’s Gemini Generative Language API.</li>
<li>What it is used for: Article generation, keyword expansion, post optimization, image generation (Gemini image models), and pre-update review — but only for the tasks you assign to “Gemini” in Task Routing.</li>
<li>What is sent and when: The prompt for the requested task and your Gemini API key, sent only when an administrator triggers an action or a configured schedule fires. Endpoint: <code>https://generativelanguage.googleapis.com/v1beta</code>.</li>
<li>Terms of service: https://ai.google.dev/gemini-api/terms</li>
<li>Privacy policy: https://policies.google.com/privacy</li>
</ul>
<h4>Perplexity (api.perplexity.ai)</h4>
<ul>
<li>What it is: Perplexity’s Sonar API.</li>
<li>What it is used for: Research tasks with live citations and, optionally, text generation — but only for the tasks you assign to “Perplexity” in Task Routing.</li>
<li>What is sent and when: The research prompt for the requested task and your Perplexity API key, sent only when an administrator triggers an action or a configured schedule fires. Endpoint: <code>https://api.perplexity.ai</code>.</li>
<li>Terms of service: https://www.perplexity.ai/hub/legal/terms-of-service</li>
<li>Privacy policy: https://www.perplexity.ai/hub/legal/privacy-policy</li>
</ul>
If you do not enter an API key for a given provider, or do not assign that provider to any task, the plugin never contacts that service.

Voxfor Autopilot

Autonomous AI SEO system: research, content generation, deep optimization, scheduling, and manual review — bring your own API keys.

Automattic

Weston Ruter

rtCamp

Google

Pascal Birchler

Joshua Wold

Alain Schlesser

Alberto Medina

Piotr Delawski

Lovekesh Kumar

Pierre Gordon

<a href="https://developers.google.com/search/docs/guides/page-experience" rel="nofollow ugc">Page Experience</a> (PX) is a set of ranking signals—including <a href="https://web.dev/vitals/#core-web-vitals" rel="nofollow ugc">Core Web Vitals</a> (CWV)—measuring the user experience of interacting with a web page. AMP is a powerful tool which applies many optimizations and best practices automatically on your site, making it easier for you to achieve good page experience for your visitors. The official AMP Plugin, supported by the AMP team, makes it easy to bring the power of AMP to your WordPress site, seamlessly integrating with the normal publishing flow and allowing the use of existing themes and plugins.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/s52JNMT59s8?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent&listType=playlist&list=PLXTOW_XMsIDRGRr5QDffrvND8Qh1RndFb" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
For more videos like this, check out the ongoing <a href="https://www.youtube.com/playlist?list=PLXTOW_XMsIDRGRr5QDffrvND8Qh1RndFb" rel="nofollow ugc">AMP for WordPress video series</a>.
The plugin’s key features include:
<ol>
<li>Automate the process of generating AMP-valid markup as much as possible, letting users follow the standard workflows they are used to in WordPress.</li>
<li>Provide effective validation tools to help users deal with AMP incompatibilities when they happen, including mechanisms for identifying, contextualizing, and resolving issues caused by validation errors.</li>
<li>Provide development support to make it easier for WordPress developers to build AMP-compatible ecosystem components and build websites and solutions with AMP-compatibility built-in.</li>
<li>Support the serving of AMP pages to make it easier for site owners to take advantage of mobile redirection, AMP-to-AMP linking, and generation of optimized AMP by default (via PHP port of AMP Optimizer).</li>
<li>Provide a turnkey solution for segments of WordPress creators to be able to go from zero to publishing AMP pages in no time, regardless of technical expertise or availability of resources.</li>
</ol>
The official AMP plugin for WordPress is a powerful tool that helps you build user-first WordPress sites, that is, sites that are fast, beautiful, secure, engaging, and accessible. A user-first site will deliver experiences that delight your users and therefore will increase user engagement and the success of your site. And, contrary to the popular belief of being only for mobile sites (it doesn’t stand for Accelerated Mobile Pages anymore!), AMP is a fully responsive web component framework, which means that you can provide AMP experiences for your users on both mobile and desktop devices.
<h4>AMP Plugin Audience: Everyone</h4>
This plugin can be used by both developers and non-developer users:
<ul>
<li>If you are a developer or tech savvy user, you can take advantage of advanced developer tools provided by the AMP plugin to fix validation issues your site may have and reach full AMP compatibility.</li>
<li>If you are not a developer or tech savvy user, or you just simply don’t want to deal with validation issues and tackling development tasks, the AMP plugin allows you to assemble fully AMP-compatible sites with different configurations taking advantage of AMP-compatible components. The plugin helps you to deal with validation issues by removing invalid AMP markup in cases where it is possible, or altogether suppressing AMP-incompatible plugins on AMP pages.</li>
</ul>
The bottom line is that regardless of your technical expertise, the AMP plugin can be useful to you.
<h4>Template Modes</h4>
The official AMP plugin enables site owners to serve AMP to their users in different ways, which are referred to as template modes: Standard, Transitional, and Reader. The differences between them are in terms of the number of themes used (one or two), and the number of versions of the site (non-AMP, AMP). Each template mode brings its own value proposition and serves the needs of different scenarios in the large and diverse WordPress ecosystem. And in all cases, the AMP plugin provides as much support as possible in terms of automating the generation of AMP pages, as well as keeping the option chosen AMP valid. In a nutshell, the available template modes are the following:
Standard Mode: This template mode is the ideal, as there is only one theme for serving requests and a single version of your site: the AMP version. Besides enabling all of your site to be AMP-first, this has the added benefit of reducing development and maintenance costs. This mode is the best choice for sites where the theme and plugins used in the site are fully AMP-compatible. It's also a good option if some components are not AMP-compatible but the site owner has the resources or the know-how to fix them. See our <a href="https://amp-wp.org/showcases/?template_mode=standard" rel="nofollow ugc">showcase</a> of sites using Standard mode.
Transitional Mode: In this mode there is also a single theme used, but there can be two versions of each page: AMP and non-AMP. The active theme is used for serving the AMP and non-AMP versions of a given URL. This mode is a good choice if the site uses a theme that is not fully AMP compatible, but the functional differences between the AMP and non-AMP pages are acceptable (due to graceful degradation). In this case, users accessing the site from mobile devices can get the AMP version and get an optimized experience which also retains the look and feel of the non-AMP version. Check out our <a href="https://amp-wp.org/showcases/?template_mode=transitional" rel="nofollow ugc">showcase</a> of sites using Transitional mode.
Reader Mode: In this mode there are two different themes, one for AMP pages and another for non-AMP pages, and therefore there are also two versions of the site. This mode may be selected when the site is using an AMP-incompatible theme, but the level of incompatibilities is significant without graceful degradation. It’s also a good choice if you are not technically savvy (or simply do not want to deal with the incompatibilities) and therefore want simplified and robust workflows that allow you to take advantage of AMP with minimal effort.
Different modes would be recommended in different scenarios, depending on the specifics of your site and your role. As you configure the plugin, it will suggest the mode that might be best for you based on its assessment of the theme and plugins used on your site. And, independently of the mode used, you have the option of serving all or only a portion of your site as AMP. This gives you all the flexibility you need to get started enabling AMP on your site progressively.
<h4>AMP Ecosystem</h4>
It is possible today to assemble great looking user-first sites powered by the AMP plugin by picking and choosing themes and plugins from a growing AMP-compatible ecosystem. In this context, the AMP plugin acts as an orchestrator of the overall AMP content creation and publishing process; it serves as a validator and enforcer making it easier to not only get to AMP experiences, but to maintain them with confidence.
Many popular theme and plugin developers have taken efforts to support the official AMP plugin. If you are using a theme like Astra or Newspack, or if you are using plugins like Yoast or WP Forms — they will work out of the box! You can see the <a href="https://amp-wp.org/ecosystem/" rel="nofollow ugc">growing list</a> of tested themes and plugins.
<h4>AMP Development</h4>
Although there is a growing ecosystem of AMP-compatible WordPress components, there is still a ways to go before majority AMP compatibility in the ecosystem. If you are a developer, or you have the resources to pursue development projects, you may want in some cases to develop custom plugin or theme to serve your specific needs. The official AMP plugin can be of great help to you by providing powerful and effective developer tools that shed light into the AMP development process as it is done in WordPress. This includes mechanisms for detailing the root causes of validation issues, the contextual space to understand them properly, and methods to deal with them during the process of achieving full AMP compatibility. Read more about <a href="https://amp-wp.org/documentation/getting-started/developer-tools/" rel="nofollow ugc">Developer Tools</a>.
<h4>Getting Started</h4>
To learn more about the plugin and start leveraging its capabilities to power your AMP publishing workflow, check <a href="https://amp-wp.org/" rel="nofollow ugc">the official AMP plugin product site</a>.
If you are a developer, we encourage you to <a href="https://github.com/ampproject/amp-wp" rel="nofollow ugc">follow along</a> or <a href="https://github.com/ampproject/amp-wp/wiki/Contributing" rel="nofollow ugc">contribute</a> to the development of this plugin on GitHub.
We have put up a comprehensive <a href="https://amp-wp.org/documentation/frequently-asked-questions/" rel="nofollow ugc">FAQ page</a> and extensive documentation to help you start as smoothly as possible.
But if you need some help, we are right here to support you in the plugin’s <a href="https://wordpress.org/support/plugin/amp/" rel="ugc">support forum</a>, as well as through <a href="https://github.com/ampproject/amp-wp/issues" rel="nofollow ugc">GitHub issues</a> (for technical bugs and feature requests). And our thriving <a href="https://amp-wp.org/ecosystem/amp-experts/" rel="nofollow ugc">AMP Expert ecosystem</a> has indie freelancers to enterprise grade agencies in case you need commercial support!

It's best AMP plugin for WP. With good support team

Best AMP plugin for WP

Memory usage jumped from 5% to 91% when this plugin was activated.

Killed Php Memory

Excellent tool.

Very good plugin


I tried it when AMP was a "must have" but it’s just adding problems to your site. All the work you make on your site to give a good experience for your users is broken by AMP rendering. SEO is worst and the product helps only Google to make money on your work. Don’t install it, choose a light theme and put your effort on the theme.


Bad Experience

An easier path to great Page Experience for everyone. Powered by AMP.

Voxfor Autopilot vs AMP