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