Summary
As a WordPress plugin developer who has implemented llms.txt generation, I'd like to propose adding WordPress-specific best practices to the llms.txt specification documentation.
Motivation
WordPress is one of the most popular CMS platforms, and many developers implementing llms.txt will be working with WordPress. Having clear guidelines would help ensure consistent, standards-compliant implementations.
Proposed Additions
1. WordPress Content Types
- How to handle custom post types
- Taxonomy organization (categories, tags, custom taxonomies)
- WooCommerce product support
2. Security Considerations
- Only including published content
- Excluding private/password-protected posts
- Handling user-generated content
3. URL Generation
- Using WordPress permalink functions
- Handling custom post type URLs
- Taxonomy archive URLs
4. Performance
- Limiting the number of URLs per section
- Caching considerations
- Large site handling
Implementation Example
I've implemented these practices in our SEO Repair Kit plugin (coming soon, v2.1.1) and would be happy to:
- Contribute documentation based on our experience
- Help test WordPress-specific scenarios
GitHub Profile: @cswaqaas
Location: TorontoDigits, Pakistan
Summary
As a WordPress plugin developer who has implemented
llms.txtgeneration, I'd like to propose adding WordPress-specific best practices to thellms.txtspecification documentation.Motivation
WordPress is one of the most popular CMS platforms, and many developers implementing
llms.txtwill be working with WordPress. Having clear guidelines would help ensure consistent, standards-compliant implementations.Proposed Additions
1. WordPress Content Types
2. Security Considerations
3. URL Generation
4. Performance
Implementation Example
I've implemented these practices in our SEO Repair Kit plugin (coming soon, v2.1.1) and would be happy to:
GitHub Profile: @cswaqaas
Location: TorontoDigits, Pakistan