LLM Friendly
| 开发者 | skreep |
|---|---|
| 更新时间 | 2026年10月30日 18:34 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
详情介绍:
/llms.txt index and optional Markdown versions of selected public content. You stay in control of what is exposed, how dense the index should be, which endpoints should be noindexed, and which posts or pages should be excluded.
What the plugin creates
/llms.txt
- Markdown exports
.md endpoints under:
/{base}/{post_type}/{path}.md
Each Markdown export includes a stable, plugin-defined JSON metadata block with title, URL, published and modified dates, language, description, author, and publisher, followed by a Markdown conversion of the post content. Frontend pages advertise /llms.txt with a describedby link, while supported singular views also receive alternate Markdown links.
An optional content-negotiation mode can return the same representation from canonical singular URLs when a client explicitly sends Accept: text/markdown. The mode is disabled by default and uses Vary: Accept, so it should only be enabled when every page cache, reverse proxy, and CDN respects that header.
Why site owners use it
- Give AI tools a concise map of your most useful public content.
- Offer Markdown versions of posts, pages, and safe public custom post types without changing the canonical HTML experience.
- Keep Markdown endpoints out of search results by default with separate noindex controls for
/llms.txtand.mdexports. - Add short AI-facing descriptions from a per-post field, SEO meta description, excerpt, or generated content summary.
- Exclude individual items from both
/llms.txtand Markdown exports without changing their WordPress visibility. - Preview generated llms.txt content before relying on the public endpoint.
- Review practical AI crawler policy guidance for OAI-SearchBot, GPTBot, ChatGPT-User, Googlebot/Search AI features, and Google-Extended.
- Independent index structure (legacy/structured) and content processing (legacy/enhanced) controls, with an unsaved comparison before applying changes.
- A short structured root map, up to 100 ordered pinned selections, detailed content-type/topic indexes and bounded cursor pagination under /{base}/catalog/.
- Paragraph-based enhanced summaries, improved lists/tables/media/code conversion, published reusable-block dependency tracking and manual override review status.
- Administrator-only HTTP availability checks and a resumable coverage scan, with conversion warnings and a clear distinction between exportable content and inclusion in the short map.
- Switching back retains new selections and manual content. Existing export URLs, JSON metadata and Essential links remain supported.
- llms.txt endpoint with cached generation, ETag/Last-Modified support, v2-compatible linked lists, main links, sitemap/RSS references, an Essential section, selected post-type sections, optional item descriptions, and an optional custom Markdown notes block.
- Markdown exports for selected public, publicly queryable post types with Gutenberg/HTML-to-Markdown conversion, plugin-defined JSON metadata, canonical/describedby Link headers, alternate Markdown discovery links, and transient-based body caching.
- Optional
Accept: text/markdowncontent negotiation on canonical singular URLs withVary: Accept; disabled by default for cache safety. - Overview dashboard with endpoint status, cache status, noindex status, sitemap URL, and quick copy buttons for
/llms.txtand the Markdown URL pattern. - Configurable Markdown base path, for example
/llm/post/example.md, with post type controls for posts, pages, and safe public custom post types. - Per-post-type exclusion picker with live title search, selected-item lists, clear buttons, and server-side validation.
- Separate noindex header controls for
/llms.txtand Markdown exports. - Auto or manual llms.txt regeneration; manual rebuilds are available from the Maintenance panel.
- Live llms.txt preview that uses saved settings and does not update the public cache.
- Optional excerpts/descriptions in llms.txt. Description priority is: per-post LLM description, SEO meta description, explicit excerpt, then a generated content summary.
- Per-post "Markdown override (LLM Friendly)" metabox for custom Markdown or Gutenberg block markup, plus a one-line llms.txt description field.
- Optional site title, site description, and author overrides for generated metadata.
- Same-site sitemap URL validation. External sitemap URLs are rejected unless a developer explicitly allows them with a filter.
- AI crawler diagnostics with policy examples and documentation links for OAI-SearchBot, GPTBot, ChatGPT-User, Googlebot/Search AI features, and Google-Extended. The plugin does not edit robots.txt automatically.
- Hardened public export boundaries: attachments, drafts, private content, password-protected posts, and non-public/non-queryable post types are excluded by default.
- KSES sanitization for users without
unfiltered_html, length caps for custom Markdown fields, and developer filters for edge cases.
- WordPress 6.0+
- PHP 7.4+
安装:
- Upload the plugin to the /wp-content/plugins/ directory, or install it through the WordPress plugins screen.
- Activate the plugin through the 'Plugins' screen in WordPress.
- Go to Settings -> LLM Friendly.
- Enable llms.txt and/or Markdown exports, choose post types, configure base path (optional).
- Save changes.
- If you changed the base path or endpoints, re-save Permalinks if your server has custom rewrite rules.
屏幕截图:
常见问题:
Will these mechanics change existing installations automatically?
No. Index structure and content processing both default to legacy. Enable them independently in Settings -> LLM Friendly after comparing the unsaved output. Switching back preserves pins, topic selections and manual Markdown. There is no destructive data migration.
How do I reach the complete structured catalog?
Enable structured index mode and llms.txt. Follow Content catalog from /llms.txt, or open /{base}/catalog/index.txt. Follow Next page links even when a filtered page has no items. Topic indexes are built in background batches; type indexes remain available while the scan runs. Catalog entries use canonical HTML when Markdown is disabled.
Why can diagnostics say Unable to check?
WordPress may block its own HTTP requests or fail local TLS/DNS checks. The plugin retains TLS verification and reports that limit honestly. It does not accept arbitrary probe URLs or send authentication cookies. Confirm actual endpoint availability separately when the environment blocks a probe.
Where is llms.txt stored?
The plugin serves llms.txt dynamically via WordPress. It is not a physical file on disk.
Markdown exports return 404. Why?
Most often this is a rewrite or web-server routing issue. If you run Nginx in front of Apache, make sure .md requests are routed to WordPress (not handled as static files).
When you change the base path, flush permalinks and confirm that .md and /llms.txt are not short-circuited by static file rules.
How do I keep Markdown out of search results?
Enable the "Send noindex header for Markdown exports" option (stored as md_send_noindex) to emit the header on all Markdown responses.
How do I enable Accept: text/markdown?
Enable "Serve Markdown when a client explicitly requests it" in the Markdown exports panel. The option is stored as enabled_content_negotiation and is off by default. Before enabling it, verify that page caches, reverse proxies, and CDNs respect Vary: Accept; otherwise a cached Markdown response could be served to an HTML visitor or vice versa.
Does llms.txt improve Google AI visibility or grant AI usage rights?
No special Google Search treatment is promised. Google states that llms.txt and Markdown are not specially used for AI Overviews or AI Mode; normal crawling, indexing, and snippet eligibility still apply. Discovery files, noindex directives, crawler access rules, and training or licensing permissions are separate controls. Publishing llms.txt or Markdown does not grant usage rights.
How do I configure the llms.txt Essential section?
Use Settings -> LLM Friendly -> llms.txt -> "Essential links". Add one item per line as Title | URL | Notes; URLs may be absolute or site-relative. The plugin also adds configured front page, posts page, and privacy policy links when available.
Can I ship a custom Markdown body, description, or exclude a single item?
Yes. Open the post editor and use the "Markdown override (LLM Friendly)" metabox. In Gutenberg it appears with the editor's additional panels/metaboxes. The override accepts plain Markdown or block markup, and the llms.txt description field provides a one-line summary for llms.txt and Markdown metadata. If you want to hide a specific entry from llms.txt and Markdown exports, go to Settings -> LLM Friendly -> llms.txt -> "Excluded items", search by title, and add it to the exclusion list.
Can I use an external sitemap URL?
By default, the sitemap field accepts site-relative paths and same-site absolute URLs. External sitemap URLs are rejected unless a developer opts in with the llmf_allow_external_sitemap_url filter.
Can a non-publicly-queryable post type be exported?
Not by default. Public Markdown and llms.txt exports require public, non-attachment, publicly queryable post types. Developers can explicitly opt in safe edge-case types with the llmf_exportable_post_type filter.
更新日志:
- Prevent an interrupted llms.txt generation from restoring content withdrawn during that generation; recheck cached visibility in both index modes.
- Batch cached visibility lookups to avoid a separate SQL query for every indexed item.
- Require redirect destinations to retain the site's origin and reject paths that can escape a WordPress subdirectory after URL normalization.
- Expand independent provider and real HTTP regression coverage, document optional redirect integrations, and declare minimum requirements in plugin headers.
- Add a provider-neutral hook for unavailable Markdown URLs, validated permanent redirects and withdrawal responses.
- Add independent opt-in structured catalog and enhanced content processing modes; legacy behavior remains the default.
- Add ordered pinned materials, public topic indexes and complete content catalogs with bounded cursor pagination.
- Improve descriptions and Markdown conversion for lists, tables, captions, media, links and code; track reusable source changes.
- Show manual Markdown review status without replacing existing overrides.
- Add unsaved output comparison, administrator-only HTTP diagnostics and resumable coverage scans.
- Revalidate cached catalog entries and reusable dependencies against current public access rules.
- Update all six translations and verify WordPress 6.0/7.1.2 with PHP 7.4/8.4.
- Restrict editor metadata to authenticated REST edit contexts.
- Render shared Markdown without visitor privileges or post password cookies.
- Immediately revoke cached llms.txt entries when posts become non-public, password-protected, or deleted, including manual mode.
- Fix administrative cache regeneration and report a held regeneration lock as a retryable error.
- Prevent metadata updates from being hidden by Apache/FastCGI conditional responses.
- Reject credentials in sitemap and other published URLs.
- Align llms.txt item sections with the v2 linked-list format and omit empty sections.
- Add
describedbydiscovery for llms.txt and combined canonical/describedby Markdown Link headers. - Add opt-in
Accept: text/markdowncontent negotiation withVary: Accept. - Update crawler guidance for ChatGPT-User and current Google/OpenAI documentation.
- Clarify that JSON metadata is plugin-defined and that discovery, indexing, crawler access, and usage rights are separate controls.