Category: AI Search Authority

Five receipts so far in this series, five living sites: 44,583 citations at BC ESG, 109,844 at Healthcare Facility Hub, 813,426 on this site, 50,607 at Risk Coverage Hub, 57,798 at Continuity Hub. The sixth site we counted is a ghost. Restoration Intel — our restoration-industry library — earned 111 AI citations in the older window we measured, and every one of them landed inside seventeen days. In the fresh ninety-day window, the same report says zero. Not a decline. A disappearance.

Here is the whole story, because the whole story is short: fifty-three days of nothing, a burst from July 22 to August 7, then silence — fifty-eight more days of it in that export, and ninety straight days of zero in the new one. One guide holds nearly two-thirds of the burst. Five questions account for all of it that the query view can see. This is the smallest receipt in the series by orders of magnitude, and the strangest.

Watch the 60-second version: Why did this site’s AI citations live for exactly 17 days? — the same receipts in 44 seconds, chapters matched to the sections below.

The burst: seventeen days

The older window is May 30 to October 4, 2026 — 128 days, exported from Bing Webmaster Tools’ AI Performance report on October 6. The daily series sums to 111; the page table sums to 110. Bing’s views differ, and at this size they nearly agree: 0.9% apart, where the other sites in this series ran 2.6% to 5.7%. Every figure below names its view.

112 of the 128 days read zero. The sixteen days that don’t sit inside one stretch, July 22 to August 7: 1, 17, 7, 10, 4, 4, 3, 5, 7, 4, 12, 5, 5, 2, 12, 0, 13. One day inside the burst — August 6 — reads zero too, a held breath in the middle. The peak is the second day: 17 citations on July 23. Then, after August 7, nothing. Not a taper — the line simply stops, and it has not restarted in any window we’ve pulled since.

The guide: 70 of 110

Nine pages were cited in the burst, ever. One of them took nearly two-thirds of the page-sum:

• Fire-damage restoration, complete professional guide — 70
• Asbestos abatement protocol — 10
• Structural drying systems & psychrometrics — 8
• Reconstruction materials matching — 7
• Emergency response: the first 24 hours — 6
• AI drone technology in restoration — 3
• Restoration carbon protocol — 2
• Emergency documentation — 2
• How to file a property insurance claim — 2

Receipt No. 3’s leader held 30.8% of a huge site and we called it a star. This is 63.6% of a tiny one. The fire guide wasn’t a page among pages during those seventeen days; for whatever the machines were doing that fortnight, it was close to the whole site. The supporting cast is the library doing its job — drying science, abatement protocol, materials matching — real professional references, cited in single digits, then gone.

The questions: five, ever

The query view for the older window holds exactly five questions. Not five hundred — five. Three of them are the same question with the words rearranged:

• “fire restoration” — 20 citations; our share 21.28%.
• “fire remediation” — 12; our share 23.08%.
• “fire damage restoration” — 8; our share 22.22%.
• “commercial property emergency water damage restoration response time” — 3; our share 27.27%.
• “commercial property fire damage restoration process” — 3; our share 14.29%.

Those five rows are the entire visible demand. The query view sums to 46 citations against the daily view’s 111 — the views don’t reconcile at this scale, and we won’t pretend they do. What’s solid is the shape: for seventeen days, when the machines answered questions about fire restoration, they reached for this library about a fifth to a quarter of the time — and reached for its fire guide most of all. Then they stopped reaching.

The silence: ninety days of zero

The fresh window is the series-standard one — August 8 to November 5, 2026, ninety days, pulled November 8. The daily series sums to 0. There is not one nonzero day in it. The report’s Pages tab and Grounding Queries tab for this window showed “No data available” — the downloads were disabled, because there was nothing to download.

Put the two windows side by side and the site has now been silent for 148 consecutive measured days — the last fifty-eight of the old export and all ninety of the new one. Every other site in this series grew, plateaued, or tripled. This one is the only line in the fleet that goes to zero and stays there.

What we can’t claim

• We don’t know why it started. Nothing in these files says what switched on around July 22. The burst also predates the export that recorded it — the data was pulled October 6, looking back — so we’re reading a fossil, not watching a feed.
• We don’t know why it stopped. A ranking change, a crawl change, a reporting change, the end of some trial on the engine’s side — the report records counts, not causes. Picking one would be storytelling.
• The report’s own coverage may be part of the story. When Bing’s AI Performance report began covering this site, and how completely, is inside the mystery, not outside it. A burst in the data can be a burst in the world or a burst in the measuring. We can’t separate those from here.
• No cause is claimed — including ours. Anything we published or changed around those dates is not established as a cause, in either direction. Correlation with the burst would still not be a mechanism.
• 111 is small. One engine, one report, one site. At this size a handful of answers moving is the whole chart. We publish it because it’s ours and it’s strange — not because it’s big.

What we do now

