OptimiseMy.AI Connector

No. The integration delivers content and configuration prepared by the paid managed service. Activation alone does not contact that service.

No. Our team creates and maintains your optimisation work through the external service. The plugin delivers that work to WordPress; llms.txt is one part of the integration alongside structured data, website-change notifications and reporting. It does not generate an optimisation strategy or llms.txt locally.

Yes. Reporting is included in the managed service. The first connection form preselects analytics and explains what is sent; the administrator can clear that choice before connecting. Plugin activation alone does not start analytics. Existing sites keep their saved analytics preference when upgrading.

No. Updates keep the saved analytics choice. On connected sites, enable analytics under Analytics and cache preferences and select Save preferences in that section. Clear page/CDN caches after changing the choice. Instant updates additionally require the separate one-time pairing step described under Installation; the scheduled refresh continues when WordPress Cron runs.

The plugin does not guarantee search rankings or AI recommendations. Requests served from a cache before WordPress runs cannot be observed by this plugin's PHP tracker. Browser analytics may be blocked by browser settings, consent tools or network failures.

The optional fallback uses WordPress's template enhancement mechanism, available from WordPress 6.9. It does not run on older WordPress versions, when the site disables template buffering to stream responses, or when a supported SEO plugin is active. Existing descriptions are preserved. The connector does not start or force its own output buffer. Other connector features remain available on supported older versions.

It can create llms.txt and llms-full.txt in the website root on supported installations. It replaces or removes only files with its ownership marker and matching saved checksum. Existing unrelated or edited files are kept. Physical robots.txt changes additionally require the service's explicit authorisation; the original is backed up and external edits are preserved. Virtual robots/sitemap output follows the preserve/override configuration managed for you by OptimiseMy.AI.

Scheduled work stops on deactivation. Unchanged plugin-owned text files and cache rules are removed, and a managed robots.txt is restored when its checksum still matches. Deactivation keeps connection settings for reactivation. Disconnect clears the saved token. Clear the site's page cache after either action. The external service's data is not deleted by deactivation; contact OptimiseMy.AI for account or data requests.

Directory installations use WordPress's standard update system. Automatic updates can be enabled by the site administrator. Updates retain this connector's saved connection and preferences. This edition uses the separate optimisemy-ai-connector folder and does not replace or import settings from the private aio-search plugin. Existing clients can stay on that integration. For a deliberate migration, back up the site, record the current settings and token, deactivate the private plugin, then connect this plugin with the same site token and verify delivery and analytics. Do not run both integrations together. The connector stays paused if it detects the private plugin is active.

No. It detects Yoast SEO, Rank Math and All in One SEO for meta/schema cooperation. Sitemaps default to deferring to WordPress or your SEO plugin unless an override is configured in the service. Compatibility must still be checked for the site's theme, plugins and caching setup.

No. From 1.12.2 the plugin no longer changes cache rules, and on update it removes the LiteSpeed rules and WP Fastest Cache exclusions that earlier versions added. Crawlers are served from your page cache like any other visitor.