Reference articles on Answer Share, machine readable infrastructure and how AI engines select what they cite. Written from methodology we run in production, on our own brands and on client builds.
Answer Share is the share of AI answers that mention or recommend your brand when real buyers ask real buying questions. It is the visibility metric of the AI answer era, and it behaves nothing like rankings or traffic.
AI agents burn most of their token budget parsing HTML built for browsers. Content negotiation lets the same URL serve a clean markdown rendition when an agent asks for it, without touching what humans and search bots see. Here is how to do it correctly, and the mistake to avoid.
Ask AI engines real buying questions and record every source they cite. The pattern is consistent: review platforms, directories, marketplaces, press, community threads and video. The brand website is rarely the evidence. That pattern should reorder most visibility roadmaps.
On 15 September 2026 Cloudflare retired its single Block AI Bots switch. Sites now set Search, Training and Agent separately, and Google, Microsoft and Apple stay allowed for search even when a site disallows AI training. What changed, who it affects and how to check, sourced to the vendors' own pages.
Since 31 August 2026 Cloudflare's Browser Run /crawl endpoint refuses crawls that go beyond a site's Content-Signal line in robots.txt. It is the first sourced case of a crawler enforcing those preferences, and so far the only one. What it enforces, why default requests now fail with a 400, and what it means for AI visibility.
Google now lets any eligible site add a Preferred Sources button, and a preferred site can carry a "preferred" badge in AI Mode and AI Overviews. That part depends on a separate Search Console setting that reached every site on 31 August 2026. What the button does and does not do, the two checks to run first, and what the JavaScript button loads before anyone clicks.
A robots.txt that allows GPTBot, ClaudeBot and PerplexityBot is a request, not a door. The door is your CDN, your firewall and your bot protection, and they decide on their own. Where a yes turns into a no, why the fetchers that run while a buyer is asking depend on that layer most, and what each test can and cannot prove.
On 30 September 2026 Cloudflare put Pay Per Use into beta. An AI company offers a price for a specific use of your content, you accept or decline in the Cloudflare dashboard, the buyer reports each use and Cloudflare bills the buyer and pays you. What it is, what the announcement leaves open and what it changes for AI visibility, sourced to Cloudflare's own posts.
On 8 October 2026 Google documented a dedicated pipeline that lets approved platforms send user-generated content and engagement signals straight to Google. What the program is, the six eligibility criteria, what it does not replace, and what a business website should take from it.
If you run a law office, a clinic or an accounting firm, you have to work out under which conditions client data may be processed by an AI tool at all. This guide explains three common approaches, what each one costs over three years for a five person office, and how to tell which one fits your constraints. It also says who should not buy a local system.
Your team already uses ChatGPT, Copilot or Gemini. There is no general ban, but data protection law sets conditions: which plan, which contract, which data, and written rules. This guide walks a non technical owner through the questions, compares what four providers state officially, and ends with a ten step checklist and a policy draft you can adapt.
READ
More articles are in preparation and will be published here.