1. Keep publishing the library. Restoration Intel exists to be a working reference for restoration professionals — the guides are useful whether or not a machine quotes them this quarter. The library is not a citation farm and we won’t run it like one.
2. Re-measure on the next sweep. The ghost gets counted again with the rest of the fleet, same windows, same instrument. If it ever flickers, we’ll see it in the series.
3. Don’t chase it. No rewrite of the fire guide to summon a burst we don’t understand, no surgery on a site whose only proven fact is that something happened once, for seventeen days, in the summer.

111 citations. Seventeen days. Then zero, for ninety straight days and counting. The ghost — published like everything else in this series, because the receipts are the receipts.

Download the field-report PDF — the same receipts in a printable report.

Method note: All figures are from Bing Webmaster Tools AI Performance exports for restorationintel.com. Older window: May 30–October 4, 2026 (128 days), pulled October 6, 2026 — the daily view sums to 111, the page view to 110 (0.9% apart), and the query view to 46; Bing notes totals may differ across views, and each figure above names its view. Fresh window: August 8–November 5, 2026 (90 days), pulled November 8, 2026 — the daily view sums to 0, and the Pages and Grounding Queries tabs showed “No data available,” so no page or query export exists for that window. Citation counts are Microsoft Copilot and partner citations as Bing reports them; citation shares are Bing’s per-query figures. Page names are shortened from the pages’ own titles. The field-report PDF is at https://tygartmedia.com/wp-content/uploads/2026/11/the-17-day-wonder-tygart-media-field-report.pdf. This is one site, one engine’s report, two windows — one of them empty.

Three shapes so far in this series: a star (Receipt No. 3 — one page, 30.8% of its site), a bench (Receipt No. 4 — no page above 7.7%), and now the shape between them. Continuity Hub — our business-continuity reference — earned 57,798 AI citations in ninety days, and one guide holds 10,579 of them: 19.2% of the page-sum.

The guide is a complete professional treatment of supply-chain resilience. The site grew +39% by halves — 538 citations a day to 747 — with the last fourteen days averaging 884 and a peak of 1,217 on October 29. An anchor, real support, steady growth. The hybrid.

Watch the 60-second version: Why does one guide hold a fifth of this site’s AI citations? — the same receipts in 47 seconds, chapters matched to the sections below.

The count

The window is August 8 to November 5, 2026, from Bing Webmaster Tools’ AI Performance report — the same instrument as the rest of this series. The daily series sums to 57,798; the page table sums to 55,029. Bing’s views differ (here by 4.8%), Bing prints a note saying so, and every figure below names its view.

55 pages, 547 questions. The halves: 538 a day, then 747. First fourteen days: 530 a day. Last fourteen: 884. Not the flagship’s plateau, not Risk Coverage Hub’s triple — a working site’s steady climb, with its biggest day, October 29, landing in the most recent third of the window.

The anchor — and the support under it

The supply-chain resilience guide’s 10,579 is a genuine lead — 2.7 times the runner-up. But read down the table and the anchor isn’t carrying the building alone:

• Supply-chain resilience, complete guide — 10,579
• Crisis communication protocols — 3,964
• Emergency exercises & drills — 3,727
• Crisis management, complete guide — 3,496
• Crisis management team structure — 2,910
• Emergency preparedness, complete guide — 2,518

Three pages hold 33.2% of the page-sum; six hold 49.4%; ten hold 64.0%. And the families are balanced: five crisis pages hold 23.4% (12,869), five supply-chain pages hold 24.7% (13,614). Two pillars of near-equal weight, one of them fronted by an anchor. If the anchor page stumbled tomorrow, this site would lose a fifth of its count, not a third — and the crisis pillar wouldn’t notice. That’s the risk arithmetic of the hybrid shape, and on these numbers it’s the most comfortable of the three.

The questions: one phrase owned, one contested

The guide’s own question is the site’s biggest, and the hold is strong:

• “supply chain resilience business continuity vulnerabilities management” — 1,965 citations; our share 32.17%.
• “crisis management team” — 688; our share 25.98%.
• And a question in full sentence form, the way someone asks a person: “during a disaster, a facility needs to quickly reach staff, volunteers, and emergency management partners. which emergency preparedness element supports this need?” — 620 citations; our share 34.39%.
• “enterprise resilience strategy regulations 2026” — 435; our share 33.67%.

Now the honest complication, and it’s a good one: the short form — plain “supply chain resilience” — earns 482 citations across the web’s answers, and our share of it is only 8.39%. The guide owns its long, precise phrasing and is a minor holder of the short, famous one. That’s not a failure; it’s a map. The long forms are where professional intent lives, and 32–34% holds there are worth more than a sliver of the generic phrase. But anyone who tells you this page “owns supply chain resilience” hasn’t read the query table. We have. It owns a specific, valuable cut of it.

What we can’t claim

