AI Rank Suite
EN DE
Free download Get it free

Downloads & releases

Which version runs, where it comes from, what changed

The free edition and Pro come from one source tree. Below is which file is current, how updates reach you, and what Freemius handles as merchant of record.

Current version
Version0.2.45
Released2026-08-29
RequirementsWordPress 6.4+ · PHP 8.1+
LicenseGPLv2 or later
SHA-256 of the free file c4383d49c11e5a3fa0d2235c0964202f4bdf77a67ea102091583e0e8b29c0984

How updates reach you

Free edition

Today as a download here on the site, after a free sign-up. The WordPress.org listing is submitted and under review; once it is approved, the free edition updates straight through WordPress.

Pro

After purchase you connect the license key in the plugin. Updates then appear like any other plugin under "Plugins → Updates" — delivered through Freemius, with no ZIP file to handle.

Manual

You can also upload any version as a ZIP: Plugins → Add New → Upload. Your settings, scores and tables are kept; the database migrates itself on the first page load.

What Freemius is — and what it sees

Freemius is our merchant of record. That means Freemius sells to you, issues the invoice, handles tax and delivers Pro updates. Your contract partner for the purchase is Freemius, Inc. — not us.

What goes there

Purchase data and your site's license status: domain, activation, version. If you opt in when activating the free edition, anonymous usage data is added — that is a question, not a default, and saying no costs you no feature.

What does not

Your content and your AI requests. Those go from your server straight to your AI provider — neither Freemius nor we see your text, drafts or prompts.

Release notes (changelog)

0.2.45 · 2026-10-09
  • The capability now stands in the route itself: all 308 registrations name a WordPress capability where they are registered, and per-post routes ask WordPress about the post.
  • The four capabilities of the plugin decide nothing any more and are removed from every role on update; the Roles screen is gone with them.
  • A test fails the build if a route is registered without a WordPress capability.
0.2.44 · 2026-10-06
  • Every REST route asks WordPress for one of its own capabilities before the plugin capability counts, and the admin menus follow the same rule.
  • Values from $_SERVER and from the consent cookie are sanitized.
  • The audit export returns rows and the browser writes the file; a cell starting with =, +, - or @ is written as text.
0.2.43 · 2026-09-22
  • Long keyword lists fold: the first twelve chips show, one says how many more, and the opened list scrolls.
  • Elementor no longer overwrites a title applied elsewhere: the panel remembers what it handed the builder and writes only the fields changed inside Elementor.
0.2.42 · 2026-09-22
  • The SEO score is a formula: keyword 40, title and description 25, structure 20, links 15. The keyword checks fed no score until now. Without a focus keyword the score cannot pass 60. The four numbers are shown under the rings.
  • llms.txt in one click: a summary for every page in both files, the site lead, both files rebuilt, with a progress bar.
  • Site Audit: seven more rules, an Optimise link on every finding, CSV export.
  • Measure has an overview: Search Console and Analytics side by side for the same days; Bing next to Google with the Search Console import one click away.
  • Image SEO counts the media library and writes missing alt texts from the template in one run.
  • Import shows the detected plugin first; Yoast and SEOPress have their marks.
  • The AI proposal compares against the page as it is now and says when the metadata changed since.
  • Job postings carry datePosted, a job ID, the applicant country and direct apply.
0.2.41 · 2026-09-22
  • The Pro package carries its translations again. The 0.2.40 Pro build shipped without the languages folder, so every screen fell back to English on a German site. The build now refuses to run without the translation sources, and the release check verifies the compiled catalogues are in the package.
  • The word counter is called Words again. The tab under Content had been renamed Length; it is the same tab with the words of every page and of the whole site.
0.2.40 · 2026-09-22
  • The dashboard takes a score reading itself. WP-Cron only runs when somebody visits the site, so on a quiet site the daily reading from 0.2.39 could wait for days. When the dashboard opens and the last reading is older than twenty hours, it takes one on the spot. The findings card gained a "Run an audit now" button.
  • The editor toolbar shows both scores. The pinned button carries GEO and SEO as two small pills in their verdict colours and sits first. With Rank Math active, its two pinned score buttons step back into the ⋮ menu, where its sidebar still opens.
  • Keywords in bulk: the keyword field in the meta box and the sidebar accepts a pasted list (commas, semicolons or line breaks) and adds every entry at once; the AI suggestions have an "Add all" button. Ten remains the ceiling.
  • The meta box and the sidebar look like WordPress: core blue for every button, the secondary as an outline of the same blue, 3 and 4 pixel corners, core input borders, no gradients and no tinted shadows. The score rings are honey rather than marigold, with the number centred in every browser.
  • The post list says what Rank Math says: the SEO details column adds the schema type and three link counts as icons (internal, external, incoming). Score pills are top-aligned like every other cell.
