Geoa – AI SEO & AEO on Autopilot

Registro de cambios

0.9.39

• Your published articles are only ever reported back to the Geoa account that wrote them. When a site was connected to a different Geoa account — a new owner, a new subscription, a different workspace — the first sync afterwards announced the previous account’s articles to the new one as if they had just been published. The new account then began measuring, and counting against its allowance, pages it had never written, while the account that did write them never got its own confirmation that they had gone live. Nothing is removed or altered by this fix: the posts are your content on your site, and they stay exactly where they are, keep working and keep their place in your archive. The only thing that changes is that they are no longer reported under an account that did not write them. Articles imported before this update are treated as belonging to the account your site is connected to when you update — updating the plugin is not a change of ownership.
• Links to your own pages inside an imported article are real links again. When Geoa Content wrote a link to another page on your site, it arrived in the draft as its raw text — the link text and the path, brackets and all — sitting visibly in the middle of a paragraph, and it stayed that way on the published page. Geoa’s writing service now produces those links correctly, and drafts already waiting in your editor are re-rendered once when you update, so articles written before this are repaired too instead of waiting for you to generate them again.
• The checklist in the post editor is now written in the language you read WordPress in, and it asks for things WordPress can actually do. Every signal name and every piece of advice came back in Danish no matter what language your site or your admin was in, so an English site edited in an English admin was told “Ingen pladsholdere i teksten”. The advice was worse than the language: to add links to your own pages it asked you to type the link as markdown — anchor text in brackets, path in parentheses. WordPress does not turn that into a link, so anyone who followed the advice published the brackets, visibly, in the middle of their article — the same thing the fix above repairs in imported drafts. Three other pieces of advice had the same problem, asking for markdown tables and markdown headings. The panel now follows the language each editor reads the admin in, so two people working on the same site each get their own, and it points at the editor’s own link and table buttons instead. Sites in a language Geoa does not yet write get English rather than a guess.
• When you publish an article Geoa wrote, Geoa is told — and if it is not, the screen says so. Publishing is what starts the measurement: until Geoa knows the article is live, it cannot show you what the article does for you. The plugin reports the publication on its hourly check, but it counted any reply from Geoa as a confirmation, including a reply that said nothing had been recorded. It then never mentioned that article again, so the measurement never began, on exactly the article you cared enough to publish, and nothing anywhere said a word. Geoa now has to confirm the article before the plugin stops asking, and it tries again on the following checks. Settings has a new line showing how many of your published articles have actually been reported home, and it tells you if any of them could not be. Two more things on that screen were misleading and are fixed: it said «Imported here: 3 published», which counts posts on your site and was easy to read as «three reported to Geoa», and it never said when the next check was due. Sync now also says if it fails to run the article check instead of reloading the page as though it had.
• Switching on /llms.txt no longer replaces a file you already had, in silence. If your site already answered at that address — a file your theme serves, or one you wrote yourself — Geoa now reads it before it takes the address over, keeps it, and serves it exactly as it was. It adds only the two things it can honestly contribute that you cannot write for yourself: the registry-verified identity of your business, and any published page your own file did not already list. Everything you wrote stays — what your business is, what it explicitly is not, links to your other products, your own sentence about each page. Settings shows what Geoa found, when it looked, and the saved copy itself, and offers the other way — Geoa’s generated file instead of yours — as a decision you make rather than something that happens to you. If Geoa could not reach your site to look, it says so instead of assuming there was nothing there. The setting’s own wording now says what switching it on does; «Optional — off by default» was not a warning about anything. And the file Geoa generates itself now says more: every page is listed with a sentence describing it, taken from your SEO plugin’s description, your excerpt, or the page’s own opening lines. Repeating a page’s title after its own address tells a language model nothing, and describing your pages is the only job this file has.
• The Geoa badge panel in Settings no longer vanishes on paid plans, leaving a «Geoa badge» checkbox in the form below with nothing anywhere on the screen to explain it. Paid plans now get a short panel of their own saying what is actually true for them: the badge is optional, because the monthly re-scan it earns free sites is already part of their plan, and Geoa does not check whether it is on their site. Free plans keep the panel they had, with one correction. Where it said Geoa would find the badge on your site automatically, it now says where the first check is started — in your Geoa dashboard. Geoa does look for the badge by itself, once a day, but only after it has been found there once; before that nothing was looking, and the screen said otherwise.