• No build story. Unlike Receipt No. 1’s stepped sites, nothing here dates the +39% to a single act. The guide predates the window’s story; the claim is the shape and the growth, not a cause.
• The views differ. Daily-sum 57,798 vs page-sum 55,029 — 4.8% apart, disclosed, each figure naming its view.
• One engine’s window. Copilot and partner citations as Bing reports them; ninety days is a snapshot, not a deed.
• Citations are not visits. Established in Receipt No. 1: this count measures being quoted into answers, not being read.

What we do now

1. Protect the anchor’s freshness. A fifth of the site rides on one guide; it gets the flagship leader’s discipline — the heartbeat watch from Receipt No. 3, at hybrid scale.
2. Build toward the short phrase carefully. The 8.39% is an invitation, not an emergency: adjacent, specific pages in the supply-chain family — the Receipt No. 1 method — rather than a rewrite of the page that’s already winning its own question.
3. Keep both pillars fed. Crisis and supply chain are near-equal earners; starving one to feed the other would unbalance the sturdiest shape in the fleet.
4. Publish the receipts — including the share we don’t hold. The map is the value; a prettier story would be worth less.

57,798 citations. One guide at 19.2%, two pillars, +39%. The hybrid — and, on the risk arithmetic, maybe the shape to aim for.

Method note: All figures are from Bing Webmaster Tools AI Performance exports for continuityhub.org, pulled November 8, 2026. Citation counts are Microsoft Copilot and partner citations as Bing reports them. Window: August 8–November 5, 2026 (90 days). The daily view sums to 57,798; the page view sums to 55,029 — Bing notes totals may differ across views, and each figure above names its view. Citation shares are Bing’s per-query figures. Guide names are shortened from the pages’ own titles. The “crisis family” and “supply-chain family” counts cover pages whose addresses contain those terms. The R4R Continuity article staged for a grant submission is a different piece and plays no part in these numbers. This is one site, one engine’s report, one 90-day window.

Receipts No. 3 was about a site with a star: one page holding a third of everything. This one is about the opposite build. Risk Coverage Hub — our insurance-risk reference site — earned 50,607 AI citations in ninety days, and it has no star at all. Its biggest page holds 7.7%.

What it has instead is growth, and spread. The site’s daily citation rate went from 275 a day to 849 a day between the halves of the window — +209%, the fastest climb in our fleet. First fourteen days: 185 a day. Last fourteen: 1,064 a day. Peak day: November 2, with 1,537.

Watch the 60-second version: How did a site triple its AI citations with no page in charge? — the same receipts in 50 seconds, chapters matched to the sections below.

The climb

The window is August 8 to November 5, 2026, from Bing Webmaster Tools’ AI Performance report — the same instrument as the rest of this series. The daily series sums to 50,607; the page table sums to 47,747. Bing’s views differ (here by 5.7%), Bing prints a note saying so, and we name the view behind every number, as always.

Read the climb honestly: it isn’t a step. Receipt No. 1 had a step — a build date you could point at. This is a slope. The rate rises across the whole window, halves 275 to 849, and we are not going to invent a single cause for a slope. What we can do is read what the slope is made of — which pages, which questions — because that’s the part an operator can actually use.

The bench: six guides, no star

The top of the page table is bunched like a peloton:

• Business owners policy (BOP) coverage guide — 3,683
• Catastrophe modeling, complete guide — 3,445
• Underwriting cycles: hard and soft markets — 3,412
• Commercial general liability guide — 3,305
• Reinsurance treaty structures — 3,193
• Climate risk pricing & catastrophe model updates — 2,680

Six professional guides within a thousand citations of each other. Together they hold 41.3% of the page-sum; the leader alone holds 7.7%. Twenty pages get you to roughly three-quarters of the site — on our flagship, five pages are a majority. This is the diversified portfolio to Receipt No. 3’s concentrated bet, and it carries the mirror-image virtue: no single page’s bad week can wound this site. The bench is the moat.

The questions: long, specific, professional

The query table explains the shape. There is no “what is X” blockbuster here. The biggest questions are working questions, asked the way insurance professionals actually phrase work:

• “innovative insurance products digital risks cryptocurrency fraud deepfake liability…” — 464 citations; our share 28.07%.
• “global insurance risk underwriting metrics: evaluating climate disaster impacts on property premiums” — 459; our share 29.86%.
• “quota share reinsurance” — 404; our share 24.21%. The one short question in the list, and a term of art.
• “best practices property risk assessment commercial insurance” — 351; our share 29.52%.

414 questions, 78 pages — and the shares sit in a band, mostly a fifth to a third. Nobody owns these questions outright, including us. The site earns by being a solid, specific answer across a whole professional vocabulary, not by holding one phrase hostage. That is a slower asset to build and a harder one to knock down.

What we can’t claim

