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.

WordPress.org

This plugin optimizes the loading of images (and videos) with prioritization to improve <a href="https://web.dev/articles/lcp" rel="nofollow ugc">Largest Contentful Paint</a> (LCP), lazy loading, and more accurate image size selection.
The current optimizations include:
<ol>
<li>Add breakpoint-specific <code>fetchpriority=high</code> preload links (both as <code>LINK[rel=preload]</code> elements and <code>Link</code> response headers) for image URLs of LCP elements:
<ol>
<li>An <code>IMG</code> element, including the <code>srcset</code>/<code>sizes</code> attributes supplied as <code>imagesrcset</code>/<code>imagesizes</code> on the <code>LINK</code>.</li>
<li>The first <code>SOURCE</code> element with a <code>type</code> attribute in a <code>PICTURE</code> element. (Art-directed <code>PICTURE</code> elements using media queries are not supported.)</li>
<li>An element with a CSS <code>background-image</code> inline <code>style</code> attribute.</li>
<li>An element with a CSS <code>background-image</code> applied with a stylesheet (when the image is from an allowed origin).</li>
<li>A <code>VIDEO</code> element’s <code>poster</code> image.</li>
</ol>
</li>
<li>Ensure <code>fetchpriority=high</code> is only added to an <code>IMG</code> when it is the LCP element across all responsive breakpoints.</li>
<li>Add <code>fetchpriority=low</code> to <code>IMG</code> tags which appear in the initial viewport but are not visible, such as when they are subsequent carousel slides.</li>
<li>Lazy loading:
<ol>
<li>Apply lazy loading to <code>IMG</code> tags based on whether they appear in any breakpoint’s initial viewport.</li>
<li>Implement lazy loading of CSS background images added via inline <code>style</code> attributes.</li>
<li>Lazy-load <code>VIDEO</code> tags by setting the appropriate attributes based on whether they appear in the initial viewport. If a <code>VIDEO</code> is the LCP element, it gets <code>preload=auto</code>; if it is in an initial viewport, the <code>preload=metadata</code> default is left; if it is not in an initial viewport, it gets <code>preload=none</code>. Lazy-loaded videos also get initial <code>preload</code>, <code>autoplay</code>, and <code>poster</code> attributes restored when the <code>VIDEO</code> is going to enter the viewport.</li>
</ol>
</li>
<li>Responsive image sizes:
<ol>
<li>Ensure <a href="https://make.wordpress.org/core/2024/10/18/auto-sizes-for-lazy-loaded-images-in-wordpress-6-7/" rel="nofollow ugc"><code>sizes=auto</code></a> is set on <code>IMG</code> tags after setting correct lazy-loading (above).</li>
<li>~~Compute the <code>sizes</code> attribute using the widths of an image collected from URL Metrics for each breakpoint (when not lazy-loaded since then handled by <code>sizes=auto</code>).~~ (This has been removed due to an <a href="https://github.com/WordPress/performance/issues/2098" rel="nofollow ugc">issue</a>; use <a href="https://wordpress.org/plugins/auto-sizes/" rel="ugc">Enhanced Responsive Images instead</a>.)</li>
</ol>
</li>
<li>Reduce the size of the <code>poster</code> image of a <code>VIDEO</code> from full size to the size appropriate for the maximum width of the video (on desktop).</li>
</ol>
This plugin requires the <a href="https://wordpress.org/plugins/optimization-detective/" rel="ugc">Optimization Detective</a> plugin as a dependency. Please refer to that plugin for additional background on how this plugin works as well as additional developer options.
👉 Note: This plugin optimizes pages for actual visitors, and it depends on visitors to optimize pages. As such, you won’t see optimizations applied immediately after activating the plugin. Please wait for URL Metrics to be gathered for both mobile and desktop visits. And since administrator users are not normal visitors typically, optimizations are not applied for admins by default.
Your site must have the REST API accessible to unauthenticated frontend visitors since this is how metrics are collected about how a page should be optimized. There are currently no settings and no user interface for this plugin since it is designed to work without any configuration.

Image Prioritizer

Prioritizes the loading of images and videos based on how they appear to actual visitors: adds fetchpriority, preloads, lazy-loads, and sets sizes.

Voxfor Autopilot vs Image Prioritizer