by
Brad Phillips
5 (2 reviews)
JumpsuitAI – llms.txt + Markdown Endpoints
Generate /llms.txt, /llms-full.txt & .md endpoints for AI/LLMs in WordPress. Works with Yoast SEO, Rank Math, SEOPress & All in One SEO.
JumpsuitAI ranks #11,279 among WordPress.org plugins with 200+ active installations, is #538 of 4,265 in the SEO & Marketing category, a 5/5 rating from 2 reviews, and was last updated Oct 18, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.1.9
Current Version v1.1.9
Updated 2 weeks ago
Last Update on 18 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#538 of 4,265 in SEO & Marketing
Top 25% by installs
Downloads -67.6% this week
Actively maintained
Rank
#11,279
—
No change
Active Installs
200+
—
No change
KW Avg Position
13
—
No change
Downloads
4K
+7 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(2 reviews)
Next Milestone 300
200+
300+
293
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 14 more installs to reach 300+
Rank Changes
Current
#11,279
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
2 reviews
Overall
100%
5
2
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Security History
Source: WPVulnerabilityNo known vulnerabilities on record for JumpsuitAI. Checked 3 months ago.
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.9
- Last Updated
- Oct 18, 2026
- Requires WP
- 5.0+
- Tested Up To
- 7.1.4
- PHP Version
- 7.2 or higher
- Author
- Brad Phillips
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 2
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Yoast SEO – Advanced SEO with real-time guidance and built-in AI
10M+ installs
#2
Rank Math SEO – AI SEO Tools to Dominate SEO Rankings
4M+ installs
#13
Redirection
2M+ installs
#21
All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)
2M+ installs
#22
MC4WP: Mailchimp for WordPress
1M+ installs
#35
Hostinger Reach – AI-Powered Email Marketing for WordPress
1M+ installs
#41
XML Sitemap Generator for Google
1M+ installs
#56
EWWW Image Optimizer
1M+ installs
#60
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners who want their public content discoverable by AI/LLM systems. It automatically generates an /llms.txt file and Markdown (.md) endpoints for public content, with a Groups & Content screen to organize what gets exposed.
- Auto-generates /llms.txt file
- Markdown (.md) endpoints
- Groups & Content screen
- Default Pages and Posts grouping
- Hide from LLMs per-item control
Frequently Asked Questions
Common questions about JumpsuitAI – llms.txt + Markdown Endpoints
After activation, visit /llms.txt 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 llms.txt in the website home root. If that is not available, the existing WordPress endpoint continues to serve the private completed artifact.
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 to retry only the root publication.
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 to see the selected path, how it was detected, the WordPress filesystem method, the server response, and every root candidate that was checked.
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 for an immediate current result.
Yes, when the last active JumpsuitAI Free or Pro build stops managing the shared artifacts. The plugin removes only an llms.txt 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.
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 WP_CONTENT_DIR 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 and public files live in the site's own document root. A jsai_llmstxt_public_root_path filter is available for uncommon custom deployments; filtered paths still have to pass the plugin's normal local-path and directory checks.
No. The opt-in setting adds only a comment containing the /llms.txt URL. It does not add or replace User-agent, Allow, Disallow, or sitemap directives. Existing robots.txt content is preserved.
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.
Not automatically. 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.
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.
