GioContextAi

开发者	giovannibevacqua
更新时间	2026年10月17日 20:11
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0 1.2.0 1.2.1 1.2.2 1.3.0

详情介绍:

GioContextAi helps WordPress websites expose their content in a clean, structured format for AI systems, crawlers, and other machine-readable applications. The plugin dynamically generates virtual endpoints for:

llms.txt — a structured Markdown index of selected website content.
llms-full.txt — an extended version containing the full text of selected published content.
ai.txt — a dedicated endpoint for AI-related crawler directives and sitemap information.

The files are generated dynamically through WordPress rewrite rules. No physical files need to be created on your server. GioContextAi is designed to work alongside your existing SEO tools. It can automatically respect noindex settings detected from supported SEO plugins, helping prevent content that should not be indexed from being included in the generated AI context. GioContextAi also includes AI Crawler Intelligence: a lightweight monitor of the requests that declared AI crawlers make to your site, as observed by WordPress. The Lite version provides the core AI context generation engine. GioContextAi Pro adds advanced controls for businesses, developers, agencies, and websites that need more control over how their content is represented to AI systems.

安装:

Upload the giocontextai folder to the /wp-content/plugins/ directory, or install the plugin through the WordPress plugin installation interface.
Activate GioContextAi from the Plugins screen.
Go to GioContextAi > Settings in the WordPress admin menu.
Select the public post types that should be included in your AI context.
Use the available preview tools to verify the generated endpoints.

If the endpoints return a 404 error after installation, go to Settings > Permalinks and click Save Changes to refresh WordPress rewrite rules.

屏幕截图:

升级注意事项:

1.3.0 Adds AI Crawler Intelligence: requests from declared AI crawlers, as observed by WordPress. A small database table is created on update. GioContextAi Pro 1.2.0 requires this version.

常见问题:

What is llms.txt?

llms.txt is a proposed convention for providing AI systems with a concise, machine-readable representation of important website content using Markdown. GioContextAi dynamically generates an llms.txt endpoint from your WordPress content.

What is llms-full.txt?

llms-full.txt is an extended context representation generated by GioContextAi that can include the full text of selected published content. It is intended for applications that need more information than the concise index provided by llms.txt.

What is ai.txt?

ai.txt is a dedicated machine-readable endpoint generated by GioContextAi for AI-related crawler directives and sitemap information. Support and interpretation of such directives depend on the individual crawler or AI system.

Will ChatGPT, Claude, Gemini, or other AI systems automatically read these files?

Not necessarily. GioContextAi makes the files available through clean public endpoints. Whether an external AI system or crawler discovers, requests, indexes, or uses those endpoints depends on the policies and technical implementation of that service.

Which AI crawlers are recognised?

GPTBot, OAI-SearchBot, ChatGPT-User, OAI-AdsBot (OpenAI); ClaudeBot, Claude-SearchBot, Claude-User, Claude-Web (Anthropic); PerplexityBot, Perplexity-User; Meta-ExternalAgent, Meta-WebIndexer, Meta-ExternalFetcher; MistralAI-Training, MistralAI-Index, MistralAI-User; Amazonbot, Amzn-SearchBot, Amzn-User; Google-CloudVertexBot; DuckAssistBot; YouBot; CCBot (Common Crawl); Bytespider (ByteDance); cohere-ai. Developers can extend the list with the giocontextai_crawler_registry filter.

Do the AI crawler statistics show that my site appears in AI answers?

No. They show requests observed by WordPress from crawlers identified by their declared user-agent. They do not show indexing, citations or use in AI answers.

Why does the AI Crawlers page show fewer requests than my server logs?

Requests served by a page cache, a server cache or a CDN without running WordPress are not counted, and crawlers that do not declare a recognised user-agent are not identified. The page reports partial coverage when a page cache is detected.

The AI Crawlers page says that a scheduled task did not run. What should I do?

WP-Cron runs only when the site receives visits, and is disabled when DISABLE_WP_CRON is set. Configure a server cron job that calls wp-cron.php regularly (for example every 5–15 minutes).

