Amplest Autopilot — AEO & AI Search Optimization for WordPress

گزارش تغییرات

1.5.2

• Fixed: add_structured_data and add_faq_schema actions 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_schema now also accepts a full FAQPage JSON-LD object (with mainEntity[].name and acceptedAnswer.text) and converts it internally to the question/answer pairs the metabox stores. Previously it required a flat [{question, answer}, ...] array.

1.5.1

• Added: /wp-json/amplest/v1/trigger-pull endpoint — allows the Amplest cloud (or an authenticated admin) to fire the pull immediately without waiting for the next WP-cron tick. Authenticated by X-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_at option records the timestamp of every pull attempt. Exposed via the /ping endpoint 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: /ping now also reports endpoints.trigger_pull and last_pull_at for observability.

1.5.0

• 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-fix for 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-fix endpoint — no longer needed under the pull architecture. /rollback and /posts/draft remain for explicit user-triggered operations from the Amplest dashboard.
• Added: /wp-json/amplest/v1/ping now reports architecture: "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) and POST https://amplest.cloud/api/wp/confirm-action (report execution result). Both authenticated via X-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.

1.4.4

• Fixed: apply-fix no longer checks current_user_can('edit_post') when authenticated via license key — removed redundant WP capability check that blocked all license-key-authenticated requests with 403.

1.4.3

• Fixed: REST API endpoints now correctly read the license key from amplest_license_data option (was referencing a non-existent amplest_license_key option, causing all authenticated requests to fail with 403).

1.4.2

• Security: REST API endpoints (apply-fix, rollback, posts/draft) now authenticate via the X-Amplest-License-Key header instead of WordPress Application Passwords. No setup required — the license key entered during activation is reused automatically.

1.4.1

• Changed: Updated plugin icon to new brand logo (wing mark) — icon.svg, icon-128×128.png, and icon-256×256.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.

1.4.0

• 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 via pre_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_attributes and a regex pass over the_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/draft endpoint — 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/ping now returns supported_actions[], endpoints{}, and detected_seo_plugin so 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-fix and /posts/draft now 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>.

1.3.1

• 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.

1.3.0

• 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.

1.2.0

• 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_SLASHES from 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

1.1.0

• Added: llms.txt auto-generation — dynamically serves /llms.txt for 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-fix endpoint was always returning 401 due to incorrect option key and field name)
• Fixed: plan_tier values from the Amplest API are now validated against a whitelist to prevent unexpected tier escalation
• Fixed: All hardcoded Japanese strings in admin.js replaced with localized amplestAdmin.* 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)

1.0.0

• 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