Geoa – AI SEO & AEO on Autopilot

Get found when your customers ask AI. On autopilot.

Your customers increasingly ask ChatGPT, Google’s AI Overviews, Perplexity and Claude instead of searching. Geoa makes your WordPress site something those engines can read, trust and verify — then does the work for you: it fixes your site, you approve, and the before/after proof comes with every fix. Built for the tradesman, the accountant and the clinic with no marketing department.

Three steps:

1. Connect your site — pair the plugin with your Geoa account in about a minute.
2. Geoa makes you AI-ready — automatically. It builds the registry-verified schema, llms.txt and structured data answer engines look for, and (with your one-click approval) publishes it to your site and keeps it in sync. No copy-pasting code.
3. Watch it work. A per-engine AI Visibility Score, Share of Voice and a live “is it published?” status show your progress — and every published fix gets a public before/after proof page.

Geoa is built for the European market: analysis runs on an EU-hosted, GDPR-safe backend, and everything here — AI-visibility scoring, approved on-page fixes, llms.txt, E-E-A-T checks and AI-crawler tracking — works wherever your business is. On top of that, and uniquely, Geoa publishes registry-verified business schema looked up live in four official national registries: Danish CVR, Norwegian Brønnøysund, Swedish Bolagsverket/Allabolag and Finnish PRH. Outside those four you use the rest of the plugin and skip that one step. Output is generated in your own language.

What it does

Structured data for AI

• Registry-verified Organization schema — enter your registration number; Geoa fetches verified legal name, VAT status (VIES), address, founding date and industry, and publishes valid JSON-LD. Contact data is hidden automatically when a business has marketing protection (GDPR).
• Entity verification (sameAs) — link your Trustpilot, LinkedIn and other profiles, plus the official registry page, so engines can corroborate your business. Nordic directories included (Krak, Finn.no, Hitta.se, Ratsit, Finder.fi and more).
• FAQ schema in your language — turns the questions and answers already in your posts into FAQPage markup for AI extraction.
• Article schema — author, dates and publisher for single posts.
• WooCommerce Product schema — price, availability, brand, GTIN, ratings and an EU return policy (14-day right of withdrawal) so AI shopping agents can cite your products. Variable products emit a proper price range, and when your business is verified the Offer is linked to a registry-verified seller — a trust signal generic Product schema can’t express. A per-product AI-readiness score sits in the product editor.
• Optional llms.txt — a curated, opt-in file for AI crawlers.

Analysis

• In-editor AEO readiness — a per-post score right in the block editor. Connected sites are scored against Geoa’s 23-signal GEO content standard (the same checklist Geoa Content uses), with a concrete hint for every missed signal; unconnected sites get a local estimate, labelled as such.
• E-E-A-T trust signals — identity, contact, about, privacy and author signals.
• Citation coverage — which third-party sources you have and which are missing. Connected sites get Geoa’s tier-ranked source list (Wikidata, Crunchbase, Google Business Profile and more) with create-links and time estimates, and the profile URLs you enter sync to your Geoa account as sameAs.
• AI crawler activity — see when GPTBot, ClaudeBot, PerplexityBot and others fetch your pages.

AI visibility & automatic fixes (connect a Geoa account)

• AI Visibility Score per engine, Share of Voice, and an AI Command Center of prioritised actions.
• Approved fixes, published for you — approve a fix in your Geoa dashboard (an llms.txt, a structured-data block, a meta title or description) and Geoa publishes it on your site and keeps it in sync — pulled hourly, and pulled again on the next visit whenever an hour has passed without one, so a quiet site does not drift out of date. An approved fix always takes precedence over the plugin’s own output, so you never get a duplicate — and you can turn it off at any time.
• Articles from Geoa Content, delivered as drafts — articles you mark “ready” in Geoa Content (content.geoa.app) appear as draft posts in WordPress, prepared with your business knowledge, an FAQ section and SEO metadata. You review and press Publish yourself — nothing goes live automatically — and once live, Geoa measures the article’s actual effect.

Geoa never emits duplicate structured data: when Yoast or Rank Math already provide a schema type, Geoa augments their graph instead of adding a second node.

External services

