Geoa – AI SEO & AEO on Autopilot -- WordPress 插件

开发者	addonnordic
更新时间	2026年9月16日 03:55
PHP版本:	8.0 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

0.9.50

Din FAQ-markup matcher nu den FAQ, dine læsere ser. Har en artikel en FAQ-sektion ("FAQ", "Ofte stillede spørgsmål", "Vanliga frågor" …), bliver præcis spørgsmålene i den sektion til FAQPage — intet andet. Uden en sådan sektion tæller kun overskrifter, der er spørgsmål med spørgsmålstegn. Før kom almindelige afsnitsoverskrifter, der begyndte med "What" eller "Hvad", med som spørgsmål, med hele afsnittet som svar; Google kræver, at FAQ-markup svarer til det synlige indhold. Målt på entitywatch.app 2026-09-15: 6 spørgsmål i markup, 4 i den synlige FAQ.
Artiklens udgiver peger nu altid på en virksomhed, der faktisk står på siden. Nyt til temaer: geoa_organization_id() giver det @id, Geoa's Organization har på den aktuelle side — Geoa's egen, den Yoast eller Rank Math udskriver og Geoa beriger, eller et godkendt schema-fix. Et tema, der overlader virksomheden til Geoa, skal pege sin publisher dertil i stedet for på en fast adresse; ellers står grafen med en reference til en virksomhed, der ikke findes.

0.9.49

Dit schema bruger nu det navn, dine kunder kender dig under — også når dit brand er et produkt, som et anderledes navngivet selskab driver. Dit brand står i name, selskabets registrerede navn i legalName, dine stavemåder i alternateName, og Brand-noden bliver stående. Det er præcis det, Google beder om: samme name som sitets eget navn. Tidligere kom selskabsnavnet i name i den situation, også når du havde godkendt et schema-fix med dit brand i dashboardet. Et ældre fix med selskabsnavnet får automatisk dit valgte navn.

0.9.48

Siderne i /llms.txt står nu som rigtige links. Standarden bag filen (llmstxt.org) kræver, at hver side skrives som et markdown-link — - [Titel](adresse): beskrivelse. Vi skrev adressen bar, - adresse: Titel — beskrivelse, og en AI-motor, der læser filen efter bogen, fandt derfor ingen links overhovedet i afsnittet med dine vigtigste sider. Det var filens ene opgave. Titler med [kantede parenteser] og adresser med (runde) bevarer nu linket i stedet for at bryde det.
/llms.txt — filen, der fortæller AI-motorer, hvad dit site handler om — henviser nu kun til et sitemap, der faktisk svarer. Bruger dit site Yoast, Rank Math, All in One SEO, SEOPress eller et andet SEO-plugin, slår det WordPress' eget sitemap fra og serverer sit eget i stedet; filen pegede alligevel på WordPress' adresse, og den svarer så "siden findes ikke". Nu findes sitets rigtige sitemap først — og kan der ikke findes noget, nævner filen ingen adresse frem for en død. Målt på fleromdomen.se 2026-09-09: /wp-sitemap.xml svarede 404, /sitemap.xml svarede 200, og llms.txt navngav 404'eren.

0.9.47

Rapporten om tømt sidecache er nu komplet. Sker der flere tømninger i samme kørsel — først den ene gang efter en opdatering, derefter den for de sider, hvor en rettelse blev ændret — nævnes de nu alle sammen med hver deres årsag. Før overskrev den sidste tømning den forrige, så dashboardet kun kendte den ene af dem, og det måtte gættes ud fra hvilken side der havde ændret sig, hvad der egentlig var sket.
Og Geoa holder ikke længere op med at efterprøve, om dine besøgende faktisk ser rettelsen. Pluginet fortalte hjem om den seneste tømning, hver eneste time — også timer efter den var sket — og efterprøvningen springes med vilje over lige efter en tømning, fordi cachen ikke er tom i samme sekund. Tilsammen betød det, at én tømning kunne udskyde kontrollen på ubestemt tid. Nu melder pluginet kun de tømninger, dashboardet ikke allerede har fået.

0.9.46

Når pluginet opdateres, tømmes sidecachen én gang for alle de sider, dine godkendte rettelser står på. 0.9.45 tømte kun cachen, når en rettelse blev tilføjet, ændret eller trukket tilbage — så et site, der allerede havde sine rettelser godkendt, viste den gamle titel til besøgende efter opdateringen, indtil cachen udløb af sig selv. Målt på entitywatch.app lige efter opdateringen til 0.9.45: pluginet så cachen, men havde ingen anledning til at tømme den.

0.9.45

