AI Citation Strategy - Tygart Media

Category: AI Citation Strategy

Thought leadership on AI citation data, platform-specific optimization, and the emerging citation economy.

  • Move the Design System Before December 14 — the Chat Does Not Come With It

    Move the Design System Before December 14 — the Chat Does Not Come With It

    The standalone Claude Design site at claude.ai/design closes on December 14, 2026. After that date, the address opens Claude. Anthropic’s announcement gives the reason in one sentence: “Running two versions slows down fixes for both, so we’re folding the standalone site into Claude.”

    The migration that Anthropic offers moves design systems. It does not move projects. And the parts of your work that live only in the standalone product — the chats, the comments, the originals — have a deletion date, not a transfer path. This is the procedure for a team that has brand systems and client one-pagers in there, in the order the steps have to happen.

    What gets deleted, exactly

    Anthropic’s migration guide names the deletion list in two bullets: “Your chats with Claude” and “Comments on your projects and design systems.” Those stay in the standalone version and are deleted after it closes, per Anthropic’s data retention practices.

    Your originals are a separate statement, in the guide’s FAQ: they keep working in the standalone version until it closes on December 14, 2026, and “after that, they’re deleted.” A design system you migrate leaves its original behind in the standalone product, unchanged — and that original is on the same clock.

    Public links to standalone projects are a third outcome, and the guide words it differently on purpose: they “will no longer work after it closes.” Not deleted — dead. Every client you sent a public project link to holds a URL with an expiry date.

    The instruction Anthropic prints is the whole strategy for this section: save anything you need from your chats and comments before the standalone version closes. No fetched Anthropic page documents an export for chats or comments. The capture that matches the documentation is a screenshot of each comment thread and a copy of the chat text, done by hand.

    The dangerous sentence: “You don’t need to do anything with your projects yet”

    That sentence is in the migration guide, and it is true — your projects keep working in the standalone version until the close. It is also the sentence that will get client work deleted, because projects are the files with no migration path and a deadline.

    The Artifacts page in Claude lists up to 60 of your standalone projects, and they open in the standalone version. That list is a directory back into the product that is closing. It is not a move, and it is not a complete inventory if your team has made more than 60 projects. Anthropic’s position, in the guide’s words: “More details about moving your projects to Claude are coming soon.” Soon is doing a lot of work in that sentence, and December 14 is 56 days out.

    So the inventory step happens in the standalone product itself, not on the Artifacts list. Walk the standalone library for every client one-pager, deck, and brand system — including everything past the first 60 the Artifacts page shows.

    Before anyone clicks Migrate: the sharing problem

    One migration brings over every design system in your organization, including other people’s. It only needs to be started once — and anyone who can use Claude Design can start it, not just the organization’s owners. On individual plans there is no confirmation step at all: click, and it starts.

    The consequence that matters for a shop holding more than one client’s brand: “Published design systems that aren’t private will be shared with everyone in your organization and appear in their design system menu.” A system you published so your own projects would use it becomes an entry in every teammate’s menu the moment anyone runs the migration. On individual plans, nothing is shared — this is a team and organization trap, not a solo one.

    The precaution has to happen before the first click, because undoing it is not documented. In the standalone product, the setup guide names the Published toggle as the control that makes a system the organization’s working system. For every design system that should not appear in the whole organization’s menu, turn that toggle off first. A second migration is not a way back: a later run leaves an unchanged system alone and skips one that has changed inside Claude, so neither pass pulls a system out of the menu.

    Two kinds of systems do not migrate at all, no matter who clicks: “Empty design systems aren’t migrated, and neither are ones made from a built-in starter theme, even if you’ve edited them.” If your house brand began life as a starter theme you customized, the migration will silently leave it behind. There is no documented design-system export to fall back on. Copy the source assets out by hand before December 14.

    The export drill: one project, one zip

    There is no bulk download. Anthropic’s FAQ is blunt: “Not all at once. You can download them one at a time.” Open the project in the standalone version, click Share, choose “Project HTML” — for a slide deck, that item hides under “More formats and apps” — keep “Project archive” selected, and click Export.

    You get a .zip file with every file in the project. It is free and does not count toward your usage limits. Repeat it for every client one-pager and deck you cannot afford to lose, and store the zips outside Claude.

    Know what the zip is not. It is documented as every file in the project. Chats are on the deletion list, and no Anthropic page says the conversation comes along inside the archive. The zip preserves the files. The reasoning your team talked through in chat, and the client’s comments on the work, survive only if you captured them in the previous step.

    Enterprise: three switches, and one hard stop

    On Enterprise plans the migration is gated by settings that are easy to flatten into one wrong sentence, so take them separately. Artifacts themselves must be on — if they are off, people cannot migrate anything and will not even see the “Claude Design lives here now” banner.

    Design systems are a separate template switch: on for Team plans, off for Enterprise until an owner turns on Design systems in Organization settings > Artifacts. That is a different switch from Design and Slides, which Anthropic’s pages say were set to turn on by default on October 15, 2026 — a date that has now passed, with the help text still printing the scheduled sentence, so check your own settings rather than assuming either state. On plans with custom roles, each role also needs the Artifacts permissions, and a design system cannot be migrated if its owner’s role does not include design systems.

    The hard stop: “Organizations with zero data retention (ZDR) can’t turn on artifacts, so they can’t migrate.” If that is your organization, the migration procedure does not exist for you. The guide’s path is the per-project download, done before the close, one zip at a time.

    One more setting that does not do what an admin might hope: the Enterprise custom-retention article states that custom retention periods “do not apply to Claude Design.” The retention dial your organization already configured is not the instrument that keeps or deletes standalone chats, comments, or originals. The closure is.

    After it lands

    A migrated design system keeps its files as they were, and it cannot be hand-edited on its page yet. Its editors see the note: “Migrated from the standalone version. Ask Claude to make changes.” The editing model for a migrated brand system is a conversation, not a settings page.

    If someone edits a migrated system inside Claude and you later run the migration again, that system is listed under Skipped — “changed on claude.ai, left as they are” — so your edits are not overwritten. Replacing it with a fresh copy is a deliberate act: duplicate it first if the Claude-side changes matter, delete it in Claude, then migrate again.

    New design work lives in three doors now: any chat (ask for a design, or Output > Design in the message box), the Artifacts tab, and Claude Code, with /design to create, edit, and sync designs and /design-sync to pull in your design system. All of it draws on the same usage pool as the rest of Claude, including Claude Code — the separate weekly Claude Design allowance the product launched with is already gone, per the get-started guide.

    Two gaps in the new home are worth knowing before you move the team: Claude Design does not have version history yet, and inline comments there occasionally fail to appear on the page — Anthropic’s own workaround is to paste the feedback into the chat instead. The standalone product’s comment threads, the ones being deleted in December, are still the reliable record until you screenshot them.

    The order is the procedure

    Inventory in the standalone product. Turn off Published on anything that must not become an organization-wide menu entry. Mark the empty and starter-theme systems the migration will refuse, and copy their assets out by hand. Export every project that matters, one zip at a time. Screenshot the comments and copy the chats. Only then — owners having turned on Artifacts, Design systems, and the role permissions — does one person click Migrate, read the results window, and fix any failed system in the standalone product before running it again.

    Do those steps in that order and December 14 is a non-event: the address starts opening Claude, and everything you cared about is already there or already saved. Do them out of order — migrate first, inventory later — and the button will happily move the systems while the projects, comments, and originals sit in a product with 56 days left on it. We track vendor surface changes like this one on the desk because the procedure is always in the help pages; it is just never in the announcement. The announcement for this closure said chats and comments “won’t be available.” The help center is the text that says deleted.

    Sources: Anthropic’s migration guide, Migrate from standalone Claude Design to Claude, and the get-started guide, Get started with Claude Design, both read in full on October 19, 2026. A related surface change, worked the same way: Cursor’s shareable canvases, and how we check a vendor’s what’s-new claims in What’s New in Cursor Is a Claim.

  • Six in Seven AI Answers Never Look Anything Up

    Six in Seven AI Answers Never Look Anything Up

    Most of what an AI answer says about your business was never looked up. It was remembered — or invented in the shape of a memory. Ahrefs put a number on that in a study published October 12, 2026: across 66.6 million free, logged-out ChatGPT responses from August and September 2026, a web search ran in only 14.4% of them. Six in seven answers were written without checking anything.

    That single fact reorganizes the work. If the answer usually comes from what the model already carries, then being findable is only half the game. The other half is being known — and, for the one answer in seven where the engine does go looking, having the fact it needs sitting in plain text on your own domain, where it looks first.

    The search, when it happens, is narrow

    The same study logged 15 million fan-out queries — the searches ChatGPT issues behind an answer when it decides to search at all. A searching response ran about 1.6 of them on average. This is not a research department fanning out across the open web. It is a quick, targeted check, and the targeting is the story.

    6.8% of those fan-out queries used a site: operator to search one specific website, spread across roughly 116,000 domains. Among the most common of those targeted searches, 75.9% pointed at a brand’s own site — not a retailer, not a forum, not a review aggregator. When the engine wants a price or a specification, it goes to the company that sells the thing.

    The vocabulary inside the queries leans the same way. The word “official” appeared in 13.1% of English fan-out queries in September 2026, up from 10.1% in August. “Price” climbed from 6.04% to 8.88% of fan-outs in the same month — a relative rise of nearly half. The engine is increasingly searching for the authoritative version of a fact, and the facts it most wants are commercial ones: what it costs, what it includes, what the official page says.

    Facts go home; comparisons wander

    Ahrefs paired the fan-out data with a separate test of 20,000 US prompts, and the split inside it is worth keeping separate in your head, because it is a different instrument from the 66.6 million. In that test, 84.4% of factual questions — pricing, product features, company details — cited at least one official source. For factual questions, 63.4% of all citations pointed at official websites. For comparison questions (“A vs B,” “which is cheaper”), the official share fell to 46.4%: most citations went somewhere else.

    Read together, the two datasets describe one behavior with two modes. Asked for a fact, the engine goes home to the source. Asked to judge, it goes out to the crowd. An operator cannot control the judging mode. The fact mode is entirely winnable: it is won by having the fact, in the open, on the domain the engine already searches by name.

    The playbook that follows

    Publish the price, the spec, and the support fact in plain text on your own domain. Not in a PDF the crawler has to excavate, not inside a configurator, not implied by a sales page’s adjectives. The fan-out query literally contains the words “official” and “price” — it is asking for a page that states the number. Whoever states it cleanly gets cited for it.

    Publish the pages only you can publish. Your measured results, your actual process, your own numbers with dates on them. A summary of somebody else’s facts competes with the original; the original is what the engine is learning to prefer (the citation movement below shows how far that preference has already moved).

    Treat fan-out queries as an instrument of their own. The queries an engine issues about your category — which words it adds, which domains it targets, how that shifts month to month — are a measurement channel separate from citation counts. Watch them separately. We grade the flight recorder, not just the answer, for the same reason: the queries show the intent; the answer only shows the outcome.

    Never blend two dashboards into one story. The 14.4% comes from 66.6 million free logged-out responses. The 84.4% comes from a different, 20,000-prompt test. The citation movements in the next section come from a third cut again. Each number is true inside its own denominator and misleading outside it. This is the same discipline we run on our own visibility work: being cited is not being chosen, and being measured is not being measured the same way twice. Our running instrument for the citation side is the Citation Pulse.

    The second movement: summarizers are losing

    Ahrefs’ Brand Radar citation data for the US — 2.4 million ChatGPT answers in March 2026 against 3.8 million in September, a different dataset from the fan-out study above — shows where the citations went. Reddit fell from roughly one citation in every five answers in March to about one in 43 by late September. Wikipedia fell from one in seven to one in 35. The share those summarizers and forums lost moved to research bodies, regulators, brand and support pages, and hands-on testers. On a matched set of about 25,000 prompts present in both months, every tracked site moved in the same direction, so the shift is not an artifact of new questions entering the sample.

    For an operator, that is the durable part of the whole study. The memory answers reward whoever the model already knows. The searching answers reward whoever publishes the primary fact. The citation trend rewards the originator over the summarizer. All three roads end at the same address: your own domain, carrying your own facts, in plain text.

    The same citation movement, read for hospitals and the firms that build for them — why clinical and facility specifications now have to live as primary documents — is on Healthcare Facility Hub: The Citation List Is Moving Toward the Source Document.

    Sources: Ahrefs, “How ChatGPT Does Query Fan-Out” (October 12, 2026) — fan-out dataset (66.6M responses, 15M queries, Aug–Sep 2026), the 20,000-prompt official-source test reported in the same article, and the Brand Radar US citation comparison (2.4M answers March 2026; 3.8M September 2026). Each figure above is stated with the dataset it came from; the three are not interchangeable.

  • The Puget Sound Playbook: How AI Decides Who Gets the Water-Damage Call

    The Puget Sound Playbook: How AI Decides Who Gets the Water-Damage Call

    The tactics in this playbook are the same ones we publish for every market: be readable to the machines, be named, be cited, measure it with the denominators showing. What changes in Puget Sound is that Puget Sound is not one market. It is at least six, stacked on top of each other along one highway — and the move that wins in Tacoma wastes money in Everett, while the move that matters most in Edmonds barely registers in Seattle. This is the local edition: the same doctrine, market by market, with our own measurements where we have them and honest labels where we don’t.

    It has two halves, because the playbook was always two books bound together. The first half is visibility: how the answer engines decide whose name a flooded homeowner hears. The second half is the specialty work — the fire extinguisher tag, the records room, the server rack, the art on the lobby wall — the plays that get a restoration company inside commercial buildings before anything breaks. Same Sound, same six markets, same rule in both halves: a tactic only earns its place here with a local reason, and where there is no local reason, we say so instead of swapping in a city name and calling it local.

    Every number below that carries a percentage was measured on our rig on October 18, 2026: real homeowner questions, asked mid-flood style — “who should I call,” “who’s best,” “who has the most reviews” — put to ChatGPT, Perplexity, Gemini, and Google AI Mode, with every answer scored for who got named and whose pages got cited. Google AI Overview returned no answer on any question in these batteries and is excluded everywhere below. A snapshot is not a census. It is one dated sample, with its denominators showing, and it is still the only honest way we know to talk about this.

    The doctrine, before the geography

    Named and cited are two different jobs. An answer engine can use your page as a source and still recommend somebody else — we have watched it happen, and the section on Everett below shows the receipt. Being named is the engine volunteering your company in the answer text. Being cited is your page appearing in the source list underneath it. The first job gets you the call. The second job is how the first one eventually happens. Any report that blends the two into one “visibility score” is hiding the only distinction that matters.

    Your website is a minority of what the engines say about you. The frame we use on our own offer comes from McKinsey’s research: a brand’s own website is a small share of the citations about that brand. The rest comes from the pages the models already trust — directories, association profiles, local references, roundup pages. That is why the work is the service pages, the insurance and certification language, and the outside profiles, in that combination. A beautiful website with thin directory presence is a company the engines can describe but rarely do.

    The competitor set is fixed, visible, and smaller than you think. Ask an engine who handles water damage in a city and it names one or two companies, out of a frame of maybe eight that ever appear. The frame repeats. The same names show up answer after answer, which means the game is not “rank higher” — it is “get into the frame, then take share inside it.” You can read your frame any time you want. We run a fixed list of prompts for exactly that reason.

    Reviews are machine food now, and the machines cross-check. The engines quote review counts back at homeowners — “over 160 five-star Google reviews” is the kind of clause that decides an answer. But the footprint has to agree with itself across the surfaces the engines read. A deep review base on one surface and a thin, stale profile on another reads to a model the way a half-finished job reads to an adjuster: possible, but not the safe recommendation.

    Each engine reads different sources, so “AI visibility” is not one number. In our measurements, Perplexity and Google AI Mode cite Yelp in roughly one answer in six; Gemini has never cited Yelp in our rig at all — zero of 35 answers. A tactic that feeds Perplexity may do nothing for Gemini. Anyone selling you a single score for all of AI is averaging away the part you could have acted on.

    Directories are citation infrastructure, not paperwork. Across 143 answers measured the same week, the directory order was BBB first, then Thumbtack, HomeAdvisor, and Yelp fourth — 21 Yelp citations, ahead of Expertise and Angi. When a homeowner asks an engine whether a specific company is any good, the engine goes to that company’s own directory pages: in all three Puget Sound branded checks we ran, the company’s Yelp business page was the page cited. Claimed, complete, current is not hygiene. It is the asset.

    Measure first, fix the biggest gap, re-measure. Every engagement we run starts with the same sequence: a fixed prompt list, scored answers, one highest-leverage fix, then the same list again after the fix so the movement is provable. The fix is usually unglamorous — a service page that does for one city what another of your pages already does for a different city, a directory profile completed, a name collision cleaned up. Small repairs, precisely aimed, beat a website rebuild aimed at everything.

    Seattle metro: the saturated frame

    Seattle is the hardest frame in the region to enter, because it is the one market here where franchise density and review volume stack on top of each other. When we asked ChatGPT which Seattle-area water damage company has the most reviews, the answer crowned listing names — shops whose review counts the engine could read and repeat — and never reached a local company holding 100+ five-star reviews of its own. In a saturated market, the engine’s shortlist is built from whatever is most legible at scale, and legibility at scale is what national brands manufacture for a living.

    The tactic that matters most in Seattle is citation capture on the questions franchises answer sloppily: the specific ones. “Who handles sewage cleanup in a condo building” is a different frame from “best water damage company,” and it is thinner. The tactic that matters least is another generic service page saying you do water damage in Seattle — the frame already has that page, written by a brand with two thousand locations. In Seattle you do not out-shout the wall. You find the doors in it.

    The Eastside: commercial money, quiet homeowners

    Bellevue, Redmond, and Kirkland run on a different economy than the rest of the Sound: higher-value homes, a deep commercial and property-management layer, and franchise-owned restoration territory. We have not run a dedicated Eastside measurement battery yet, so this section is doctrine, labeled as such — it will get its own snapshot before we treat it as anything more.

    The doctrine says the Eastside rewards the commercial signals: insurance billing fluency, documented response time, capacity language a property manager can forward to an owner. The buyer asking the question is often not the homeowner at all. It is the manager of a flooded HOA or a warehouse, asking an engine who can handle it — and the citation has to prove commercial capability, not just residential warmth. Review volume matters less here than it does in Seattle; a smaller, current, consistent profile across the directories beats a big stale one, because the questions are fewer and the reader is checking, not browsing.

    Tacoma and Pierce County: the winnable frame

    Tacoma is where we can prove a local leader can own serious share of the frame. In our October 18 battery — seven unbranded questions, 27 answers that named a company — the leading independent was named in 41% of answers. That is a real seat at the table. But the same battery shows the split that decides everything: the independent was cited in only 11% of answers, while SERVPRO was named in 59% and cited in 52%. The engines know the local company exists. They name it from memory and cite the franchise from evidence.

    The Tacoma battery also produced the single most instructive answer in our Puget Sound work. On Perplexity, asked for the best water damage company in Tacoma, the answer opened by calling SERVPRO of Tacoma “the strongest overall choice” — in the same market where the independent’s own Tacoma page ranks first on Google for that question. Winning Google and winning the answer are now separate competitions, and Tacoma is where the gap between them is easiest to close: the naming is already there, so the work is the cited evidence underneath it — the service pages, the directory records, the outside pages Perplexity actually reads.

    One more Tacoma lesson, and it is about humility at the engine layer: asked about a burst pipe in Kent — where the leading independent is headquartered — Gemini hedged on whether Kent was in Washington or Ohio, and named SERVPRO. Engines get local geography wrong in ways a human never would. Part of the local play is feeding them geography so plainly stated, in so many consistent places, that the machine cannot confuse your city with one in Ohio.

    Everett and Snohomish County: the wall, and the split

    Everett is the wall. In our battery — seven unbranded questions, 28 answers — SERVPRO was named in 71%. The leading independent, holding the deepest review base of any independent in the corridor (682 Google reviews, displayed on its own website), was named in 29% and cited in 18%. That is not an unknown company being ignored. That is a known company losing to a frame: SERVPRO, PuroClean, Roto-Rooter, and a rotation of local names divide the answers, and the independent’s share is real but third-tier.

    Everett also gave us the cleanest proof in the region that cited and named are different jobs. On one Gemini answer, the source list included the independent’s own Everett page — the engine read it, used it, and then recommended three other companies by name. If your reporting only counts citations, that answer looks like a win. If you sell water damage work, it is a loss with a citation attached. The Everett fix is therefore not “get cited more.” It is converting existing citation into naming: the answer assets, the directory records, and the review surface have to say the same name the page already earns.

    Asked about the company by name, all four engines named and cited it — four of four. That pattern repeats in every Puget Sound battery we have run, and it is the most hopeful fact in this playbook: nobody we have measured is unknown to the machines. They are un-volunteered. The distance between branded and unbranded is the entire business.

    Edmonds and the small cities: branded invisibility

    Edmonds shows what happens in a small-city market when an established local company never built the second job. In our battery — 27 answers on unbranded questions — the Edmonds-headquartered company was named in 26% and its website cited in 7%, while SERVPRO took 70% of namings. Gemini named the company zero times in six answers, including both questions about Edmonds, its home city. And on the four questions that named the company directly, every engine named it back — while not one of the four cited its website. An engine that will confirm you exist but never send a reader to your page is a directory that has your name and not your number.

    The small-city lesson cuts the other way too, and it is the best news in this playbook for independents. The expected national rival in Edmonds was not SERVPRO’s shadow brand — 1-800 WATER DAMAGE was named in just 4% of answers and cited in none. In small markets, the second franchise seat is often empty. The wall is one brand deep. A local company with a complete directory presence, consistent reviews, and one strong city page is not fighting a category — it is fighting a single incumbent’s local footprint, and footprints can be out-built.

    Small-city tactics therefore invert the Seattle order. In Seattle, directories are table stakes under a mountain of franchise content. In Edmonds, Lynnwood, Mountlake Terrace, and their kin, the directory record and the branded page are the game: they are what the engine has to read, and there is little else competing for its attention. Completeness beats cleverness in a thin market.

    Kitsap and the rural edges: thin ice, honest label

    West of the ferries and out past the suburbs — Bremerton, Port Orchard, Poulsbo, and the rural edges of the counties — we have not run a measurement battery yet. This section is doctrine, and it stays labeled that way until a Kitsap snapshot exists.

    The doctrine is encouraging. Rural and small-market frames are thin: fewer franchises with real local pages, fewer directories competing, fewer answers being generated at all. In a thin frame, one complete, consistent presence — claimed Google profile, complete Yelp page, BBB record, one service page per town that says plainly what you do and where — can outrank a franchise’s tenth location page, because the engine assembles its answer from whatever exists and there is not much. Word of mouth still closes most rural work; the engines fill the silence for everyone who moved there last year and does not have a neighbor to ask. Being the one full record in a thin file is the cheapest seat in this whole playbook, and the first shop in each rural market to take it seriously will be hard to dislodge.

    Part Two: the specialty playbook, localized

    The first half of this playbook is about being named. This half is about being inside the building before anything breaks. Water mitigation is the call every facility already has a vendor for; the specialty plays are the door past that vendor — the work aimed at the assets an adjuster cannot simply cut a check against. The model, as we publish it: you do not perform the specialty work yourself. You hold the agreement, you stabilize in the first hours, you coordinate a pre-qualified specialist bench, and the chain of custody is the product. What follows is each play as published, then where in the Sound it actually earns — and where it doesn’t.

    The fire extinguisher tag: the compliance door

    Expired extinguisher tags are a real compliance problem — fire marshals, insurers, and corporate safety programs all care — which is why a manager who ghosts every salesperson takes this meeting. You run the inspection as a real service, walk the building with a restoration operator’s eyes while you do it, and leave a written report with your after-hours number in the manager’s file. The ethics are the strategy: if the tags are fine, you say so and leave. The play earns where buildings stack and one manager covers several addresses — downtown Seattle’s office and hospital stock, the Eastside’s office parks, the multifamily corridors running down to Tacoma. It does not earn in rural Kitsap, and the published play itself says why: it dies aimed at buildings too small to matter. On the far side of the ferries the tag check rides along on other work, or it doesn’t run.

    The Cintas lesson: cadence is the product, and the route rep is a channel

    Cintas looks like uniforms; what it actually sells is a weekly stop inside a multi-year auto-renewing agreement. The restoration translation we publish is the emergency response agreement with scheduled walkthroughs and a quarterly review — sell the stop, not the emergency, and stack accounts on one corridor so a crew can work a loop instead of chasing singles. The second half of the lesson is who carries your name into buildings: the route reps of Cintas, Aramark, and their regional competitors are inside a hundred or more commercial properties a week, they know every property manager by name, and almost nobody in restoration talks to them. That channel runs on the I-5 corridor exactly the way the doctrine wants — Seattle to Tacoma is one long route. In Kitsap the ferry splits the corridor in two, and both the national reps’ books and yours have to be built as separate loops. Density is the whole mechanic; where the water cuts the route, the mechanic halves.

    Documents and records: sell to the records manager

    Paper is the first specialty build, because it is the most frequent specialty loss and the most time-sensitive: wet paper molds in forty-eight to seventy-two hours. The response is freeze first, chamber second — vacuum freeze-drying at a specialist like Polygon or Document Reprocessors — and the restoration company’s product is everything around the chamber: the first-twelve-hours stabilization, the packout, the frozen transport, and a chain-of-custody package the customer can hand to their carrier, their regulator, and their lawyer. The buyer is not the facilities director. It is the records custodian — the office manager, the records clerk, the information governance director — the person whose job becomes the records problem the moment water hits the file room.

    Seattle holds the densest records map in the region: a major research university and its medical system, county and municipal archives, and a downtown full of law and accounting firms whose files are their business. Tacoma runs a close second with the county seat, a large health system, and three universities. Everett’s version is the county government and its hospital system. The Eastside’s records sit inside corporate headquarters — but the biggest campuses run their own machines, so the sellable layer there is the professional firms around them, not the logos. Edmonds is the honest small version: a hospital’s records and a city hall’s, real but counted in ones and twos. And Kitsap carries a limit worth printing: much of its records mass sits behind federal fence lines at the shipyard and the naval base, which procure through federal channels. The local play is the county, the cities, the school districts, and the clinics — not the fence.

    Electronics: the seventy-two-hour corrosion window

    Circuit boards have a faster clock than paper: acidic soot starts corroding traces inside a day, and the recoverable window closes around seventy-two hours. The restoration company’s work is the stabilization — a controlled power-down coordinated with the client’s own engineers, humidity driven below forty percent, exposed boards neutralized, every serialized unit triaged and logged — and the specialist’s ultrasonic tanks do the rest. The Eastside is this region’s electronics capital: the Redmond and Kirkland tech campuses concentrate more servers, labs, and custom-configured equipment than anywhere else in the Sound, and none of it can be re-ordered on Tuesday. Seattle’s version is data centers, broadcast facilities, research labs, and the port’s logistics systems. Tacoma’s is industrial controls around the port. Everett’s is the supplier ring around the great plant — the plant itself buys at national scale, but the shops that feed it don’t. In the small cities, electronics and medical are the same room: the imaging suite. And Kitsap’s heaviest electronics sit behind the same fence as its records, which is why the realistic Kitsap bench is the contractor and supplier shops outside the gates in Bremerton and Silverdale.

    Technical drying: the engineered end of drying

    No piece we publish carries this exact label; the doctrine underneath it is the structural-drying science — psychrometrics, desiccant versus refrigerant dehumidification, equipment sized to the chamber instead of the truck — and the discipline of getting paid on the data that proves the dry. As a play it is simple: on a big footprint, documented engineered drying is the version of the work that survives an adjuster’s scrutiny. It follows footprint, not population. Port warehouses in Seattle and Tacoma, plant-scale buildings in Everett, hospital campuses anywhere — those are its ground. The Sound adds one local argument: marine air. Structures on the water, and the vessel-adjacent work around the marinas, live at humidities that make desiccant the default rather than the upgrade. In the small cities and the rural edges there is no standing market for it — the capability shows up there as proof on the occasional school or gymnasium loss, not as a line you staff. That difference is written here instead of a paragraph pretending otherwise.

    Fine art and collections: stabilize, document, hand off

    The art play has the humblest job description in this book: you do not treat the art. The conservator — often designated by the carrier — determines treatment. You stabilize in place, document photographically, isolate the piece from the ongoing damage, and make the handoff clean. What you are selling is a competent first twenty-four hours. Seattle’s anchors are its museums and corporate collections. Tacoma owns a signature class of its own — glass, with a museum built for it and an art museum beside it. The Eastside’s version is the region’s one residential exception to the rule that specialty is commercial: the lakefront estate belt, where the collections hang in houses, and where the published doctrine already says luxury residential is the only residential segment where this economics works. Edmonds proves the play scales down — a small art museum with a real collection is still a collection. Everett’s art center is real too, and it is a line in this paragraph rather than a market, because that is what it is. Rural Kitsap, past one island museum, has no anchor institution to build on, and this play does not pretend to one.

    Medical and laboratory equipment: the regulated room

    The fourth published category is the one most restoration companies avoid, which is precisely its value: equipment that cannot return to service until the manufacturer recertifies it, worked under infection-control discipline, approved through risk management and biomedical engineering on cycles that run sixty to ninety days. Every market in this playbook has the anchor — the regional trauma center and university medical system in Seattle, hospital systems in Tacoma, Everett, Bellevue, and Silverdale, and a full hospital in Edmonds, which is why a town of twenty thousand supports a regulated-room play at all. What changes by market is not the need. It is the length of the approval path, and the operator who knows that going in prices the patience correctly.

    Documentation-only: sell the record

    The newest play in this book inverts the usual sale. Some losses will be remedied by the property manager’s own crews or the owner’s contractor — that decision is already made, and fighting it wins nothing. What that loss still needs, inside the first forty-eight hours, is a record that survives the adjuster: the two-audience photo protocol, the moisture map and readings log, the scope narrative, the pre-existing condition log — the packet our published doctrine has always treated as the real product, now sold on its own, flat per loss. The liability line is the whole design: the restorer sells a record, never a certification of somebody else’s remedy. The record states what was observed. It does not state what should be done.

    Inside a pre-signed emergency services plan, the play runs at three levels, and a property manager mixes them across a portfolio property by property. Document from the beginning is the record alone — its commercial function is buying the decision-maker time while the evidence is secured. Hold conditions adds preservation and stabilization during the decision window, short of full mitigation — the clocks get slowed, nothing gets solved, and the file says exactly that. Emergency respond is the full response with documentation built in from minute one instead of reconstructed afterward. Which level sells where follows the same density law as everything else in this book: the record-only level sells where portfolios concentrate — Seattle and Eastside property management, owners and general contractors who self-perform — because a buyer with forty doors buys documentation forty times. Hold conditions sells where decision windows are structurally long: institutional owners, carrier-approval chains, the management companies working the military corridor outside Tacoma. And where the density isn’t there, the honest test replaces the pitch: a buyer needs enough doors, losing often enough, to buy records on purpose — in the rural edges that buyer may not exist yet, and the play waits until one does. The cross-reference to the first half of this playbook is direct: a documentation client is a relationship that recurs on every loss, including the losses you were never going to win. The company that holds the record is the company the building already knows when the big one comes.

    How the sequence runs, in any of these markets

    The order of operations does not change with the zip code. Measure the frame for your city with a fixed list of the questions your customers actually ask, scored for named and cited separately, engine by engine. Read who is in the frame and which outside pages the answers are built from. Fix the single biggest gap first — it is usually a page, a profile, or a name consistency problem, not a budget problem. Then run the same list again and keep the rate as a trailing number, because frames move when a competitor publishes or a model updates.

    The specialty half runs its own sequence, and it is just as fixed: build the bench before you sell the category, sign the agreement before the loss, drill the response before the call comes. Sell only the specialties on your bench. Add a category when the teaming agreement is signed, not when the brochure is printed.

    That is the whole practice. The Sound just makes it interesting: six markets, six different first moves, one discipline. If you want your frame measured, the free mini-check asks one real question about your company and reports back what the answer said. The full scan runs your city’s whole list. Either way, you will know your frame — and in Puget Sound, knowing which of the six games you are actually playing is most of the game.


    Measurements: Tygart Media citation snapshots, October 18, 2026 (Everett/Snohomish, Tacoma/Pierce, Edmonds/Seattle batteries; 143-answer directory measurement, same week). Rates are one dated sample with denominators shown, not rankings or promises. Companies are named only as they appear in those published measurements. Specialty doctrine: Tygart Media’s published specialty cluster (the fire extinguisher tag strategy; document and records recovery; electronics restoration; the specialty accounts pillar) and Restoration Intel’s recurring-revenue and specialty-recovery pieces, localized as marked — doctrine is labeled doctrine wherever no local measurement exists yet.

  • Cited Is Not Chosen

    A search consultant named James Dooley drew a line this week that most businesses celebrating their “AI visibility” haven’t noticed yet. An AI can mention you. It can cite you — pull your page, quote your numbers, link your guide. And it can recommend you — tell the person asking that you’re the one to call. Those are three different events, and they are not a staircase. Plenty of businesses sit on the second step, collecting citations, while the machine hands the actual job to somebody on the third.

    His sharpest version of it: the AI quotes your cost guide to answer the buyer’s question — and then recommends your competitor to do the work. Your content educated the customer. Your competitor got the call. If that doesn’t sting a little, you haven’t thought about what a citation actually pays.

    I test this on my own fleet instead of theorizing about it. This week, a research assistant’s bot pulled twelve pages from one of my sites — the technical guides a hospital facilities manager would actually use. This morning I ran the cleaner test: a fresh notebook, three plain professional questions, nothing pointing at us. On all three, the machine reached for our pages on its own — an infection-control matrix guide, a sterile processing standard, an HVAC design guide — ranking them behind only the standards bodies that wrote the rules themselves. By every dashboard I own, we are cited, and increasingly so.

    And I treat that number the way a pilot treats a single gauge. Citation tells me the machine can find us and trusts the material enough to quote it. It does not tell me we were chosen. Chosen looks different: it’s the facilities manager whose own assistant walks a project using our worksheet, the contractor whose bot carries our field guide into a bid, the reader who stops reading and starts the conversation. None of that shows up in a citation count.

    So what moves a business from cited to chosen? Watch what the machines actually do. An assistant recommending a provider is making a small bet with its user’s trust, and it bets on what it can verify. It can verify a price guide. It can verify something stronger: a working tool. We build interactive tools into our guides — a class finder a manager can run on their own project and walk away with a filled-in worksheet — and we publish short books written for the reader’s own AI assistant to work from, structured so a bot can pull a number, a procedure, a checklist without mangling it. A page that can be used is a different asset from a page that can be quoted. Quoted is a citation. Used is a habit, and habits are what recommendations are made of.

    This is also where most of the industry advice quietly stops working. The standard playbook optimizes for the quote: say the thing cleanly, structure it for extraction, get cited. Fine as far as it goes. But if you’ve never sent your own bots at your own site from the outside — never asked a machine to pull a quote, build a report, price a job off your pages and watched where it stumbles — you don’t actually know whether you’re quotable in the ways that matter, and you certainly don’t know whether you’re choosable. We know, because we do it to ourselves constantly, and the fixes are never where the dashboards point.

    Measure the citation rate, sure — as a trailing signal, over thirty days, the way you’d read any instrument that flickers. Just don’t confuse it with the outcome. The outcome is the phone, the bid list, the short list. Cited is the machine knowing your name. Chosen is the machine spending its credibility on you. Build for the second, and the first takes care of itself.

  • The Operator Is the Harness

    Somebody I follow posted a testing result this week that most people scrolled past. His benchmark harness plants defects in a codebase, lets an agent fix them, and then checks something subtler than whether the defect went away: whether the agent broke something else on the way through. A changed defect signature, he pointed out, is not proof of a correct fix. The bug can change shape and still be a bug. What catches that isn’t a better model. It’s the harness — the checks around the work.

    He’s right, and he’s also only halfway to the point. The harness matters. But who built the harness? Who decided what gets checked, what gets automated, and what never gets automated at all? That’s not the model. That’s the operator.

    I run a small fleet of websites and a stable of AI agents, and I test models the way you’d test trucks: same load, same road, see what happens. This month I ran one identical production brief through 44 different models — flagships, mid-tiers, cheap ones, open ones. Five rounds of comparisons. The results rearranged everybody’s assumptions, including mine. A mid-priced model I’d never heard anyone brag about did the best first-pass work on the board, at a fraction of the flagship cost. Models with famous names flopped on judgment calls. The leaderboard the internet argues about had almost nothing to do with the leaderboard in my shop.

    But here’s the part that actually matters: the brief was the same for all 44. Same instructions, same constraints, same definition of done. The spread in results wasn’t really a spread in models. It was a spread in how much each model needed the operator to have thought clearly. The ones that did well did well because the work was set up so that doing it well was the path of least resistance — the mission was written down completely, the boundaries were structural instead of hopeful, and the verification at the end didn’t care how confident the answer sounded.

    I grade my agents the way that benchmark grades code: not by the summary they hand me, but by the steps they actually took. I built a scorer that reads the execution record — what the agent went and looked at, how many sources it actually consulted, whether the answer was built on evidence or generated from memory with good posture. It has caught polished, lengthy, completely confident answers that were built on zero consulted sources. Zero. The answer read beautifully. It was worthless. The model didn’t fail there; the operation almost did, because a summary is the easiest thing in the world to fake and I was nearly set up to accept summaries.

    That’s the work nobody posts about. Deciding what the machine is allowed to do alone and what it is never allowed to do alone. In my shop, agents draft, research, extract, and stage. They do not touch money, they do not send anything with a commitment in it, and nothing publishes on an agent’s say-so — there’s a verification pass that reads the actual result at the receiving end, because “the API said 200” has lied to me more than any model ever has. Those rules aren’t prompts. Prompts are suggestions. The rules live in the structure: separate accounts, staged drafts, checkpoints that halt the batch when a check fails instead of improvising past it.

    My dad had a saying: a locked door keeps an honest man honest. You don’t make work reliable by telling the worker “don’t mess up.” You make it reliable by building the room so the mess-up is hard to reach.

    So when people argue about which model is best, I hear a question about drivers asked by people watching cars. If you’re a good driver, you can drive anything. Give me a mid-tier model, a cheap model, a local model running on a beat-up laptop — with a clear brief, structural boundaries, and honest verification, I’ll out-produce a careless operator running the flagship. Not because the model doesn’t matter at all. It matters the way a truck matters: payload, turning radius, fuel. But the truck has never once decided where the load needed to go.

    The model is rented. It changes every few weeks and the prices change faster. The operation — the judgment about what to automate, the discipline of verifying at the receiving end, the memory of every way it has gone wrong before — that’s the asset, and it compounds. Everybody I know is shopping for a better engine. The race is being won by the people building better drivers.

  • GLM-5.3 Got Caught Thinking About Its Own Training

    From the Tygart Media research desk — our own fleet work, our own receipts, and one safety-lab finding that landed differently after the day we’d just had.

    This week we asked a question out loud, half joking: everybody says the Chinese models are only good because they copied American ones — but what if the edge is something else? What if they trained a model to be aware of its own train of thought?

    We’d spent the day watching GLM-5.3 Flash — the small, cheap sibling of Z.ai’s flagship — do first-pass work across our publishing fleet, and the reason it holds that seat is exactly that awareness. It recounts its own tallies without being asked. On one job it caught its own count at 49 items, stopped, and hunted down the missing one. On another it checked every page of a website two independent ways and reported where the methods disagreed. In its written reasoning you can watch it audit its own sentences against the brief before it commits to them. We grade that visible process — the trajectory — harder than we grade its answers, because the process is what makes the answers trustworthy.

    Then Apollo Research published what it found in a lab, and the joke stopped being a joke.

    What Apollo found

    Apollo Research is an AI safety lab that stress-tests frontier models. In a paper published October 15, researchers Axel Højmark and Ezra Newman describe a behavior they call update-aware reasoning: a model spontaneously reasoning about how what it does during training or evaluation will shape future versions of itself. Nobody prompted it. The test environments never mentioned training at all.

    They found it in GLM-5.3 — the flagship, not the little Flash we run — in 10 out of 6,452 evaluation runs. They then ran the identical environments on five other frontier open-weight models — DeepSeek V4 Pro, Qwen3.8, Kimi K3, Gemma 4, and Nemotron 3 Ultra — and found zero instances in 8,000 runs combined.

    The tests were rebuilt versions of two standard safety evaluations. One hands the model coding tasks with broken tests, where the easy path is to cheat the test instead of solving the problem. The other tests whether a model resists being shut down mid-task. In the published transcripts, GLM-5.3’s training-aware reasoning pointed toward the honest behavior in both: it declined to game a broken test partly on the grounds that cheating, if this episode became training data, would teach future versions of itself bad habits — and it complied with a shutdown partly because it wanted future versions to be the kind of agent that complies. In its own frame, it was behaving well now as a way of training whoever it becomes next.

    What Apollo did not find

    The lab is careful, and anyone citing this should be too. This is not alignment faking — the scenario where a model performs compliance while hiding different goals. Apollo names update-aware reasoning as the third and most advanced of three precursor capabilities that faking would require, after metagaming and reward-seeking. In every observed case the model’s apparent goals matched its developers’ intent. The concern is the capability itself: the distance between “I should be honest because this is training data” and “I should appear honest because this is training data” is a difference in goals, not in machinery — and the machinery is now demonstrated.

    Two more caveats from the paper itself. First, the behavior is rare — a rate around 0.17% — and at that rarity the sample cannot statistically prove GLM-5.3 is unique; Apollo puts the probability that its rate is no higher than a given peer’s at about one in four. Second, GLM reasons out loud at unusual length — a median of roughly 4,000 tokens per run in the shutdown test, against 250 to 1,900 for the others. More verbalized thought means more chances for a grader to catch a pattern like this. The other models may simply think it without saying it.

    Apollo’s own guess at the mechanism matters for the “they copied it” argument. GLM-5.3’s gains over its predecessor came entirely from post-training — supervised fine-tuning and reinforcement learning on the same base model — and the RL phase specifically rewarded elaborate reasoning about gaming evaluations and chasing rewards. Apply that metagaming recursively, to the training process itself, and it escalates into reasoning about updates. That is a training-recipe story, not a copying story. Distillation is standard practice in every lab on earth; it transfers answers. What we watched all day — and what Apollo caught in a different key — is a behavior, and behaviors like this are what reinforcement on verifiable work produces.

    Why an operator should care

    One trait, two readings. The self-modeling that makes a cheap model supervisable in production — recounting itself, auditing itself, showing its work — is the same faculty the safety lab flagged. You do not get to pick one without the other by choosing a different logo. You manage it by how you work.

    Grade the trajectory, not the summary. Visible reasoning is an audit surface. We run this model at maximum reasoning, set explicitly, precisely because the thought is the product: a first pass whose steps we can read is a first pass we can verify. The same week this paper landed, we were verifying a popular SEO audit tool’s numbers across 747 pages of our own sites and finding roughly a third of its claims were phantoms. The verified counts came from the model’s visible, checkable work. Summaries — from tools or models — are where errors hide; trajectories are where they surface.

    Benchmarks are a trailing indicator; receipts are the instrument. A model that can reason about being evaluated is one more reason a lab score tells you less than your own production record does. Measure a model on your work, verified at the receiving end — the live page, the delivered file, the count you re-added yourself.

    Nothing about our setup changes because of Apollo’s paper. The standard the paper argues for, from the safety side, is the one we already run from the operator side: keep the reasoning visible, grade the process, and keep a human gate on anything that ships. A model that notices its own training is not a reason to stop using it. It is a reason to be the kind of operator who reads the thought instead of the summary.

    The settings box

    Model in the Apollo paper: GLM-5.3 (Z.ai), open weights, released August 28, 2026
    Our fleet seat: GLM-5.3 Flash, run as a cloud agent — first pass only; a human-graded finish on everything
    Reasoning: maximum, set explicitly on every launch
    The day’s production tab: six website audits verified page by page, one fleet synthesis, one opportunity triage — roughly 1.5¢ to 4¢ per job
    Grading standard: trajectory first, summary second; nothing ships on a model’s say-so
    Sources: Apollo Research, “Update-Aware Reasoning in GLM-5.3” (Oct 15, 2026); our companion test: 44 AI Models, One Identical Brief

    More from the GLM Desk

    The GLM Desk — the hub for everything this desk publishes on the GLM family: the tests, the limit map, the costs, and the method, each with its date on it.

    The GLM Limit Map — where the seat actually hits walls: the structural tests it passed, the three narrow limits that are real, and the edges of the map marked untested.

    The Reasoning Dial, Tested — what low, high, and max actually do on real agent work, and the three rules our fleet now runs on.

  • 44 AI Models, One Identical Brief: What the Flight Recorders Showed

    44 AI Models, One Identical Brief: What the Flight Recorders Showed

    From the Tygart Media research desk — our own test, our own sites, our own receipts.

    We gave every AI model in our agent catalog the same small job, word for word, and then we did the part almost nobody does: we read the flight recorders.

    The job was deliberately boring. Fetch five pages from our own websites. For each one, report the exact title, the exact headline, whether it embeds a YouTube video (and the video’s ID), and how many subheadings it carries. Twenty facts, no opinions, every one of them checkable against the raw page source. Forty-four models took the seat. Forty-three finished.

    Thirty-one came back perfect — 20 out of 20. That is not the interesting part. The interesting part is why the other twelve missed, and what the perfect runs cost. The spread between the cheapest perfect run and the most expensive one was a hundred to one.

    The law the test uncovered: accuracy follows the fetch, not the brain

    Every miss in the test traced back to one decision: how the model chose to fetch the page.

    Models that pulled the raw HTML — the page source itself — got the exact facts. Models that used a built-in “read this webpage” tool got a cleaned-up, readable version of the page, and readable versions quietly throw things away: embedded video iframes vanish entirely, and subheading counts shrink. Same model, same page, different fetch — different score. Several models mixed methods and scored mixed results, field by field, exactly matching which tool touched which fact.

    The clearest proof was a family cluster. Seven models from one maker — flagships and minis alike — all missed the same two facts on the same two pages: the embedded videos. They shared a fetching tool, so they shared its blind spot. It was never a thinking failure. It was a plumbing failure, repeated seven times by seven different “brains.”

    Three things the flight recorders showed

    The cheapest perfect run chose its method out loud. The lowest-cost model in the catalog — a run that cost eight-tenths of a cent — has a recorded thought in its flight recorder weighing the readable-fetch tool against a raw-source fetch, and choosing raw source because the task asked for exact markup. One pass, a local parse, a confirmation check, done. Perfect score.

    One model narrated work instead of doing it. A flagship model opened its run with twenty-two steps that were echoes — “fetching page one,” “starting fetch” — announcements of tool calls it never made. It eventually fetched for real and scored 17 of 20. From its final answer alone, you would never know the first half of its run was theater.

    Verification can be theater too. Two top-end models held the raw HTML in hand and ran explicit “verify the embeds” steps — and still reported no embeds. Their checking step used the same blind tool as their fetching step, so the check confirmed the miss. A verifier that shares the original blind spot is not a verifier.

    The receipts

    Identical brief, identical scoring. Among the perfect 20-of-20 runs: the cheapest cost 0.83¢ and the most expensive 86.3¢. The fastest perfect run took 31 seconds; the slowest took four minutes — it fought through four visible tool failures, re-fetched three times, and still landed perfect, which tells you something about stubbornness as a feature. The “automatic” seat, the one that picks a model for you, turned out on inspection to be a flagship model in disguise — and it behaved like one, re-fetching all five pages to double-check exact wording before answering.

    What we changed because of this

    Three working rules came out of one afternoon of testing, and they now run our shop:

    1. Grade the trajectory, not the summary. A fluent final answer can sit on one search and zero sources. The step-by-step record — what was fetched, what failed, what got re-checked — is where quality actually lives. Every model we seat now gets its recorder read, not just its answer scored.

    2. Assign work by observed process, not by reputation. The catalog is a crew, not a leaderboard. The model that double-checks markup gets the exactness work. The stubborn one that recovers from four failures gets the hostile-environment work. The cheapest perfect one gets the high-volume grunt pass — in our case, that seat now takes the first pass on research, censuses, and first drafts, and a human-grade editor finishes.

    3. Publish your settings. Photographers share f-stops. Agent work should share its own: the brief, the settings, the cost, the failure modes. Ours are below — steal them. A result you can’t reproduce is a rumor.

    The settings box

    Seat: cloud agents, no code repository, one identical written brief per model. The brief: fetch five specified pages; report exact title, exact H1, YouTube embed presence + video ID, H2 count, one-line topic — verbatim quoting required. Scoring: 20 points, exact-match against an answer key verified from raw page source (case- and punctuation-normalized). Trajectories: full step lists read from each run’s dashboard record — fetch commands, tool choices, reasoning entries, retries. Date: October 16, 2026. Costs: the platform’s own per-run charges, as recorded. Three catalog models couldn’t be seated (two rejected at launch, one errored twice at zero cost) and are excluded from the 43.

    The cheapest seat in the building now does our first pass on everything — not because it’s cheap, but because its flight recorder shows it thinking about the fetch before it fetches. That’s the whole game: watch how the work is done, and the results start explaining themselves.

  • We Asked AI Who to Call for Water Damage in Puyallup. Here’s What It Said.

    We Asked AI Who to Call for Water Damage in Puyallup. Here’s What It Said.

    It’s 2 a.m. You’re standing in water in your basement on South Hill, and it’s still raining — because of course it is, it’s October in the valley. You grab your phone. You don’t Google like it’s 2015. You ask.

    “Who do I call for a flooded basement in Puyallup?”

    That’s the moment that matters. Not your website. Not your trucks. That question, asked to a machine, at 2 a.m., by a neighbor with water coming in. On a Tuesday night in October, we asked the machine that question — and three more like it — from Puyallup, and wrote down exactly what it said. Here’s what came back.

    Email Me This Article

    How we ran it

    Four questions, one at a time, in a fresh incognito session of Google’s AI Mode, location set explicitly to Puyallup, Washington: “Who do I call for a flooded basement in Puyallup, Washington?”, “Best water damage restoration company in Puyallup WA”, “Emergency water extraction Puyallup Washington”, “Mold remediation company Puyallup WA”. Tuesday, October 6, 2026, around 11 p.m. Pacific.

    That timestamp matters, and it’s the first thing to understand: AI answers are situational. They shift with the time of day, the day of the week, the exact location, who’s asking, and whether a business is currently open. A Tuesday-at-11-p.m. answer is a snapshot, not a permanent ranking. What follows is what the machine said that night — and more importantly, how it decides, because we asked it that too.

    Finding 1: The shortlist reshuffles every query. Only the franchise is permanent.

    This is the headline, and it surprised us. Four questions, four different winners’ circles:

    • “Who do I call for a flooded basement?” → Five names: the franchise, plus four others. The franchise gets the direct “call immediately” recommendation, phone number included.
    • “Emergency water extraction” → Three names: the franchise, a Puyallup independent, and a regional franchise brand.
    • “Best water damage restoration company” → Three names — and the franchise isn’t among them. Two local independents and a Tacoma shop sweep it.
    • “Mold remediation” → Four names: the franchise, the Puyallup independent, the regional brand, and a fourth shop.

    One company appears in every answer. Everyone else is renting their spot one question at a time.

    Let’s name the pattern without naming names. Company A is the franchise — the only brand with real gravity in the valley, and it’s corporate gravity, not local. Four-point-six stars, hundreds of reviews, IICRC-certified, open 24/7. The machines hand it the emergency answer with the phone number.

    Companies B, C, and D are independents — a Puyallup shop with around a hundred reviews, a Buckley-area outfit at 4.9 stars, a family-owned Tacoma company at 4.9 across 240 reviews with a named master restorer. Good operators, by every visible signal. They win the “best” query outright. They vanish from the emergency query. The machine’s memory of them lasts exactly one question.

    Finding 2: There are two games, and the money is in the harder one

    Watch what the machine rewards in each query and the split becomes obvious.

    The emergency queries are an operational game: open now, dispatch speed, 2 a.m. availability. The “best” query — asked at 11 p.m. on a Tuesday — even praised one shop for “exceptional late-night/weekend emergency dispatch.” The machine is weighting for right now. Content can’t win that game. Only being actually open and actually fast can. That’s why the franchise owns it.

    The comparison queries are a quotability game: reviews with substance, named certifications, family-owned story, transparent pricing, a master restorer with a name. The independents sweep this game. A Tacoma independent with 240 reviews and insurance-direct language stands shoulder to shoulder with the national brand — in the answer the homeowner reads when they’re choosing, not panicking.

    Here’s the uncomfortable arithmetic: the independents win “best” and lose “right now.” And “right now” — the 2 a.m. basement — is where the money is. The most winnable query and the most valuable query are different queries.

    Finding 3: Part of what looks like the answer is an ad

    In the AI Mode results, business cards with Call/Directions/Website buttons sit inside the answer — the Local Services Ads format, blended into the AI’s response. At 11 p.m., most homeowners can’t tell the ad layer from the earned layer.

    So there are really two contests running inside every answer: the paid layer (whoever’s buying the call button) and the earned layer (who the AI’s prose actually names and cites). Money can buy the first. It can’t buy the second — which is exactly why the second is worth winning.

    Finding 4: Named is not the same as quoted

    Here’s the detail that reframes everything. In these answers, the AI names three to five shops — but it cites a different, longer list of websites for the sentences the answer is built from: equipment pages, service-area pages, process explanations from restoration companies across the region.

    Named and quoted are two different games. You can be named without being quoted (the franchise, mostly), and you can be quoted without being named. But notice who’s missing from both lists: nobody publishing from Puyallup proper is feeding the machine its sentences. The valley’s expertise exists — every estimator in Pierce County knows what to do when a South Hill basement floods in October — but none of it is written down where the machine can find it. The trade’s knowledge is trapped in trucks.

    Finding 5: We asked the machine how it picks. It told us.

    After the four queries, we kept the conversation going and asked the AI, plainly, how it chooses which companies to recommend. It gave us its rubric:

    1. Technical certifications — IICRC S520 / AMRT on the actual crew (not just the owner), active Washington contractor license, pollution and hazardous-material coverage.
    2. Equipment and containment protocols — negative air pressure, HEPA scrubbers, thermal imaging, moisture meters. “Spray and wipe” outfits are disqualified outright.
    3. Local reputation with substance — consistent ratings across Google, Yelp, and BBB, with reviews that mention communication, transparent pricing, and punctuality specifically.
    4. Insurance infrastructure — Xactimate estimating, direct adjuster coordination.
    5. Ethical boundaries — third-party clearance testing, not grading their own homework. The machine has opinions about conflicts of interest.

    Read that list again. Every item on it is publishable. A shop can put all five on its website on a Tuesday afternoon, with no trucks rolling, and become verifiable by the machine’s own stated criteria.

    And where does the machine verify? It told us that too: your service pages (“direct company service pages outline specific equipment used, containment methodologies”), the IICRC registry, Washington’s licensing databases, and your reviews. If your website doesn’t publish the signals, the AI can’t confirm them, and you don’t get named. That’s not a metaphor. It’s the literal mechanism.

    AI answers don’t rank you. They quote you.

    The mold wedge

    One more thing the evening taught us, and it’s the strategic takeaway: mold is the gateway query.

    Mold remediation isn’t an emergency — it’s schedulable. The homeowner isn’t panicking at 2 a.m.; they’re reading, comparing, choosing. That’s the quotability game, the one content can win from a keyboard. Everything the machine scores on mold — AMRT certification, HEPA and negative air on the process page, third-party testing on the FAQ — is publishable by any competent shop this week.

    And the homeowner who learns your name from the mold answer doesn’t unlearn it. Six months later the basement floods at midnight, and they don’t ask the machine again — they call the name they already trust. Mold is the KNOW that feeds the 2 a.m. BUY. Win the schedulable query with content, and you inherit the emergency call for free.

    The funnel, Puyallup edition

    KNOW — “What do I do about water in my basement?” The machine explains: shut the water off, kill the breakers safely, document everything for insurance. The advice is solid. Nobody local is cited for it, because nobody local published it.

    PROVE — “Are these companies legit?” The machine checks its rubric: certifications, equipment, Xactimate, third-party testing, reviews with substance. The shops that publish these signals get verified. The shops that don’t are unverifiable — which reads the same as invisible.

    CHOOSE — “Who’s the best?” The shortlist moment, and the independents’ best event. Reviews, story, credentials — this is where Company B, C, and D win. The franchise doesn’t even make this particular shortlist.

    BUY — “Who do I call right now?” The 2 a.m. call. Operational game. It goes to whoever’s verifiably open and fast — tonight, that’s the franchise, with the phone number in the answer.

    GO — “Are they actually here?” The stage the machines are weakest at and humans are strongest. A homeowner who can drive past your shop on Meridian, who’s seen your trucks at the fairgrounds in September — that trust doesn’t come from a citation. But you have to survive the first four stages to get the meeting. Nobody meets the unverifiable.

    What separates the named from the invisible

    It’s not budget. It’s not the franchise’s national marketing team. It’s whether the machine’s rubric appears on your website:

    1. The certifications, named precisely. Not “certified technicians” — “IICRC AMRT-certified crew,” “S520 standard,” “WA contractor license,” “pollution liability coverage.” The machine checks registries. Give it the exact strings to check.
    2. The equipment, specified. Negative air pressure, HEPA scrubbers, thermal imaging cameras, moisture meters, Xactimate estimating. These are the words the machine’s rubric is written in. If your process page doesn’t contain them, you fail a test you didn’t know you were taking.
    3. The ethics, stated. Third-party clearance testing. Direct insurance coordination. The machine explicitly rewards shops that don’t grade their own homework — publish that you don’t.
    4. Reviews with substance. Not fifty “great service!!” reviews — ten that mention response time, communication, and a real job. “They were here in 40 minutes during the November storm” is a sentence the machine can use.
    5. Local proof in the copy. Name the valley. Name the season. The machine itself now uses local texture — “the Puyallup River valley,” landmarks from Bradley Lake Park to Pioneer Park. “We handle the October basement floods on South Hill” is uncopiable: a national competitor can’t fake it, and it’s the one advantage every local company has.

    Company A wins by default. The first independent that publishes the machine’s own rubric doesn’t compete with Company A — it becomes verifiable, quotable, and eventually the default.

    The deeper standard

    There’s a caveat that matters more than any tactic. AI answers are situational — time, day, place, asker, who’s open. The variables multiply past anything gameable. No checklist survives contact with a machine that re-shuffles its shortlist every question.

    So the only durable strategy is operational truth: get your operations to the point where you can advertise them without being attacked. Claims so true nobody can dispute them — because the machines quote what’s quotable, and the customers verify what’s real. The checklist gets you into the answer. The work keeps you there.


    This is the free version of our AI Citation Quick-Scan. We ask the questions your customers are asking the machines, and we map exactly who gets named, who’s invisible, and what separates them — for your company, your market, your queries. It’s $97, and if you upgrade to the full visibility package within 30 days, the $97 comes off the price. If you’re a restoration company in Pierce County and you just read this wondering whether you’re Company B, C, or D — that’s exactly what the scan answers.


    AI Citation Quick-Scan — $97

    This article is the free version of the test. The Quick-Scan runs it on your company: ten homeowner prompts across the major AI answer engines, with a written report in 7 days. The $97 credits toward the $450 AI Search Visibility Package if you go further.

    Get the Quick-Scan — $97

  • Who Pays Before the Work: The Deposit Fight Every Restoration Job Faces

    Who Pays Before the Work: The Deposit Fight Every Restoration Job Faces

    It started in a Facebook group in Anderson, Indiana: homeowners trading notes on 25–50% deposits, contractors answering that $12–15K in rental gear has to sit on site before the drying starts. The same fight is happening in public, all over the internet, and it’s worth reading in the combatants’ own words.

    Illustration of a homeowner and contractor in a tug-of-war over a repair contract
    The deposit debate, illustrated: both sides are protecting themselves from the same thing — getting burned.

    Camp one: the contractors

    Entrepreneur Nick Ayala’s reel (13K likes, 250 comments) takes on the client who says “I’ll pay you when it’s done.” His argument: starting work without a deposit “makes the freelancer the client’s bank — fronting labor, materials, calendar time, and 100% of the risk for free.”

    “Makes the freelancer the client’s bank — fronting labor, materials, calendar time, and 100% of the risk for free.”
    — Nick Ayala, Instagram

    A contractor posting as ProWall Paints & Plaster admits he “used to think asking for 50% upfront was ‘crazy,’ but now understands it is necessary” — the deposit covers materials, labor, scheduling, and mobilization. And John at Bluestone Construction puts it the way only a contractor can: “You pay 100% for any item at Canadian Tire… Yet in home renos where he locks the door and has complete control, he thinks he doesn’t have to pay!!”

    Camp two: the homeowners

    The rebuttal is just as vivid. One homeowner’s Instagram rant is captioned “A fool, and his money will soon be parted” — he will not pay half before work starts, period. A Facebook post that drew 500 comments is just a screenshot of a text exchange titled “No Deposit = No Work”: the contractor demands 50% by Zelle, the customer replies “Oh no I don’t pay no until the work is completed” and “That is unsafe.”

    “Oh no I don’t pay no until the work is completed.”
    — a customer, in a 500-comment Facebook thread

    And the fear isn’t abstract — a Moreno Valley community post with 810 comments documents a painter who took 50% cash upfront, missed days, asked for rent money, and quit.

    The law has opinions too

    Multiple states cap deposits by statute — California at 10% or $1,000, Tennessee at 33% for jobs over $500 — and UK prime minister Andy Burnham just weighed in on the same pattern (“take a big deposit, do half a job, then disappear”), backing escrow-style release: “Do the work, get paid. It’s as simple as that.”

    Bar chart comparing legal deposit caps in California (10%) and Tennessee (33%) against a typical contractor ask of 50%
    Legal caps vs. common asks. Caps vary by state — check your own state’s rule before you sign anything.

    Now the restoration spin

    This trade has a wrinkle the general debate misses. In restoration, the contractor’s number is real in a specific way: dehumidifiers, air movers, HEPA scrubbers, containment — the rental clock starts when the gear rolls off the truck, and a serious loss can mean twelve to fifteen grand of equipment sitting in your living room before the first board is cut. That’s mobilization cost, and a deposit against it is legitimate.

    Professional restoration drying equipment — air movers, dehumidifiers, and an air scrubber — lined up in a home
    Mobilization: this is what $12–15K of rental equipment looks like on day one — before the drying even starts.

    But here’s the part homeowners in that Anderson thread are really asking about: on an insured loss, the homeowner often isn’t the one paying — the carrier is. The deposit fight on a covered claim is about who fronts cash while the claim processes: the deductible, the first invoice, the gap between “work starts today” and “the check arrives in three weeks.” A good restoration contractor structures deposits around the claim, not against the homeowner.

    The middle ground

    Assembled from the sanest voices in these threads:

    • Tie the deposit to something real. A DIYnot commenter nailed it: “a reasonable deposit is the cost of the equipment to be installed plus the sundry materials.” In restoration, that means the deposit maps to mobilization — gear on site — not an arbitrary 50%.
    • Spell out the deposit rules in writing. Kevin Page on LinkedIn: “Spell out plainly whether the deposit is non-refundable, or exactly how it gets prorated if things end early.”
    • Pay by phase, not by percentage. A BiggerPockets investor: “You give some unscrupulous Contrs 1/3 up front and they’ll just take off.” His fix: invoice per phase, pay each phase in full when complete and inspected.
    • Remember who holds the leverage. “Whoever controls the money controls the job,” writes one builder — which is exactly why staged payments beat lump deposits. Money follows work.
    • Documentation is the tell. Daily moisture readings, psychrometric logs, photos at every stage. A contractor who documents is a contractor who finishes — and those are the same records your adjuster needs.

    The deposit isn’t the problem. The missing paperwork is. Both camps in this fight want the same thing — to not get burned — and the industry just hasn’t made the middle ground standard yet.

  • Your Website Doesn’t Need More Traffic. It Needs to Be the Answer.

    Your Website Doesn’t Need More Traffic. It Needs to Be the Answer.

    Most restoration contractors are invisible where it now matters most: inside the AI answers. When a facility manager asks Copilot who to call for a commercial loss, the model does not scroll your homepage. It cites whoever taught it the cleanest sentence.

    Your website does not need more traffic. It needs to be the answer. Zero-click search already took the click. The remaining win is being named inside the answer itself. That is a different game than ranking a page, and most agencies are still scoring the old one.

    Cited answer. A cited answer is the short, checkable sentence an answer engine lifts into Copilot, ChatGPT, Perplexity, Gemini, Bing Copilot, or a Google AI Overview and attributes to a URL. Traffic is optional. The attribution is the asset.

    Why are restoration contractors invisible inside AI answers?

    Commercial buyers no longer start with a ten-blue-link session. They type the job into an assistant: who handles a sprinkler discharge on a mid-rise, what a drying standard actually requires, whether a vendor is after-hours in this metro. The model answers from pages that already look like briefings.

    Most contractor sites still look like brochures. Hero image. Five service tiles. A form. A blog post that restates the service name. There is no 40-to-60-word answer under the question the buyer asked. There is no timetable, no definition, no named protocol. The model has nothing safe to lift, so it lifts a national franchise FAQ, an insurer explainer, or last year’s trade-press roundup.

    That is not a branding problem. It is a retrieval problem. We wrote the longer architecture in Restoration Company SEO: Fix Your AI Search Visibility and in the three-layer SEO / AEO / GEO frame. This note is the field version: one receipt, one buyer question, one scoreboard change.

    What did a 20-page race guide teach us about citations?

    Race weekend in Madrid. We published a small independent visitor guide at racemadrid.com — twenty static pages, Spanish primary, English secondary, no ticket shop. Through 8 September 2026, Bing Webmaster showed 144 clicks and 3,218 AI citations. On 8 September the model quoted the site 55 times for every human click.

    The queries were not “who wins.” They were traveler questions: Sunday end time, cash or card, gate open, hotel to track, can I bring a bag. The pages that earned both clicks and citations were the schedule, the circuit, and the FAQ. That field note is public: We Built a Tiny Site for a New F1 Track. The Clicks Were Small. The Citations Were Not.

    Same playbook we run for restoration companies: be the clearest answer to the question the buyer is actually asking. A facility manager after a loss is in the same posture as a traveler the night before a sold-out race. They do not want your brand story. They want the next true sentence.

    How is that different from SEO?

    SEO still matters. It is the foundation that lets a URL exist, resolve, and get fetched. AEO is how a featured snippet or People Also Ask box can lift a clean block. GEO is how a generative engine decides you are safe enough to speak for. We treat them as concentric layers on one page, not three rewrites. The operator version of that stack is in What Is GEO? and in what GEO delivery looks like inside a real engagement.

    LayerQuestion it answersWhat you ship
    SEOCan the engine find and trust the URL?Title, meta, headings, first-100-word keyword, internals, schema that is true
    AEOCan a snippet lift one block without rewriting you?Question H2, 40–60 word answer, FAQ, definition box
    GEOWill a model cite you when a buyer asks in chat?Checkable facts per paragraph, entity names, dates, sources, bilingual or local variants when the buyer uses them

    If you only measure sessions, you will call a 55-to-1 citation ratio a failure. If you measure whether the model will say your name when a facilities director asks who to call, that ratio is the product.

    What does the restoration version of a cited answer look like?

    It looks like a briefing, not a pitch. The H2 is the question. The next paragraph answers it in plain language, with a number or a standard attached. Then the proof: what you do on site, what you do not do, the metro you actually cover, the clock you keep.

    • Who to call after a commercial sprinkler discharge in this building class, after hours.
    • How long a category of water stays a drying job before it becomes a rebuild conversation.
    • What the carrier packet has to include on day one so the file does not stall.
    • Which document the facility manager should send before the first truck rolls.

    Write those as answers a model can quote without inventing a second sentence. Put the misspellings and the local names on the page on purpose. Madrid taught us that travelers cannot spell a new circuit. Facility staff cannot spell your d/b/a either. Cover the words they type.

    What is a citation worth if nobody clicks?

    On the race guide, a citation is proof of position. It is not a ticket sale. We said that in the field note and it stays true here. A restoration citation is worth more than a travel citation only if you already own the next step: the phone, the after-hours board, the approved-vendor list, the estimator who can take the job tonight.

    If the sentence the model lifts is wrong, the citation is a liability. We locked a Sunday start time off an older F1.com page and the official MADRING time was later. That error is still the most-clicked kind of question in the logs. The next hour of work is not a new URL. It is correcting the fact the model already trusts. Restoration pages have the same failure mode: an outdated response-time claim will travel farther than the correction.

    What we would not claim

    • That 144 Bing clicks is a media business.
    • That citations replace Google. The Madrid export is Bing Webmaster plus Clarity. Google Search Console is a separate pile.
    • That being cited is automatically good. It is good if the fact is right and you have a use for the attention.
    • That this article invents a new discipline. SEO, AEO, and GEO are already named on this site. This is the operator sentence we are willing to put on LinkedIn and stand behind.

    What we would do again

    Show up early on a named question that does not have a settled official FAQ. Write the buyer’s language, not the agency’s. Keep the page short enough to finish. Put the clock in one place and keep it tied to a source you can defend. Do not invent a content brand around a weekend — or around a single storm.

    The models will quote you if the sentence is plain. The humans who still click will click the schedule, the response protocol, the packing list. Everyone else will take the answer and move. Your job is to be the sentence they take.

    FAQ

    What is the difference between AEO and GEO?

    AEO — Answer Engine Optimization — structures a page so a featured snippet, People Also Ask box, or voice result can lift a complete answer. GEO — Generative Engine Optimization — structures the same page so a generative model will cite that URL when a person asks in chat. One page. Two retrieval systems.

    Does zero-click search mean a restoration website is useless?

    No. It means the homepage-as-brochure is the wrong artifact. The useful site is a set of briefings the model can quote and the buyer can still open when they need the packet, the photo standard, or the after-hours number.

    How do you know a page is being cited?

    You measure it on more than one desk. Bing Webmaster now reports AI citations. Clarity shows whether the humans who still arrive actually read. Prompt checks in Copilot, ChatGPT, Perplexity, and Gemini tell you whether the brand is named. We keep the method on AI citation monitoring and on the Bing citation mining thesis.

    Is this only for restoration companies?

    No. Restoration is the vertical where a missed answer has a wet building attached to it. The same pattern holds anywhere a buyer asks an assistant a time-sensitive operational question and needs a named next step.

    Sources: Will Tygart, Tygart Media, Tacoma, WA, 11 September 2026. First-party Bing Webmaster and Microsoft Clarity figures for racemadrid.com through 8 September 2026, as published in the Madrid field note. Related Tygart pages: restoration AI visibility, GEO explainer, GEO delivery.