0.2.39 · 2026-09-22
  • The AI search score is read once a day. The "AI search score over time" card promised one point per recalculation, by hand or on schedule, and only the first half was true: a point was stamped only when somebody pressed Recalculate, so on a site where nobody did, the last date stayed for weeks. A daily job now takes a reading, and the line moves on its own.
  • Both trend cards say when they last moved and when they move next: last and next automatic reading under the score, last completed and next scheduled audit under the findings, or the note that an audit has to be run or scheduled.
  • The "Open findings" tile updates with the chart under it. Finishing an audit cleared the chart's cache but not the tile's.
0.2.38 · 2026-09-22
  • Recurring events are scheduled on init, not on plugins_loaded. Scheduling an event asks every plugin for its cron schedules, and WooCommerce translates its schedule labels while answering. Asked during our boot, that made WooCommerce load its translations before init, which WordPress 6.7 and later report as a notice under WP_DEBUG, against this plugin. All eight recurring events now go through one helper that waits for init. Without WooCommerce nothing changes; with it the notice is gone.
  • Running an import needs a WordPress administrator. 0.2.37 added that check to the settings import and the backup restore and left it off the plugin importer, which can replace settings, redirects and post data just the same. Starting, ticking and cancelling an import run, and reading an uploaded file, now also require manage_options.
0.2.37 · 2026-09-19
  • Changing who may do what needs a WordPress administrator. The plugin has its own capabilities so that an agency can hand "manage settings" to an editor. That capability alone also opened the role editor, so somebody who had been given it could have passed it on to further roles. The role editor now also requires WordPress' own promote_users. The same second check (manage_options) covers everything that reaches beyond the plugin's settings: writing and restoring .htaccess, importing settings, restoring a settings backup, the maintenance tasks under Developer tools, and webhooks. Nothing changes for administrators.
  • Values reach JavaScript as JSON. The toolbar script received its REST address and nonce by text substitution, and the Matomo snippet had its address and site id pasted between quotes. Both now get one JSON object built by wp_json_encode().
  • Structured data is printed with the default JSON encoding. Every slash is escaped, no headline can close the script element, and it is the same data to every consumer.
  • Six importer queries (Redirection, Rank Math, All in One SEO) pass the table name as an identifier placeholder, like everywhere else.
0.2.36 · 2026-09-18
  • Everything the plugin names is named "airanksuite" now: options, tables, meta keys, capabilities, scheduled events, hooks, constants, the REST namespace and the WP-CLI command. Your data moves by itself on the first request after the update; shortcodes already in your pages keep working under their old names. Custom code using the old hooks, constants or REST paths must replace "airs" with "airanksuite".
  • A route that names a post now asks WordPress about that post: reading needs read_post, writing needs edit_post, also where post ids arrive in the body or in a list.
  • No SQL statement is assembled from fragments any more; sort columns travel as identifier placeholders and unused filters are switched off by flags.
  • The sitemap's browser view is a file, assets/sitemap/sitemap.xsl, instead of a string inside the PHP source.
  • Four external services were missing from the documentation and are now listed with what is sent, when, and their terms and privacy policies: OpenStreetMap Nominatim, our connect service behind "Sign in with Google", the Google Ads API (Pro) and webhooks you configure yourself.
0.2.32 · 2026-09-03
  • A plugin role could edit and read posts WordPress would not open for it; the content route now makes the object check.
  • A clean audit run no longer leaves the previous run's findings on the dashboard, and a run in progress is not counted.
  • A large redirect import is applied in slices, so a timeout can no longer leave it half-written.
0.2.31 · 2026-09-03
  • The page drawer stays inside the window at around 1100px: its column can no longer be pushed wider than the drawer, and the rail, the header chips and the tab strip stay visible.
  • Titles show their dash instead of the HTML entity.
0.2.30 · 2026-09-03
  • The admin looks like WordPress again: system typeface, core blue, core radii; the violet survives only on the score ring.
  • The dashboard verdict now considers audit findings.
  • Every calculation was read end to end and checks out; the score ring no longer tells screen readers "0 / 100" for an unscored page.
  • Every route the screens call exists and every field they read is sent; six more fragments are translated.