En godkendt rettelse når nu også dine besøgende — ikke kun serveren. Sider, der ligger i sitets sidecache (LiteSpeed, WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, Cache Enabler, SiteGround, Cloudflare), blev ved med at vise den gamle titel eller det gamle indhold, indtil cachen udløb af sig selv — målt: en uge. Nu bedes cachen slippe præcis de sider, en rettelse har ændret, i samme øjeblik rettelsen anvendes eller trækkes tilbage. Geoa fortæller også dashboardet, om det skete, så "live" betyder live for dem, der besøger siden.
Den godkendte titel gælder nu også som og:title og twitter:title, når Rank Math, Yoast, All in One SEO eller SEOPress skriver sidens sociale titler. Før stod den nye titel i fanen og den gamle i det, Facebook, LinkedIn og AI-læsere ser — to titler på én side.
Kvitteringen på indstillingssiden nævner nu alle slags godkendte rettelser. Før talte den kun llms.txt, schema og meta, så en godkendt indholdsrettelse gav teksten "No approved fixes yet", selv om den lå i feedet og blev anvendt. Og en indholdsrettelse, der ikke blev skrevet, efterlader nu et spor: pluginet melder hjem, om siden ikke fandtes, om rettelsen ikke kunne udføres, eller om den ikke ændrede noget.

0.9.44

Rettelse til de interne links, fundet før nogen fik dem: linket lægges nu på ordet, præcis som det står på din side. Før kunne et link på et ord i begyndelsen af en sætning gøre det lille — "Hårdttræ holder i mange år" blev til "hårdttræ holder i mange år". Vi lægger et link på dit ord; vi retter ikke din tekst.
Og links virker nu også, når ordet på siden begynder med Å, Æ, Ø eller et andet særtegn med stort. Før sprang de over i tavshed.

0.9.43

Geoa kan nu skrive selve købsguiden ind på din kategori- eller serviceside — ikke bare foreslå den. Teksten, du har godkendt i Geoa, lander under produkterne og over footeren, dér hvor de sider, der ligger nr. 1 på Google, selv har deres guide. På en WooCommerce-kategori vises afsnittet af pluginet, så du fjerner det igen ved at afvise rettelsen i Geoa; på en almindelig side skrives det ind i sidens eget indhold, hvor du kan redigere det bagefter.
Produkttekster kan nu lægges direkte på varen. Godkender du en serie unikke produktbeskrivelser i Geoa, skrives beskrivelsen (og den korte beskrivelse, hvis der er skrevet en) på selve varen i WooCommerce, i stedet for at du skal kopiere hver enkelt ind i hånden. Som altid: intet skrives, før du har godkendt det, og WordPress' egen versionshistorik er fortrydelsesknappen.
Manglende alt-tekster på billeder kan nu udfyldes for dig. Geoa foreslår teksten ud fra billedets eget filnavn og sidens overskrift, og du godkender den. En alt-tekst, du selv har skrevet, bliver aldrig overskrevet — kun de tomme fyldes ud.
Sidens overskrift kan nu rettes til det, kunderne faktisk søger på — ikke kun sættes på en side, der manglede en. Hidtil kunne Geoa kun tilføje en overskrift til en side uden; en side med en forkert overskrift kunne kun rettes i hånden.
Interne links kan nu sættes ind midt i brødteksten i stedet for som en "læs også"-liste til sidst. Linket lægges på ord, der allerede står i teksten, ét pr. afsnit, og aldrig i et afsnit der allerede har et link.

0.9.42

Nyt (slået fra som standard): når en WooCommerce-ordre er gennemført, kan din butik selv sende én neutral mail, der beder køberen anmelde netop det køb — på Google eller Trustpilot. Geoa skriver ordlyden og nævner de varer, der blev købt; køberens navn og e-mail forlader aldrig dit site. Alle spørges, én mail pr. ordre, aldrig til adresser du har sat på fravalgslisten, og du kan se en lille log over, hvad der er sendt. Det er sådan, en anmeldelsesopfordring er lovlig uden samtykke: straks efter handlen, om netop den oplevelse, uden tilbud eller ros.

0.9.41

Artikler fra Geoa Content ankommer nu som rigtige blokke i WordPress' editor — afsnit, overskrifter, lister, tabeller, citater — i stedet for én klump, du kun kunne redigere alt eller intet i. Gennemgangen før du trykker Publish er hele pointen med rail'en, og indtil nu havde du ikke en flade at gennemgå i. Kladder, der allerede ligger i din editor, bliver lavet om til blokke ved næste tjek, uden at du skal gøre noget. EU AI Act-mærkningen følger med som før: den menneskelæsbare oplysning står i teksten, og den maskinlæsbare markering lægges om artiklen, når siden vises — den kan nu ikke længere slettes ved et uheld, mens du redigerer.
Artiklens titel bliver ikke længere gentaget som overskrift øverst i brødteksten. Temaet skriver allerede titlen som sidens ene store overskrift, så siden sagde det samme to gange lige efter hinanden. Det blev rettet i 0.9.38, men rettelsen virkede kun, når overskriften stod allerførst; siden er artiklerne begyndt at åbne med et kort svar på spørgsmålet, og så stod dubletten igen. Nu fjernes den, uanset hvad der står over den — og en overskrift længere nede, du selv har skrevet, bliver stående.
"Sync now" står nu også ved artiklerne. Knappen har hele tiden hentet artikler, men den lå under de godkendte rettelser længere nede på siden, så der ved artiklerne kun stod "næste automatiske tjek om ca. 11 minutter" og ingen måde at gøre det nu.

