M7tawa LLMS.txt Manager

M7tawa LLMS.txt Manager is a local management and safety tool for llms.txt and robots.txt. It generates an editable llms.txt file from WordPress site data and provides a separate Robots.txt manager plus a consistency and safety audit.

The plugin supports automatic and manual llms.txt modes, public post types, exclusions, custom text, SEO descriptions, file checks, and Arabic/English administration screens. It can create a physical llms.txt file when the site root is writable and falls back to a WordPress virtual route when needed.

The Robots.txt tab reviews the current robots.txt file, suggests a safe WordPress baseline, detects physical-file conflicts, and prevents saving an exact full-site blocking rule such as Disallow: /. The Safety Audit checks public llms.txt availability, physical versus virtual delivery, write/read status, physical robots.txt conflicts, full-site blocking, and explicit /llms.txt blocking without modifying files or settings.

Features

• Automatic or manual llms.txt generation.
• Fast physical llms.txt file with a virtual WordPress fallback.
• Automatic refresh when published content changes.
• Pages, categories, posts, products, and public custom post types.
• Search and exclude individual content items.
• Custom text before or after generated content.
• Rank Math and Yoast descriptions and noindex support.
• Separate Robots.txt review and management tab.
• LLMS.txt and Robots.txt Safety Audit with Healthy, Warning, and Action Required status.
• Checks public llms.txt availability and physical versus virtual delivery.
• Detects physical robots.txt conflicts, full-site blocking, and explicit /llms.txt blocking.
• Full-site robots.txt block protection for an exact Disallow: / rule.
• Physical robots.txt conflict detection without overwriting the existing file.
• English is the source language. The plugin is fully internationalized and ready for community translations through WordPress.org.
• Human-readable JavaScript source is included directly in the plugin; no build process is required.
• No telemetry or bundled third-party AI SDK. Optional AI requests use the official WordPress AI Client and the provider configured by the administrator.

Optional AI Features

Version 1.4.0 adds an optional AI Workspace. The existing LLMS.txt, Robots.txt, and Safety Audit features continue to work without AI.

• Uses the official WordPress AI Client available in WordPress 7.0 and newer.
• Uses the AI provider configured by the site administrator under Settings > Connectors.
• Does not store provider API keys.
• Makes no automatic or background AI requests.
• Generates an editable LLMS.txt draft that must be reviewed before it is applied. AI receives opaque URL IDs; PHP restores the original WordPress URLs after validating those IDs.
• Generates an XML sitemap preview using opaque entry IDs only. AI selects IDs and priorities; PHP keeps the real WordPress URLs and constructs the XML itself.
• Publishes the optional AI sitemap at /m7tawa-ai-sitemap.xml only after explicit administrator approval. The default WordPress sitemap remains unchanged.

External Services

The optional AI Workspace sends data to the AI provider that the site administrator has configured through the WordPress Connectors screen. The provider is selected and managed by WordPress, not by this plugin.

Data is sent only after an administrator explicitly clicks Test AI Setup, Generate LLMS.txt with AI, or Generate AI Sitemap. Depending on the requested action, the request can include the site name, site description, content titles, descriptive LLMS.txt context, and opaque entry identifiers. Real website URLs are kept by PHP and restored locally after the AI response is validated.

M7tawa LLMS.txt Manager does not store provider API keys and does not maintain its own history of prompts or AI responses. Provider terms and privacy policies depend on the provider chosen by the site administrator in Settings > Connectors.

Source Code

The JavaScript source used by this plugin is included directly in assets/admin.js in human-readable form. The plugin does not require npm, webpack, transpilation, minification, or another build process to regenerate its distributed JavaScript.