MonoRanks – AI SEO Audit, AEO and GEO with One-Click Fixes

Rexistro de cambios

0.1.25 – 2026-10-25

• New: After activation, the plugin opens its MonoRanks screen, and the Plugins list shows a Connect link.
• Fix: Settings shows “Fixes: Not set up” with an Allow link when no MonoRanks app password exists, instead of saying fixes are written with one.
• Fix: The “What to do next” cards show “Checking…” after one slow answer and try again within minutes, not an hour.
• Fix: No “Could not connect” message on a site that is already connected.
• Fix: Content is sent right after connecting, on every way of connecting.
• Fix: After Disconnect, Connect works again for the same website.
• Enhancement: Connect opens MonoRanks in the same tab and comes back there.
• Enhancement: The connector key button now reads “Save key”.

0.1.24 – 2026-10-23

• New: Category, tag and product category pages are sent to MonoRanks with their SEO title and meta description.
• New: MonoRanks can write and undo the SEO title and meta description of these pages in Rank Math and Yoast SEO. Without an SEO plugin, it writes the category description.
• Enhancement: Edited or deleted categories and tags are rechecked in MonoRanks within minutes.

0.1.23 – 2026-10-17

• Enhancement: Sites MonoRanks cannot reach, such as local or firewalled sites, now connect with one button too: the key comes back by itself, nothing to copy.
• Enhancement: Simpler Settings and Overview screens: short rows, with details in (i) tips.
• Enhancement: “What is sent” opens on a click.

0.1.22 – 2026-10-16

• New: Connect to MonoRanks with one button: sign in or sign up, approve in WordPress, done. The settings page shows “Connected” by itself.
• Enhancement: The WordPress approve screen shows the MonoRanks logo and what it can do.
• Enhancement: Shorter connect steps on the Overview and Settings screens.

0.1.21 – 2026-10-09

• Enhancement: The content sync also sends each image in a post with the alt written in the post body, next to the alt stored on the image.
• Fix: Image alt text is checked and written where it shows: the alt in the post body when the image sits there, and the stored alt. Fixes are no longer refused as changed when the page and the stored alt differ.

0.1.20 – 2026-10-07

• Enhancement: Each fix on the Overview reads “Image alt on ” and shows the old value, an arrow and the new one, with the image name.
• Enhancement: The Reports panel lists the website’s weekly emails (name, next send, recipients, on or off) next to its reports.
• Fix: A fix whose value was changed in WordPress after it was reviewed is no longer listed as ready to apply. It shows under “Needs review in MonoRanks” with a link, and MonoRanks moves it back to review.
• Fix: The apply error no longer says the whole page changed; it names what happened.

0.1.19 – 2026-10-04

• New: “What to do next” on the Overview: outreach, backlinks, competitors and keyword movers.
• New: A MonoRanks box in the post editor with search, visits, revenue and lost links for the page.
• Enhancement: The Posts list card shows clicks, revenue and lost links.
• Fix: Persian translation file header.

0.1.18

• After every fix MonoRanks writes (or undoes), the plugin clears that page from the active page cache, so the change shows right away. Adds WP-Optimize, Nginx Helper, Breeze, Kinsta, WP Engine and Pantheon to WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache and SiteGround Optimizer.
• MonoRanks is told which cache was cleared, so it can tell you when a page may still show the old version.

0.1.17

• After MonoRanks writes llms.txt or the AI crawler rules, the plugin clears /llms.txt or /robots.txt from WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache and SiteGround Optimizer, so an old cached copy does not hide the change.
• /llms.txt is sent with headers that tell caches not to keep it.

0.1.16

• The Overview says how many fixes are ready to apply and how many still need a value in MonoRanks, instead of counting them all as ready.

0.1.15

• Works with The SEO Framework: approved titles, descriptions, canonicals and noindex go into its own fields, and the page shows them once.
• On the homepage, if The SEO Framework’s Homepage Settings already set that field, the fix is refused with the reason, because that setting wins.
• With an SEO plugin MonoRanks cannot write into yet (such as SEOPress), those fixes are refused with a reason that names the plugin, and no second set of tags is printed.

0.1.14

• In block editor posts, the approved opening paragraph goes in as its own paragraph block before the first block. Other blocks, including those from other plugins, are never changed.
• Every body edit is checked right after it is saved. If a block would break, the post is put back as it was and the fix is reported as failed, with the reason.

0.1.13

• The description lists only the fixes the plugin can write.
• With All in One SEO active, approved titles, descriptions, canonicals and noindex go through its own tags instead of adding a second set.
• Without an SEO plugin, an approved noindex joins WordPress’s robots tag instead of adding a second one.

0.1.11

• When no fix is approved yet, the MonoRanks screen says how many fixes MonoRanks can write for this site, by type, with a link to review them.

0.1.10

• The search clicks change on the MonoRanks screen says what it is compared with: the previous 28 days, not this week.
• Persian: the last untranslated messages on the MonoRanks screen are translated.
• A site that was never connected no longer offers to erase data it does not have.

0.1.9

• An empty score ring in the Posts list explains that the page has not been checked, instead of looking like a fault.

0.1.8

• Reads every score again after this update, so posts left without one get theirs back.

0.1.7

• Scores arrive for every post on large sites: a pull that runs out of time carries on where it stopped.

0.1.6

• Scores appear as soon as you open the MonoRanks screen, also on sites where WP-Cron is switched off.
• “Sync content now” brings the scores back with it.
• The remaining pages still update in the background.

0.1.5

• Disconnecting in WordPress tells MonoRanks, which revokes this website’s key.
• “Open MonoRanks” goes to this website, not the home page.
• Audit results are asked for again within the hour after MonoRanks gains support for them.

0.1.4

• The Plugin URI and Author URI headers point at plain addresses, without tracking parameters.
• The contributor list uses the right WordPress.org username.
• The public ping route says in the code why it is public: MonoRanks calls it before the site is paired, it reads nothing, and every other route needs an administrator.

0.1.3

• On a site with many plugins the admin menu is taller than the page; the plugin’s screens now stretch to the bottom of it, so the footer is the last thing on the page with nothing left over under it.

0.1.2

• On a site with a long admin menu the plugin’s screens now reach the bottom of the page, so the footer is the last thing on it: no strip and no empty space under it.

0.1.1

• On a site whose admin menu is taller than the page, the plugin’s screens ended in a grey strip under the footer. The dark band now runs to the bottom of the page.

0.1.0

• Beta, before the first WordPress.org release: MonoRanks menu with an Overview (scores, search clicks, pages needing attention, fixes ready to apply, changes with Undo) and Settings; a MonoRanks column with health and AEO scores in Posts and Pages; content sync and one-click fixes with undo; a danger zone that erases everything the plugin stored; Persian translation.