[WordPress] 外掛分享: Tyralix AI Discoverability

首頁 › 外掛目錄 › Tyralix AI Discoverability
全新外掛
安裝啟用
—
尚無評分
11 天前
最後更新
—
問題解決
WordPress 6.4+ PHP 8.1+ v4.1.5 上架:2026-10-04

內容簡介

Tyralix AI Discoverability 外掛為網站準備 AI 優先的網路環境,能自動偵測網站類型並生成適合的結構化資料(JSON-LD),提升網站在搜尋引擎及 AI 助手中的可見度。

【主要功能】
• 自動偵測網站類型(商店、部落格、當地商業等)
• 生成完整產品結構化資料(Product schema)
• 提供主要 AI 爬蟲的控制選項
• 發佈 llms.txt 指南以協助 AI 理解內容
• 進行網站整體 AI 準備健康檢查
• 免費提供所有功能,無需付費升級

外掛標籤

開發者團隊

⬇ 下載最新版 (v4.1.5) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Tyralix AI Discoverability」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

Tyralix AI Discoverability prepares your website for the AI-first web. It is website-centric, not ecommerce-only: it detects what kind of site you run — a store, a blog or publisher, a local business, or a general organization — and automatically generates the most appropriate structured data (JSON-LD) for it. When WooCommerce is present, it adds full ecommerce features (product schema, AI-native feeds, agentic commerce) on top.
It publishes an llms.txt guide, gives you per-crawler controls for the major AI bots, and runs a site-wide AI readiness health check — so search engines, AI assistants, and shopping agents can understand and recommend your content.
WooCommerce is optional. Without it you still get website, article, and page schema, llms.txt, and crawler controls. Install WooCommerce to unlock product schema, feeds, and agentic commerce.
Everything in this edition is free. There are no locked features, no paid tiers, and no upsell nags.
Website schema — adapts to your site

Automatic site-type detection — store, blog/publisher, local business, or organization (with a manual override).
Store / Organization / LocalBusiness — emits OnlineStore, Organization, or LocalBusiness (with address, hours, geo, phone) on your home page based on the detected type.
WebSite schema with a site SearchAction.
Article / BlogPosting — for posts, with author, publisher, dates, images, sections, and keywords.
WebPage — for pages, auto-detecting About, Contact, and FAQ pages.
BreadcrumbList — for products, posts, and pages.

Structured data (schema.org / JSON-LD)

Product schema — complete Product markup with offers, price, availability, ratings, images, brand, GTIN, and MPN.
Store schema — Organization, WebSite (with site SearchAction), and OnlineStore markup on your home and shop pages so AI models understand your brand as an entity.
FAQ schema — auto-generated FAQPage data from product attributes, stock info, and custom FAQ fields.
Speakable schema — SpeakableSpecification markup for voice assistants.
BreadcrumbList schema — automatic breadcrumbs from your category hierarchy.
SEO plugin conflict detection — detects Yoast SEO, Rank Math, and All in One SEO and suppresses only their duplicate Product schema, leaving their site markup intact.
Schema validation — structural checks for required and recommended fields.

AI crawler controls

robots.txt AI rules — allow or block the major AI crawlers (OpenAI GPTBot / ChatGPT-User / OAI-SearchBot, Anthropic ClaudeBot, Google-Extended, PerplexityBot, Applebot-Extended, Amazonbot, Bytespider, Meta-ExternalAgent, CCBot, DuckAssistBot, and more) by vendor family.
Crawler monitor — lightweight, privacy-respecting logging of AI bot visits with per-bot analytics.
llms.txt — a /llms.txt guide describing your store, catalog structure, feeds, and crawl policy for LLMs.

AI-native product feeds

Generate Google Shopping, OpenAI, Bing, and Perplexity product feeds.
Change detection regenerates feeds only when products change.

Agentic commerce (optional)

MCP server and tools so AI agents can query products and (optionally) initiate checkout.

AI content tools (optional, bring your own API key)

Optimize product descriptions and image alt text using OpenAI, Anthropic, or Google Gemini — only when you add your own API key.

Insights

