AEO for WordPress: approve it, and it's a live page.

On WordPress, AEO Action runs its entire loop without a developer.Daily scans ask AI engines the questions your buyers ask; the department prepares the fix; and when you click Approve, the WordPress plugin publishes the finished landing page on your own site — title, slug, meta description, and the page's JSON-LD in wp_head — usually within the hour. No theme edits, no copy-paste, no snippet to place. This page walks the mechanics hour by hour, explains what the Approve click actually authorizes, and lists — honestly — what the plugin does not do.

The WordPress owner's reality

If you run your business on WordPress, you have probably lived some version of this: an SEO guide says “add LocalBusiness schema,” and the instructions start with functions.php. Or a tool hands you a snippet and a cheerful “just paste this into your header” — on the site where the last theme update broke the menu. The distance between knowing what to fix and touching the theme is where most WordPress AEO work quietly dies.

Meanwhile the answers moved. Buyers now ask AI assistants who to hire and what to buy, and Google itself answers ahead of its own links — roughly 48% of searches return an AI Overview above the organic results (Similarweb, March 2026). Ranking well no longer proves you are in those answers:

Most tools respond to that gap with a dashboard and a to-do list. On WordPress, a to-do list has a failure mode with a name: who pastes the schema? Who builds the page? Who clicks Publish, and when? If the answer is “you, after hours,” the work stalls — not because it is hard, but because it repeats. The premise of answer engine optimization done as software is that the repeating part should not be yours.

What the plugin does, on a clock

The plugin is a scheduler with four jobs. Once your project API key is pasted in — the whole install is a ZIP upload and one paste — this is its day:

• Every hour — approved landing pages.The plugin fetches any landing pages you approved in your AEO Action queue and creates each one as a real WordPress page: title, your chosen slug, meta description, the full body, and the page's own JSON-LD stored as post meta and emitted in wp_head on that page only. Not an iframe, not a hosted subdomain — a standard page in your site's theme that you can edit like any other.
• Every hour — schema. Your site-wide structured data — LocalBusiness, Organization, FAQPage, Service, Article, and BreadcrumbList — refreshes from the platform and is injected into the right pages through the standard wp_head hook. Structured data here does one job: it states your prices, hours, services, and Q&A in a format a machine can parse without interpreting, and it feeds classic rich results.
• Every six hours — blog drafts.Drafts from the content engine land in the plugin's Content screen for review. Auto-publish is off by default — drafts publish when you click, unless you deliberately flip the setting. Drafts are not approved pages, so they get a manual gate.
• Once a day — verification.The plugin reports what is actually live back to the platform, so your next scan's technical-readiness read reflects your real site, not an assumption about it.

Two details that matter more than they sound. Impatience is handled: a Publish approved pages now button on the plugin dashboard runs the sync immediately instead of waiting for the hour. And repetition is handled: the plugin keeps a local map of everything it has published, so a double-click or two overlapping cron runs cannot create the same page twice.

What the Approve click actually authorizes

The order of events is the whole design. Each day the orchestrator picks the highest-value move from your scan and prepares the full artifact — a landing page aimed at a question your buyers actually ask, a FAQ page, schema, or a Reddit pack — into an approve queue. Nothing publishes without your approval. That is not a WordPress setting; it is how the platform works everywhere.

The plugin's feed enforces the same rule from the server side. The endpoint it syncs from serves a landing page only when three things are true: you approved it, it has never been published to WordPress before, and it has real renderable content. The plugin cannot fetch — let alone publish — anything you did not approve, because the feed never contains it.

So when the page goes live without a second prompt, that is not the plugin being pushy — it is delivery of a decision you already made. The Approve click was the approval. If you want a WordPress-side second gate anyway — some owners do, and that caution is reasonable — it exists: one filter line sets aeo_platform_landing_post_status to draft, and every synced page arrives as a WordPress draft awaiting your second look.