0.9.40

The one sentence /llms.txt gives an AI engine about each of your pages now says something. Every line read “Page title — Page titleand then the page’s own words”: the title spent twice, and the last word of your heading welded onto the first word of the paragraph under it — “your businessReviews decide who customers choose”. Two things caused it. Themes that do not print a post title make page builders write the heading into the body copy instead, so a page with no SEO description and no excerpt described itself with text that began with its own title; and taking the markup out closed the gap where the heading ended, inventing compound words that exist in no language and therefore match nothing anyone would ever ask. The description is now the page’s own summary — your SEO plugin’s description, your excerpt, or the opening of the page, with the title removed where it opened its own summary. Word boundaries are kept, and where a description is too long to print in full it is now cut between two words instead of inside one. Descriptions written before this update are rebuilt the first time the file is asked for.

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 them.
Counts and the words after them now agree, wherever a number can be one. "1 AI-motorer", "1 billede(r)", "1 navn(e)" — a parenthesis is not a plural, it is a way of not choosing. Danish, Norwegian, Swedish and English all now read correctly at one and at many, in the weekly and monthly emails, the fix backlog and the published measurement claims.

0.9.29

Geoa now measures the name your own site goes by, instead of your web address. When your account had never been asked for a name, Geoa fell back to the domain — so a site trading as WonMetrics was measured as "wonmetrics.com", and that is what went into your schema as the name AI should know you by. WordPress knows something your Geoa account cannot see: the name you typed into your own site. The plugin now offers that name once, marked as a suggestion — Geoa still asks you to confirm it, and it will never overwrite a name you have chosen yourself.

0.9.28

The AI Command Center no longer tells you to run a scan there is no button for. That card printed "run a Geoa scan to generate your action list" while the plugin had no scan control anywhere — an instruction you could not follow. There is now a real one: Analyse my site now, on the card itself.
The same card printed that one line for four different situations. It now tells them apart: Geoa could not be reached (a connection problem, and explicitly not an all-clear), your account was not found, an analysis is running right now (with what it is doing, and the card follows it to the end on its own), your scans for the period are used up, or your site was analysed and genuinely has nothing worth listing — with the date it was checked.
A site Geoa already knew now gets analysed when you install the plugin. Reinstalling, or connecting a site that had been scanned from geoa.app before, reconnected you to the same account without starting a new analysis — so the action list stayed empty with nothing on screen able to change it.
The score now says which AI engines it was measured on. The circle read "Overall across AI answer engines", the line under it said one engine, and a card further down the same page named a second one. All three were reading the same measurements through different time windows: the recurring scan only asks ChatGPT, so within two days every other engine dropped out of the score while still being named in your writing suggestions. Every card now shares one definition of "the current measurement" — each engine counts from its own most recent scan — and the heading names them: Measured on ChatGPT, or Measured on ChatGPT and Gemini, instead of implying a breadth the measurement did not have. Each bar also says when that engine last answered, so engines scanned on different days do not look like one simultaneous check.
Your contact details no longer disappear when Geoa publishes your schema. Geoa's business node is built from the national register, and the registers carry no public email — so on a site whose theme stood aside for Geoa (as it should), the site ended up with less contact information than before Geoa arrived. Two things change: you can now enter a public email and phone number under Geoa → Settings, published alongside the registry data; and a theme or plugin that yields to Geoa's node can hand over the fields it was carrying, through the new geoa_organization_node filter. Taking over must never leave the page knowing less.
knowsAbout is now what you are an expert in, not your industry code. Geoa published the registry's industry text — in the register's own language, in an otherwise English schema — as the subjects your business understands. For a company-verification tool that read "Computer programming". There is a new Expert in field for the subjects customers actually come to you for; left blank, nothing is published, because a wrong subject is worse than none.
The citation list no longer asks you to create the website you are reading it on. "Your own website" is the highest-value source on the list — about half the AI citations we measure land on the business's own site — but it arrived as an unmet task with a "create" link, inside a plugin running on that very site. It is now shown as met, pointing at your site, with a line about what Geoa does to it.
Activating the plugin now leads somewhere. There was no notice, no redirect and no link on the plugins page, so the two-minute setup was there only for people who thought to look in the sidebar. The plugins row now has Get started and Settings, and a one-time notice points at setup after activation.
If your country's registry is not one of the four Geoa looks up, you are no longer stuck on step 1. The first screen now says which four registries are covered and what works without one, and offers Continue without registry verification so you can use the rest of the plugin. Step 1 stays waiting under Settings for when your registry is added.
The dashboard now speaks one language at a time. Cards had English headings with Danish text inside them — “AI Visibility Score” over “AI-synlighed: 40% på tværs af 1 AI-motorer”, “Citation sources” over Danish explanations, “What to write next” over Danish reasoning. The rule is now simple and applied everywhere: the interface is English, and the only thing kept in your own language is the material itself — the questions people actually ask an AI — shown in quotation marks, word for word, because that is the form you need it in to answer it.
Suggested questions no longer show the blanks in our own template. “Which local businesses in Denmark offer service?” was a template we had failed to fill in with your industry — and “service” was the placeholder, not a word about you. Where your line of work is known, it is used; where it is not, that question is left out rather than shown with a gap in it. Questions already measured with the gap in them are no longer suggested as articles to write.
A suggested question is no longer cut off mid-word. Long questions were trimmed at a fixed length, so “… name specific company names.” arrived as “… name specific company name” — which read as the product not knowing how to spell rather than as a line that ran out of room. Trimming now happens between words and is marked.