0.2.29 · 2026-09-03
  • Build housekeeping only. The second output folder was copied by hand and was therefore always one release behind; the script writes both now.
0.2.28 · 2026-09-03
  • The dashboard said "0 open findings" while the audit it linked to reported 335. It reads the audit now, from the same query as the chart below it.
  • "Pages scored over time" stopped at 20,000 pages, paginated without a stable order, and started its cumulative total at zero.
  • More English on a German install: the audit summary line, the severity counts and "Page 1 of 7".
0.2.27 · 2026-09-02
  • The AI can no longer write a meta description or title longer than the limit; the length is enforced in code, not merely requested in the prompt.
  • The cut ends on a full sentence where one fits, on a whole word otherwise, and drops a word left hanging by the cut.
0.2.26 · 2026-09-02
  • "Fill in street and number" did nothing but set the tab to itself. It goes to the field now.
  • The bulk job card said "Finished" in English on a German site; those three states were never marked for translation.
0.2.24 · 2026-09-02
  • The link graph could not be built on hosts that withhold the temporary-table privilege, and never said so. It uses ordinary tables now.
  • A failed build was indistinguishable from one nobody had started; the reason is read back and shown.
0.2.23 · 2026-09-02
  • "Write 3 descriptions (AI)" counted drafts but only ran on published posts. It takes drafts, pending and scheduled posts now.
  • "Show broken links" set the filter correctly but the table is far below the button, so nothing moved. It goes to the results now.
0.2.22 · 2026-09-02
  • An AI-improved SEO title was audited against the title it replaced, because writing post meta does not change the modified time.
  • The link scan looked stuck at 100%; it now says it is writing the results.
  • Seven more buttons lowercased German nouns, the same call 0.2.21 fixed in one place.
0.2.21 · 2026-09-02
  • The eight explanations on the link structure screen were English on every install; they had never been marked for translation.
  • Local SEO offered a button reading "firmenname ausfüllen" because it lowercased the field name.
0.2.20 · 2026-09-02
  • The link structure filters said "Orphans (undefined)". They count the list each one switches to now, and are translated.
0.2.19 · 2026-09-02
  • The link graph can finish. A column that stored the "resolved, not a post" and "broken" markers was unsigned, so the database turned both into the value meaning "not resolved yet" and the resolving phase looped forever.
  • A phase that resolves nothing now fails with a message instead of looping in silence.
0.2.18 · 2026-09-02
  • The link graph progress bar now covers the whole run, not just its first phase, and names the phase it is in.
0.2.17 · 2026-09-02
  • The link graph finishes now: the screen drives the run itself instead of handing it to WP-Cron and hoping.
  • Reloading no longer loses a run in flight, and opening the screen resumes an abandoned one.
0.2.16 · 2026-09-02
  • Fixes a crash on the six start screens: pressing the button that starts the first run threw an error on Links, Broken links, Link structure, URLs, AI visibility and Site tests.
  • The release now runs a JavaScript linter, and a failure stops it.
0.2.15 · 2026-09-02
  • Fixes a crash on the Links and Bulk screens introduced in 0.2.14. Update straight away if you are on 0.2.14.
0.2.14 · 2026-08-31
  • Disconnecting Search Console no longer depends on the report loading — the panel that held the only Disconnect button was inside it.
  • The answer simulation shows a progress bar; it is the slowest thing in the plugin.
  • The link scan says it needs this tab open, because it is driven from the browser.
0.2.13 · 2026-08-31
  • A running job now looks like one, on every screen that reports one. The stripes moved into the shared bar rather than into each screen, so anything reporting a job gets them.
0.2.12 · 2026-08-31
  • The graph scan shows its progress instead of "Working…" — the same block the site audit uses, with the count, a moving bar and a note that the run carries on in slices.
  • "Working…" was hardcoded English in the shared first-run panel, so every first-run screen said it in English to a German customer.
0.2.11 · 2026-08-31
  • The link graph was building all along and never said so. "Build the graph" answered in two seconds with "not built", which is what a dead button looks like. A stale fifteen-minute lock could block every press for a quarter of an hour — two minutes now — and a crawl that continues in the background now reports its progress instead of "not built".