• No single cause for the slope. Unlike the stepped sites in this series, nothing here dates the rise to one build. The honest sentence is: the site tripled while publishing steady, specific, professional guides — and correlation across a portfolio is not a mechanism.
• The views differ more here. Daily-sum 50,607 vs page-sum 47,747 — 5.7% apart, disclosed, each figure naming its view.
• One engine’s window. Copilot and partner citations as Bing reports them; ninety days is a snapshot, not a deed.
• Citations are not visits. Established in Receipt No. 1: this count measures being quoted into answers, not being read.

What we do now

1. Feed the bench, not a star. The next guides get chosen from the question map where a working question is landing on an adjacent page — the Receipt No. 1 method, applied to a bench instead of a doorway.
2. Watch for bunching changes. If one page starts separating from the peloton, that’s a signal — good or bad — worth a diagnosis, the way we diagnosed the flagship’s leader in October.
3. Keep the shares honest. A fifth to a third on the big questions means the work is depth and currency, not defense of a crown we don’t hold.
4. Publish the receipts — including the part where the growth has no single hero. A slope you can’t attribute is still a slope you can measure.

50,607 citations. 275 to 849 a day. No star — a bench, a vocabulary, and a climb. That’s the count and the shape.

Method note: All figures are from Bing Webmaster Tools AI Performance exports for riskcoveragehub.com, pulled November 8, 2026. Citation counts are Microsoft Copilot and partner citations as Bing reports them. Window: August 8–November 5, 2026 (90 days). The daily view sums to 50,607; the page view sums to 47,747 — Bing notes totals may differ across views, and each figure above names its view. Citation shares are Bing’s per-query figures. Guide names are shortened from the pages’ own titles. The Risk Coverage Hub underwriting explainer published today (post 1495 on that site) is not a driver of these numbers — it postdates the window. This is one site, one engine’s report, one 90-day window.

This site — tygartmedia.com, the one you’re reading — earned 813,426 AI citations in ninety days. That’s the whole portfolio: 578 cited pages, 1,698 different questions that assistants asked and answered with our work. One page holds 244,307 of them.

The page is our Claude pricing page: a plain, kept-current answer to what Claude costs. It holds 30.8% of everything this site earned. The runner-up — our pricing-tiers comparison — holds 81,011. The leader triples it.

This is Receipts No. 3, and it’s the uncomfortable one. The first two pieces in this series were about growth — a hospital site stepping up, two doors built in a night. This one is about shape: what it means when a third of your citation count lives at one address.

Watch the 60-second version: Why does one page hold 244,307 of this site’s AI citations? — the same receipts in 49 seconds, chapters matched to the sections below.

The count

The window is August 8 to November 5, 2026, from Bing Webmaster Tools’ AI Performance report — the same instrument as the rest of this series. The daily series sums to 813,426; the page-level table sums to 792,317. Bing’s own views disagree by 2.6%, and Bing prints a note saying totals may differ across views. We use each view for what it measures and say which is which, every time.

The site’s halves are flat: 9,087 citations a day in the first half of the window, 8,989 a day in the second. Peak day: September 2, with 14,526. Nothing about the total is a growth story. The total is a plateau — and a plateau is exactly where shape matters, because the composition is the whole story.

The shape of the portfolio

Read the page table by rank and the portfolio stops looking like a portfolio:

• 1 page holds 30.8% of the page-sum.
• 3 pages hold 44.9%. 5 pages hold 52.1% — a majority of the site is five addresses.
• 10 pages hold 63.4%. 25 pages hold 81.1%.
• The remaining 553 pages share what’s left — about 19% between them.

And the concentration has a subject. Thirty-six of the 578 pages are pricing pages — their addresses carry “pricing” or “cost” — and together they hold 396,978 citations: 50.1% of everything. Half this site’s citation count is one question family, asked over and over in slightly different words: what does Claude cost, what does the Team plan cost, is there a student discount, what does Enterprise run. We didn’t set out to become a pricing reference. The assistants decided that’s what this site is for — and the page table is what that decision looks like from the inside.

The questions are bigger than the page

Here’s the part that keeps the story honest. The pricing page is enormous — and on the biggest question it serves, we are a minority holder:

• “claude pricing” — 45,425 citations earned across the web’s answers; our share is 14.95%.
• “claude ai pricing” — 32,101 citations; our share 24.79%.
• “anthropic console” — 14,638; our share 48.37%, the strongest hold on a big question.
• “claude enterprise pricing” — 13,775; our share 28.92%.
• And at number five, a tell: “citation rate calculation AI-generated responses” — 12,478 citations at a 34.42% share. That’s our own trade, reading about the instrument itself.

A page can hold a third of a site and a seventh of its biggest question at the same time. Both numbers are true, and the second one is the opportunity measured precisely: the demand under the leader is roughly seven times the leader.

What concentration means

Two things, and they’re the same fact read from opposite ends.

