Acid AEO — AI Readiness, Citations & Rich Data

Changelog

1.0.4

Released 2026-10-08.

• Changed: with the IndexNow module switched off, nothing is sent any more, whoever asks: wp acid-aeo indexnow submit and POST /indexnow/submit now refuse with a clear message instead of sending.
• Changed: the Documentation link on the Plugins screen opens the documentation, not the product page.
• Fixed: the Content tools option read “On ?format=md only”; the query value is ?format=markdown.
• Fixed: the setup wizard and the admin notice said “five short steps”; there are seven.

1.0.3

Released 2026-10-08.

• Changed: the admin screens and the setup wizard are redrawn in the Acid Studios light style: Inter and Space Mono, black on white, one green used as a fill under black text. Nothing was moved and no setting changed.
• Changed: two typefaces now ship with the plugin (Inter and Space Mono, SIL Open Font License 1.1, in assets/fonts/ with their licences). They load on the plugin’s own admin screens only; nothing is requested from another server.
• Fixed: text that was white on green (the mark, the step numbers, the yes/no buttons, the success message) did not meet WCAG AA contrast. It is black on green now.
• Fixed: a switch that is off was drawn too faintly to see against the page.
• Fixed: in a right-to-left language the wizard’s switches slid the wrong way.
• Fixed: the wizard’s yes/no buttons showed their radio circles on top of the labels.
• Fixed: at phone width the settings screen, the crawler table and the Tools screen scrolled sideways.
• Fixed: the “AI readiness” widget on the WordPress dashboard showed its score as plain text.

1.0.2

Released 2026-09-18.

• Changed: the line crediting Acid Studios in humans.txt is off by default. It was on, which put a link to the plugin author’s site in a public file on every install that did not go looking for the switch. The switch is still in the wizard and in Settings for anyone who wants to leave it on.
• Fixed: on a site given its own directory for WordPress — core’s supported layout, where siteurl is home plus a folder — the optional static files were written into the WordPress folder while every address the plugin publishes pointed at the folder above it. The files were invisible, and the audit then reported them missing. They are now written where the site is actually served from, and an uninstall removes them from there.
• Fixed: on a multisite network, switching the static files on from a site other than the main one overwrote the main site’s llms.txt, humans.txt and ai-context.json with that site’s content, published at the network’s address. Network sites now decline to write to the shared directory and say why; virtual delivery is unchanged, so every site still answers its own files.
• Fixed: the Allow: lines in robots.txt named /llms.txt and its neighbours even on sites where those addresses do not answer — with plain permalinks the files are served through a query variable, and on a site in a subdirectory every path carries that directory. The lines are now taken from the addresses the files are actually served at.
• Fixed: the audit’s loopback requests called the core https_local_ssl_verify filter with one argument where core passes two. A site with a callback written to core’s documented signature took a fatal error on every audit.
• Fixed: the sitemap probe accepted any HTTP 200 as a sitemap, so a host that answers unknown paths with the home page had an HTML page stored and then advertised to every crawler as its sitemap. The answer now has to read as a sitemap.
• Fixed: a fresh audit settled which sitemap answers before dropping its cached responses, so the probe read answers up to ten minutes old and then fetched every address a second time. It now happens after, once, inside the run.
• Fixed: a summary taken from a post’s excerpt was published with the page builder’s shortcodes still in it, while the same text taken from the content had them removed.
• Fixed: the headings the AI blocks print — “In short”, “Frequently asked questions”, “Key takeaways” — were English on every site, whatever its language, because the defaults were never translated. They now follow the site language like the rest of the interface.
• Added: the acid_aeo_llms_full_documents filter. llms-full.txt considered at most two hundred documents with no way to change it and nothing saying so; the byte budget beside it was already a setting.
• Fixed: the audit read authors from post alone, so a site whose content is entirely in a custom post type was told every author profile was empty. It now reads the post types the plugin publishes; the same goes for the key pages fallback, which now recognises every page-like post type, and for the published counts behind the wizard’s guess at what kind of site this is.
• Fixed: the Documentation link on the Plugins screen pointed at a page that did not exist; it now opens the plugin’s page on acidstudios.ro.
• Changed: the readme now names, one by one, the URLs that appear in the source without ever being requested, so an automated scan can match the constant it reads against a sentence about that constant.
• Changed: Contributors now lists the wordpress.org account that owns the plugin.
• Fixed: uninstalling now also removes the per-post “hide the last updated line” flag introduced in 1.0.1, instead of leaving it behind in the database.
• Changed: the readiness audit’s loopback requests now respect the https_local_ssl_verify filter, the same switch WordPress core uses for its own loopbacks.
• Fixed: on a site running Yoast SEO, robots.txt named the same sitemap twice. The AI crawler block is now the last thing added to the file, so the line another plugin contributes is seen and not repeated.
• Fixed: on a site built with a page builder — WPBakery, Divi, Elementor — llms.txt, llms-full.txt and the Markdown endpoint printed the builder’s own shortcodes instead of the text inside them. The tags are now removed whether or not the builder registered them for the request, and the prose they wrap is kept.
• Fixed: a page kept out of search by the site’s SEO plugin was still advertised in llms.txt and ai-context.json. The noindex set in Yoast SEO, Rank Math, SEOPress, All in One SEO, The SEO Framework or Slim SEO is now read, each in that plugin’s own vocabulary, and the page is left out. The acid_aeo_is_noindex filter answers for anything else.
• Fixed: on a WooCommerce store the generated files led with Cart, Checkout and My account — three pages that read as a form to anyone who fetches them. They are left out; the shop page, which is the catalogue, stays.
• Fixed: a page built with Elementor, Bricks or Oxygen was published as a bare link, because those builders keep the content in post meta and leave post_content empty. The rendered content is read instead, so the page gets a summary like any other.
• Fixed: the audit reported llms.txt as “written by something else” on most sites — it looked for the signature in the first two kilobytes, and llms.txt signs its last line. It now asks the same question, of both ends of the file, as the module that writes it.
• Fixed: the sitemap address the files point at was worked out from which SEO plugin is installed, which is not the same question — Rank Math, SEOPress and All in One SEO ship the sitemap as a module that can be off, and The SEO Framework and Slim SEO answer at their own address while core’s stops. The audit now settles it by asking the site, and robots.txt adds no sitemap line when another plugin has already written one.

1.0.1

Released 2026-09-17.

• Fixed: the “Updated on” line gave its <time datetime> attribute in UTC while printing the visible date in the site’s own timezone, so the two could name different days on any site that is not on UTC. Both halves are now the site’s local time, and the visible date is localised rather than always English.
• Added: Hide the “last updated” line on this post, a per-post checkbox in the AI readiness box, for the pages the site-wide line does not suit.
• Added: the acid_aeo_last_updated_html and acid_aeo_last_updated_threshold filters, so a theme can move, restyle, replace or remove the line and choose how old a revision has to be.

1.0.0

Released 2026-09-15.

• Initial release: AI crawler policy (robots.txt, ai.txt, Content-Signal), llms.txt and llms-full.txt, humans.txt, ai-context.json, security.txt, JSON-LD rich data, AI head tags and HTTP headers, IndexNow, AI citation tracking, content tools with Markdown for agents, optional static files, the readiness audit, the setup wizard, a REST API and WP-CLI commands.