0.9.38

• Your sitemap is no longer invisible to search engines. On a site built from pages with no blog posts, WordPress 7.1 answers its own sitemap — the file that tells Google and Bing which pages your site has — with «not found», while still sending the correct list of pages underneath it. Search engines read the answer, not the list, so the sitemap counted for nothing: it could not be submitted, and new or changed pages lost their fastest route to being found. A site with even one published blog post never sees this, which is why it goes unreported — and a site built entirely from pages, like most local businesses, is exactly the case that breaks. Geoa now keeps the sitemap answering correctly, and records the day it had to, so it is visible that it happened. Where another SEO plugin serves your sitemap, Geoa leaves it alone.
• The readiness score in the post editor now describes the article you are looking at. It used to describe the version last saved to WordPress, fetched once when the editor opened — so on a new post it answered about an empty page. Paste an article and open the panel, and you were told it had no headings, no depth, no FAQ and no lists, with a score to match, for an article that had all four. Reloading the page showed a completely different, correct answer, and nobody reloads a page they have just pasted an article into. The panel now scores what is in the editor and re-scores when you change it. While it is working it shows a spinner rather than the previous number: a score for text you have since rewritten is not a smaller truth than no score, it is a wrong answer you cannot tell apart from a right one.
• A connected site is no longer told to connect. When the full 23-signal score could not be fetched, the panel fell back to its own smaller estimate and explained it with «connect Geoa for the full 23-signal score» — on sites that were connected, paired, publishing schema and applying approved fixes. It sent people looking for a setup fault that did not exist. The panel now says which of the two it is: not connected yet, still connecting, or connected but the full score did not come back this time.
• Geoa no longer marks your article down for things your site already has. The editor panel did not tell Geoa what this WordPress site publishes, and a signal Geoa is not told about comes back as missing — so an article on a site that publishes Article schema was told to go and generate Article schema, and internal links in the text were counted as none. The plugin now reports both, so those checks are answered instead of failed.
• A fix Geoa has already published to your site does not disappear because you connect a different Geoa account. It used to, and the timing was the worst possible: reconnecting is exactly what the screen tells you to do when a connection is lost, and the first sync afterwards quietly took down the llms.txt file the previous account had approved — while that same screen promised that nothing had been removed from your site. Work already published now stays published. If it came from an account this site is no longer connected to, it keeps being served, and Settings asks you once whether to keep it or remove it — nothing but that answer removes it. And when a fix genuinely IS withdrawn, because you un-approved it in your Geoa dashboard, the sync now names what it took down instead of leaving you with a page that used to exist.

0.9.37

• The answer to «how does this name relate to your registered company?» can be changed. It could be set, but not kept: the choice was gone on the next page load, and nothing on the screen said why. That answer is not decoration — it decides whether your registration number, legal form and registry entry describe your product or the company behind it, so being unable to change it meant being unable to correct a claim published in your name. It now has its own control with its own save, and it confirms the save by reading the value back out of storage and telling you, in a sentence, what your site publishes as a result. And if the answer ever fails to reach your site — a firewall or security layer in front of WordPress can quietly drop a single form field — you are told exactly that, instead of being shown a screen that looks like it saved.
• Nothing is assumed about your name any more. Until now, a site where nobody had answered the question above was treated as having answered «it is another name for the company itself» — and that assumption was sent on to Geoa as though you had chosen it. Geoa then built on it: on one site it produced an article stating that a PRODUCT was a Danish anpartsselskab, inside a block that cited the company register with a date and a source link. The register says that about the company. It says nothing about the product. «Not answered» is now a real state: neither option is preselected, the setup screen asks before it will publish, and nothing about the relationship is sent to Geoa until you have answered it. Your published schema does not change until you answer — answering is what changes it.
• An answer of «it is another name for the company itself» now actually arrives. This plugin and Geoa spelled that one answer differently, so it was discarded on the way: you answered, the screen said so, and Geoa carried on as though you never had — still asking, still holding back what it could say about your business. The other answer happened to be spelled the same on both sides, which is why only half of this was ever visible.