It’s a moat. A page that answers a money question plainly, stays current, and gets cited 244,307 times becomes the reference the assistants reach for — and every citation is a small vote that makes the next one likelier. Nobody at this desk did anything exotic to earn it. The page does one job, in the asker’s words, and it’s kept honest. That’s the whole trick, and Receipt No. 1 showed what happens when you build that shape on purpose.

It’s a single point of failure. If that page stumbles — a pricing change at Anthropic that makes it stale overnight, a careless rewrite, a bad week — a third of this site’s citation count reprices with it. We don’t have to imagine the exposure; we watch it. In October we ran a full formal diagnosis on this one page — its pattern had broken in ways we needed explained before we touched anything. You don’t commission a diagnosis for a page that doesn’t matter. You commission one for the page that carries the building.

The hedge is the bench. The tiers comparison at 81,011 is a genuine understudy — same question family, different cut. Team pricing, the student discount page, the console page: the family is deep, and the family is the insurance. Concentration at the page level, diversification at the family level. That’s the actual structure, and it happened before we were wise enough to plan it.

What we can’t claim

• One engine’s window. These are Copilot and partner citations as Bing reports them. It’s the cleanest instrument we have; it is not the whole sky.
• The views differ. Daily-sum 813,426 vs page-sum 792,317 — 2.6% apart, disclosed above, used consistently.
• Citations are not visits. Receipt No. 1 established it on another of our sites: 57 citations per human visit. This count measures being quoted, not being read.
• Ninety days is a snapshot, not a deed. Questions mutate — the BC ESG piece watched pharma’s biggest phrasing change between pulls. Shares move. This is the shape on November 8, 2026.

What we do now

1. Watch the leader’s daily line like a heartbeat — not the site’s total, which can hide a dying leader inside a healthy plateau for weeks.
2. Keep the bench current. The understudy pages get the same freshness discipline as the star; the day the leader stumbles is the wrong day to start.
3. Build adjacent doors the measured way — when the question map shows demand landing sideways (Receipt No. 1’s method), build the page the question is asking for.
4. Publish the receipts — including the shape we’d rather not have. A third of the building on one page is a fact we’re better off saying out loud, because saying it is what keeps us watching it.

813,426 citations. 244,307 of them at one address. That’s the count, that’s the shape, and that’s what we’re doing about it.

Method note: All figures are from Bing Webmaster Tools AI Performance exports for tygartmedia.com, pulled November 8, 2026. Citation counts are Microsoft Copilot and partner citations as Bing reports them. Window: August 8–November 5, 2026 (90 days). The daily view sums to 813,426; the page view sums to 792,317 — Bing notes totals may differ across views, and each figure above names its view. Citation shares are Bing’s per-query figures. The “pricing family” count is pages whose addresses contain “pricing” or “cost.” The October diagnosis referenced was an internal workup of the pricing page’s citation pattern. This is one site, one engine’s report, one 90-day window.

Receipts, No. 2 — Healthcare Facility Hub. First in this series: We Watched the Questions AI Was Asking Our Site.

In October we believed one of our sites was declining. We said so in writing, with a chart. The chart was honest; the window was the problem — it ended October 4, and Healthcare Facility Hub spent the rest of October doing the opposite of declining.

This morning we pulled the full ninety days. Between August 7 and November 6, AI answers cited Healthcare Facility Hub 109,844 times. The first half of the window averaged 984 citations a day; the second half averaged 1,720 — up 75%. The last fourteen days ran at 2,032 a day, and the peak, October 20, hit 3,510. It is the fastest-growing property we run.

So we went looking for its biggest page, expecting to find the usual pattern from the rest of the fleet: a page the machines read and the humans barely visit. We found the opposite. This is the story of that page — including the part where we shipped its companion file split in two and the citations divided themselves between a summary and the real thing.

Watch the 60-second version: Why does one hospital page get cited 11,181 times by AI? — the same receipts, in 52 seconds, with chapters matched to the sections below.

The page

The page is a guide: What Is ICRA in Healthcare? (ASHE 2.0) — infection control risk assessment for construction and maintenance work in occupied hospitals. It holds 11,181 citations, the most-cited page on the site, about a tenth of everything. Around it sits a small family: a sibling ICRA guide at 2,053, a Class IV–V requirements page at 173, a matrix explainer at 121, a class finder at 23.

The query that feeds it hardest is plain: “icra meaning.” Five hundred ninety-three citations, and 592 of them land on this one page. Its daily rhythm tells the build story. Through mid-October it ran flat, a handful a day. Then, on the October build dates, it stepped: 45 on October 21, 55 on the 23rd, 57 on the 27th, peaking at 84 on November 3.

Then we checked the humans

On the beauty-industry site in our first report, the pattern was stark: hundreds of citations, a handful of human sessions, visits that lasted about ten seconds. Machines verifying, nobody reading.

