Includes important public-output security hardening, reliable root llms.txt publishing and cleanup, clearer diagnostics, and an optional robots.txt discovery comment. Updating is strongly recommended.<\/p>","1.1.6":"
Adds pre-generated static resources, fixes trailing-slash handling and unresolved Rank Math descriptions, improves Markdown tables, and enables \/llms-full.txt by default while preserving saved preferences.<\/p>","1.1.5":"
Updating stable WordPress version.<\/p>","1.1.4":"
Fixes Markdown endpoint output and includes content by default (use Hide in llms.txt output to exclude).<\/p>","1.1.3":"
Adds an optional \/llms-full.txt endpoint and improves Markdown output.<\/p>","1.1.2":"
Initial public release on WordPress.org.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":2},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3456659,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3456659,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3456659,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3456659,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3456659,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.2","1.1.3","1.1.4","1.1.5","1.1.6","1.1.7"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3456659,"resolution":"1","location":"assets","locale":"","width":1400,"height":770},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3456659,"resolution":"2","location":"assets","locale":"","width":1400,"height":770},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3456659,"resolution":"3","location":"assets","locale":"","width":1400,"height":770},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3456659,"resolution":"4","location":"assets","locale":"","width":1400,"height":770},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3456659,"resolution":"5","location":"assets","locale":"","width":1400,"height":770}},"screenshots":{"1":"Main settings screen (free).","2":"Post editor meta box with Hide control.","3":"Groups & Content screen (free) showing default grouping and visibility controls.","4":"Example \/llms.txt output.","5":"Example .md endpoint output."}},"plugin_section":[],"plugin_tags":[2353,13224,244604,4608,186],"plugin_category":[55],"plugin_contributors":[255478],"plugin_business_model":[],"class_list":["post-278193","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-content-discovery","plugin_tags-llms-txt","plugin_tags-markdown","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-bradphillips","plugin_committers-bradphillips"],"banners":{"banner":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/banner-772x250.png?rev=3456659","banner_2x":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/banner-1544x500.png?rev=3456659","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/icon.svg?rev=3456659","icon":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/icon.svg?rev=3456659","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/screenshot-1.png?rev=3456659","caption":"Main settings screen (free)."},{"src":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/screenshot-2.png?rev=3456659","caption":"Post editor meta box with Hide control."},{"src":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/screenshot-3.png?rev=3456659","caption":"Groups & Content screen (free) showing default grouping and visibility controls."},{"src":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/screenshot-4.png?rev=3456659","caption":"Example \/llms.txt output."},{"src":"https:\/\/ps.w.org\/jumpsuitai-llms-txt\/assets\/screenshot-5.png?rev=3456659","caption":"Example .md endpoint output."}],"raw_content":"\n
JumpsuitAI \u2013 llms.txt + Markdown Endpoints automatically publishes:<\/p>\n\n
Plugin website: https:\/\/jumpsuitai.com<\/p>\n\n
The plugin pre-generates these resources from a private cache instead of rebuilding site content during each public request. Relevant content, visibility, grouping, and settings changes automatically queue regeneration. The physical root file uses the completed private artifact and the existing WordPress endpoint remains available as a fallback when root publishing is unavailable. A cache status and manual regeneration control are available on the Settings screen.<\/p>\n\n
An optional setting, disabled by default, can add a clearly marked comment containing the public llms.txt URL to robots.txt. It preserves existing crawler rules and works with WordPress-generated robots output, including output assembled by common SEO plugins. When a physical robots.txt already exists, only the JumpsuitAI managed comment block is added or removed; the plugin never creates a physical robots.txt file.<\/p>\n\n
Markdown output includes valid pipe-table formatting for standard WordPress tables. Complex tables that cannot be represented reliably in pipe-table syntax are retained as sanitized HTML.<\/p>\n\n
It also includes a simple Groups & Content<\/strong> screen to keep your output organized with sensible defaults (Pages and Posts), plus per-item controls like Hide from LLMs<\/strong>.<\/p>\n\n JumpsuitAI \u2013 llms.txt + Markdown Endpoints Pro adds:<\/p>\n\n This plugin uses Freemius for plugin updates and (optional) usage analytics. Any data collection is opt-in.<\/p>\n\n After activation, visit \/llms.txt<\/strong> on your site. The canonical URL does not use a trailing slash. On a supported single-site installation with direct filesystem access, JumpsuitAI synchronizes the completed artifact to JumpsuitAI does not overwrite or delete a file it cannot prove it created. The Settings screen reports the conflict. Remove or rename the other file, or disable the other llms.txt generator, and then use Retry public \/llms.txt now<\/strong> to retry only the root publication.<\/p><\/dd>\n The website root may not allow unattended direct writes, a conflicting file may already exist, the server may use an unusual filesystem layout, or the site may use WordPress multisite. The virtual endpoint remains available whenever WordPress handles the request. The Settings screen distinguishes root-detection, permissions, existing-file, symbolic-link, temporary-write, activation, and verification failures. Expand Technical details<\/strong> to see the selected path, how it was detected, the WordPress filesystem method, the server response, and every root candidate that was checked.<\/p><\/dd>\n A previous background worker may have stored an error before a later attempt successfully activated the file. Version 1.1.7 associates status, errors, and ownership records with the exact publication attempt and runtime, so an obsolete result is shown only as previous history. Use Retry public \/llms.txt now<\/strong> for an immediate current result.<\/p><\/dd>\n Yes, when the last active JumpsuitAI Free or Pro build stops managing the shared artifacts. The plugin removes only an Version 1.1.7 resolves the logical directory represented by the site's Home URL instead of treating the resolved WordPress-core path as the public root. It first maps No. The opt-in setting adds only a comment containing the No. If a physical robots.txt exists, JumpsuitAI can add or remove only its marked comment block. If no physical file exists, the plugin uses WordPress's virtual robots.txt filter so SEO plugin output remains intact.<\/p><\/dd>\n Not automatically in version 1.1.7. Multiple multisite sites can share one document root, so JumpsuitAI keeps the existing virtual endpoints rather than risk one site overwriting another site's root file.<\/p><\/dd>\n Relevant WordPress content and plugin-setting changes queue regeneration through WordPress cron. The previous complete artifacts remain available while normal updates are being built. Changes that make content nonpublic are withheld until safe replacement artifacts are ready.<\/p><\/dd>\n Check JumpsuitAI \u2013 llms.txt + Markdown Endpoints \u2192 Settings<\/strong> for the static file status. Use Retry public \/llms.txt now<\/strong> for an immediate root-publication result without rebuilding content, or Regenerate all static artifacts<\/strong> when the private Markdown artifacts also need to be rebuilt. WordPress cron must be able to run queued full rebuilds. An external page cache or CDN may also need to revalidate or purge its stored response.<\/p><\/dd>\n The plugin supports requesting an eligible public URL with .md<\/strong> appended. Content must be published, password-free, selected by post type in Settings, and allowed for anonymous public output. Post types controlled by an active access-restriction system may be withheld from public exports.<\/p><\/dd>\n Yes, it is enabled by default for new installations and installations that have never saved an explicit preference. An existing manual choice to disable it is preserved during the upgrade.<\/p><\/dd>\n The plugin automatically tracks normal WordPress content, reusable blocks, plugin visibility\/grouping data, and relevant settings. Custom integrations can request regeneration with Pro (separate plugin)<\/h4>\n\n
\n
External Services<\/h3>\n\n
\n
\n
\/wp-content\/plugins\/jumpsuitai-llms-txt\/<\/code>, or install via the WordPress Plugins screen.<\/li>\n\n
Where is the llms.txt file?<\/h3><\/dt>\n
llms.txt<\/code> in the website home root. If that is not available, the existing WordPress endpoint continues to serve the private completed artifact.<\/p><\/dd>\nWhat happens if a root llms.txt file already exists?<\/h3><\/dt>\n
Why is the physical root file not active?<\/h3><\/dt>\n
Why can an older error appear even though \/llms.txt exists?<\/h3><\/dt>\n
Is the physical file removed when the plugin is deactivated or deleted?<\/h3><\/dt>\n
llms.txt<\/code> file whose path and exact hash prove that JumpsuitAI created it, and removes only its marked robots.txt block. A byte-identical file left by an earlier 1.1.7 test build can be recovered once from the completed private artifact so it can be cleaned up safely. A file changed by another system is left untouched.<\/p><\/dd>\nDoes physical root publishing work on managed hosts with a symlinked WordPress core?<\/h3><\/dt>\n
WP_CONTENT_DIR<\/code> and its public URL back to the Home URL, then considers the server document root and validated WordPress fallbacks. This supports layouts where WordPress core is symlinked but wp-content<\/code> and public files live in the site's own document root. A jsai_llmstxt_public_root_path<\/code> filter is available for uncommon custom deployments; filtered paths still have to pass the plugin's normal local-path and directory checks.<\/p><\/dd>\nDoes the robots.txt option change crawler permissions?<\/h3><\/dt>\n
\/llms.txt<\/code> URL. It does not add or replace User-agent<\/code>, Allow<\/code>, Disallow<\/code>, or sitemap directives. Existing robots.txt content is preserved.<\/p><\/dd>\nDoes the plugin create a physical robots.txt file?<\/h3><\/dt>\n
Is physical root publishing supported on multisite?<\/h3><\/dt>\n
How are the generated resources kept current?<\/h3><\/dt>\n
Why don\u2019t I see updates right away?<\/h3><\/dt>\n
Which URLs get a Markdown endpoint?<\/h3><\/dt>\n
Is \/llms-full.txt enabled automatically?<\/h3><\/dt>\n
What if rendered content depends on an external system or custom data source?<\/h3><\/dt>\n
do_action( 'jsai_llmstxt_request_regeneration', $post_id, false );<\/code>, or pass 0, true<\/code> to request a full rebuild.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.7<\/h4>\n\n
\n
after_uninstall<\/code> cleanup so the last active Free or Pro build removes only its proven-owned root file and managed robots.txt block.<\/li>\nwp_tempnam()<\/code> helper and added separate diagnostics for reservation, writability, content write, byte verification, hash verification, activation, and final verification.<\/li>\nis_writable()<\/code> fallbacks with WordPress Filesystem API checks for WordPress.org Plugin Check compatibility.<\/li>\nWP_CONTENT_DIR<\/code>, the content URL, the Home URL, the server document root, and validated WordPress fallbacks.<\/li>\n1.1.6<\/h4>\n\n
\n
1.1.5<\/h4>\n\n
\n
1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n