0.2.10 · 2026-08-31
  • The editor panel sat 24px past the right of the window, so its live preview and "fix next" list were off screen. Its entrance animation, a slide in from the right, was stranded on its first frame; the slide is gone.
  • "Too many requests, please wait a moment" — when the wait is an hour. It now says how many runs are allowed and how many minutes are left.
  • Building the link graph allowed three runs an hour, the strictest limit in the plugin. Six now.
  • The answer-score chart keeps the whole row when nothing sits beside it.
0.2.7 · 2026-08-31
  • "Check for a new version" on the licence screen. A released update could stay invisible for an hour while the button beside it reported all was well — that one only re-read our own answer.
  • The Indexing API key can be pasted, not only uploaded as a file.
  • Post types are listed by name rather than by slug.
0.2.6 · 2026-08-29
  • The discount code is GETNOW30, in the plugin and on this site. The old LAUNCH30 stays valid — it is compiled into every copy already installed, and a code that has quietly stopped existing is a sale lost without anybody finding out.
0.2.5 · 2026-08-29
  • The dashboard says whether the AI is actually doing anything. "The AI at work" brings what only the autopilot screen knew to the screen everybody opens: the current task, the cursor, the calls made today and what they cost — counted, not estimated.
  • It moves only while something is genuinely running. A card that animates when nothing is happening teaches you to stop looking at it.
0.2.4 · 2026-08-29
  • The Measure screen could not be drawn. A shared chart component asked for a list of score bands that two of its three callers never passed, and read it without checking — so on a fresh install, before any history exists, the screen threw.
  • One broken screen no longer takes the whole plugin with it. The error panel never cleared itself, so every other screen was behind it, including the sidebar you would use to leave.
0.2.3 · 2026-08-29
  • Every link out of a setup wizard did nothing. The wizards are overlays in front of the whole application, and the code watching the address bar could only ever switch one on — never off. "Open AI Engine" did change the page underneath; the overlay simply stayed on top of it.
  • "Add a key, then come back here" now has a way back.
  • "Open developer tools" pointed at an address that does not exist — in the one place where you are already stuck. Two new checks hold both.
0.2.2 · 2026-08-29
  • "160 pages have no description" was false: the counter read our own field only. Descriptions from Rank Math, Yoast, SEOPress, AIOSEO — or from a template, which has no field at all — now count.
  • The colours harmonise, and no bare brown appears on a white card.
  • Fixed: a job's memory baseline was never cleared, so the second job in a request yielded after one record.
0.2.1 · 2026-08-29
  • A description written by the SEO plugin you are migrating from now counts as a description — Rank Math, Yoast, SEOPress, AIOSEO and four more.
  • The colours harmonise: green, amber and red come from the same set as the website, and no bare brown appears on a white card.
  • Fixed: a job's memory baseline was never cleared, so the second job in a request yielded after one record.
0.1.6 · 2026-08-29
  • Trend cards show something real from day one: where the score stands in its range, and what the findings total is made of.
  • The weakness bars have a legend; the per-page checks explain their weight dots and pin their one action to the right edge.
  • Score pills read "60 / 100"; the Links column is gone where the link graph is not installed.
0.1.4 · 2026-08-29
  • Fixed: the whole app was welded to the admin menu — the page has a gutter again, and headings, rows and cells share one left edge.
  • Trend charts stop pretending: a line needs three readings and two different values, otherwise the card says so.
0.1.3 · 2026-08-29
  • Fixed: the content list showed the same eight posts unless you scrolled past every group to the pager. Each group now says "8 of 135" and offers "Show all 135".
  • PageSpeed measures your front page on demand instead of only storing an API key.
  • Fixed: the Pro strip printed near-black text on its violet ground.
0.1.2 · 2026-08-29
  • The GEO and SEO columns in the posts list write "73 / 100" instead of "73".
0.1.1 · 2026-08-29
  • Phase two — the controls: one height, one radius, a visible focus ring, calm table rows, an unmistakable selected screen.
  • Phase three — the screens people photograph: a brand diagonal behind the score, a Pro strip in the product's own dark register, empty states with room to breathe.
0.1.0 · 2026-08-29
  • The plugin has a face: DM Sans, bundled not fetched; one violet instead of the WordPress blue every SEO plugin shares; rounder surfaces on a canvas that carries a trace of it.
  • The editor sidebar, the metabox and the block styles moved with it — one palette rather than four.
  • Phase one of a visual upgrade. No behaviour changed.
0.0.10 · 2026-08-29
  • Fixed: "Sign in with Google" in the Analytics panel asked for an OAuth URL built from your own Google Cloud credentials, which almost no site has. It takes the one-click path first now.
  • Every GET route is called on a real install before a release: 114 routes, 0 unexplained failures.