The ICRA page breaks that pattern completely. Microsoft Clarity, last thirty days: 231 human sessions (seventeen bot sessions excluded), 162 people, an average of 4.4 active minutes inside a 7.8-minute visit, 1.72 pages per session, scroll depth 36%, zero rage clicks, almost no friction. Three quarters of them arrive from Bing search. And the browser split gives the audience away: 73.6% Microsoft Edge, 88% desktop. That’s facilities and infection-prevention staff on managed hospital workstations, in the middle of a workday, using a page to do a job.

The site as a whole is built the same way: 2,412 human sessions in thirty days against 1,091 bot sessions excluded — the most human audience in our fleet. The machines cite this site the fastest-growing amount, and the humans actually read it. Both. At the same time. On the same pages.

The machinery question, again

Our first report noted that the beauty site had no llms.txt file and full FAQ schema on its winning guides. Healthcare Facility Hub is the mirror image: it has an llms.txt, and its most-cited page carries no FAQ schema at all — video markup, breadcrumbs, speakable, that’s it. Opposite machinery, same explosion. Whatever is being selected here, it isn’t a schema flavor.

What the two winners share is more ordinary: one real question answered completely on one page, and a downloadable artifact attached to it — a field sheet a person (or an agent) can take away. On this site that second layer is not small: 91 cited PDF field sheets hold 7,317 citations — compliance checklists for the Joint Commission, evacuation, fire drills, medical gas. Books for bots, and for the people who print them.

What we got wrong

Here is the part we would rather skip, which is exactly why it’s in the report.

The ICRA guide links its field sheet twice — and the two links go to two different files. The first version, published October 15, sits at the clean, obvious filename. It is a summary sheet: the direct answer, the framing, no numbers — the actual Class I–V barrier matrix is not on it. It holds 68 citations.

On October 29 we published the real sheet — the full matrix, barrier requirements by class, negative-air sizing, the decommissioning sign-off sequence, stamped on its face as the current version. But it went up under a new, dated filename instead of replacing the old file. It holds 47 citations. An email-gate on the same page points at the clean filename too, so the older, thinner sheet has a third door in.

A page and its download are supposed to be one asset, saying one thing. Ours said two, and the citation record split along the seam — with the lead going to the version that has less in it. Anybody who followed the most-cited link got the summary. Anybody who followed the page’s own button got the matrix. We built both halves of that on purpose, two weeks apart, and never noticed the seam until we pulled the page-level export this morning.

The fix is two file renames, and nothing else. The October 15 file moves to an archive name — its bytes preserved, its history intact. The October 29 sheet takes the clean filename. The page doesn’t change; no link anywhere changes. Every door — the page, the email gate, the citation record — then opens onto the full matrix.

As this publishes, the fix is staged and waiting on a server door, not on a decision: the file host has refused our automated connections this morning, so the two renames run the moment that door reopens, or by hand in the hosting panel. When it lands, this article gets a dated line below saying so — the same update-lineage rule we apply to the pages themselves. If you’re reading this without that line, the fix is still in flight and we’d rather tell you that than round it off.

What we’d tell another operator

Check your cited PDFs for version splits. If a page was ever refreshed by uploading a new file instead of replacing the old one, you may have two assets dividing one citation record — and the split favors whichever file got the cleaner name, not whichever is better. This took one page-level export to find.

Read the session data before you call a page machine-only. The fleet’s loudest page turned out to have its most human audience. The machines and the people are not reading different sites; on the good pages, they’re reading the same one.

A trend is a window, not a verdict. We wrote “declining” in October because our window ended October 4. The site was already turning. The correction cost us nothing but a sentence — because the first claim was in writing, with its dates on it.

Method. Bing Webmaster Tools, AI Performance, pulled November 8, 2026, window August 7–November 6, 2026. Daily totals sum to 109,844; the page-level sum runs slightly lower (106,101) — Bing notes totals can differ between views. Query figures from the filtered pull for “icra meaning” (593 total; 592 to the ICRA guide, 1 to a sibling). Microsoft Clarity figures are the last 30 days, bot sessions excluded as reported; the citation and session windows differ, so comparisons between them are directional. Field-sheet contents verified by reading both files this morning.

The full dataset — every chart above, the site table, and the field-sheet comparison — is in the companion field report: Built for the Question: Healthcare Facility Hub (PDF).

Working on a site where AI answers are sending mixed signals? Book a call with Will Tygart.

Update history

November 8, 2026 — Published. Field-sheet consolidation staged; completion line to be added here when the renames verify live.
November 8, 2026 — The 60-second video version published on YouTube (linked at the top of this page); its chapters match the sections below, and each chapter links back to its section.

In early October, a spreadsheet landed on my desk that I can’t stop thinking about.

It was an export from Bing Webmaster Tools — the AI Performance report for BC ESG, one of the sites we run. Filtered to a single question people were asking AI assistants: “pharmaceutical companies esg executive compensation.” Five days, October 1–5: 51 citations. Our pages, being read into AI answers about how drug companies tie executive pay to sustainability targets.

