內容簡介
Ooky AI Visibility 外掛讓您的 WordPress 網站能夠被 AI 助手（如 ChatGPT、Claude 等）準確發現，並提供清晰的結構化數據，提升網站在 AI 爬蟲中的可見性。
【主要功能】
• 提供乾淨的 HTML 給 AI 爬蟲
• 注入 schema.org JSON-LD 結構化數據
• 在知名 AI 路徑提供品牌資訊
• 追蹤 AI 爬蟲的訪問紀錄
外掛標籤
開發者團隊
原文外掛簡介
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.
Injects schema.org JSON-LD into your pages. Your latest published structured data is added to
so AI and search crawlers can index your brand facts.Serves brand intelligence at well-known AI paths. When an AI bot fetches /llms.txt, /llms-full.txt, /agents.md, /.well-known/ai-manifest.json, or /.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 every front-end request—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. 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.
The same integration is also available as a Node/Next.js SDK (@ooky/sdk) and a Cloudflare Worker, all sharing an identical API contract.
You need a free Ooky account 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
The plugin transmits data to the Ooky API (default: https://api.ooky.ai) in two situations.
Manifest fetch. When an AI bot (or anyone) requests one of the plugin’s served paths (/llms.txt, etc.), the plugin fetches your brand manifest from https://api.ooky.ai/api/public/manifest/
Bot event. When the User-Agent of an incoming front-end request matches a known AI bot (e.g. GPTBot, ClaudeBot), the plugin POSTs a small event to https://api.ooky.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.
If you uninstall the plugin via the Delete action in Plugins, WordPress runs uninstall.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.
For our full privacy policy and DPA, see https://ooky.ai/privacy.