0.0.9 · 2026-08-29
  • Fixed: the site audit stopped when you closed the tab and never continued. Audit and link-check registered with the background resumer inside a REST hook, which WP-Cron never fires.
  • The screen continues an abandoned run as soon as you open it.
0.0.8 · 2026-08-29
  • Analytics connects the way Search Console does: it states what it is connected to, or offers the one button that connects it.
  • Finding the property saves it — the server was already saving it and the screen was still asking for a second click.
0.0.7 · 2026-08-29
  • Fixed: the Measure screen crashed on load. A state hook sat below an early return, so React saw six hooks on the first render and seven on the second and refused. Analytics was unreachable on every install.
  • Second-level tabs are a segmented control instead of the old pipe-separated link row.
  • The setup checklist sits on the card's own margin, and its steps read as titles rather than blue links.
  • "Upgrade to Pro" is a designed screen: what the product is for, the picture that explains it, then the three plans.
  • The asset cache buster is the file timestamp, so a rebuilt bundle is always a new URL.
0.0.6 · 2026-08-29
  • Fixed: every way of buying Pro ended on the WordPress dashboard. All four upgrade buttons resolved to a Freemius page the SDK does not register until a customer has opted in and connected, and WordPress answers an unregistered admin page by sending the visitor to the dashboard.
  • Fixed: the 0.0.5 fix for that was wrong in a second way — it redirected through wp_safe_redirect(), which refuses any host that is not this site.
  • "Upgrade to Pro" is now a screen inside the plugin: three plans, what each includes, the price, and one button to the checkout. It cannot redirect, so it cannot dead-end.
  • The buy button prefers the Freemius checkout inside WP-Admin when that page exists, because a purchase there activates the licence on this site by itself.
  • Fixed: the "Support" link pointed at the Freemius contact form, which this plugin does not register either.
0.0.5 · 2026-08-29
  • The opt-in screen after an update now speaks in our own voice, and leads with the fact that matters: it is optional, and skipping changes nothing.
  • Fixed: seven tabs in the free edition led to "no route matched the URL" instead of a Pro notice — URLs, Bulk, Checker, Internal, Structure, Keywords and Reports. Found by clicking through all forty-odd screens on a real install rather than reading the code. Three checks hold it now.
  • The assistant marks on the home page are the real ones (OpenAI, Claude, Gemini, Perplexity, Mistral) instead of hand-drawn shapes that looked like asterisks.
  • Fixed: "Upgrade to Pro" led to "you are not allowed to access this page" — the menu pointed at a Freemius screen the plugin deliberately does not register. The destination is checked before it is used.
  • Fixed: after an import the dashboard kept showing the old counts, so an import that brought 151 keywords across looked like it had done nothing. Imports now clear the counter caches too.
  • Fixed: the licence screen showed a raw PLAN_TITLE placeholder, an empty product row, and English status words inside a translated admin.
  • The three letters before each page title are explained above the table now, not only in a tooltip.
  • Home page: the hero is fully centred now — pill, headline, copy, buttons, price line and trust row on one axis. Left-aligned text with centred buttons looked like an accident, because it was one.
  • New on the home page: the Ask → Measure → Fix → Ask again sequence as four panels, a one-question-five-assistants matrix (ChatGPT found, Claude missing …), and the questions customers actually type, drifting past.
  • The setup checklist numbered the wrong things: finished steps show a tick, and the rest were numbered by their position in the whole list, so you read "2, 6, 7, 8, 9" and never a 1. The open steps now count 1, 2, 3.
  • Freemius' German opt-in read "die Kompatibilität von pluginmit deiner Website". Six strings in the shipped catalogue glue the placeholder to the next word — and the placeholder is our product name. Corrected and recompiled.
  • Fixed: the published free build could not sell anything. It was packaged with placeholder store credentials, so it classified itself as a development copy and "See Pro" landed on a notice written for developers. Both editions are built with the real store credentials now, and the packaged file is checked for them afterwards.
  • The sitemap screen counted "published" in its rows and real URLs in its header — two numbers about the same thing that never matched. Each row now shows what it actually contributes.
  • The menu group is called "AI search (GEO)". The content list ranked pages by a GEO score while the menu called the same thing AI search.
  • Fixed: "Connected services" in the settings showed Google Search Console as not connected — while the Search Console screen beside it displayed live Google data. Three of the four rows read option names nothing writes. They ask the same storage the modules use now, and three checks in the test suite hold that in place.
  • Fixed: the free edition showed four tabs whose modules it does not contain ("URLs & languages", "Bulk", "Keywords", "Reports"). Clicking one produced a routing error instead of a Pro notice — which reads as a broken plugin, not a paid feature.
  • Fixed: the automatic search for your Analytics property gave up after twenty accounts. The first real test had 55 properties with the right one at position 54. Candidates are ranked by name against your domain first, which moves that property to position 1.
  • Fixed: "Sign in with Google" failed at the last step on servers without PHP cURL. The token exchange no longer uses cURL and reports Google's own error message.
  • Fixed: o4-mini was offered in the model list but could never work · a bulk run's cost ceiling counted other AI calls on the site · undoing an autopilot change restored only the first 500 characters · a file import through the API bypassed the 8 MB limit.