Here’s the thing. We had never built a page for that question. The citations were landing on a generalist compensation guide — a good page, but a sideways answer to a specific question. The demand was real, measured, and unanswered on purpose by nobody. It was just there.

We did try to find out what sparked it. There was movement around a company — I’m not naming it, because we never could source it, and guessing in public is how you become the thing we don’t want to be. So we made a rule out of it: build on the demand you can measure, never on the attribution you can’t. The demand we could measure. So we went and measured all of it.

Watch the 60-second version: How did two missing pages step AI citations from 11 a day to 30? — the same receipts in 56 seconds, chapters matched to the sections below.

The map: count everything before you build anything

On October 19 we pulled the full report — every query, every page, counted by value instead of skimmed. The clusters that mattered:

• Beauty companies, executive pay, sustainability targets — 68 citations on the main phrasing, more scattered across variants. Again: no dedicated page. The generalist guide was absorbing all of it.
• Pharmaceutical executive comp — 51 citations across four related phrasings.
• ICMA green bond principles — 159 citations at a 45.43% citation share. The site’s #1 query — and this one already had real pages behind it.
• Pay-equity reporting — small. 9 citations. Noted, not built.

Two of the four clusters were demand with no door built for it. That’s the whole insight, and it’s not complicated: AI assistants were asking our site specific questions, and we were answering adjacent ones.

The build: one night, two pages

That same night — October 19 — we published two guides:

• Beauty Companies: Executive Pay & Sustainability Targets
• Pharmaceutical Companies: ESG Executive Compensation

The rules we built them by:

1. One real question per page, in the asker’s own words. The page’s address is the question, word for word — because that’s the string the assistants are already carrying.
2. Answer first. No throat-clearing, no “in today’s rapidly evolving landscape.” The answer is at the top; the depth is below it for whoever wants it.
3. Every page carries its download. Each guide has a companion PDF — a scorecard pack, a design pack. A page and its PDF are one asset. If the content changes, both change, same run. You’ll see why in a minute.

Then we waited. Three weeks later — this morning — we pulled the reports again and counted.

What happened: the step

Read the daily series, not the totals, and the story tells itself. The beauty query was running at 11 citations a day. The day after the guides went live it stepped to 30 a day — peak day, 50 — and it has stayed at the new level. The pharma query went from 3 a day to 11 a day, same step, same date. Nothing else changed on those pages’ behalf that week. The step is dated, and the date is the build.

Against the October snapshot, the beauty query is at 684 citations and now holds a 57.33% citation share — when an assistant answers that question, it cites our site more than half the time, and the page it cites most is the one we built for it. The pharma cluster totals 600 across its phrasings.

Now the two honest complications, because a report that only shows the wins isn’t a report.

The tide rose too. ICMA green bond principles grew from 159 to 417 with no new build from us — the pages already there just kept earning. The whole site went from 420 citations a day to 797 a day across the same line. So no, I won’t claim every new citation is ours by construction. The claim I’ll defend is narrower: on the two queries we built for, the daily rate stepped on the build date and held, and the built pages took the lead or second place in earning them. The tide explains growth. It doesn’t explain a step.

Small stayed small. Pay-equity reporting — the cluster we noted and didn’t build — went from 9 to 24. Fine, and roughly what you’d expect: no door, no step.

Who earns the query

This is the chart I keep coming back to. On beauty, the guide we built leads — 306 citations to the generalist’s 233 — and the generalist didn’t lose anything in absolute terms. The pie grew; the new page took the bigger slice of a bigger pie. That’s the answer to the cannibalization worry, at least this once: building the specific page grew the specific query.

On pharma, the built guide is second — 93 to the generalist’s 145. A strong second, on a query whose daily rate tripled, but second. One difference between the two builds: the beauty page’s address is the query word-for-word. The pharma page’s address drops one word of it. Is that the reason? Two data points is a hypothesis, not a law — I’m labeling it as one, and it’s the first thing we’ll test on the next build.

And look at the bottom of both panels: the PDFs get cited. Six for the beauty scorecard, two for the pharma design pack in these filtered windows — and across the whole site, four PDFs hold 45 citations, one pharma scorecard alone at 23. The downloads aren’t lead magnets bolted onto the content. In an AI answer, they are content. That’s why the page and its PDF ship as one asset here, and why this article has a companion report instead of a screenshot gallery.

The companion report: Built for the Question — a Tygart Media field report (PDF). The same findings in the form built to travel: all four charts, the tables, the method note. Take it, share it, keep the method note attached.

The other half of the instruments: what the humans did

Everything above comes from Bing’s report — the machines’ side of the glass. We also run Microsoft Clarity on the site, so we went and looked at the humans’ side: recordings and friction data for the two guide pages, last 30 days.