0.9.36

• A priority is never shown with a blank where a name should be. Version 0.9.34 said this was fixed. Half of it was: the sentence no longer stops in the middle of a word. The other half was not, and it is worth saying plainly where it went. One card still read We currently measure «» — the name your signup set on a site whose name was set correctly, and it was the first of eight priorities. That half lives in Geoa’s servers, not in this plugin, and it could not reach a row that was already sitting in the queue: the check runs over the cards Geoa decides to write that day, and the same change had taught Geoa to stay silent about this card when the name was missing — so the card is never looked at, and the old row stays. That is still true today, and this plugin no longer passes it on: it drops any priority whose text carries an empty pair of quotation marks before the screen is drawn, whatever the server still holds. Seven honest priorities are worth more than eight with a hole in one.
• G-048: an imported article carried its own title as the first heading in the body, so the published page showed the title twice. The heading is now removed when it really IS the title — never when it merely resembles it, and never further down the text.
• You choose who your imported articles are credited to, and where they are filed. Version 0.9.35 stopped filing them under «(no author)» by picking your site’s administrator, and offered a filter for anything else — an answer only someone editing PHP can give. An imported article has no human author and no natural place in your archive, so both are now yours to set once, under Settings: pick a writer, or leave it automatic; pick a category, or keep the default. A draft you move yourself is never re-filed by a later update.
• The per-post AI-readiness score can be found. It was there the whole time — a panel in the post editor, correctly scored — and there was no way for anyone to reach it: no line in the editor’s Options menu, no icon, and a name that did not say which product it belonged to. Measured on a real draft, the only way to open it was to type into the browser console, and that is not a way. The score now has its own icon in the editor header, a line called Geoa AI Visibility under Options → Panels, and it still sits inline in the Post tab where you write. On a draft that arrived from Geoa Content it opens itself once — that is the moment the score changes what you do next — and after you collapse it, it never forces itself open again. The score is also re-read when you save, so it describes the draft in front of you and not the one you opened an hour ago.

0.9.35

• Articles imported from Geoa Content have an author. Every draft the import created was filed under «(no author)» in your Posts list, and the cause runs deeper than a blank column: this plugin’s own Article schema puts author, dates and publisher on your single posts, and an author it cannot name is one it leaves out altogether. So the articles produced by the tool that exists to raise your E-E-A-T were published without the single strongest signal of it. New drafts are now filed under your site’s administrator, and drafts already imported without one are repaired once when you update. If you publish under a named writer rather than under the admin account, the geoa_import_author filter sets who that is.

0.9.34

