Changelog

What shipped, and when

Dated notes on the changes you can actually see — new pages, new measurements, and the times we corrected something we had been counting wrongly.

One name for the thing your plan counts

Pricing and the help pages now use a single term — tracked questions — for the unit every plan is measured in. No number changed; the wording did, because it used to switch names between the page that sells the plan and the page that explains it.

See it →

Availability and accessibility, in writing

Two new public pages. One says what we promise about uptime — including that there is no contractual service-level agreement yet, and why. The other says which parts of the site are known not to meet the accessibility standard we aim at, and where to report a barrier.

See it →

Tax is added at checkout, and every price now says so

Prices are quoted without tax, and the sentence saying so now appears wherever an amount is shown — the plan cards, the plan picker, the capacity packs and the pricing questions. The rate is worked out at checkout from your own country, and companies in the EU can enter a VAT number there.

See it →

See what is left this month before you run out

Your settings now show how many checks you can still start yourself this month, the date the month resets, and the fact that your automatic weekly checks hold a separate share your own runs can never spend. The same figures are readable through the API.

The weekly summary and the win/loss alerts are separate switches

They used to be one setting, so turning off the weekly summary also silenced the alerts that tell you an engine has started or stopped citing you. Each has its own switch now, and the account mail we cannot turn off — receipts, sign-in, password — is listed separately and labelled as such.

Yearly billing, and more capacity without changing plan

Every paid plan can now be paid yearly, and each tier states plainly what that does to the price rather than implying a discount it does not give. Pro and Agency can also add tracked questions or client sites in packs, so a growing account no longer has to jump a tier to fit.

See it →

The AI Source Index — which sources the engines really cite

A public panel of forty buyer questions is put to every engine we track, once a week, and every source those answers cite is published. Each week keeps its own permanent page, and a separate log records changes in the engines themselves.

See it →

A documented API, an MCP server and signed webhooks

Your visibility data is now reachable from your own tools: a read API with a published specification, an MCP server so AI agents can query it directly, and outbound webhooks that push results to your server instead of you asking for them. The developers page documents all three.

See it →

The site audit reads your whole site, not just the homepage

The deep scan starts from your sitemap and works outwards through the site, up to the page budget your plan allows. Findings now name the individual pages that carry each problem, so a fix has an address instead of being advice about the site in general.

A rebuilt home page

The front page was redrawn around a live product card and a band of things we can actually evidence — what the product measures, the public scoreboard, the written method. A young product has no customer quotes to show, so it shows the proof it does have.

See it →

First signals, for a site nothing cites yet

A new site used to open on a wall of zeros. The dashboard now shows the smaller wins that arrive first — being named in an answer without a link, or turning up for a question about your own brand — and says what each of them is actually worth.

An engine repeating your name is no longer counted as a mention

When the question itself names your brand, the answer usually repeats it without recommending you. Those echoes were being counted as mentions; they are not any more, and a question about yourself can no longer lift your own visibility score.

A feed for the guides, and rivals on the public scoreboard

The guides publish a feed you can subscribe to, in both languages. On the public scoreboard, every question we are not mentioned for now names the competitors the engine recommended in our place.

See it →

Every public page is served from cache again

The language moved into the address, and the theme and signed-in state moved into the browser. Marketing pages, guides and free tools are now prepared ahead of time instead of being built for each visitor: they open faster, and both languages can be crawled.

Promvia measured on itself, in public

A public scoreboard shows what the answer engines currently say for our own tracked questions, taken from the product's own checks rather than written by hand. The questions we lose are on it too — that is the reason for publishing it.

See it →

Two more free tools, with no signup

A citability check scores any homepage on the citation-readiness signals we can verify. A head-to-head runs the same scoring against a competitor and names exactly which signals they have and you lack.

See it →

Turkish pages have addresses of their own

The language used to be remembered in a browser setting, which meant a search engine only ever saw one version of the site. Every public page now has its own Turkish address, and the guides were written in Turkish to match.

A library of guides

Long-form guides on getting recommended by AI assistants: what the engines look for, how to measure what they send you, and where the honest limits are. Each one opens with a direct answer and names its sources. The library has kept growing since.

See it →

Only changes a customer can see are listed here. A great deal of the work never surfaces; that is a good sign rather than an omission.