What we do not do

A tool that installs software on your site owes you the negative list, so here is ours, unprompted:

• No theme edits. Everything rides the standard wp_head hook, deliberately late in head output so theme and SEO-plugin markup goes first. Full-page caching plugins capture it automatically.
• No fights with Yoast or Rank Math. Existing SEO plugins keep doing exactly what they do; our JSON-LD blocks are added alongside, never in place of theirs.
• No plugin-directory listing yet. You install from a ZIP in your dashboard. And because we are pre-launch, the honest install count is zero — judge the mechanism, because there is no crowd to follow.
• No multisite, for now. Version 1 is built for single-site installs; multisite support ships in a later release.
• No emailed reports and no card checkout yet. Reports live in the product and export as PDFs; nothing lands in an inbox on a schedule. And the 7-day trial takes no card because card billing is not live — the same fact, read from both sides.

From a scan to a dated receipt

Publishing is the middle of the loop, not the end. Start to finish, on WordPress:

1. The scan. Every day, your buyer questions — regenerated from your business profile each run, 50 per scan on Solo — are asked across the engines your plan covers, from a pool of up to six: ChatGPT and Gemini through their live consumer interfaces, Perplexity via its API, Google AI Overviews from live results, Copilot from Bing's answer layer, and Claude in a labeled model mode. Who gets named, and who gets cited, is recorded. The full playbook this feeds is in how to get mentioned by AI.
2. The preparation.The orchestrator picks one move and prepares the finished artifact into your queue. You read it. You approve it — or you don't.
3. The publish.The plugin's next hourly sync turns the approved page into a live WordPress page, slug and meta and schema included.
4. The report-back.The moment the page exists, the plugin reports its live URL to the platform, and four things happen at once: your dashboard flips the page to published, the Work Log records the event with the live link, fate-tracking is handed the URL it has been waiting for, and the URL is submitted through IndexNow — within minutes, provided your domain's key file is in place. Submission is our half; Bing decides what to index. The mechanics of that half are in Bing and Copilot optimization.
5. The receipt. Fate-tracking checks the page against its target question on every following scan for up to 120 days. If it gets cited, you get a dated receipt — shipped this date, first cited that date — and either way, a plain-English work report lands in the product every 7 days.

Why the Bing submission is automated at all — a measured reason:

The math, laid flat

A WordPress site has three realistic ways to buy this work. The rows below hold each one to the same questions; the arithmetic is yours to do. Wider cost context, every option priced, is in how much AEO costs in 2026.

When this is not your buy

The plugin is the right tool for a specific owner: a WordPress site, nobody on staff whose job is writing and shipping pages, and a willingness to spend one click a day approving finished work. Step outside that and the honest advice changes:

• You employ writers and want volume.Our orchestrator prepares one scan-chosen artifact a day; it is a department, not a printing press. If the job is high-output article production driven by your own writers, Writesonic's writer-led agent with one-click WordPress publishing is the sharper tool for that specific job — a competitor, recommended without a wince.
• Nobody will click Approve.The queue is the product's spine, not a formality. If prepared artifacts will sit unreviewed, you would be paying for a department that idles.
• Procurement runs the purchase. No SOC 2, no SSO, no panel-scale query-volume analytics. An enterprise checklist disqualifies us today, and pretending otherwise would waste your evaluation cycle.
• Your site is not WordPress. Different platform, different honest answer: Squarespace gets direct publishing with no plugin at all, Webflow is a genuinely contested platform worth comparing vendors on, and Wix gets paste-ready pages and schema with live verification — real output, but somebody pastes it.

And the exit cost, since every install decision should price the exit: close to nothing. Published pages are standard WordPress content that stays live and editable after the plugin is gone; uninstalling removes the plugin's own options, scheduled tasks, and post meta, and nothing else. What you would actually leave behind is the loop — the daily scan, the prepared artifacts, the receipts — not your pages.