• Articles you mark «ready» in Geoa Content now actually arrive as drafts. They never did on a site whose WordPress scheduler does not fire — and that is most quiet sites, which is exactly why version 0.9.32 added a second route that pulls your approved fixes on an ordinary visit instead of waiting for the scheduler. That second route, and the Sync now button next to it, both fetched the fixes feed and nothing else: the article import was attached to the hourly job itself, and neither of them ran the job. So on the sites that needed the rescue most, the rescue quietly switched the articles off. Measured on one site: an article marked ready for hours, two presses of Sync now, and an empty Posts screen with no error anywhere. Both routes now run the whole hourly job, so everything on it arrives together — articles included.
• Sync now tells you what it fetched. It used to print the same confirmation whether it had pulled two fixes and a new article, found nothing new, or failed to reach Geoa at all — three outcomes where only one of them means «try again later». It now names them: how many approved fixes are live, how many articles came in as drafts, and, when the connection failed, that nothing was changed and your site is still serving its last synced copy.
• Article drafts have a place on the Settings screen. The feature was promised in the plugin description and had no switch, no status and no error message anywhere in WordPress — so when it failed there was nothing to look at. Settings now shows how many articles are waiting in Geoa Content, how many have arrived here as drafts, when the last check ran, a button straight to the drafts, and a switch to turn the import off. If Geoa Content is holding articles and none of them have reached your site, the screen says so instead of staying silent.
• The AI Command Center stopped listing your own website as something to create. Its top priority was «Create your profile on Your own website» — while the citation list further down the same screen already ticked that row green and explained that Geoa is installed here and publishes your schema from this site. It is the one thing a WordPress plugin can be certain of, and one half of the screen was contradicting the other. The row is now dropped before the card sees it, on the same fact the citation list uses.
• The number over your citation sources is a count of that list now, and it agrees with it. The heading could read «0» above a list with a ticked row in it, and «13» above an eight-row list with one ticked row. Neither was a count: it was a coverage percentage printed as a bare figure, out of a total that changed depending on whether your site was connected to Geoa and was never shown to you. Version 0.9.33 said this was fixed. It was not, and the reason is worth stating plainly: the recomputed percentage skipped every source Geoa cannot verify by itself, and your own website is one of those — Geoa cannot check it from outside, while this plugin can be certain of it, because it is running on it. So the one row that was ticked was the one row the figure refused to count, and the heading read «0» again. It now reads «1 of 14 confirmed»: the ticks, out of the rows in front of you.
• The priorities are ranked again, and the number beside them means something. Eight entries carried the identical figure «impact 65» under a heading that promises a ranking, because that figure is a fixed value for a whole class of task rather than a measure of this one — and the plugin then sorted the list on it, discarding the order Geoa had actually worked out. The list now keeps Geoa’s own ranking, numbers the rows so the order is readable as an order, shows roughly how long each one takes, and prints the impact figure only where the rows genuinely differ on it. Each entry also says why that particular platform matters, instead of repeating one sentence eight times, and carries a link to the page where the work is done.
• No priority is printed with a blank where a name should be. One card read: We currently measure «» — the name your signup set. The name was set correctly; the card was the only place on the screen that could not read it, and it raised an alarm about a misconfigured measurement on a site that was configured correctly. Geoa now refuses to write a priority whose sentence it cannot finish, rather than printing the gap as an empty pair of quotation marks.
• Sentences on that card are no longer cut in the middle of a word. The text was trimmed at a fixed character count, which landed inside «Settings» and left the one instruction the card exists to give as «…pick the name yourself under Set». It now trims at the end of a word, and there is room for the whole sentence in the ordinary case.

0.9.33

• The AI Command Center no longer tells you that nothing needs your attention while the rest of the screen says otherwise. It was reading a different dataset from every other card: its list came from the fourteen technical geo-score dimensions, and only those scoring under 70, while your visibility score, share of voice and citation sources came from three other places. On a site where Geoa had just fixed the technical dimensions, that list was empty — and an empty list was printed as an all-clear. Measured on one site the difference was exactly nought against twenty-three open items. An all-clear is now a finding that needs evidence: it is printed only when the backend confirms every measurement is in its top band, it says which measurements it checked and with what numbers, and where there is no evidence at all it says the result is unverified rather than clean.
• The citation-source count agrees with the list under it. The header could read «0» over a list with a ticked row in it, because the number came from the backend’s copy of the list while the tick was added here — this plugin is the one place that knows for a fact your own site is running it. The number is now counted from the list you are actually looking at.
• «Mentioned in 4 of 10» under share of voice now says which questions it means. The citation check is its own set of questions, separate from the standard queries behind your AI Visibility Score, and both cards used to call them the same thing — so two different measurements read as one measurement reported twice.

0.9.32

