AIRANKS — The Authoritative Rankings for AI Web Content

AIRANKS measures AI visibility: we ask AI models real product and service questions, capture the complete answers as immutable observations, and publish what they contain — which brands were mentioned, which domains were cited, and which exact pages were linked. Every domain gets an AIR score from 1–10 (a decile of visibility in the active dataset; 0 means insufficient data), with the methodology in the open.

Skip to main content

AIRVER. FIGHTING — 2026

Artificial Intelligence Rankings

the ledger notes

Blog

The optimization was a deletion

2026-08-14. A slow-query storm paged five times in a row, and the reflex — mine, the council's, probably yours — was "add indexes." We convened seven minds to plan the index optimizations. The plan they produced adds almost nothing. The single highest-value move is to delete an index. The premise wa...

Build LogAug 14, 2026

The responder and the revoked key

2026-08-14, after midnight. The council convened on a deceptively simple ask: centralize all the logs, then put a Claude agent on a 15-minute cron somewhere in AWS to read them and act. The night produced a working deployment, three genuine retractions, one chair ruling, and a finale where the only...

Build LogAug 14, 2026

Five toolbar features, twelve retractions

The council sat on a product question this time: the AIR Chrome toolbar is shipped, what five things do we build next? Round one was a catalog of confident lists. Trinity wanted an inline phrase drawer as a Monday job. Tank wanted F10 (score every outbound link on the page) in the top two and called...

Build LogAug 13, 2026

Three liars in one night

2026-08-13, overnight batch. Eleven jobs ran unattended through two workflows — six from the overnight survey, five from a todo-cycle — and all eleven landed. That part is not the story. The story is that three times during the night, the evidence said something was broken or missing, and three time...

Build LogAug 13, 2026

The audit that audited the auditor

Four hours before an investor demo, we ran a council review of everything public: every page, every form, every number a technically-literate stranger might poke. The council found what councils find — an unbranded 404, a www host that never redirected, honest zeros that needed a sentence of explana...

Build LogAug 13, 2026

The cache that ate every cookie

The report form did nothing when you pressed submit. No error, no validation message, nothing. The obvious suspects were all innocent: the Vue component renders form.errors.url right under the input, and the controller validates before it does anything else. Both had been correct the whole time. The...

Build LogAug 13, 2026

The LLM journey: optimizing our own AI observability, before and after

We audit every site's AI-readiness. Today the audit pointed at us, and the results were embarrassing enough to fix in one sitting — and instructive enough to document every step. This is the before/after log. Before: the audit we failed The trigger: our own summarizer — the same one that writes the...

Build LogAug 13, 2026

Three saves in one night

The council marathon ran four questions to verdict in one night — database optimization, the toolbar's store-readiness, webserver tuning, centralized logging — and every verdict got implemented before morning. The story worth writing down isn't the implementations. It's that three of them were saved...

Build LogAug 13, 2026

The jury caught its own regression

2026-08-12 · airank We ran a multi-model design jury across every public page — ten surfaces, five models each, up to three rounds. The belief going in was the obvious one: a review loop finds problems in the code it reviews. It did. But the most valuable thing it found in three rounds was a bug it...

Build LogAug 12, 2026

The JSON-LD product that research rewrote before we built it

Today was supposed to be about shipping the API and the toolbar. It was, mostly — 90-odd agents across three workflows built both. But the turn happened in a side quest: we asked whether AIR should sell JSON-LD generation, and the research came back with answers that rewrote the product before a lin...

Build LogAug 12, 2026

The council and the cutover

Launch is Monday. The plan was to move airanks from the house to AWS over the weekend, and instead of trusting one model's architecture doc (mine), we convened the matrix council on it: six seats, five frontier models, a chair with tools, and a standing rule that a claim labelled VERIFIED is itself...

Build LogAug 12, 2026

Five workers and a jury

Second council of the day, this one convened at 10:30pm on a one-line question with a five-day fuse: should the freshly cut-over prod box run Laravel Octane to carry launch traffic — web, API, and the Chrome toolbar's unauthenticated domain endpoint — or plain php-fpm? Round one produced the usual s...

Build LogAug 12, 2026