0.9.27

The name shown here is now the name Geoa actually measures. When your Geoa account had not been asked for a name yet, this screen quietly showed your registered company name instead — under a sentence promising that the plugin and your dashboard can never disagree about what is measured. They could, and on a site trading under a product brand they did: the register answers what your company is called, which is by construction the other name.
Left to fall back, Geoa now publishes your site's own name before your registered one. Your registered name is still always published as legalName, where it is true.
When nobody has chosen the measured name yet, the screen says so plainly instead of presenting a guess as a settled fact — and tells you where to choose it.

0.9.26

Citation sources now matches your kind of business. A tradesman, a clinic or a webshop was shown the same developer-facing checklist as a software company — Product Hunt, "Show HN", GitHub, software and startup directories — under the heading "for your business". The list now follows your registered industry. One entry even asked you to list Geoa on a comparison site instead of your own business; that text was written about us, not about you, and it is gone.
When Geoa does not know your industry yet, the card says so instead of calling the list tailored. You get the general list — the profiles that matter for any business — with a line on how to narrow it. This wording reached you in 0.9.25 without a changelog entry of its own; the matching behind it went live on the Geoa side on 30 August 2026.
The name AI should know you as is no longer filled in for you. Setup used to pre-fill it with your registered name — the very name the field says is kept separately as legalName — so simply continuing measured you on a name your customers never search for, for a whole period, without anything saying so. You now pick from named candidates (what your site calls itself, your registered name without the company form, your registered name as the register has it) or type your own, and Geoa will not publish until you have picked one.
Your registered name is now always published as legalName, including when it is identical to the name you chose. The field promised this; before, it only happened when the two names differed.
A website that is a product run by a differently named company can now say so. If the name you choose is not your registered name, Geoa asks one question — is this another name for the company, or a product it operates — and publishes accordingly: your name as the organization's own, or the registered company as the organization with your name as its brand. Geoa measures the name you chose in both cases.

0.9.25

Fixed: "Look up in registry" in Step 1 could do nothing at all — no result, no error, no sign it had been pressed. If the country and registration number reached the fields in a way the screen did not register (browser autofill, a password manager, some browser extensions), the button was switched off while the form looked filled in. Step 2 waits for Step 1, so the whole first run stopped there. The lookup now reads what is actually in the fields, and the button is never switched off silently.
Nothing on this screen ends in silence any more: an empty field gets a specific message, a lookup in progress shows a spinner and says what it is doing, and a failure tells you what went wrong instead of nothing at all.
Your half-finished first run is now saved. Type a country and a number, get interrupted, come back — the fields are still filled in. Unfinished entries are kept separately and never reach your published schema.
"This is my business — publish schema" now explains that Step 1 has to run first, instead of sitting there inactive.

0.9.24

Your first finding now follows your site's own language. A site running in English was shown the finding in Danish, because the text followed the country your business is registered in rather than the language you run WordPress in. Danish, Norwegian, Swedish and English are written out; any other locale gets English.

0.9.23

