| 1 |
=== Search Atlas SEO - OTTO AI SEO Automation for WordPress === |
| 2 |
Contributors: shahrukhlinkgraph |
| 3 |
Tags: seo, ai seo, otto, otto seo, schema |
| 4 |
Requires at least: 6.3 |
| 5 |
Tested up to: 7.1 |
| 6 |
Requires PHP: 8.1 |
| 7 |
Stable tag: 2.7.2 |
| 8 |
License: GPL v3 |
| 9 |
License URI: https://www.gnu.org/licenses/gpl-2.0.txt |
| 10 |
|
| 11 |
AI-powered SEO & GEO for WordPress: OTTO auto-optimizes meta, schema & content, and helps you rank on Google and in AI search. |
| 12 |
|
| 13 |
== Description == |
| 14 |
|
| 15 |
**AI-powered SEO for WordPress — built for Google rankings and the new era of AI search.** |
| 16 |
|
| 17 |
Search Atlas connects your WordPress site to the Search Atlas platform and its OTTO AI optimization engine, automating the technical SEO work that used to take hours. Optimize for traditional search engines and for AI answer engines (GEO — Generative Engine Optimization), publish content in one click, and manage your entire on-page SEO from a single dashboard. |
| 18 |
|
| 19 |
### OTTO — AI SEO on autopilot |
| 20 |
OTTO server-side optimizes your pages for search crawlers and AI engines: meta titles and descriptions, image alt text, headings, and internal links are applied automatically, without changing your theme. Roll fixes out across up to 100 pages at once, exclude any URL, and optionally save optimizations into native WordPress fields so they persist even if you switch tools. |
| 21 |
|
| 22 |
### Get found in AI search (GEO) |
| 23 |
A built-in /llms.txt endpoint serves clean, AI-readable content to AI crawlers such as ChatGPT and Perplexity — so your site can surface in AI answers and AI Overviews, not just classic search results. |
| 24 |
|
| 25 |
### One-click publishing from Search Atlas |
| 26 |
Push blog posts, landing pages, and content updates straight from the Search Atlas dashboard to WordPress — complete with optimized titles, meta descriptions, image alt text, formatted headings, and internal links. |
| 27 |
|
| 28 |
### Bulk AI optimization |
| 29 |
- AI bulk meta updates — rewrite titles and descriptions across your whole site in one pass |
| 30 |
- AI alt-text generation & auditing — find missing or weak alt text and fix it library-wide |
| 31 |
- Bulk status and content operations to manage many posts at once |
| 32 |
|
| 33 |
### A complete on-page SEO toolkit |
| 34 |
- 13 schema / structured-data types (Article, FAQ, Product, Recipe, Event, LocalBusiness, HowTo, VideoObject, and more) with JSON-LD output |
| 35 |
- XML sitemaps, including dedicated news and video sitemaps |
| 36 |
- Virtual robots.txt editor — manage rules with no file editing |
| 37 |
- Redirection manager — 5 match types (exact, wildcard, regex, contains, start/end) and 4 status codes (301/302/307/308), with automatic redirects on slug changes |
| 38 |
- 404 monitoring with hit tracking and smart redirect suggestions |
| 39 |
- Breadcrumb schema, canonical URLs, and hreflang (multi-language) support |
| 40 |
- Open Graph and Twitter Card meta with automatic de-duplication |
| 41 |
|
| 42 |
### Instant indexing |
| 43 |
Submit new and updated URLs directly to Google (Instant Indexing API) and Bing (IndexNow) for faster crawling — one at a time or in bulk. |
| 44 |
|
| 45 |
### MCP server — control WordPress with AI agents |
| 46 |
A built-in Model Context Protocol (MCP) server exposes 138 tools across 31 categories, letting AI assistants create and edit content, manage SEO and schema, submit URLs for indexing, handle redirects, and audit your site — secured with API-key or token authentication. |
| 47 |
|
| 48 |
### Media & performance |
| 49 |
- Convert images to WebP/AVIF, smart lazy-loading, and automatic width/height attributes to reduce layout shift (CLS) |
| 50 |
- Automatic cache purging for popular caching plugins (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, and more) |
| 51 |
- Edge/CDN cache purging for Cloudflare, Fastly, Akamai, and Sucuri |
| 52 |
|
| 53 |
### Works with your stack |
| 54 |
- Page builders: Gutenberg, Elementor, Divi, Oxygen, and Beaver Builder |
| 55 |
- WooCommerce breadcrumbs and shop pages |
| 56 |
- Coexistence and migration with Yoast SEO, Rank Math, and All in One SEO |
| 57 |
- Google Search Console and GA4 integration |
| 58 |
- Agency-ready white-label settings to show or hide features per client |
| 59 |
|
| 60 |
### Search Atlas account & external service |
| 61 |
Search Atlas is a companion plugin for the Search Atlas platform, an external service. A Search Atlas account is required to use the AI optimization, OTTO, and content-publishing features. When connected, your site sends and receives data from Search Atlas servers to provide these features. Learn more in the Search Atlas Terms of Service (https://searchatlas.com/terms/) and Privacy Policy (https://searchatlas.com/privacy-policy/). |
| 62 |
|
| 63 |
== Installation == |
| 64 |
1. In your WordPress admin, go to Plugins, then Add New, and search for Search Atlas SEO. Click Install Now, then Activate. |
| 65 |
2. You need a Search Atlas account. If you do not have one, start a free trial at searchatlas.com. |
| 66 |
3. In Search Atlas, add your site as a project. Then, in WordPress, open the Search Atlas menu and click Connect to Search Atlas. The plugin will automatically complete the secure SSO connection. |
| 67 |
4. Switch OTTO on. |
| 68 |
|
| 69 |
Installing by hand: download the ZIP, upload the `metasync` folder to `/wp-content/plugins/`, then activate it from the Plugins menu. After that, continue from step 2. |
| 70 |
|
| 71 |
== Frequently Asked Questions == |
| 72 |
|
| 73 |
= What does the Search Atlas SEO plugin do? = |
| 74 |
It connects your WordPress site to Search Atlas so OTTO, our AI optimization engine, can work on your pages. It applies titles, descriptions, alt text, headings, internal links and schema, and it lets you publish content straight from Search Atlas into WordPress in one click. You need a Search Atlas account to use it. |
| 75 |
|
| 76 |
= Do I need a paid Search Atlas account to use this plugin? = |
| 77 |
Yes. The plugin connects to your Search Atlas account, and OTTO's AI-driven SEO features are available on paid Search Atlas plans. |
| 78 |
|
| 79 |
= Where do I get my API key? = |
| 80 |
You don't need to enter one manually. Use the "Connect to Search Atlas" option in the plugin settings, and it will generate your API key and connect your account automatically. |
| 81 |
|
| 82 |
= Does it work alongside Yoast SEO or Rank Math? = |
| 83 |
Yes. The plugin detects Yoast SEO, Rank Math, and All in One SEO, avoids duplicate meta tags and schema conflicts, and includes an "Import from Other SEO Plugins" feature that imports meta titles, descriptions, canonical tags, schema, and redirects from those plugins directly into Search Atlas SEO. |
| 84 |
|
| 85 |
= How do I turn OTTO off for one page? = |
| 86 |
You can exclude individual URLs from OTTO processing in the plugin's OTTO settings, so those pages render as they normally would without OTTO's changes. |
| 87 |
|
| 88 |
= Can I manage 404 errors and redirects with this plugin? = |
| 89 |
Yes, along with a lot more - the plugin also includes media optimization, code snippets, code minification, cache busting, and much more. |
| 90 |
|
| 91 |
== Screenshots == |
| 92 |
1. General Settings |
| 93 |
|
| 94 |
== Upgrade Notice == |
| 95 |
= 2.6.22 = |
| 96 |
2.6.22 fixes OTTO breaking Divi-built pages and stops a partly finished update from taking your site's front end down. Update as soon as you can. |
| 97 |
|
| 98 |
== Changelog == |
| 99 |
= 2.7.2 = |
| 100 |
* New Feature: Opt-in product analytics for the plugin admin, sent only after the site owner gives consent; existing installs are asked once through a dismissible notice that can be snoozed |
| 101 |
* New Feature: The Classic Editor SEO box now includes the Breadcrumb Title, Language Alternates and Primary Category fields |
| 102 |
* New Feature: OTTO webhook deliveries are now recorded in an audit log that is kept for seven days |
| 103 |
* Fix: OTTO's canonical URL is now kept on every render path instead of falling back to the permalink when the full OTTO render is skipped |
| 104 |
* Fix: OTTO no longer saves the og:description as the page's meta description |
| 105 |
* Fix: OTTO deployments are no longer lost when a cache warm-up fails, and stored OTTO titles, descriptions and keywords now refresh when the OTTO cache expires, so a missed OTTO notification no longer leaves stale SEO values behind |
| 106 |
* Fix: Fresh OTTO titles and descriptions now take priority over older persisted copies, and focus keywords follow the same priority order with duplicate meta keywords tags removed |
| 107 |
* Fix: Persisted OTTO keywords are now stored separately and no longer overwrite the customer's own keyword; the global priority setting is now named SEO Meta Priority |
| 108 |
* Fix: OTTO is now skipped on paginated archive pages only on Divi sites instead of on every site |
| 109 |
* Fix: Invalid values can no longer be stored as the OTTO Pixel UUID, and the UUID field is now read-only |
| 110 |
* Fix: The OTTO crawl data option no longer grows without limit, and the old stored data is cleaned up on upgrade |
| 111 |
* Fix: External schema import now reports accurate eligibility and results for Yoast, Rank Math and AIOSEO, and schema fields are no longer lost when a schema type is saved before its fields finish loading |
| 112 |
* Fix: Content publishing no longer takes over and unpublishes an existing post with the same title, and updates now return the correct permalink |
| 113 |
* Fix: White-label branding is now preserved when the plugin settings are reset, and invalid branding can no longer be saved, with each field showing its own error |
| 114 |
* Fix: The old Instant Indexing admin URL now redirects to Indexation Control instead of showing an access error |
| 115 |
* Fix: Indexation Controls now save each checkbox correctly instead of switching other archive rules on |
| 116 |
* Fix: Maintenance and diagnostics tasks can no longer be triggered by anonymous visitors, and access checks, error logging, sitemap size reporting and the blank page template have been hardened |
| 117 |
* Fix: Redirects that have never been used now show "Never" instead of a zero date, and the redirect form no longer saves empty rows |
| 118 |
* Fix: MCP category and tag creation now returns the existing term instead of failing when it already exists |
| 119 |
* Fix: Resolved the remaining errors from WordPress.org Plugin Check scans |
| 120 |
* Improvement: Media, REST API and 404 Monitor queries are optimized for large sites, and the 404 log is now capped |
| 121 |
* Improvement: Redirects that share the same source path now show a "Shadowed" badge and a warning on save |
| 122 |
* Improvement: The 404 Monitor now has clearer summary labels, short and distinct chart labels (including for non-ASCII URLs), and a cleaner toolbar and pagination |
| 123 |
* Improvement: Compatibility toggles have moved to the Compatibility page, the unused HTTP option was removed from the SiteGround setting, and WP Rocket is now detected reliably |
| 124 |
* Improvement: The robots.txt "Never block your entire site" warning now appears at the top of the editor sidebar, and the Excluded URLs Recheck button and match type badges are now consistently sized |
| 125 |
* Improvement: The Breadcrumb Title Override is now hidden when breadcrumbs are disabled |
| 126 |
* Improvement: Plugin issue reports now include white-label context, and white-label settings are no longer exposed through the MCP plugin settings tool |
| 127 |
* Improvement: Removed the orphaned standalone Instant Indexing save path and obsolete temporary admin access code |
| 128 |
|
| 129 |
= 2.7.1 = |
| 130 |
* Fix: The Changes Log admin page no longer shows misaligned headings or inconsistent toolbar control sizing |
| 131 |
* Fix: A "%" character in a saved settings value no longer fatals the page, and the plugin now survives partially-completed upgrades |
| 132 |
* Fix: Direct-access protection was added to PHP files that were missing it |
| 133 |
* Fix: Discouraged PHP functions were replaced with WordPress-native APIs across the codebase, confirmed dead code was removed, and the remaining intentional native calls are now documented |
| 134 |
* Fix: Audited and resolved SQL query safety findings across the plugin |
| 135 |
* Fix: Audited and resolved input sanitization and output escaping gaps across admin and public-facing code, including AJAX and settings save paths |
| 136 |
* Fix: Added missing nonce and capability checks across admin endpoints, AJAX handlers, and settings page actions |
| 137 |
* Fix: Redirects are now routed through safe WordPress redirect functions, data-directory writes are centralized, and legacy redirect rows with un-sanitized source URLs are healed automatically |
| 138 |
* Fix: Removed stray production debug logging and correctly scoped error handlers |
| 139 |
* Fix: The plugin FAQ now uses American spelling ("optimization"), matching the rest of the listing |
| 140 |
* Fix: Audited direct database queries, caching, and schema changes for WordPress.org compliance |
| 141 |
* Fix: Resolved internationalization findings so plugin text is properly translatable |
| 142 |
* Fix: Resolved the remaining zero-risk and newly-reported findings from ongoing WordPress.org Plugin Check scans |
| 143 |
* Improvement: Compatibility-checker plugin icons are now bundled locally instead of loaded from an external host |
| 144 |
|
| 145 |
= 2.7.0 = |
| 146 |
* New Feature: Headless WordPress support — the WordPress backend and a decoupled public frontend now stay in sync through SSO and heartbeat, with SEO data exposed over WPGraphQL, frontend-aware canonical and og:url rehosting, taxonomy canonical overrides, bulk payload resolution, and a dedicated Headless Mode section in Advanced settings |
| 147 |
* New Feature: Safe OTTO Persistence restore — original Yoast, Rank Math and AIOSEO values are backed up before OTTO writes to them, nothing is written without explicit consent, and a restore action rolls every value back to its original state |
| 148 |
* New Feature: Language Alternates (hreflang) can now be switched on or off per post and page from the editor settings |
| 149 |
* New Feature: A global setting now controls whether OTTO or custom SEO values take priority across the site |
| 150 |
* Fix: Core infrastructure sweep — resolved deactivation data loss, wp-config fatals and media metadata corruption across the plugin |
| 151 |
* Fix: SEO Health now credits titles and descriptions that OTTO has already applied instead of reporting them as missing |
| 152 |
* Fix: Classic Editor post saves no longer discard persisted OTTO schema |
| 153 |
* Fix: OTTO titles and descriptions containing curly quotes or dashes now save correctly instead of failing silently |
| 154 |
* Fix: OTTO renders now keep third-party og:title and twitter:title instead of stripping them |
| 155 |
* Fix: Sitemaps no longer include URLs that redirect elsewhere, whether the redirect comes from MetaSync, Rank Math or Yoast |
| 156 |
* Fix: The Visual HTML Editor now refuses saves that cannot preserve the stored document, protecting landing pages and full-document templates |
| 157 |
* Fix: Redirect destination and loop guards now apply on every write path, closing the gaps that allowed self-referencing and looping redirects |
| 158 |
* Fix: Language Alternates no longer emit duplicate tags on WPML sites, always include a self-reference, and validate their entries |
| 159 |
* Fix: The Instant Indexing service account file can now be saved, with clear upload confirmation and the ability to remove or reselect it |
| 160 |
* Fix: Plugin updates no longer fatal on a stale admin class during a White Label import |
| 161 |
* Improvement: SEO Health missing title and description filters are now optimized for large catalogues |
| 162 |
* Improvement: SEO Health exclusion queries, counting and CSV export are optimized for sites with heavy post metadata |
| 163 |
* Improvement: Frontend assets are now loaded only where they are needed, and duplicate WebPage schema nodes are removed |
| 164 |
* Improvement: The third-party SEO plugin sync screen has been redesigned and now respects white-label branding |
| 165 |
* Improvement: The duplicate Instant Indexing admin page has been removed and its functionality consolidated into Indexation Control |
| 166 |
* Improvement: The duplicate Primary Category control has been removed from the MetaSync editor sidebar |
| 167 |
* Improvement: The redirection list no longer repeats the match type in the From column |
| 168 |
* Improvement: The Changes Log now distinguishes OTTO cleanup events from new SEO deployments, so log entries reflect what actually happened |
| 169 |
|
| 170 |
= 2.6.26 = |
| 171 |
* Fix: Yoast schema conflict handling no longer emits invalid JSON-LD on OTTO-covered pages |
| 172 |
* Fix: Third-party SEO sync now reports success only when SEO data was actually written, preventing stale titles from being treated as current |
| 173 |
* Fix: The Gutenberg SEO sidebar no longer uses OTTO suggestions as field values, so pages are not silently frozen out of OTTO |
| 174 |
* Improvement: Breadcrumb settings are now managed from one dedicated settings page instead of duplicate controls |
| 175 |
* Fix: News and video sitemaps now use consistent source ordering and regenerate news entries within the required freshness window |
| 176 |
* Improvement: The Visual HTML Editor now bundles its own runtime, so it loads correctly for raw-HTML pages without relying on a CDN |
| 177 |
* Fix: Redirection and 404 list filters no longer trigger a selected bulk action accidentally |
| 178 |
* Fix: Open Graph opt-out now suppresses all matching MetaSync social output paths |
| 179 |
* Fix: The Gutenberg SEO sidebar no longer shows a duplicate URL Slug field |
| 180 |
* Fix: Social titles and descriptions no longer persist pre-filled post defaults, so renamed posts and edited excerpts update their social metadata correctly |
| 181 |
* Security: White Label JSON imports no longer lock out the settings password recovery flow, so Forgot Password keeps working when a new whitelabel-settings.json is deployed |
| 182 |
|
| 183 |
Older release notes are available in the CHANGELOG.md file included with the plugin. |
| 184 |
|
