OptimiseMy.AI Connector

OptimiseMy.AI is a managed, done-for-you AI visibility service. Our team creates and maintains clients’ optimisation work through our platform. This plugin acts as the bridge between that service and a client’s WordPress website; clients do not need to create or manage the material themselves.

The wider service includes website analysis, content preparation, ongoing maintenance and reporting. The connector delivers the WordPress part of that work: managed structured data and published files, notifications when website content changes, and optional crawler and referral reporting. llms.txt is one component of this workflow, not the purpose or full scope of the service.

An active paid OptimiseMy.AI service arrangement and a site token are required. The WordPress plugin is free to download. The external service provides website analysis, content preparation, managed publication and reporting. It is not a standalone optimisation generator or a licence-unlocking service. Visit https://optimisemy.ai to arrange service access and get a token for your website.

Features:

• Add service-provided JSON-LD to pages and request complementary schema when supported SEO plugins are detected.
• Notify the service when public, non-password-protected content changes so the managed work can be reviewed and maintained.
• Optionally report recognised crawler requests, human visits and AI-referral visits for service reporting.
• Deliver files prepared and published by the service, including llms.txt, llms-full.txt, facts and schema files.
• Preserve existing meta descriptions and defer to supported SEO plugins. On WordPress 6.9 or later, add a service-prepared description when absent and template enhancement is enabled.
• Use the service’s preserve/override settings for robots.txt and sitemaps.
• Optionally manage marked LiteSpeed cache rules and tracked WP Fastest Cache crawler exclusions.

The plugin does not guarantee search rankings, AI recommendations or complete traffic measurement. A request served from a cache before WordPress runs cannot be observed by the PHP tracker. Browser analytics may be blocked by browser settings, consent tools or network failures.

The service connection and data sharing are explained on the plugin’s settings page. Analytics and cache management are optional. New installations leave these options off until the administrator enables them. Updates to this connector retain its saved connection and preferences. Settings from the separate private AIO Search plugin are not automatically imported.

The plugin includes its JavaScript source locally and uses WordPress.org for plugin updates. It does not download executable updates from OptimiseMy.AI or inject hidden crawler-only text.

External services

Service provider: OptimiseMy.AI (https://optimisemy.ai).
API host: https://hpmambxmbgedptuquoba.supabase.co/functions/v1/.

No requests to the OptimiseMy.AI service are made by a new, unconnected installation. Selecting Connect after confirming the service notice sends the token and site/home URLs to verify-wordpress-connection. A successful connection stores the token in WordPress settings. The token used for browser analytics is a public site identifier, not a WordPress administrator credential. A public browser API key is bundled for the service gateway; no privileged service key is included.

After connection:

• serve-file, get-schema and get-meta-description receive the token, site/page URL and relevant file type or SEO-plugin detection flag. They return the published files, structured data and descriptions used on the website. File/configuration refreshes run about every five minutes when WordPress Cron runs; page data is requested and cached as needed.
• get-diagnostic-stats receives the site token during configuration refreshes and authorised diagnostics. It returns delivery configuration and service status.
• wp-content-changed receives the token, public post ID/type/title, permalink and change type when public content is created, updated, unpublished or deleted. Requests are signed with the site token. Password-protected and non-public post types are excluded.
• log-plugin-error can receive the token, page URL and a short description of duplicate or unusually sized existing meta descriptions to help diagnose delivery issues.

When analytics is enabled:

• track-visit receives the token, visited URL, user-agent, referring page and request type. AI-referral receipts include a platform label, landing URL and referrer or recognised utm_source value. Server-side crawler receipts also include crawler identity, timestamp and available visitor IP/country data. Browser requests expose their connection IP to the service in the usual way. URLs may include campaign parameters.
• log-unclassified-ua receives an unrecognised bot-like user-agent, page path and site domain to improve crawler classification.

Cache verification and dynamic file-delivery checks make loopback requests to your own website. These checks do not create analytics receipts. Cache-management checks run only after connection and opt-in.

The site owner is responsible for explaining their analytics use to visitors and configuring consent controls where required. The plugin does not provide a consent-management platform. Disabling analytics or disconnecting stops new tracker output; clear any page/CDN cache to remove already cached output.

Terms of service: https://optimisemy.ai/terms
Privacy policy: https://optimisemy.ai/privacy
Support: https://optimisemy.ai

1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin, or install OptimiseMy.AI Connector from the directory once available.
2. Activate the plugin and open OptimiseMy.AI Connector in the admin menu.
3. Paste the site token supplied by OptimiseMy.AI for this website.
4. Read and confirm the service connection. Choose whether to enable analytics and cache management, then select Connect.
5. Check your published files and the connection diagnostics linked from the settings page. OptimiseMy.AI manages content and publication for you; a client dashboard login is not required.

The plugin is intended for a single WordPress site. Physical root-file and .htaccess management are disabled for multisite and subdirectory installations. Those installations require separate delivery verification and are not claimed as fully supported.

Does this work without the OptimiseMy.AI service?

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

Is this an llms.txt generator?

No. OptimiseMy.AI provides managed AI visibility work, and the plugin connects a client’s site to that work. It does not generate an optimisation strategy or llms.txt locally. Our team creates and maintains the material in the external service; file delivery is one part of the integration alongside structured data, website-change notifications and optional reporting.

Why is a missing meta description not always added?

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.

Does the plugin change existing files?

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.

What happens when I disconnect or deactivate?

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.

How are updates delivered?

Directory installations use WordPress’s standard update system. Automatic updates can be enabled by the site administrator. This directory edition uses the separate optimisemy-ai-connector folder and does not replace 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.

Does the plugin replace my SEO plugin?

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.

1.11.3

• Update the displayed plugin name to OptimiseMy.AI Connector.

1.11.2

• Add at most one missing meta description when a theme calls wp_head more than once.
• Clarify the managed, done-for-you service and the connector’s role beyond llms.txt.
• Use WordPress’s template enhancement filter for optional meta descriptions, without a plugin-owned output buffer.
• Keep analytics and cache management disabled when no explicit preference has been saved.

1.11.0

• Prepare the standalone WordPress.org distribution with bundled, readable scripts and standard WordPress updates.
• Repair browser analytics payloads and distinguish AI referrals from ordinary page views.
• Add explicit connection information and optional analytics/cache preferences.
• Harden request handling, JSON-LD output, diagnostics and protection of existing files.
• Preserve this connector’s connection settings during upgrades and deactivation.
• Use a separate directory identity and settings; pause while the private AIO Search integration is active.