Does GioContextAi replace my SEO plugin?

No. GioContextAi complements traditional SEO plugins by providing additional machine-readable context for AI systems and other automated applications. It can work alongside plugins such as Yoast SEO, Rank Math, and SEOPress.

Does GioContextAi expose private content?

GioContextAi is designed to avoid exposing inappropriate content through its generated context. Password-protected content is excluded, and supported noindex directives can be respected. Sensitive system pages can also be excluded from the generated context. You should always review the generated endpoint using the built-in preview tools before making assumptions about what is publicly exposed.

Do I need to create physical files on my server?

No. GioContextAi uses WordPress rewrite rules and virtual endpoints. No physical llms.txt, llms-full.txt, or ai.txt files need to be created.

What should I do if an endpoint returns a 404 error?

Go to: Settings > Permalinks and click Save Changes. This refreshes WordPress rewrite rules.

Does GioContextAi work with WooCommerce?

The Lite version can work with standard WordPress content and selected public post types. GioContextAi Pro provides additional support for custom post types and advanced structured content management, including WooCommerce products.

Does GioContextAi support multilingual websites?

Multilingual compatibility depends on the multilingual plugin and the configuration of the website. Dedicated integrations with multilingual plugins may be provided as GioContextAi evolves.

更新日志:

1.3.0

Added: AI Crawler Intelligence, a monitor of the requests that declared AI crawlers make to the site, as observed by WordPress (new page GioContextAi > AI Crawlers).
Added: requests per day by type of crawler, requests by type of resource and by response, requests to each AI context file (llms.txt, llms-full.txt, ai.txt, products.json), periods of 7 and 30 days, accessible charts with data tables.
Added: built-in list of 25 AI crawlers from OpenAI, Anthropic, Perplexity, Meta, Mistral AI, Amazon, Google, DuckDuckGo, You.com, Common Crawl, ByteDance and Cohere, with their documented purpose; extendable with the giocontextai_crawler_registry filter.
Added: monitoring diagnostics (active, partial coverage, no requests observed, recording error, database upgrade, not working), a separate warning with the number of crawler requests that could not be recorded during a database upgrade, and warnings when a scheduled task has not run.
Added: "AI Crawlers" summary card on the AI Analytics page.
Added: option "Delete all GioContextAi data when the plugin is deleted" (off by default) and a complete uninstall routine, also on multisite.
Changed: crawlers are identified by their declared user-agent and are shown as not verified; no IP address or personal data is stored.
Changed: "posts indexed" on the AI Analytics page now reads "published posts".
Developers: filters giocontextai_crawler_registry, giocontextai_crawler_retention_days, giocontextai_crawler_periods, giocontextai_crawler_verifier, giocontextai_show_lite_crawler_section.
Requires a daily WP-Cron task (or a server cron job calling wp-cron.php) to delete expired data.

1.2.2

Fixed: /llms.txt, /llms-full.txt, /ai.txt and /products.json no longer redirect (301) to a trailing-slash URL on sites with a static front page; they now answer directly with 200.
Fixed: titles, site name and description are written as clean plain text (no HTML entities such as & or ’).
Fixed: URLs with query parameters are no longer encoded as & in the generated files.
Fixed: the giocontextai_post_item_output filter is now applied to every resource line.
Improved: rewrite rules are checked after all endpoints are registered, including products.json.
Improved: cache is cleared when included post types change and when posts or terms are deleted or created.

1.0.0

Initial release of GioContextAi Lite.
Added virtual llms.txt endpoint.
Added virtual llms-full.txt endpoint.
Added virtual ai.txt endpoint.
Added configurable public post type inclusion.
Added noindex compatibility with Yoast SEO, Rank Math, and SEOPress.
Added password-protected content safeguards.
Added safeguards for selected WordPress and WooCommerce system pages.
Added transient caching for generated context output.
Added automatic cache invalidation when relevant content changes.
Added endpoint preview tools.