Your first finding is now written for you to read: one named gap, with the schema type that actually fits your kind of business — and Geoa publishes the fix from your verified details once you approve it. Previously this card could show raw technical output and a code template to hand to a developer, which is not how Geoa works.
The dashboard now reads the real connection state. A freshly installed site connects itself (it proves it controls the domain), but the first-run screen still asked you to "connect your site under Settings" while Settings already said connected — a step you were asked to repeat after it was done.
Renaming the name Geoa measures no longer hits the plan ceiling. Changing your one name is not the same as tracking a second brand, so it is now a rename, not an add. Previously a rename could be refused while the site went on publishing the new name in its schema — Geoa measured one entity, your pages declared another, and nothing said so. If a name still fails to sync, the plugin now says which name Geoa is actually measuring.
An AI-visibility score is a measurement of a name, so after a rename the previous score is withheld instead of being shown under the new name. The new measurement arrives with the next scan.
The score card now says what it measured, on which name, and that its queries are Geoa's own standard set — separate from the monitored questions you add under Settings, which is why that counter can read 0 while the score reports queries. The score explanation is also written in English now, instead of passing through the Geoa dashboard's Danish wording.
Clearer wording on plugin deletion: your Geoa account is identified by your domain and is not deleted with the plugin, so a reinstall reconnects to the same account automatically with a new key.

0.9.22

Persist: when you cancel, everything Geoa manages is written permanently into your own site — llms.txt as a real file, approved titles/descriptions into your SEO plugin's own fields — and the plugin stops syncing. Your site keeps what it has. Nothing is ever held hostage.

0.9.21

New public helper for theme developers: geoa_approved_meta_description() returns the Geoa-approved meta description for the current URL ('' when none), so themes that print their own description tag can yield to it — one page, one description tag.

0.9.20

