Amplest Autopilot — AEO & AI Search Optimization for WordPress
| 开发者 |
amplest
2ndbrospec |
|---|---|
| 更新时间 | 2026年5月19日 18:40 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
AI is reading your content. But is it recommending your site?
Every day, ChatGPT, Gemini, Perplexity, Copilot, and Claude scrape WordPress sites to answer user questions. They use your content to build their answers — but without AEO (Answer Engine Optimization), they cite your competitor instead of you.
Strong Google SEO doesn't fix this. A #1 ranking means nothing to AI citation. A competitor with weaker SEO can beat you in AI search if their structured data, FAQ schema, and authority signals are better configured than yours. Your content feeds the AI. Someone else gets the customer.
Amplest Autopilot adds the AEO layer that makes AI cite you — without touching your Yoast SEO, Rank Math, or All in One SEO configuration.
It works alongside your existing SEO setup. Never overwrites. Never conflicts. The plugin detects which SEO plugin you're running and integrates through its official hooks — so you keep one clean
<meta name="description"> and no duplicate structured data.
This plugin is the on-site engine of Amplest — an AI search optimization platform. Install it and your WordPress site connects to Amplest's cloud intelligence: continuous LLM citation monitoring, AI-powered diagnosis, and automated fixes pushed directly to your site. The plugin handles the on-site layer; Amplest handles the strategy.
What works on your site from day one (free, no account needed)
Activate the plugin and your site immediately gets the AEO foundation that makes AI citation possible — no license key, no account, no configuration required.
- Structured Data (JSON-LD) — Automatically generates and injects Organization, WebSite, Article, FAQPage, and BreadcrumbList schemas into
<head>. Works alongside Yoast, Rank Math, and All in One SEO without duplicate tags. - Auto FAQ Detection — Scans post content for question-pattern headings (English and Japanese) and converts them into FAQPage schema automatically. No manual markup needed.
- AEO Metabox — Add an AI summary, target keywords, and custom Q&A in the post editor to guide how AI reads and cites your content.
- llms.txt — Dynamically serves
/llms.txtper the llmstxt.org standard — an always-current map of your key content for AI crawlers. - AI Score Widget — See your AI visibility score directly in the WordPress dashboard.
- LLM Citation Monitoring — Your site is tested across ChatGPT, Gemini, Perplexity, Copilot, and Claude to track whether and how they cite you.
- AI-Powered Diagnosis — Amplest scans your site, identifies what's limiting your AI visibility, and generates a prioritized improvement list.
- Automated Fix Application — Approved improvements are pushed to your site through the plugin's REST API — structured data, meta tags, and AEO fields updated without touching your theme or post content.
- Snapshot & Rollback — Every applied fix is snapshotted before it runs. Roll back any change at any time from the Amplest dashboard.
- Monthly / Weekly Reports — Track your AI visibility score over time with detailed diagnosis and improvement history.
安装:
- In your WordPress admin, go to Plugins > Add New
- Search for Amplest Autopilot
- Click Install Now, then Activate
- Go to Settings > Amplest Autopilot to configure the plugin
- Enter your license key and click Activate License
- Upload the plugin folder to
/wp-content/plugins/amplest-autopilot/ - Activate the plugin from the Plugins screen in WordPress
- Go to Settings > Amplest Autopilot to configure
屏幕截图:
常见问题:
My SEO is strong. Why isn't ChatGPT recommending my site?
Because SEO and AEO are different games. Google ranks pages by authority, backlinks, and relevance. AI tools like ChatGPT, Gemini, and Perplexity cite pages based on structured data completeness, FAQ schema, answer-ready content structure, and authorship signals — none of which SEO rankings measure. A competitor with weaker SEO but proper AEO setup can outrank you in AI search. Amplest Autopilot adds that AEO layer automatically.
Does this replace Yoast SEO or Rank Math?
No — it runs alongside them. Amplest Autopilot handles AEO (AI citation optimization), which is a separate layer from what Yoast and Rank Math do. Yoast and Rank Math optimize for Google search. Amplest optimizes for AI citation. You need both. As of v1.4.0, Amplest integrates through Yoast's and Rank Math's official filter hooks, so there are no duplicate meta tags and no conflicts.
I already use a structured data plugin. Will this conflict?
Amplest Autopilot detects existing structured data output from Yoast SEO, Rank Math, All in One SEO, and The SEO Framework. Where those plugins already emit breadcrumb schema, Amplest skips its own BreadcrumbList output to prevent duplicates. Meta description and title are written through each plugin's official hooks — one clean tag, no conflicts.
Can I use this alongside Yoast SEO, Rank Math, or All in One SEO?
Yes — and as of version 1.4.0, Amplest Autopilot explicitly integrates with them. When Yoast SEO, Rank Math, All in One SEO, or The SEO Framework is active, Amplest applies its meta description and title through that plugin's official filter hooks (wpseo_metadesc, rank_math/frontend/description, aioseo_description, the_seo_framework_description), so you keep a single <meta name="description"> tag with the Amplest-optimized value — no duplicate tags, no conflicts. BreadcrumbList JSON-LD is also automatically skipped when one of these plugins is already emitting breadcrumb schema, to avoid duplicate structured data warnings in Search Console.
Where do I get a license key?
Create an account at amplest.cloud, choose a plan, and your license key will be issued immediately.
What can I use on the Free plan?
The Free plan automatically injects all structured data types (Organization, WebSite, Article, FAQPage, BreadcrumbList), enables the AEO metabox in the post editor, generates /llms.txt for AI crawlers, and shows the AI Score widget in your dashboard — no license key required. All on-site features are fully functional without an account.
How does Auto FAQ Detection work?
Amplest Autopilot scans your post content for H2/H3 headings that look like questions — headings ending with ?, or starting with words like "What", "How", "Why", "Can", etc. (English) or containing patterns like「とは」「方法」（Japanese). Matching heading + paragraph pairs are automatically converted into FAQPage structured data.
What is the AI Score?
The AI Score reflects how well your site is positioned to be cited by the 5 major LLMs. Amplest scans your site across ChatGPT, Gemini, Perplexity, Copilot, and Claude and returns a score from 0–100. Higher scores mean better AI visibility.
What is llms.txt?
llms.txt is an emerging standard (llmstxt.org) that helps AI crawlers quickly understand a website's structure and key content — similar to robots.txt but designed for large language models. Amplest Autopilot generates this file dynamically, so it always reflects your latest pages and articles.
Can I roll back an automatic fix?
Yes. Before every automatic fix is applied, the plugin creates a snapshot of the existing data and saves a WordPress post revision. You can roll back any applied fix at any time from the Amplest dashboard.
更新日志:
1.5.2
- Fixed:
add_structured_dataandadd_faq_schemaactions now accept content wrapped in<script type="application/ld+json">...</script>tags (the format that AI commonly outputs). Previously, the plugin rejected anything but raw JSON, causing approved actions to fail silently. Both formats are now accepted and normalized. - Fixed:
add_faq_schemanow also accepts a fullFAQPageJSON-LD object (withmainEntity[].nameandacceptedAnswer.text) and converts it internally to the question/answer pairs the metabox stores. Previously it required a flat[{question, answer}, ...]array.
- Added:
/wp-json/amplest/v1/trigger-pullendpoint — allows the Amplest cloud (or an authenticated admin) to fire the pull immediately without waiting for the next WP-cron tick. Authenticated byX-Amplest-License-Key. Returns processed/success/failed counts and duration. Essential for sites where WP-cron is disabled, blocked by WAF, or unreliable due to low traffic. - Added:
amplest_last_pull_atoption records the timestamp of every pull attempt. Exposed via the/pingendpoint so the Amplest cloud can detect "stuck" sites (no recent pull despite pending actions) and trigger them on demand. This makes the pull architecture resilient to WP-cron failures — the cloud watchdog ensures approved actions are applied even if the site never spawns its own cron. - Added: Activation now immediately invokes
do_action('amplest_pull_actions')after scheduling, so the first pull runs at activation time instead of waiting up to 15 minutes. - Added:
/pingnow also reportsendpoints.trigger_pullandlast_pull_atfor observability.
- Changed (Architecture): Migrated from push-based to pull-based action delivery. The plugin's own WP-Cron now polls the Amplest cloud every 15 minutes for approved improvement actions, applies them locally, and reports the result back. The Amplest cloud no longer pushes inbound requests to
/apply-fixfor normal action delivery. This removes the need for the Amplest cloud to reach your site over the public internet, improving compatibility with sites behind authentication, IP allowlists, staging environments, or restrictive WAF rules. - Removed:
/wp-json/amplest/v1/apply-fixendpoint — no longer needed under the pull architecture./rollbackand/posts/draftremain for explicit user-triggered operations from the Amplest dashboard. - Added:
/wp-json/amplest/v1/pingnow reportsarchitecture: "pull"so the Amplest cloud can detect the plugin's communication mode. - Added: Outbound calls —
GET https://amplest.cloud/api/wp/pending-actions(poll for approved actions) andPOST https://amplest.cloud/api/wp/confirm-action(report execution result). Both authenticated viaX-Amplest-License-Key. - Action delivery latency: previously near-instant after approval (push), now up to 15 minutes (next pull cycle). Manual rollback from the dashboard remains immediate.
- Fixed:
apply-fixno longer checkscurrent_user_can('edit_post')when authenticated via license key — removed redundant WP capability check that blocked all license-key-authenticated requests with 403.
- Fixed: REST API endpoints now correctly read the license key from
amplest_license_dataoption (was referencing a non-existentamplest_license_keyoption, causing all authenticated requests to fail with 403).
- Security: REST API endpoints (
apply-fix,rollback,posts/draft) now authenticate via theX-Amplest-License-Keyheader instead of WordPress Application Passwords. No setup required — the license key entered during activation is reused automatically.
- Changed: Updated plugin icon to new brand logo (wing mark) — icon.svg, icon-128x128.png, and icon-256x256.png refreshed to match current brand identity.
- Changed: Admin settings page now displays the Amplest logo icon in the page header alongside the page title.
- Changed: Admin UI brand color updated from purple to emerald green to align with current brand identity.
- Fixed: improve_meta now actually replaces meta description and document title. Previous versions emitted a non-standard
<meta name="amplest:description">tag that had no SEO effect. The plugin now detects Yoast SEO, Rank Math, All in One SEO, or The SEO Framework and overrides the description/title via that plugin's filter hook (avoiding duplicate tags). When no SEO plugin is active, a standard<meta name="description">is emitted and the document title is filtered viapre_get_document_title. - Added: improve_alt action_type — image alt attributes can now be auto-applied via post meta override (no post_content modification, fully reversible by deleting the meta entry). Renders at output time via
wp_get_attachment_image_attributesand a regex pass overthe_content. - Added: add_breadcrumb action_type — per-post breadcrumb flag plus a new
[amplest_breadcrumb]shortcode for HTML breadcrumb display. HTML breadcrumb is opt-in (shortcode placement), respecting WordPress.org guidelines on not surprising users. BreadcrumbList JSON-LD output now skips when Yoast / Rank Math / AIOSEO already emits it (duplicate-detection). - Added:
POST /wp-json/amplest/v1/posts/draftendpoint — receives AI-generated articles from the Amplest cloud and saves them as drafts for user review. Meta description is synced to Yoast / Rank Math / AIOSEO meta keys when detected. Idempotent by topic_id (reuses existing draft on retry). - Added: optimize_meta_for_ctr action_type — alias for improve_meta.
- Added:
/wp-json/amplest/v1/pingnow returnssupported_actions[],endpoints{}, anddetected_seo_pluginso the Amplest cloud can adapt requests to the installed plugin version. - Added: Dashboard widget now shows the 5 most recently applied improvements across the site (post title, change type, timestamp) with direct edit links.
- Changed:
/apply-fixand/posts/draftnow return HTTP 402 with an upgrade URL for sites on the Free plan. The Free plan provides local features (structured data, AEO metabox, llms.txt, AI Score widget) without restriction; auto-apply and article generation require a paid Amplest plan. - Removed: legacy
<meta name="amplest:description">/<meta name="amplest:title">output — these had no SEO effect and only added noise to<head>.
- Security: Improved REST API endpoint permissions — /apply-fix and /rollback now require edit_others_posts capability (Editor or Administrator) instead of edit_posts, and additionally verify the authenticated user can edit the specific target post (current_user_can('edit_post', $post_id)).
- Fixed: Refresh Score no longer sends an HTTP request to Amplest when no license key is configured — returns an informational error message instead.
- Fixed: Dashboard widget footer link now uses a direct UTF-8 arrow character instead of an HTML entity inside esc_html_e(), correcting display on English-locale sites.
- Fixed: Custom JSON-LD injected via the apply-fix REST endpoint is now output via wp_json_encode(json_decode()) instead of wp_kses(), ensuring valid and safe JSON output in all cases.
- Fixed: /apply-fix and /rollback REST endpoints now use WordPress Application Passwords for authentication instead of requiring an active paid license.
- Fixed: Settings page upgrade CTA now references cloud-only features (LLM monitoring, AI diagnosis, automated fix delivery) — no longer implies that local features require a paid plan.
- Fixed: Removed "Planner plan or higher required" notices from the Auto FAQ Detection and AEO Metabox settings. Both features are fully functional on all plans including Free.
- Added: "Amplest Cloud Connection" section in settings explaining how to set up WordPress Application Passwords for the Amplest service.
- Updated: External Services section in readme now separately documents outbound (plugin → Amplest) and inbound (Amplest → plugin webhook) communication, with specific API endpoint URLs and data sent.
- Changed: JSON-LD structured data (Article, FAQPage, BreadcrumbList, AEO summary) now available for all plans including Free
- Changed: AEO metabox (AI summary, keywords, FAQ) now fully accessible for all plans including Free
- Fixed: Removed
JSON_UNESCAPED_SLASHESfrom JSON-LD output to prevent potential XSS via</script>in content strings - Removed:
load_plugin_textdomain()call — WordPress auto-loads translations for plugins hosted on WordPress.org
- Added: llms.txt auto-generation — dynamically serves
/llms.txtfor AI crawlers (top 30 pages + 30 articles, with total count shown for larger sites) - Added: Snapshot and rollback system — every automatic fix creates a WordPress revision and a meta snapshot; roll back any change from the Amplest dashboard
- Added: Custom JSON-LD and meta tags injected via the Amplest REST API are now correctly output in
<head> - Fixed: License authentication in the REST API (
apply-fixendpoint was always returning 401 due to incorrect option key and field name) - Fixed:
plan_tiervalues from the Amplest API are now validated against a whitelist to prevent unexpected tier escalation - Fixed: All hardcoded Japanese strings in
admin.jsreplaced with localizedamplestAdmin.*values - Internationalization: all UI strings converted to English; Japanese .po/.mo files included
- Updated plan names to Free / Planner / Operator / Autopilot (aligned with amplest.cloud pricing)
- Initial release
- Auto JSON-LD injection (Organization, WebSite, Article, FAQPage, BreadcrumbList)
- Auto FAQ detection
- AEO metabox (AI summary, keywords, FAQ)
- AI Score dashboard widget
- License management system