Configuration

All settings live under LLMs.txt → Settings. Changes take effect on the next generation run - click Generate or Regenerate from the Generate tab after saving.

Site Information

These three fields appear at the top of every generated llms.txt file.

The plugin pre-fills Site Name and Tagline from your WordPress Settings → General values. Edit them here without changing your site settings.

Homepage & About Page

Controls how the homepage and “about” page are handled - these pages often contain navigation or CMS-injected boilerplate that doesn’t read well in Markdown.

Homepage handling - choose one of:

• Read & include - read the homepage content and include the converted Markdown body, just like any other page.
• Summary only - include a brief one-line entry in the index without a body.
• Skip - omit the homepage from the output entirely.

About page - the plugin auto-detects a page called “About” or “About Us”. Use the dropdown to pin a different page if your about page has an unusual title.

Content to Include

Choose which content types are scanned and which items are excluded.

Post types - toggle each type on or off:

• Blog Posts
• Pages
• WooCommerce Products (visible when WooCommerce is active)
• Any registered custom post types

Max Items per Content Type - limits how many entries per type are included in the output (default: 200). Useful on large sites to keep file size manageable.

Exclude specific pages - a checkbox list of individual pages to skip. Common candidates are auto-populated: Cart, Checkout, Login, Thank You, and similar utility pages.

Content Options

Fine-tune what’s extracted from each page.

Integrations

Add pointer to robots.txt - when enabled, the plugin appends a # llms.txt comment block to your robots.txt file pointing AI crawlers to /llms.txt and /llms-full.txt. This helps AI assistants that start from robots.txt discover your structured content files.

Import tools - third-party import plugins such as WP All Import can trigger regeneration when a bulk import completes. Add a small snippet to your theme or a site-specific plugin that fires do_action( 'llmstxt_regenerate' ) on the import hook. See Regeneration triggers → for the full list of actions and WP All Import examples →.

Notifications

Email on failure - if generation fails or encounters errors, an email is sent to the notification address.

Notification email - defaults to the WordPress admin email. Change it here without affecting the site-wide admin address.

Advanced Settings

Click the Advanced disclosure to expand:

Extraction Method - controls how the main body of each page is read (this only affects {{content}}, not mapped fields):

• Auto (default) - reads your published content the way it appears to visitors, including blocks, shortcodes, and page-builder layouts. If a page comes back empty, it automatically loads the full page and pulls just the main content. Best for most sites.
• Post content only - uses just the content saved in your editor, with blocks and shortcodes applied. Fastest option, but can miss anything your theme or plugins add outside the editor. Pick this if scraping causes errors or timeouts on your host.
• Full-page scrape - loads each page like a browser, then keeps the main content and removes the header, footer, menus, and sidebars. Pick this if part of your page body is missing, for example a section your theme renders outside the editor or a builder like Elementor that stores its layout separately. It is slower, because it requests every page one by one.

Custom Content Selector - a CSS selector (e.g. .entry-content, main article) that tells the scraper exactly which part of the page HTML to extract. Use this if the default Readability-style algorithm picks up unwanted sidebars, headers, or widget areas. Leave blank to use the automatic selector.

Custom Field Mapping Pro - pull extra data into each content type’s Markdown output. Enter a comma-separated list of meta key names (e.g. _yoast_wpseo_metadesc, rating). These become available as {{meta_keyname}} variables in Templates. ACF fields are detected automatically and exposed as {{acf_fieldname}} variables. Free users can view this panel; configuring field mapping requires Pro.

File Delivery Mode - controls how the output files are served:

• Physical file (default) - the plugin writes static files to the WordPress root directory. Fast, no WordPress overhead on each request.
• Live Endpoint - files are served dynamically by WordPress rewrite rules. Required if the root directory is not writable.

A green/red indicator shows whether the root directory is currently writable.

Individual .md Files Pro

When enabled, the plugin writes a Markdown file for every post, page, and product at /llms/slug.md. For example, a post at /blog/my-post gets a file at /llms/blog/my-post.md.

Per-type serving mode override - override the site-wide File Delivery Mode for each content type separately. The settings panel shows a recommendation badge based on content count:

• Sites with fewer than 500 products or 2,000 posts → Physical file recommended.
• Larger sites → Live Endpoint recommended to avoid generating thousands of static files.

Auto-Regeneration Pro

When enabled, the plugin automatically regenerates the output files whenever a post, page, or product is published or updated. A 5-minute debounce prevents rapid successive saves from triggering multiple back-to-back regeneration runs.

Free users see a Pro upgrade prompt here. Manual regeneration from the Generate tab is always available regardless of plan.

Post Editor Integration Pro

Controls which post types show the Project LLMs.txt: AI Preview meta box in the post editor. Check each type you want to monitor per-page without visiting the plugin dashboard.

See Templates → for details on per-page Markdown overrides in the post editor.