GioContextAi

Beschreibung

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.

Features

AI Context Files

  • llms.txt generation — Automatically creates a structured Markdown index of selected published content.
  • llms-full.txt generation — Provides an extended machine-readable version including the content of selected posts and pages.
  • ai.txt generation — Provides a dedicated endpoint for AI crawler directives and sitemap information.
  • Virtual endpoints — Files are served through WordPress rewrite rules without creating physical files on the server.

Content Control

  • Post Type selection — Choose which public post types should be included in the generated context.
  • Published content only — Only appropriate published content is considered for inclusion.
  • Noindex awareness — Automatically excludes content marked as noindex through supported SEO plugins.
  • Protected content safeguards — Password-protected content is not exposed through the generated context.
  • System page safeguards — Sensitive WordPress and WooCommerce system pages can be excluded from AI context generation.

AI Crawler Intelligence

  • Requests observed by WordPress — Counts the requests made by known AI crawlers (for example GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Meta-ExternalAgent, Amazonbot, CCBot) when WordPress handles them.
  • What crawlers request — Requests by type of resource (posts and pages, home page, archives, AI context files, REST API, feeds, sitemaps, search, 404 and redirects) and by response (served, redirected, not found, server error).
  • Requests per day — Daily chart by type of crawler (training, AI search, user-initiated, other AI) for the last 7 or 30 days.
  • AI context files — Requests to llms.txt, llms-full.txt, ai.txt and products.json, file by file.
  • Monitoring diagnostics — The AI Crawlers page states whether monitoring is active, active with partial coverage (for example when a page cache is detected), active with no requests observed yet, or not working, together with any database error.
  • Light by design — One small daily aggregate table, one write per crawler request, no request is recorded for regular visitors.

See „About AI Crawler Intelligence“ below for what these figures mean and their limits.

Performance

  • Transient caching — Generated context files are cached to reduce unnecessary database queries when crawlers request the endpoints.
  • Automatic cache invalidation — Cache is refreshed when relevant content is modified.
  • No physical files — The plugin does not create or maintain static files on your server.

Administration

  • Simple configuration — Configure included post types directly from the WordPress administration area.
  • Endpoint previews — Preview the generated context files directly from the plugin settings.
  • Native WordPress integration — Uses WordPress rewrite rules and APIs rather than requiring server-level configuration.

Pro Version

GioContextAi Pro extends the core engine with advanced AI context management tools.

Pro features include:

  • Global Brand Voice — Define your brand personality, tone, and communication style.
  • Custom AI Instructions — Add global instructions that can be included in the AI context.
  • Custom Post Type support — Extend context management to custom post types such as WooCommerce products and portfolios.
  • Taxonomy support — Include categories, tags, product categories, and other public taxonomies.
  • Per-content controls — Exclude individual posts, pages, products, or taxonomy terms from AI context.
  • Custom context instructions — Add contextual notes and instructions to individual resources.
  • AI Readiness Audit — Analyze multiple dimensions of your site’s AI context configuration and receive actionable recommendations.
  • AI Context Inspector — Inspect how individual content is represented within the generated AI context.
  • Per-content AI crawler statistics — Rankings of the most requested posts, pages, WooCommerce products and taxonomy terms, filters by crawler and provider, 12 months of history and the request history of each content, also shown in the editor.
  • Advanced AI feed capabilities — Create structured machine-readable feeds for selected WordPress content.
  • Priority support and updates — Pro customers receive priority support and product updates during their active license period.

For information about Pro features and licensing, visit the GioSuite website.

How It Works

After activation, GioContextAi registers virtual WordPress endpoints for the generated context files.

For example:

  • /llms.txt
  • /llms-full.txt
  • /ai.txt

When one of these endpoints is requested, GioContextAi generates the appropriate output using your WordPress content and configuration.

The generated files can then be accessed by compatible crawlers, AI systems, developer tools, or other applications that retrieve machine-readable website information.

GioContextAi does not guarantee that a specific AI service or crawler will access or use these endpoints. The plugin provides the structured endpoints and content; how external systems discover, retrieve, or use them is determined by those systems.

About AI Crawler Intelligence

What is counted. A request is counted when WordPress handles it and the user-agent matches one of the AI crawlers in the built-in list. Figures are aggregated per day, crawler, type of resource and response class.

Declared user-agents, not verified identities. Crawlers are identified by the user-agent they declare. A user-agent can be imitated by anyone, so every request is shown as „Declared user-agent (not verified)“. Verification against the IP ranges published by the providers is not active in this version.

Partial coverage with caches and CDNs. Requests answered by a page cache, a server cache (for example Varnish or Nginx FastCGI cache) or a CDN without running WordPress are not seen by the plugin and are not counted. When a page cache plugin is detected, the AI Crawlers page reports partial coverage. The figures are therefore a lower bound of the real crawler traffic.

What the figures do not show. A request shows that a crawler asked for a page. It does not show whether the page was indexed, cited, recommended or used in an AI answer, and GioContextAi does not claim to improve the visibility of your site in AI services.

Scheduled tasks. Expired data is removed by a daily WP-Cron task. WP-Cron runs only when the site receives visits: on low-traffic sites, or when DISABLE_WP_CRON is set, configure a server cron job that calls wp-cron.php. The AI Crawlers page warns when a scheduled task has not run within the expected time.

Free and Pro. The free plugin shows site-wide figures for the last 7 or 30 days. GioContextAi Pro adds per-content detail: rankings of posts, pages, WooCommerce products and taxonomy terms, filters by crawler and provider, a 12-month period and the request history of each content.

Data on uninstall. Deactivating or deleting the plugin keeps the statistics, unless „Delete all GioContextAi data“ is enabled in the settings.

Performance and Caching

GioContextAi uses WordPress transient caching for generated context output.

This prevents the plugin from rebuilding the same content for every request and reduces unnecessary database queries, particularly when context endpoints are accessed repeatedly by automated crawlers.

Relevant caches are automatically invalidated when supported content is modified.

SEO Plugin Compatibility

GioContextAi is designed to work alongside traditional SEO plugins.

The Lite version can detect noindex settings from supported SEO plugins, including:

  • Yoast SEO
  • Rank Math
  • SEOPress

Content marked as noindex can therefore be excluded from the generated AI context.

GioContextAi does not replace your SEO plugin. It provides an additional machine-readable representation of your website content.

Privacy

GioContextAi does not send your website content to an external AI service in order to generate the core context files.

The generated files are served directly by your WordPress installation.

AI Crawler Intelligence stores only daily aggregate counters: date, crawler, type of resource, response class and number of requests, plus the time of the last request. It does not store IP addresses, full user-agent strings, URLs of regular visitors, cookies or any personal data, and it records nothing for regular visitors. Data older than 30 days is deleted daily (developers can extend the period with the giocontextai_crawler_retention_days filter).

External Services

GioContextAi’s core context generation does not require an external third-party service.

The plugin generates and serves the context endpoints directly from your WordPress installation. AI Crawler Intelligence works locally and does not contact any external service.

Screenshots

Installation

  1. Upload the giocontextai folder to the /wp-content/plugins/ directory, or install the plugin through the WordPress plugin installation interface.
  2. Activate GioContextAi from the Plugins screen.
  3. Go to GioContextAi > Settings in the WordPress admin menu.
  4. Select the public post types that should be included in your AI context.
  5. 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.

FAQ

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.

Rezensionen

There are no reviews for this plugin.

Mitwirkende & Entwickler

„GioContextAi“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

Übersetze „GioContextAi“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

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.