AuditAE AI Search Toolkit

Recent releases are below. WordPress.org truncates this section at 5,000
characters, so older entries are kept in the plugin’s development history
rather than here, where they would push the current release out of view.

0.27.0

• New free feature: orphaned content report. A new Links tab lists every published post and page that nothing else on your site links to. A page with no internal links pointing at it is hard for a crawler to find and hard for an AI engine to judge important — and until now you had no way to see which of yours were in that state. Yoast charges for this report in Premium.
• New free feature: internal linking suggestions with one-click insertion. Pick an orphan and AuditAE shows you which existing pages already say its name in ordinary prose, and offers to link the phrase for you. Adding the link changes nothing else in the post: one phrase is wrapped, exactly once, in a page that already mentions it. Yoast Premium and Rank Math PRO both charge for internal link suggestions.
• Fix: the link graph is now site-wide instead of one page deep. Incoming links used to be counted only within the current page of results, so anything linked from an older post reported zero incoming links — on any real site, most of the answer was wrong. The graph is now built across the whole site, cached, and refreshed daily and whenever you edit a post.
• Fix: internal link insertion can no longer corrupt a post. The anchor phrase used to be matched anywhere in raw content — including image alt text, Gutenberg block comments, and scripts — where wrapping it in a link breaks the tag or the block. It now only ever links visible prose, and declines entirely on malformed markup.
• Performance: resolving a link to a post no longer runs WordPress’s URL parser once per link. Both link endpoints previously did, which meant queries proportional to the number of links on the page; they now use a lookup table built once per scan.
• Fix: uninstalling the plugin left four keys behind — the two schema probe caches added in 0.26.0 and their stored results. They are now removed with everything else.
• Fix: the orphan report no longer lists your front page or blog index, which are reached from your navigation and, in the front page’s case, cannot receive a measurable content link at all.
• Fix: the link graph now works on sites using Plain permalinks. Every URL there names its post as ?p=123, which path matching ignored — so everything was reported as an orphan. ?p= shortlinks in content now also count on any permalink structure.
• Fix: renaming a large image no longer destroys its scaled copy. Uploads past WordPress’s big-image threshold keep a scaled working copy beside the pristine original; renaming mapped both to the same new filename, and the second move silently overwrote the first. The renamed copy now keeps its -scaled suffix.
• Fix: redirects created from a full URL on a site installed in a subdirectory pointed at a doubled path (/blog/blog/page) and 404’d. Destinations are now stored home-relative, and existing rules self-correct when they fire.
• Fix: literal backslashes in content written through the connected assistant (Windows paths, regular expressions, escaped JSON) were silently stripped on save, and again on every edit. All write paths now preserve them.
• Fix: this changelog had grown past the 5,000-character limit and was being silently truncated on WordPress.org, hiding the most recent entries.

0.26.0

• New free feature: FAQ schema editor in the post editor. Add question-and-answer pairs to any post or page from a metabox and AuditAE publishes them as schema.org FAQPage JSON-LD. No account, no pairing, and your post content is never modified. Previously FAQ schema could only be written by the paid assistant, which made it the one AI Readiness Score check with no free fix.
• New: the Score tab’s FAQ row opens a filtered Posts list showing only the published posts still missing FAQ schema, so the score becomes a worklist. Two other checks (content freshness, AI crawler activity) also gained free actions.
• Fix: FAQ coverage no longer scores 0 on sites using Yoast or Rank Math FAQ blocks. The site-wide score counted only AuditAE’s own FAQ meta, while the per-post checklist and the front end both counted the other plugins’ blocks. All three surfaces now agree.
• Fix: the Organization schema check no longer awards points for schema that isn’t on the page. It passed as soon as Yoast or Rank Math was installed — but Yoast emits no Organization node until you set a site name, and Rank Math emits nothing until its setup wizard runs. It now verifies against your live homepage, falls back to reading the SEO plugin’s settings, and stays quiet when it can’t get clear evidence.
• Fix: the Article / Product schema check had the same false positive and is fixed the same way, against a real post rather than the homepage.