0.0.4 · 2026-08-29
  • Fixed: the AI autopilot's "at most X changes per run" ceiling did nothing. The counter was written to the database and immediately overwritten by the running slice — a run capped at one change made four and kept going. That is the one hard promise we make about an agent that edits live content; it holds now.
  • Fixed: cancelling a run mid-slice could be undone. Clicking stop while an AI request was in flight left you with a running job again — and ten minutes later the resumer picked it up and carried on spending. Affected bulk runs and the autopilot; both now check what is really stored before writing.
  • Fixed: a bulk "fill in missing descriptions" run could loop forever. An empty answer from the model counted as done, wrote nothing — and because the page was still missing a description, it came back into the queue. Only the cost ceiling stopped it. An empty answer now counts as a failure.
  • Fixed: the analyzer treated a meta description as missing when it came from a template or the excerpt — although that is exactly the description the page publishes. On template-driven sites this pushed the "Snippet" area down to around 29 and reported nearly every page as needing work. The analyzer now judges what the page actually publishes.
  • Fixed: pages were not re-scored after an edit. Only the editor sidebar analyzed as you typed; a page changed by quick edit, an import or the block editor kept its old numbers — which is why the dashboard kept listing the same pages. Every published page is re-analyzed on save.
  • The analysis carries a version now: when the scoring rules change, every stored result reports itself stale and is recomputed, instead of showing old numbers until somebody happens to edit the page.
  • The setup wizard now detects all 14 import sources. It used to ask an older importer that knows nine: a site running Squirrly, Genesis, Jetpack, WooCommerce or Redirection was told during setup that there was nothing to bring across, and found its data on the import screen later.
  • New: "Sign in with Google" — one click connects Search Console and Analytics with no Google Cloud project. The matching Search Console property and GA4 account are found automatically from the domain, and the wizard has its own step for it in plain language.
  • New: agentic browsing as a single switch — allow or block the on-demand fetchers from ChatGPT, Claude and Perplexity together, with an explanation of what that means for a customer asking about you.
  • Sitemap: term IDs can be excluded, and the featured image can be included independently of content images.
  • Design: in the rich-result cards the field count fell out of the card whenever a translation ran long, and "12 fields" was never translated at all. The header is rebuilt with the count in its own column.
  • "Where this site is weak" now speaks the customer's language: "Snippet — title, description, slug" became "Title & description — the two lines Google and ChatGPT show before anyone clicks". And where one row counts fewer pages than the row above it (search terms only exist on pages that have one), it now says how many pages are not counted and why.
  • The page-cache entry is gone from the admin bar.
0.0.2 · 2026-08-28
  • An installed but not yet activated Pro copy is now asked to connect its license — with a direct path to activation — instead of being shown the sales card again.
  • The "See Pro" links say "Activate license" on a Pro install and lead straight to Freemius activation.
0.0.1 · 2026-08-28
  • First public release.
  • Design: the whole admin uses WordPress's own design language — native menu, nav tabs, core buttons, notices and list tables — in light and dark, in English and German.
  • Licensing runs entirely through Freemius; the plugin never stores a key of its own.
  • llms.txt and llms-full.txt pass Google's PageSpeed "Agentic Browsing" audit; the panel shows the three rules and the verdict before you run the report.

The complete development history ships with the source (docs/CHANGELOG.md).

14-day money back · no questions asked

Find out what the assistants say about you

The free edition installs in a minute and needs no key. Pro is $49 a year — $34.30 for the first year with code GETNOW30, and if it does not fit, you get your money back.