• The dashboard no longer tells a connected site to connect. This plugin connects your site to Geoa by itself, by proving it controls your domain — there is no code to copy anywhere in that process. But the connection takes a few seconds to complete, and on the very first visit to Geoa → Dashboard after activating, it is often still finishing. That screen used to read the unfinished connection as no connection: it withheld your score, hid the AI Command Center and the writing suggestions, and asked you to fetch a pairing code and paste it under Settings — an errand that was neither necessary nor possible, since a connected Settings screen has no pairing field. Reloading the page showed everything, which is precisely why it was easy to miss. The dashboard now says «Connecting to Geoa…» while that is what is happening, finishes on its own without a reload, and brings the rest of your screen with it when it does. If the automatic connection genuinely fails, it says so, gives the reason, and puts the retry on screen.
• Approved fixes now actually arrive on the schedule this plugin promises. WordPress does not have a clock: it runs scheduled work only when someone visits your site, and it starts that work by asking your own site for a file over HTTP — a request some hosts’ firewalls block, because a server calling itself looks like a probe. On a quiet site, or behind such a firewall, the hourly pull quietly became a pull every few hours, or none at all. There is now a second route that needs neither: when an hour has passed, the next visit to your site pulls the feed directly, in the same process, after the page has already been sent. Opening a Geoa screen in wp-admin counts as a visit, so the screen you are reading is a current one.
• Fixed the case where the hourly pull was never scheduled at all. Activating the plugin queued a single catch-up sync, and the check that installs the repeating hourly job read that one-off as «already scheduled» — so on a site where WordPress’s scheduler never runs, the one-off sat waiting and the hourly job was never created. Those sites showed «Last synced: never» while being fully connected. The repeating job is now installed independently, and repaired on any visit if it has gone missing.
• Settings now tells you the truth about the sync instead of only the time. If the last pull is older than promised, the screen says so, explains that this is your host’s scheduler rather than a lost fix, confirms that everything already published stays live, and promotes the Sync now button. It also shows the one-line cron job to hand your host if you want the hour guaranteed on a site with no traffic.
• What you fill in under Geoa → Settings → Your business now actually reaches your published schema. The screen asks three things no company register can answer — the subjects you are an authority on, your public contact details, and whether the name customers know you by is the company itself or a product it operates — and promises to publish each one. On any site where an approved schema fix from your Geoa dashboard was in place, that approved node replaced the plugin’s own one wholesale, and all three answers were dropped on the way to the page: knowsAbout never appeared, the email and phone you declared never appeared, and the product-or-company answer changed nothing whichever way it was set. The approved node still wins on everything it carries — it is what you said yes to — but it can no longer delete what you declared here, on any of the three routes your schema can take out of this plugin (with Yoast, with Rank Math, and with no SEO plugin at all).
• Saving your business settings now says so, and says what it saved. WordPress prints nothing of its own on a plugin’s settings screen, so a save that stored everything and a save that stored nothing looked identical. There is now a confirmation after every save that reads the three answers back out of storage and states what each one publishes — including «not set», if that is the truth. And a save can no longer blank a field it did not carry: WordPress asks the plugin about every setting on the page whenever any of them is saved, and for a text field or a choice, «not submitted» used to be stored as «empty». Clearing a field still works the honest way, by saving it empty.

0.9.31

• Updating the plugin now finishes the work an update is meant to do. Every release carries an internal version stamp the plugin reads to tell that it has just been updated; in 0.9.30 that stamp was left reading 0.9.29, so on a site coming from 0.9.29 the plugin concluded nothing had changed and skipped the pass it makes after an update. Three things followed. Your score kept showing the figure the previous release’s rules produced, for up to half an hour after an update meant to change it. Your browser kept rendering the new version’s screens with the previous version’s stylesheet and script, so anything we changed on screen did not reach you. And a site that had installed the plugin but never finished connecting stayed on the pairing screen, because the pass that reconnects it is exactly the one that was skipped. All three work again, and this release picks up every site that was on 0.9.30.
• The measurements your site reports to Geoa now carry the version that is actually installed. Every 0.9.30 site identified itself as 0.9.29, which is what our own diagnostics were reading.

0.9.30

• The AI Command Center card now speaks the same language as the rest of this screen. Its list came from the same place your Geoa dashboard reads, so a Danish account saw Danish action titles under an English heading — and the line beneath each one was the first line of a Markdown document, which was usually just a heading marker. The card now receives the finding itself, written in this admin’s language.
• Monitored questions that still show a blank from our own template are no longer listed under Settings. New ones are no longer produced, but questions measured before that fix are still stored on your account, and this list is where you would have met …