by
Acid Studios
0 (0 reviews)
Acid AEO — AI Readiness, Citations & Rich Data
Help ChatGPT, Perplexity and Google AI cite you: llms.txt, one AI crawler policy, rich data, IndexNow and a readiness score, set up in two minutes.
Acid AEO ranks #71,247 among WordPress.org plugins with 0+ active installations, is #3,076 of 4,265 in the SEO & Marketing category, and was last updated Oct 9, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.0.5
Current Version v1.0.5
Updated 4 weeks ago
Last Update on 09 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#3,076 of 4,265 in SEO & Marketing
Downloads -43.5% this week
Actively maintained
Rank
#71,247
—
No change
Active Installs
0+
-100%
KW Avg Position
126
—
No change
Downloads
365
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
43,679
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 10 more installs to reach 10+
Rank Changes
Current
#71,247
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
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.5
- Last Updated
- Oct 09, 2026
- Requires WP
- 6.4+
- Tested Up To
- 7.1.4
- PHP Version
- 8.0 or higher
- Author
- Acid Studios
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- 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
Frequently Asked Questions
Common questions about Acid AEO — AI Readiness, Citations & Rich Data
No. Acid AEO detects the SEO plugins listed above and turns off the structured data pieces they already emit (Organization, WebSite, Breadcrumb, Open Graph and Twitter tags). What stays on is what SEO plugins do not do: FAQPage, Speakable, extended Person data, AI-specific files and the crawler policy. You can force any piece on or off yourself.
They are virtual by default: llms.txt, humans.txt, ai.txt, ai-context.json and security.txt are produced on request through WordPress rewrite rules, so they are always current. If a real file with the same name already exists in your webroot, that file wins and the plugin tells you about it in the audit.
The web server answers with the file on disk before WordPress runs, so the copy this plugin generates is never seen for that path. The audit reports it ("No robots.txt on disk", "No conflicting llms.txt on disk") rather than overwriting anything: a file the plugin did not write is never touched. Delete or rename the file and the generated one takes over immediately. robots.txt is a special case — the plugin never writes it to disk; it only filters the virtual one WordPress serves.
Server-side tracking sees only the requests that reach PHP, so a page served from a full-page cache is invisible to it. The wizard detects the common cache plugins and offers the browser beacon: one small first-party script that reports a visit arriving from an AI answer to your own site's REST endpoint (/wp-json/acid-aeo/v1/beacon). It sends the page URL, the referrer and the utm_source parameter, once per page per browser session, and nothing else. No third party is involved. Behind a proxy or CDN, restore the real visitor address at the web server or with the acid_aeo_client_ip filter, otherwise visits are under-counted.
No. Generated files are cached in transients and invalidated only when content or settings change. Front-end output is a single JSON-LD block plus a few header tags; there is no JavaScript on the front end unless you switch the optional citation beacon on.
It is designed to be. No cookies are set, no personal data is stored: visitor IPs are hashed with a salt that rotates daily and truncated, and user agents are reduced to a bot name. Rows are deleted automatically after the retention period you choose.
Yes. Switch Static files on and pick which of llms.txt, llms-full.txt, humans.txt, ai.txt, ai-context.json and .well-known/security.txt are written into your webroot through the WordPress filesystem API. You need this on hosts that answer /*.txt and /.well-known/* from disk and only fall through to PHP when the file is missing — a CDN, an edge cache or a static export in front of WordPress. The writer is deliberately conservative. It never writes robots.txt, which belongs to WordPress core and to your SEO plugin. Every file it generates carries a marker (generated by Acid AEO, or the "generator" field in ai-context.json), and a file without that marker is never overwritten and never deleted — so an llms.txt that was already in your webroot stays exactly as it is. Writing needs the direct filesystem method: if WordPress would have to ask for FTP credentials, the audit says so instead of asking. The files are rewritten when the settings change, when you publish, and once a day. Each write also prunes: a file the plugin wrote that you have since unticked — or whose module you switched off — is deleted by the same pass, so your server stops answering with a copy the settings no longer stand behind. Switching the module off removes the ones the plugin wrote, and so does uninstalling it. See docs/hosting-notes.md for server and cache configuration.
Nothing, by default. Deleting the plugin keeps your settings, the citation log and the post and user meta it added, so a reinstall picks up where you left off. Tick Remove all data when the plugin is deleted under Settings → Advanced before deleting if you want a clean wipe: that removes the settings, the events table, its cron events, the post and user meta, its transients and any file in the webroot that carries the plugin's own marker. Files it did not write are never touched.
Multisite: activate per site or network-wide; each site keeps its own settings, table and cron. A network activation prepares every site that already exists, and a site created afterwards is prepared as it is created.
Yes, every screen has a command behind it: wp acid-aeo audit [--fresh] [--format=<table|json>] — runs the readiness audit and exits with status 1 when the score is below 50, so a deployment pipeline can gate on it. wp acid-aeo regenerate — drops every cached file and rebuilds the rewrite rules. wp acid-aeo static write|remove — writes the generated files to disk, or removes the ones the plugin wrote. wp acid-aeo indexnow submit [<url>...] [--all] and wp acid-aeo indexnow log. wp acid-aeo export [--file=<path>] and wp acid-aeo import <file> — move settings between staging and production. wp acid-aeo citations stats [--days=<n>] and wp acid-aeo citations purge [--older-than=<days>]. wp acid-aeo preview <llms|llms_full|robots|humans|ai_txt|ai_context|security> — prints what a file would say right now, even when its module is switched off.