AI Readiness Score — a 0–100 score per product with priority fixes.
Store health check — a one-click, store-wide AI readiness audit with an actionable checklist.
Admin dashboard, schema preview, and settings — plus a Gutenberg sidebar panel and REST API.

Requirements

WordPress 6.4+
PHP 8.1+
WooCommerce 8.0+ is optional — required only for ecommerce features (product schema, feeds, agentic commerce).

External services
This plugin can connect to third-party services, but only when you enable the relevant feature and provide your own credentials. Out of the box, the plugin does not send your data anywhere. No data is sent to Tyralix or any analytics service.
Each integration is described below, including what is sent, when, and links to the provider’s terms and privacy policy.
OpenAI API (optional — AI content optimization)
Used only if you add an OpenAI API key and run description or alt-text optimization. When you do, the product title, description, and attributes for the product you are optimizing are sent to https://api.openai.com to generate improved copy. No data is sent otherwise.
Terms: https://openai.com/policies/terms-of-use — Privacy: https://openai.com/policies/privacy-policy
Anthropic API (optional — AI content optimization)
Used only if you add an Anthropic API key and run content generation. The product content you are optimizing is sent to https://api.anthropic.com to generate improved copy.
Terms: https://www.anthropic.com/legal/consumer-terms — Privacy: https://www.anthropic.com/legal/privacy
Google Gemini API (optional — AI content optimization)
Used only if you add a Google AI (Gemini) API key and run content generation. The product content you are optimizing is sent to https://generativelanguage.googleapis.com.
Terms: https://ai.google.dev/gemini-api/terms — Privacy: https://policies.google.com/privacy
Google Merchant Center / Shopping Content API (optional — Google product feed)
Used only if you connect a Google account and enable Google feed submission. Product data from your catalog (titles, prices, availability, images, identifiers) is sent to https://shoppingcontent.googleapis.com via Google OAuth (https://accounts.google.com, https://oauth2.googleapis.com) to publish your product feed. The plugin may also call the Search Console mobile-friendly test endpoint (https://searchconsole.googleapis.com) to assess a page.
Terms: https://developers.google.com/terms — Privacy: https://policies.google.com/privacy
Microsoft Bing IndexNow (optional — URL submission)
Used only if you enable Bing/IndexNow submission and provide a key. Changed product URLs from your site are submitted to https://api.indexnow.org so search engines re-crawl them. Only public URLs are sent.
Terms: https://www.bing.com/webmasters/url-submission-api — Privacy: https://privacy.microsoft.com/privacystatement
Stripe API (optional — agentic checkout)
Used only if you enable Stripe agentic commerce and provide your Stripe API keys. Cart and checkout session details are sent to https://api.stripe.com to create a checkout session for an AI-agent-initiated purchase.
Terms: https://stripe.com/legal/ssa — Privacy: https://stripe.com/privacy
Product feeds for OpenAI and Perplexity are generated as static files served from your own site; those providers fetch them like any other public URL — the plugin does not push data to them.
Privacy

The plugin does not phone home and does not collect analytics about your site.
AI crawler visits can be logged locally for reporting. IP addresses are anonymized before storage, and logs live only in your own database.
The /llms.txt file never publishes your WordPress admin email. A public contact email is included only if you explicitly set one in the plugin settings.
API keys you enter are stored in your database (encrypted where supported) and are used only to authenticate with the service you configured.

Source Code
This plugin ships as fully human-readable source. There is no build or compile
step and no minified code:

All PHP is autoloaded from src/ via a small built-in PSR-4 autoloader (no
Composer vendor/ directory, no third-party runtime PHP libraries).
The admin app (assets/build/index.js) and the product-editor panel
(assets/build/gutenberg-panel.js) are hand-written, un-minified JavaScript.
They use only the React runtime and UI components that WordPress already ships
(wp.element, wp.components, wp.apiFetch, wp.i18n) via
wp.element.createElement — no JSX, webpack, or Babel — so the files you can
read in the plugin are exactly what runs in the browser.
Stylesheets in assets/build/ are plain, hand-authored CSS.

延伸相關外掛

文章
Filter
Mastodon