Rank Math coexistence verified live (1.0.277.1) and hardened: a fresh Rank Math install renders no schema or description output before its setup wizard has run, which silently swallowed Geoa's filter-based delivery. Both the registry-verified Organization and approved meta descriptions now have a late failsafe: delivered through Rank Math's (or Yoast's) own filters when they render, emitted directly by Geoa when they don't — never duplicated, never lost.

0.9.19

Yoast SEO / Rank Math coexistence hardened (verified live against Yoast 28.3): Geoa's registry-verified Organization now always lands in the SEO plugin's own schema graph — enriching their Organization node when it exists, and adding one when it doesn't (previously, a fresh Yoast install could make the Organization node disappear entirely). Approved dashboard fixes take precedence.
Approved meta descriptions are now routed through the active SEO plugin's own description filter (Yoast, Rank Math, All in One SEO, SEOPress) instead of printing a second meta description tag next to theirs — one page, one description.
All in One SEO and SEOPress are now detected as SEO plugins, so Article schema, canonical/Open Graph basics and description handling defer to them correctly.

0.9.18

The site-environment facts in the hourly status ping now also cover: installed-but-inactive plugins (cleanup advice), whether WordPress core's own sitemap is enabled, a small whitelist of Yoast/Rank Math settings (sitemap toggle and organization/knowledge-graph name — needed to explain sitemap ownership and schema overlap), and taxonomy hygiene counts (categories, empty categories, tags, published posts left in the default category). Counts and names only — never option blobs, term contents or personal data.

0.9.17

The hourly status ping now includes a compact inventory of the site's own published posts (id, title, URL, edit link, last modified) so your Geoa employee can suggest refreshing outdated posts and answer questions about your published content.
The ping also reports the site environment as raw facts: active theme and plugins (name/version), the "discourage search engines" flag and the permalink structure — so the employee can warn about SEO conflicts and misconfigurations.
No new data classes leave the site beyond the above; see the Privacy section for the full list of what is shared with the Geoa service.

0.9.16

Post-fix render verification with automatic rollback: after a content patch is applied, Geoa fetches the page as a visitor sees it and verifies the result (exactly one H1 after inserting one, heading count never increases after demoting, inserted text actually visible on the rendered page). On positive evidence of harm — for example a theme that also outputs an H1, or a page builder that ignores post content — the change is rolled back automatically and reported to your dashboard with the reason. Fetch failures never trigger a rollback: only proven harm does.

0.9.15

New content-patch operation: FAQ section — 2-4 customer questions with direct answers, generated strictly from the page's own content and approved by you first, appended as a visible section (H2 + question headings). The plugin's existing FAQ module then picks the questions up into FAQPage schema automatically: content first, schema follows. Same guarantees as before: nothing changes without your approval, every change is a normal WordPress revision (one-click undo), each patch applies exactly once, and unknown operations are ignored.

0.9.14

Two new content-patch operations on the remediation rail: an answer block (a customer-question H2 with a direct answer, generated strictly from the page's own content and approved by you first — appended as its own section) and a refreshed intro (the first paragraph replaced with an answer-first opening for pages that have gone stale). Same guarantees as 0.9.13: nothing changes without your approval, every change is a normal WordPress revision (one-click undo), each patch applies exactly once, and unknown operations are ignored.

0.9.13

Content patches (the remediation rail): approved content fixes from the Geoa dashboard are now applied to the post itself — first two operations: insert a missing H1 (generated from the page's own content, approved by you first) and demote extra H1 headings to H2 (the first one is kept). Every change is stored as a normal WordPress revision, so undo is one click in wp-admin. Nothing is ever changed without your explicit approval, each patch is applied exactly once, and unknown future operations are ignored.

0.9.12

Head basics: on sites without a dedicated SEO plugin, Geoa now emits rel=canonical (only when WordPress core does not), Open Graph/Twitter tags (og:title reflects an approved Geoa meta fix automatically) and BreadcrumbList JSON-LD built from the page's own ancestry. The whole module stands down when Yoast, Rank Math or SEOPress is active — double tags are worse than missing ones.

0.9.11

Fix: approved schema fixes holding several JSON-LD script blocks (Organization + SoftwareApplication) rendered nothing — each script body is now decoded on its own, and every valid node is emitted.
Fix: the plugin only takes schema ownership from its own local, registry-verified output when the approved fix actually decodes — an unparseable feed no longer removes the site's Organization markup.

0.9.10

Fix: the "Sync now" button for approved fixes submitted the whole settings form to options.php instead of running the sync (invalid nested form). It is now a nonce-protected link and works.

0.9.9

Schema aggregation: when Yoast or Rank Math owns your page's schema graph, approved Organization schema from your Geoa dashboard is no longer emitted as a second node — Geoa's registry-verified fields are already merged into the SEO plugin's own Organization node, so your page keeps exactly one. Approved non-Organization nodes (FAQ, …) still apply. The Geoa scan now also flags duplicate Organization nodes from other sources as a fix.
Docs: the Geoa MCP connector (use Geoa from Claude and other AI agents) is documented in the FAQ below and on geoa.app/free-geo-tools.

0.9.8

Fix: the hourly status ping now actually includes the "images missing alt text" count, so the Geoa dashboard can raise the alt-text card. The 0.9.7 release announced this but the field never made it into the ping.

0.9.7

Bulk alt text: a new "Alt text" screen under the Geoa menu finds images without alt text and lets Geoa write suggestions FROM the actual images, in your account language (paid plans). Every suggestion is shown for review — editable, ticked per image — and nothing is saved until you click Apply. Applied counts appear in your Geoa dashboard timeline.
Broken links in your articles: the plugin now reports each article's links to Geoa on the hourly sync (rotating through your posts and pages). Geoa checks the targets server-side — only real 404/410 answers count as broken — and raises "broken link in article X" fixes in your dashboard. Links you remove disappear from the inventory on the next sync.

0.9.6

AI bot control, both directions: a new toggle under "Approved fixes" lets you block AI TRAINING bots (GPTBot, ClaudeBot, Google-Extended, CCBot, Bytespider, …) in WordPress' robots.txt. The bots that fetch and cite your pages in AI answers are different crawlers and always stay allowed — blocking training bots does not cost you AI visibility. The rule list is built and versioned by Geoa (never hardcoded in the plugin), and switching the toggle off removes the rules again within minutes. Off by default; if your site has a physical robots.txt file the settings screen says so honestly instead of pretending.

0.9.5

Approved redirects: fixes of the new type "redirect" from your Geoa dashboard are applied as 301s on the exact dead path you approved. Targets are validated against your own site before redirecting, only front-end GET/HEAD requests are touched, and rejecting the fix in the dashboard removes the rule again within the hour — nothing is written to your site.
404 log: real front-end 404 hits are counted locally (path only — no IP, no user-agent, query strings stripped, bot probes filtered) and reported to Geoa on the hourly sync, so the fix engine can propose "404 → nearest page" redirects for you to approve.

0.9.4

Approved internal links: fixes of the new type "internal link" from your Geoa dashboard are now applied on the page they belong to — the plugin links the approved anchor text to the target page (or adds a small "read also" line if the text does not occur). Nothing is written to your posts: it is a render-time filter, and rejecting the fix in the dashboard removes the link again within the hour. Links are only ever inserted after you approve them.
Status reporting fixed: the hourly status ping now reports the actual fix IDs from the feed, so the Geoa dashboard correctly shows your applied fixes as "live". Before this, WordPress-applied fixes never got their live badge.
AI-crawler activity in your dashboard: connected sites now report detected AI-crawler visits (GPTBot, ClaudeBot, PerplexityBot, …) to the Geoa connect service — batched, asynchronous and fail-open, so it can never slow your site. Powers the new "AI crawlers on your site" card. No IP addresses, no visitor data; see "External services".

0.9.3

Article import: the share image (og:image card) Geoa renders for each article is set as the draft's featured image, so shared links get a real preview card. Only when the draft has no featured image yet; your own image always wins.

0.9.2

Connect your Geoa account: sites that connected automatically now show a one-click card (welcome screen + settings) linking the site to YOUR Geoa account — so your subscription and settings follow you, not the site's admin email. The card disappears by itself once the account is linked.
The plugin now publishes the name your Geoa account actually measures: once connected, schema.org name/alternateName and a new "Known as" line in llms.txt follow the tracked name from your dashboard (refreshed hourly) — the published name and the measured name can no longer drift apart.
Faster, more precise business-type detection: the automatic connection now sends your locally saved registration number along, so Geoa derives your business type from the official registry instead of guessing from the domain.
Profile URLs follow the same one-owner rule as your name and questions: read-only here while connected, edited in Geoa — so a link you delete in the dashboard is actually deleted everywhere.

0.9.1

The "Edit in Geoa" links now land directly on your dashboard's Settings page — the screen where monitored questions and your brand name + spellings are actually edited — instead of the dashboard front page.

0.9.0

One owner per setting. What Geoa MEASURES (your monitored questions, and the name + spellings AI should know you by) is now owned by your Geoa dashboard once the site is connected: the plugin shows those values read-only, with your usage against the plan limit and an "Edit in Geoa" link. Editing them in two places at once is how the plugin and the dashboard could disagree about what was being measured — that can no longer happen.
Not connected yet? Everything still works standalone: the name and spellings stay editable in the plugin, and the moment the site connects they are pushed to your Geoa account once, so nothing you set up beforehand is lost.
What your SITE emits stays yours to control right here, exactly as before: FAQ/Article/Product schema, llms.txt, the badge, return window, registry verification and schema publishing.
Fixed: connecting to a (different) Geoa account could briefly show the previous account's monitored questions from cache.

0.8.2

Disconnect now sticks. Before, pressing Disconnect was silently overruled: the settings page attempted an automatic reconnection in the very same page load, so the site re-paired itself one second later. A deliberate disconnect now pauses every automatic-connection path until you reconnect yourself — with a pairing code, or the new one-click "Reconnect automatically" button.

0.8.1

Zero-field connection now also works for existing installs: updating the plugin (not just activating it) triggers the automatic connection attempt on unpaired sites, and opening any Geoa screen retries it directly — no dependency on WP-Cron.
The domain-proof route is never page-cached anymore (no-store headers): LiteSpeed-style page caches could serve a stale token to the verifying backend and reject a correct connection attempt.

0.8.0

Zero-field connection: the plugin now connects itself to Geoa on activation. It proves control of your site with a short-lived token served from your own REST API — no account signup, no pairing code, nothing to type. The pairing-code flow remains as a manual fallback.
Your first finding, in seconds: right after connecting, the welcome screen shows one real, named finding about your site (live structured-data probe plus your official business-registry identity) — honestly reported, never invented.

0.7.1

Deleting the plugin no longer erases your setup. Your business identity, chosen name, profile URLs and feature settings now survive a delete + reinstall — until now they were wiped, which silently un-published your verified schema and dropped the site back into onboarding. Connection keys and caches are still always removed; if you want a truly clean removal, tick the new "Remove all Geoa data when the plugin is deleted" option under Geoa → Settings first.

0.7.0

One rulebook instead of three. Connected sites now get their scores and task lists straight from Geoa, instead of the plugin computing its own local versions that could disagree with your dashboard.
In-editor scoring now uses Geoa's GEO content standard — the same 23-signal checklist Geoa Content scores its own articles with — with a concrete hint under every signal you miss. The panel says whose verdict you are looking at; unconnected sites keep the local estimate, labelled as such.
Citation sources are now Geoa's tier-ranked list (Wikidata, Crunchbase, Google Business Profile, Bing Webmaster Tools and 15+ more), each with a why, a create-link and a time estimate. Wikidata replaces Wikipedia in the built-in list — a small business can actually get a Wikidata item, and it is what anchors your entity for AI.
Profile URLs you enter in WordPress are now saved to your Geoa account, so they appear as sameAs in every schema Geoa publishes — including dashboard-approved fixes. Until now those links lived only in WordPress and vanished from the page the moment an approved fix took over its schema.
New "What to write next" card: questions AI already answers where your business is not mentioned — straight from your Geoa measurement, each one an article waiting to be written.
A partially met trust signal now looks different from a fully met one (half-filled dot) — the E-E-A-T list could previously read as complete when it wasn't.

0.6.0

You now choose what AI should know you as. The registry says what your company is called — but a shop is known by its brand and a SaaS by its product, and that is the name customers ask for. Setup suggests the registered name and lets you replace it; it becomes schema.org name, while the registered name stays on as legalName, so nothing verified is lost.
New "Other spellings" field. AI writes a name the way it likes — "Addon Nordic" for AddonNordic — and a mention it cannot connect to you is a mention you get no credit for. Your variants are published as alternateName.
The name you pick is sent to your Geoa dashboard, so the schema on your site and the AI visibility Geoa measures are finally about the same thing. Sites without a Geoa account keep working exactly as before.
Corrected the engine list: Geoa measures ChatGPT, Gemini, Perplexity and Claude. Copilot was listed but has never been measured.

0.5.1

The Geoa mark now appears in the WordPress admin menu instead of a generic icon, and the plugin's listing artwork matches the rest of Geoa.
Corrected the company name to AddonNordic, and the screenshot captions so each one describes the screen it actually shows.

0.5.0

AI-generated articles imported from Geoa Content now carry their AI marking (EU AI Act art. 50(2)) as the last paragraph of the draft, where your readers can see it — until now the marking travelled with the article but was never shown. The wording comes from Geoa, in the article's own language.
Tables in your articles now arrive as real tables. Until now a table came through as a row of raw pipe characters in a single paragraph — and a table is one of the strongest signals that gets your page quoted by AI answers, so it is worth having intact. Quotes and code examples now come through properly too.
Drafts that are still unpublished are refreshed once so the marking is added and any broken table is rebuilt. Posts you have already published are never touched, as always.
Drafts you have started editing yourself are no longer overwritten when a newer version arrives from Geoa. Your work is yours; only untouched drafts are refreshed. (The one-time update above still reaches every existing draft, since the plugin has no record of earlier edits — after that, your edits are always respected.)
New: a "Your Geoa plan" panel in Geoa → Settings shows the plan this site is on, how many of your monitored AI questions you have used, and what each plan includes.
Nothing is gated: every feature that worked before works exactly the same on every plan. The panel only shows you where you stand.
If your plan cannot be loaded, the plugin says so rather than guessing — it never displays a plan it has not confirmed.
"Refresh plan" re-reads your plan immediately, so an upgrade shows up without waiting for the hourly cache.
New: manage the questions Geoa monitors you for, directly in WordPress — see the current set, add one, paste a whole list (one per line), or remove one.
If part of a pasted list doesn't fit your plan, the plugin says exactly how many were added and how many didn't, and keeps your text so nothing has to be retyped.
New: the Geoa badge — show it on your site and Geoa re-scans you every month for free, with score history, instead of the free plan's single one-off scan. Add it with a block, a widget or the [geoa_badge] shortcode.
The badge is off until you switch it on, and your public pages never call Geoa to render it.

0.4.0

New: articles you mark "ready" in Geoa Content (content.geoa.app) are now imported automatically as draft posts — reviewed and published by you in WordPress, never auto-published.
Drafts are refreshed if the studio version changes before you publish; posts you have published are never touched.
When a Geoa draft goes live, the plugin reports the permalink back so Geoa can measure the article's actual effect (Google clicks and AI visits) in the Effekt view.
Article import can be disabled with the geoa_articles_enabled option.

0.3.3

The connected status is now verified against the Geoa backend (cached hourly) instead of only checking that a key is stored locally.
If your site's key is revoked or deactivated on the Geoa side, the plugin now shows a clear reconnect warning in wp-admin (with a one-step re-pair form) instead of a green "connected" checkmark.
Approved fixes already published stay live from the last synced copy while the connection is broken — nothing is silently removed — and the sync status says so explicitly.

0.3.2

Added a single, dismissible in-admin prompt that asks engaged users (after real use) to leave a review. No incentive is offered and no functionality is gated behind it.

0.3.1

Renamed to "Geoa – AI SEO & AEO on Autopilot" to describe more clearly what the plugin does. No functional changes.

0.3.0

Approved fixes: fixes you approve in your Geoa dashboard (llms.txt, structured data, meta) are now pulled hourly and published on your site, with an always-visible status and a "Sync now" button under Geoa → Settings. Requires a connected account and is off unless enabled.
An approved fix takes precedence over the plugin's own local output (no duplicate llms.txt or schema).

0.2.0

WooCommerce: Product Offers are now linked to your registry-verified seller (name + tax ID) when your business is verified.
WooCommerce: variable products emit a correct price range (AggregateOffer with low/high price and offer count) instead of a single minimum price.
WooCommerce: Product schema now merges into Yoast or Rank Math's graph (adding the EU return policy and verified seller they lack) instead of staying silent, so its value is never lost on stores that already run an SEO plugin.
WooCommerce: added itemCondition and, for active sales, priceValidUntil to Offers.
WooCommerce: a per-product AI-readiness scorecard in the product editor (works in both the classic and block product editor).

0.1.0

Initial release: registry-verified Organization schema (DK/NO/SE/FI) with sameAs; FAQ, Article and WooCommerce Product schema; optional llms.txt; in-editor AEO readiness; E-E-A-T and citation-coverage scorecards; AI crawler log; per-site pairing with AI Visibility Score, Share of Voice and AI Command Center.

Geoa – AI SEO & AEO on Autopilot

标签

下载

详情介绍:

安装:

屏幕截图:

常见问题:

更新日志: