Virtual LLMS.TXT Generator
| 开发者 | oreshkin |
|---|---|
| 更新时间 | 2026年9月11日 18:56 |
| PHP版本: | 8.3 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
/llms.txt. The default map contains the site title, an optional summary, and curated link lists for the public content types you select. It follows the format proposed at llmstxt.org: an H1, optional context, and H2 link-list sections.
Safe by default
Only public, eligible content is included. The plugin excludes unpublished and password-protected entries, configured post IDs, supported SEO noindex signals, hidden WooCommerce products, and content rejected by an access-control integration.
The optional /llms-full.txt endpoint is disabled by default. When enabled, it publishes only bounded static text and does not execute shortcodes, dynamic blocks, embeds, or arbitrary plugin blocks.
Built for real WordPress sites
Maps are generated as revisioned background artifacts instead of rebuilding during public requests. The plugin supports multisite lifecycle operations, HTTP cache validators, automatic or manual map content, taxonomy filtering, conservative migration from the public 3.x release, and an automatic endpoint handoff when CYBERMAPS is active.
The plugin is useful on its own. When a site needs broader discovery endpoints, sitemap tooling, governance, or reporting, the settings page includes a restrained link to CYBERMAPS.
Virtual LLMS.TXT editor by CYBER BRAND. The unminified source and release build process are public on GitHub.
Developed by Alex Oreshkin (@oreshkin).
Features
- Virtual
/llms.txtendpoint with no physical root file to manage. - Clean H1/context/H2 Markdown output without YAML frontmatter.
- Automatic curation or an explicitly selected manual map body.
- Public post type, taxonomy-slug, and post-ID controls.
- Fail-closed filtering for unpublished, private, password-protected, noindex, hidden-product, and access-vetoed content.
- Compatibility adapters for Yoast SEO, Rank Math, All in One SEO, SEOPress, and WooCommerce visibility.
- Optional
/llms-full.txt, disabled by default and bounded by item, input, output, and total-byte ceilings. - Static-text rendering that does not execute shortcodes, dynamic blocks, embeds, or arbitrary plugin blocks.
- Revisioned background generation with a minimal safe map while
/llms.txtrebuilds. - ETag and Last-Modified support for efficient conditional requests.
- Optional advisory crawler and policy labels that add context without allowing or blocking crawlers.
- Optional content-license notices that remain descriptive and do not create or enforce legal terms.
- Local, opt-in 30-day aggregate request counts with no IP addresses or raw user-agent storage.
- Multisite-aware activation, scheduling, site creation/removal, and uninstall cleanup.
- Automatic endpoint handoff when CYBERMAPS is active.
llms.txt is an experimental discovery signal. It does not guarantee crawling, training, ranking, citation, or legal compliance. Crawler, policy, and license fields are descriptive metadata; they do not grant, deny, or enforce access.
安装:
- Install and activate Virtual LLMS.TXT Generator.
- Open Tools → LLMS.TXT.
- Review the endpoint health and included content.
- Save any changes.
/llms.txtremains available from a safe minimal artifact while the complete background build runs. - Enable
/llms-full.txtonly after reviewing its publication warning and limits.
屏幕截图:
常见问题:
Does this plugin block AI crawlers?
No. It publishes discovery context. Use robots.txt, authentication, application access rules, and appropriate legal advice for access control.
What is published by default?
The title, optional site summary, and bounded links to selected public posts and pages. Analytics and the full-content endpoint are disabled by default. No license, crawler, or policy label is asserted automatically.
Why does /llms-full.txt return 404?
It is intentionally opt-in. Enable it under Advanced settings and acknowledge that it publishes selected public post bodies. While an enabled export is rebuilding, it returns HTTP 503 rather than serving stale content.
How is protected content handled?
Both endpoints exclude non-public statuses, password-protected posts, configured exclusions, noindex content from supported SEO plugins, hidden WooCommerce products, and content vetoed through the cyberllms_post_is_access_restricted filter.
There is no universal membership-plugin API. The full renderer therefore omits shortcodes, dynamic or unknown blocks, embeds, and executable rendering. Membership plugins can use the veto filter for their own access metadata.
If an integration stores visibility rules in custom post metadata, it should also return true from cyberllms_meta_change_requires_rebuild for those keys. This keeps the map current without rebuilding it for unrelated counters and editing metadata.
What happens when “Discourage search engines” is enabled?
Both endpoints return 404. The settings page explains the state.
Do root endpoints work with Plain permalinks?
That depends on the web server. On many standard configurations, root-level virtual files reach WordPress only when rewrite routing is enabled. Choose a non-Plain permalink structure or configure the server to route /llms.txt and /llms-full.txt to WordPress. The settings page warns when Plain permalinks are selected.
Does analytics contact an external service?
No. When explicitly enabled, the plugin stores only the date, endpoint, a locally matched user-agent label, and an aggregate count in the site database. It stores no IP addresses or raw user agents, and removes records older than 30 days.
Can I edit the generated map?
Yes. Automatic mode is read-only and follows the content controls. Manual mode accepts a map body containing H2 headings and Markdown link-list entries. Site identity and additional context remain separate.
Do crawler labels or license notices control crawler access?
No. Both fields publish optional advisory metadata only. Use robots.txt, authentication, application access rules, and appropriate legal advice when you need access or licensing controls.
What happens when CYBERMAPS is active?
Virtual LLMS.TXT Generator yields /llms.txt and /llms-full.txt, stops its build and analytics jobs, and links to the CYBERMAPS settings page. It does not transfer settings or deactivate either plugin.
更新日志:
- Rebuilt the plugin on a WordPress 7.1-tested and PHP 8.3+ foundation.
- Changed
/llms.txtto the proposed H1, context, and Markdown link-list format. - Made
/llms-full.txtan explicit, safety-bounded opt-in. - Added shared public-content, noindex, password, taxonomy, WooCommerce, and access-veto filtering.
- Added optional advisory crawler and policy labels and content-license notices with explicit non-enforcement guidance.
- Removed logged-in fragment rendering, post-meta fragments, cold-cache generation, and year-long transients.
- Added revisioned background artifacts, reliable endpoint states, HTTP validators, local atomic analytics, multisite lifecycle support, and complete uninstall cleanup.
- Added automatic endpoint handoff and a contextual link for CYBERMAPS.
- Added a conservative migration for settings from the public 3.0.1 release.
- Hardened concurrent artifact publication, generation integrity checks, cron warning retention, UTF-8 input limits, and multisite lifecycle handling.
- Replaced unsupported performance, bot-identification, legal-enforcement, and “AEO standard” claims.
- Added public source, security, contribution, and release documentation.
- Legacy generated caches and analytics logs are intentionally not migrated.