This plugin is a client for the Geoa service (https://geoa.app), operated by AddonNordic ApS. It sends requests to the Geoa API at https://api.geoa.app to verify your business against official national registries and to run AI-visibility analysis, and (only after you connect a Geoa account) to the Geoa connect service at https://connect.geoa.app to report AI-crawler activity on your site. It uses no other external service.

What data is sent, and when:

• Registry verification — when you enter your country and registration number in Geoa → Settings (or open that screen with them saved), that registration number is sent so the service can verify your business and return your official company data (legal name, VAT status, address, industry, founding date).
• Structured-data and analysis features — when you use them, the URL and the public content of the page(s) you choose to analyse are sent.
• AI-visibility scoring — only after you connect a Geoa account: your per-site pairing key (obtained from the Geoa dashboard) is sent as an authentication header so the service knows which account to read. The free tier never triggers a paid backend call.
• Approved fixes — only after you connect a Geoa account and enable “Apply approved fixes”: once an hour the plugin fetches the fixes you approved in your Geoa dashboard (llms.txt, structured data, meta) and reports back which are live. Only your pairing key is sent; you can turn this off at any time.
• Article import — only after you connect a Geoa account: once an hour the plugin fetches articles you marked “ready” in Geoa Content and creates them as draft posts for your review. When an article comes with a share image (a PNG card with the article’s title and your business name, served from https://geoa.app), the plugin downloads it once into your media library and sets it as the draft’s featured image, unless the draft already has one. It reports back which drafts were created and, when you publish one, its permalink — so Geoa can measure the article’s effect. Only your pairing key, post IDs and permalinks are sent; drafts are never published automatically, and you can turn this off at any time.
• Plan and usage — only after you connect a Geoa account, and only inside wp-admin: when you open Geoa → Settings the plugin reads your own plan, limits and monitored-question count so it can show them. Only your pairing key is sent; the result is cached, and no request is made from your site’s public pages.
• Monitored questions — only after you connect a Geoa account, and only inside wp-admin: when you open Geoa → Settings the plugin reads your monitored questions from your Geoa account so it can show them. Only your pairing key is sent; the questions themselves are edited in your Geoa dashboard, not in the plugin.
• Chosen name — only after you connect a Geoa account, and only when you set the name your business should be known as (setup or Geoa → Settings): that name and its spelling variants are sent so the schema on your site and the AI measurement in your dashboard describe the same entity.
• Profile URLs — only after you connect a Geoa account, and only when you save a profile URL (Trustpilot, LinkedIn, …) in Geoa → Settings: that URL is sent so it can appear as sameAs in every schema Geoa publishes for you.
• In-editor scoring — only after you connect a Geoa account, and only when you open a post in the block editor: the post’s title and content are sent so Geoa can score the draft against its GEO content standard. The result is cached until the content changes; nothing is stored server-side.
• Content opportunities and citation sources — only after you connect a Geoa account, and only inside wp-admin: when you open the Geoa dashboard the plugin reads your opportunity list and source checklist. Only your pairing key is sent; results are cached.
• Alt-text suggestions — only after you connect a Geoa account, and only when you click “Write suggestions” on the Alt text screen: the public URLs, filenames and parent-post titles of up to 10 images missing alt text are sent to https://api.geoa.app, where the alt texts are written from the images. The count of images missing alt text is included in the hourly status ping. Nothing is written back until you approve it on the review screen.
• Article links — only after you connect a Geoa account: on the hourly sync the plugin sends the outbound and internal link URLs (with anchor text and the article’s title/URL) from a rotating batch of your published posts to https://api.geoa.app, so Geoa can check for broken links server-side. No visitor data is involved.
• Content & site overview — only after you connect a Geoa account: the hourly status ping includes a compact list of your published posts (post ID, title, public URL, an admin edit link and the last-modified date — never the post content) and your site’s environment facts (theme and plugin names/versions incl. whether each plugin is active, whether search engines are discouraged, the permalink structure, whether core sitemaps are enabled, a small whitelist of Yoast/Rank Math settings — their sitemap toggle and organization/knowledge-graph name — and taxonomy counts). This lets your Geoa employee suggest refreshing outdated posts and warn about SEO conflicts with other plugins. No visitor data, no user accounts and no post content are sent.
• AI bot choice — only after you connect a Geoa account, and only when you flip the “Block AI training bots” toggle: the plugin sends that single yes/no choice to https://api.geoa.app, which returns the robots.txt rules to apply. No other data is sent.
• 404 traffic — only after you connect a Geoa account: the plugin counts real front-end 404 hits (the path only — query strings are stripped; no IP address, no user-agent, no visitor data) and sends the per-path counters to https://api.geoa.app on the hourly sync, so Geoa can suggest redirects for lost traffic. Bot-probe paths (wp-login, .env, …) are filtered out locally and never sent.

• AI-crawler activity — only after you connect a Geoa account: when a known AI crawler (e.g. GPTBot, ClaudeBot, PerplexityBot) fetches one of your pages, the plugin sends that crawler’s user-agent, the page path (query string stripped), a timestamp and the status code to https://connect.geoa.app — batched and asynchronously (at most one background request every 5 minutes), so it never slows your site. This powers the “AI crawlers on your site” card in your Geoa dashboard. No visitor data and no IP addresses are ever sent — only requests already identifying themselves as known AI crawlers. Disconnect your Geoa account and nothing is sent.

• Geoa badge (optional, off by default) — if you switch the badge on and place it on your site, your visitors’ browsers load the badge image from https://geoa.app. The image is an anonymous, unguessable address; the fetch is not logged per visitor, sets no cookie and assigns no identifier. Switch the badge off and no such request is made.

This plugin does NOT track your site’s visitors. It sets no cookies, adds no front-end tracking scripts, assigns no visitor identifiers, and never sends visitor or personal data to any external service. The AI crawler log records only the user-agent of known AI crawlers (e.g. GPTBot, ClaudeBot) that request your pages; it is stored locally in your own database, and is only transmitted (to https://connect.geoa.app, as described above) after you have connected a Geoa account — never IP addresses, never human visitors.

Service: https://geoa.app
Terms of Service: https://geoa.app/terms
Privacy Policy: https://geoa.app/privacy

1. Upload the geoa-ai-visibility folder to /wp-content/plugins/, or install it from the Plugins screen.
2. Activate the plugin.
3. Go to Geoa → Settings, choose your country and enter your registration number, then publish your registry-verified schema.
4. (Optional) Connect a Geoa account with a pairing code from your Geoa dashboard to see live AI-visibility scores.

1. 

   Verify your business against the official national registry and publish registry-verified schema — Geoa → Settings.

2. 

   Per-post answer-engine readiness, right in the block editor.

3. 

   Per-product AI readiness and enriched Product schema for WooCommerce.

4. 

   E-E-A-T trust signals and citation coverage.

5. 

   AI crawler activity — which answer engines fetched your pages.

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 …