Geoa – AI SEO & AEO on Autopilot

ਤਬਦੀਲੀ-ਚਿੱਠਾ

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 …