Ooky AI Visibility

Ooky AI Visibility makes your WordPress site discoverable and accurate to AI assistants: ChatGPT, Claude, Perplexity, Google’s AI Overviews, and other LLM-driven crawlers.

The plugin does four things:

-

Serves distilled “cleaned HTML” to AI bots. When a known AI crawler hits a content page and an eligible artifact has been published, the plugin returns a noise-free, parity-gated version of that page (no nav/footer/scripts) in place of your theme’s markup, so models read your facts instead of your chrome. Humans always get your normal page.

-

org JSON-LD into your pages. Your latest published structured data is added to <head> so AI and search crawlers can index your brand facts.

-

Serves brand intelligence at well-known AI paths. well-known/mcp, the plugin returns a structured summary of your business, revalidated against the current Ooky hostname owner on every request.

-

Tracks AI-bot visits. On eligible public front-end requests—including the discovery paths—the plugin checks the User-Agent against a maintained registry. Detected visits enter a persistent, retrying local queue with stable IDs before delivery to Ooky.

Cleaned-HTML serving and JSON-LD injection read the same published artifacts as Ooky’s managed edge through an authenticated per-page API. They are revalidated rather than stale-served; if nothing is published or a fetch fails, your page renders normally. Logged-in, preview, password-protected, private, search, missing, WooCommerce cart/checkout/account, and recognized session requests keep their normal WordPress response.

Removing the local API key disables both behaviors. A site with a strict Content-Security-Policy (no unsafe-inline for script-src ) may need to allow the injected JSON-LD block.

js SDK ( @ooky/sdk ) and a Cloudflare Worker, all sharing an identical API contract.

You need an Ooky account with integrations enabled and the reveal-once domain API key. Without that key, manifest serving, cleaned HTML, JSON-LD, and analytics stay inactive; this prevents a former domain owner from fetching the successor’s intelligence after a transfer.

What you get

• /llms.txt answered by your own domain, not a third-party

• AI-bot visit log per model, per page, per day in the Ooky dashboard

• No file writes, so it works on read-only managed hosts (WP Engine, Kinsta, Pantheon)

• Request-local event queueing; WP-Cron delivers and retries outside the visitor response

• Compatible with caching plugins (W3 Total Cache, WP Rocket, LiteSpeed) for your normal content

• Honors WordPress permalinks; no Apache mod_rewrite or nginx config needed

Who it’s for

• Brands worried that ChatGPT or Claude is making things up about their company

• SaaS, ecommerce, and content sites that want to be cited by AI assistants

• Agencies managing several client sites who want a single dashboard for AI visibility

• Anyone curious which AI crawlers are actually visiting their site

Privacy

ai ) in two situations.

Manifest fetch. ai/api/public/manifest/<your-domain>/<kind>. It sends the registered domain in the URL, the reveal-once API key as a Bearer credential, and a fresh random nonce.

Ooky uses them only to bind the response to the domain’s current hostname claim and echoes the nonce; the plugin does not send visitor data in this fetch.

Bot event. g. ai/api/ingest/events.

The event contains: the matched bot name, the User-Agent string, the request path, the HTTP method, the request timestamp, a client-generated event ID, and (when present) the visitor’s two-letter country code from Cloudflare’s CF-IPCOUNTRY header (never the IP address itself). The event includes your API key as a Bearer token to authenticate the source.

AI-referral event. For a human visit referred by a recognized AI platform, the plugin sends the classified source, only the referrer’s scheme and host (never its path, query, or fragment), the destination path/method, timestamp, event ID, and optional two-letter country. Events first enter a capped per-site database outbox; WP-Cron atomically claims and retries delivery with the same event ID, and Settings → Ooky shows queue depth, the last successful delivery, and any safety-cap drops.

The plugin does not transmit:

• Human visitor IP addresses, cookies, session identifiers, or full AI conversation/search URLs

• Page content or POST bodies

• Logged-in user identities

• Form data, search terms, or any input fields

All outbound calls are made over HTTPS. The API endpoint and base URL can be overridden via the Settings → Ooky → API base field for self-hosted Ooky deployments.

php, which removes every option, transient, scheduled event, and per-site outbox table the plugin created. After uninstall no Ooky data remains in your database.

ai/privacy.