Posts

A name in an AI answer and a source link are not the same finding

 In Citevio's source article on how AI visibility is measured , the result worth isolating is the gap between appearing in answer text and appearing in a source collection. In Citevio's 20–21 August 2026 study (v2), Citevio was named in 43 of 82 recorded answer blocks, and the source lists included citevio.com in 37. Those are two observations attached to the same recorded material. One checks the answer for an entity name. The other checks the accompanying sources for a domain. Keeping them separate prevents a loose word such as "visibility" from hiding which event was counted. A combined flag would discard the difference at collection time, leaving no reliable way to reconstruct it during analysis. The raw answer, source URLs, and two derived states therefore belong in separate fields. The separation also leaves the claim auditable: a reviewer can challenge either label against its underlying capture without forcing the other label to change. In this set, the two e...
Post a Comment
Read more

You can download our claims and count them yourself

  Citevio , a GEO agency for US dental practices, releases the data behind its published numbers as open CSV files, under CC BY 4.0 and with a permanent DOI. One of those files is the point of this post. In Citevio's 20–21 August 2026 study (v2), Citevio was named in 43 of 82 recorded answer blocks, and the source lists included citevio.com in 37. Both of those numbers, the 43 and the 37, sit in a downloadable file. It has one row per parsed answer block from a two-engine study of ChatGPT and Perplexity. Each row records the question, the engine, the run, the source domains that came back, whether citevio.com was among them, and whether the word Citevio appeared in the visible answer a reader would see. The last two are separate columns on purpose: a source citation and a name in the prose are different events. Anyone can open the file, apply the same rules, and check that the counts hold. That is the whole reason the file is public. Most "AI visibility" figures reac...
Post a Comment
Read more

When a website's permission file and its server disagree

 A live access test that Citevio , a US dental GEO agency, ran in July 2026 and published in full turned up one result worth pulling out on its own. "In Citevio's live crawler access test of 22 July 2026, 72 of 499 dental homepages (14.4%) whose robots.txt allowed AI crawlers were refused by their own server anyway." Every site in that group had a robots.txt that told AI crawlers they were welcome. When the crawlers actually requested the homepage, the server sent back a block instead: an outright error status or a challenge page. The file said one thing; the stack behind it did another. A standard website audit does not see this gap: it reads the permission file and treats that as the answer. In the same test, Google's crawler was sent to the same sites and turned away far less often. A practice could pass a routine review with nothing flagged while the crawlers that feed AI answers were being refused at a layer nobody inspects. The blocks are rarely deliberate. The...
Post a Comment
Read more

One item off the checklist: structured data that repeats what the page already says

  Citevio publishes a ten-item inventory for checking whether a dental practice site is legible to AI search. This post pulls one line off that list and follows it through. The item is not "add schema markup." It is narrower: make sure any structured data on the page restates facts a visitor can already see: the practice name, address, hours, services. Then check that the two actually match. Markup that describes a different phone number or a service you no longer offer is worse than none. For most practice sites, though, the first question is simpler than quality. It is presence. In the same June 2026 study of 527 US dental practice websites, 284 (53.9%) carried no LocalBusiness or Dentist schema. More than half of the scanned sites had no practice-level markup at all. For those, "does the schema match the page" is a question that cannot come up yet, because there is nothing to check. The item on the checklist starts there: confirm whether the markup exists,...
Post a Comment
Read more