The honest headline: there is almost nobody there. The beauty guide — 725 citations in the new report — has had 7 human sessions in 30 days. The pharma guide — 301 citations — has had 2. Sitewide it’s the same shape: 786 human sessions against 44,583 citations. The citation economy runs at roughly 57 citations per human visit, and on the built pages it’s over a hundred to one. The audience for this content is not visiting. It’s being quoted.

And the handful of humans who do land on the beauty guide arrive from a telling set of doors — among the seven sessions, referrers include claude.ai and gemini.google.com. Not the channel the citations live in (that’s Copilot, which sends almost no one), but the same species of door: a person reads an AI answer, then clicks through to check the source. They stay 10 seconds, scroll 5% of the page, click nothing, and leave. No rage clicks, no dead clicks, no errors — zero friction of any measured kind on either page. They’re not reading. They’re verifying — and the page’s job, for them, is to be checkable at a glance: answer first, sources visible.

Meanwhile the bots Clarity filtered out tell their own story: on the pharma page, 6 of its 8 total arrivals were bots; the beauty page, 4 of 11. Sitewide, 2,526 bot sessions excluded against 786 human ones kept. Even the “traffic” is mostly machines.

This is what the PDF citations meant, seen from the other side. If the content’s real consumers are assistants pulling pages and files into answers, then the page is a source document that occasionally gets audited by a human — and it should be built like one. Which brings us to the machinery people argue about.

About llms.txt, JSON, and the rest of the folklore

There’s a standing argument in our trade about what a site must hand the machines: a special llms.txt file, elaborate JSON schema, structured feeds — with one camp saying none of this can work without them and another saying it’s all decoration. We’re in the odd position of not having to argue. We can look.

This site has no llms.txt. None. The address returns our 404 page. It has never existed on bcesg.org — and the site earned 44,583 citations in 90 days without it. Whatever llms.txt is for, “getting cited at all” is not it.

The pages do carry JSON-LD — a FAQ block, article markup, breadcrumbs. And we don’t credit it for the step, because the evidence we trust most on that question — including a controlled test on 1,885 pages that added JSON-LD and got no citation lift — says schema buys eligibility and accuracy, not selection. Our dates agree: the schema was there before October 19 too. What changed on October 19 was the content — a page built to be one question’s answer, carrying a file built to travel.

That’s the whole machinery conclusion, and it’s almost embarrassingly plain: the assistants cite what answers the question, in a form they can carry. A clean page whose address is the question. A PDF that is the answer, portable. The rest is garnish — some of it harmless, some of it a whole industry’s worth of billable garnish.

What we can’t claim

• Bing’s own tables don’t perfectly agree with Bing’s own charts. On one filtered view, the chart total was 247 and the pages beneath it summed to 246 — Bing prints a note saying totals may differ when filters are applied, and they do. We report the chart totals and say so.
• The windows differ. Each export covers the range Bing gives it; every chart here carries its window on its face. Comparing across windows without saying so is how case studies become fiction.
• Leaderboards move. The single biggest pharma phrasing in the new report — “pharmaceutical companies ESG metrics executive compensation,” 248 citations — isn’t the phrasing we built for in October. It was second then. Questions mutate. The map is a snapshot, not a deed.
• This is one site, one engine’s report, one month. Copilot citations are what Bing measures. It’s the cleanest window we have, and we say what it is.

What we do now

This is the operating loop, and it’s the same one we’d run on any site, including a client’s:

1. Pull the AI citation report and count it by value. Not impressions-vanity — which questions, which pages, what shares.
2. Find the clusters where demand lands on pages that weren’t built for it. That gap is the work list. It’s usually short.
3. Build one page per question, in the asker’s words, answer first, with its download attached as part of the same asset.
4. Wait, then re-pull and read the daily step — not the cumulative total, which flatters everything.
5. Publish the receipts, including the parts that complicate the story.

BC ESG’s whole portfolio, for the record: 44,583 AI citations in 90 days, across 75 cited pages and 428 distinct questions. We didn’t buy that. We counted, we built two doors where the traffic already was, and we wrote down what happened.

If you’re running a site and wondering what the assistants think it’s for — the report that answers that question already exists. It’s sitting in your Webmaster account, unopened. Open it, count it, and build what it’s asking for.

That’s what we did. This is what we saw.

Method note: All figures are from Bing Webmaster Tools AI Performance exports for bcesg.org, pulled October 8 (query-filtered), October 19, and November 8, 2026. Citation counts are Microsoft Copilot and partner citations as Bing reports them. Behavior figures are from Microsoft Clarity (project for bcesg.org), last 30 days as of November 8, 2026, with Clarity’s bot sessions excluded as reported. Page structure and file checks (llms.txt, JSON-LD, PDF links) were verified directly against the live pages on November 8, 2026. Windows: site-wide overview Aug 7–Nov 6, 2026; filtered views as labeled on each chart. Where Bing’s chart totals and table sums differ under filters, chart totals are used and the difference is disclosed above. The two guides discussed were published on bcesg.org on October 19, 2026.