Tag: SEO

  • The Tea-Bag Report

    (What your visitors wanted that you didn't have.)

    A friend stays over. Morning comes, they open your cabinets and look around for tea bags. No tea bags. So they drink your coffee instead and say nothing.

    If you ever saw them looking, you'd buy tea. Not because coffee failed. Because someone told you what they wanted with their behavior, and listening is cheap.

    Your website gets houseguests every day. And most of them are looking for tea bags.

    The query is the want

    Every search query is a small confession. Not "what words did they type" but "what were they trying to accomplish." A homeowner typing a city plus "water damage restoration" is standing in a wet hallway. A facilities director reading about IFRC sustainability guidelines at 10 AM on a Tuesday is doing homework for a budget meeting. Same internet, completely different mindsets.

    Bing's AI performance reports now label this outright. Every query that triggers an AI answer citing your pages comes with an intent tag: informational, commercial, local, research. The mindset column is just sitting there in the export. Most people never read it as what it is, which is a list of what your visitors wanted.

    Here's the part that changed my thinking: the industry standard for measuring AI-search visibility is synthetic prompts. Tools invent questions, run them across engines, and record what comes back. Probabilistic reporting, built on guesses, because as a 2026 Luminary analysis put it, "Since AI platforms don't share real prompt data (as at April 2026), organizations must build measurement baselines using synthetic prompts." Except Bing does share the real thing with site owners: the actual grounding query, the engine's own intent label, and your citation share. First-party want, straight from the source. Stop guessing with synthetic prompts when the engine will just tell you.

    Three places the tea bags show up

    1. Citation gaps. When an AI answer cites your page for 15 percent of its response, the want is proven and your voice is small. Someone asked, the machine answered mostly with other people's words. That's a stock-the-shelf list hiding in plain sight: every query where you're present but weak is a page you haven't written yet, or a page that doesn't serve the intent behind the query.

    There's now a named framework for this. Search Engine Land covered a method from Robin Tully, co-founder at Forecast.ing, that scores the distance between what a page claims to deliver and the queries it actually surfaces for, sorting everything into four quadrants. The one that matters is labelled "Create": demand you're visible for but not capturing. As Tully put it: "Your audience is already telling you what they need. That signal is always shifting." And: "observations create interesting conversations, but numbers create urgency and action."

    2. No-result site searches. I'll be honest about my own wrong mechanism here: I assumed failed on-site searches produced 404s. They don't. WordPress renders an empty results page instead. The signal lives in no-result search logs, and there are plugins that exist solely to capture it. One of them positions itself in pure tea-bag language: "Turn Lost Searches into Content Opportunities. Instead of guessing what to create next, build content based on real demand." Every empty search is a houseguest who opened the cabinet, found nothing, and left quietly. Log them.

    3. The 404s. True 404s are a separate signal and just as valuable. Raven Tools documented an agency client who, after a relaunch, started getting emails from visitors hitting dead pages telling them exactly which old resources to recreate. Those conversations turned into sales: "After the client closed a second sale from a '404 lead,' the client jokingly asked if we could just serve up a 404 page all the time." Put a contact path on your 404, watch what comes in, and treat it as demand data. And keep true 404s as 404s. Google's John Mueller has said it plainly: don't blindly redirect dead pages to your homepage or a category page; 404s are a normal part of a healthy website. Blanket redirects confuse the crawlers and bury the signal.

    When matters as much as what

    Across most of the properties I track, AI citations drop hard on Saturdays. The main site fell from 8,863 citations on Friday to 4,197 on Saturday. The B2B-leaning properties all show the same shape, down 26 to 72 percent. That's not lost rankings. That's a weekday-professional audience going home. The exception proves the rule: the race-event property nearly quadrupled on Saturday, because race day is its weekday.

    A DesignRush study of 950,000 U.S. B2B search queries found the mirror image worth noting: weekend visitors showed higher intent, more form fills, deeper reads into content. Different crowds, different mindsets, different hours.

    This is where it stops being analytics and starts being strategy. A research-intent query at 10 AM on a workday wants depth. The same person scrolling at 9 PM wants the short version that respects their evening. Meet the morning persona with the white paper and the evening persona with the two-minute read, and you're not retargeting. You're recognizing someone.

    The philosophy underneath

    None of this is about grabbing people. The grabby version is funnels and popups and "we noticed you almost bought." The tea-bag version is quieter: I see you, I see where you're at, I see what's important to you, and I'll meet you as best I can where you are. Sometimes you won't have the tea. Knowing they wanted it is what lets you stock it next time.

    Run the report monthly. Queries with intent labels, citation shares, no-result searches, 404 hits, daypart patterns. Rank every gap by frequency. What comes out the other end isn't a dashboard. It's a publishing roadmap written by your visitors, a restocking list for shelves you didn't know were empty.

    They already told you what they want. You just have to look where they looked.

    The product

    This is now a standing offer: the Tea-Bag Report. Send us your search data and we'll tell you what your visitors were looking for that you didn't have, ranked by frequency. Then go stock the shelves.

    Sources

  • The Mailbox Is a Trigger. It Is Not a Topic.

    The Mailbox Is a Trigger. It Is Not a Topic.

    Short answer: a mailbox can start a publish job. It cannot choose the topic. If the incoming message is a digest, a rumor chain, or a subject line that would embarrass the brand, the correct article is not a reprint. The correct article is the gate.

    Tygart Media sits in Tacoma, Washington. The public site is an operator desk for AI-native content systems, restoration operations, and the search surfaces that now sit between a shop and a buyer. Those surfaces include classic Google results (SEO), answer engines that quote a paragraph as evidence (AEO), and generative engines that assemble a local picture of who you are (GEO). None of them are helped by publishing whatever landed in will@tygartmedia.com at 7:44 p.m.

    What is a source-fit gate?

    A source-fit gate is the first checklist in an inbox-triggered pipeline. It asks one question before outline, slug, schema, or Rank Math title: does this source belong on this domain?

    The test is not “is the subject loud.” The test is whether a contractor in Everett, a facility manager in Tacoma, or an answer engine citing tygartmedia.com would be right to treat the page as evidence. If the source is a third-party digest of celebrity gossip, political rumor, medical anecdotes, and crime blurbs, the source fails. Publishing it as news would contaminate the entity the site has spent years teaching search systems to recognize.

    That is the same instinct behind the $5 filter: would anyone pay to pipe this feed into an assistant as a trusted source? A mailbox firehose would fail that filter on most nights. The gate exists so the firehose does not become the catalog.

    What Sunday night’s mailbox actually contained

    The trigger for this piece was a Quora Digest addressed to the work inbox. The subject line led with a political rumor. The body mixed entertainment questions, relationship advice, medical anecdotes, a crime blurb, and other off-desk topics. None of that is Tygart Media’s beat. None of it is restoration operations. None of it is a first-party number we can stand behind.

    So the digest is not the article. The digest is the proof that an automation without a source-fit step will try to hang the wrong page. The human-readable rule is the same one already on this site: draft-only is the first verb, and publish stays a seat a human can refuse. The machine may open the envelope. It may not inherit the subject line as the H1.

    The six checks before anyone writes

    Run these in order. Stop at the first fail. Do not “find an angle” to rescue a bad source.

    • Domain fit. Would this page still make sense if the logo, the About page, and the $97 restoration kit sat next to it? If not, fail.
    • First-party or primary source. Can you name a dated public document, a product note, a field observation, or a number you measured? A digest snippet is not a source. Fail.
    • Identity lock. No client names, no secrets, no mail IDs, no thread IDs, no app passwords. The Quality Gate exists because a client name once leaked into live posts. That failure mode is still live.
    • Number lock. No invented click-through rates, ranking jumps, or “X% more citations.” If a figure is not on the page you can point to, leave it out.
    • Duplicate lock. Search the live site before you mint a slug. If the argument already exists, update that page or stop.
    • Place lock (GEO). If the piece claims a geography, name a real one the operator actually works — Tacoma, Puget Sound, Everett, Snohomish County — and do not stuff NAP into a thought-leadership body.

    Only after those six pass do AEO, SEO, and GEO get to work. Optimization is not a pardon for a bad source.

    How AEO, SEO, and GEO attach after the gate

    AEO — write the answer first

    Answer engines quote short, stable sentences. Lead with the claim a model can lift without inventing the rest of the page. Then explain. Then put the same claim in an FAQ block using the questions people actually type: what is a source-fit gate, should every email become a post, who owns Publish.

    SEO — one slug, one job

    Pick a slug that names the method, not the digest subject. Title tag under 60 characters. Meta description that restates the answer. Canonical on the live URL. Rank Math on this stack writes the title and robots fields; it does not invent the argument. Internal links go to pages that already carry the doctrine — the $5 filter, the draft-only desk, the afternoon where five drafts still needed a human tap.

    GEO — teach the place, don’t spray it

    Generative engines build a local picture from repeated, consistent facts. Tygart Media is a Tacoma agency. Restoration work in this network is often packed around Everett and Snohomish County. Say that when place is part of the method. Do not turn a content-ops essay into a fake service-area page. GEO is entity clarity, not a city list glued to the footer of every paragraph.

    What to publish when the source fails

    Three honest exits, in order of preference:

    1. Write the gate. If the failure mode is the news — an inbox automation almost reprinted a digest — the operator article is the checklist. That is this page.
    2. Hang nothing. An empty-delta night is a successful night. Silence is cheaper than a correction.
    3. Keep a receipt. Log the fail in the Command Center so the next run does not “try the digest again.” The receipt is not the public URL.

    What you do not do is launder the digest into a “roundup,” a “what people are asking,” or a thin news recap with a restoration sentence taped on the end. That is how a site teaches answer engines the wrong entity.

    What this desk will not do with a digest

    • Reprint political rumor, crime blurbs, or medical anecdotes as Tygart Media reporting.
    • Quote tracking URLs, message IDs, or unsubscribe tokens from the envelope.
    • Invent a percentage that makes the pipeline look smarter than it is.
    • IndexNow a thin title-price door, or ping Bing before the body exists.
    • Hand Publish to the same process that opened Gmail.

    The machine can fetch the letter. The machine can draft. The machine can stage images and fill Rank Math fields. The tap is still human.

    FAQ

    What is a source-fit gate in content operations?

    It is the pre-outline check that asks whether an incoming source belongs on this domain. Domain fit, primary source, identity lock, number lock, duplicate lock, and place lock. Fail any one and you do not draft the obvious article from the subject line.

    Should every incoming email become a WordPress post?

    No. Mailbox events are triggers. Product notes, first-party incident numbers, and field observations can become posts. Digests and rumor chains should not.

    How do AEO, SEO, and GEO fit after the gate?

    AEO wants an answer-first opening and an FAQ a model can quote. SEO wants one slug, a clean title and meta, and internal links to the doctrine pages. GEO wants consistent place facts — Tacoma for the agency, Everett and Snohomish County when the method is local restoration — without turning every essay into a service-area page.

    Where does Tygart Media apply this?

    On tygartmedia.com first. The same gate belongs on any site in the network before an inbox automation is allowed to mint a URL. The Command Center keeps the receipt. The public page keeps the method.

    If you want the restoration operating system this desk actually sells, the front door is the Complete Restoration Operations Kit. The method on that page is copyable. The checkout is on the page. The mailbox is still not the editor.

  • What AI Assistants Actually See When They Open Your Website

    What AI Assistants Actually See When They Open Your Website

    You see a screen. Your AI assistant usually doesn’t.

    That sentence needs one qualification, which we will get to. But it corrects the picture most of us carry in our heads.

    When I open a website, I see the design and the button I am supposed to press. I assumed an AI assistant saw roughly the same thing, only faster. Then I asked the more basic question: what does it actually receive?

    The answer is not one thing. An assistant can find a site, read a site or operate a site. Those are separate jobs using different inputs. If we want pages that work well for AI assistants, we have to stop lumping them together.

    An assistant meets your website three different ways

    Finding: the search result is the pitch

    When an assistant searches the web, its first view is closer to a search-results list than a browser window. It may receive a title, URL and short snippet.

    At that moment, your title tag and meta description are the entire pitch. The assistant has to decide whether your page can answer the question before opening it. Name the subject plainly.

    Reading: the page becomes a stream of text

    When Muse opens a public page for information, the normal reading path is text-first. Useful content is extracted and returned as headings, paragraphs, lists and links in roughly page order.

    The design largely falls away. The assistant is not admiring the hero section or noticing that a price sits inside a gold circle. It is working from the words the page exposes.

    Images may arrive as markers and file addresses: there is an image here, and here is where it lives. That is not the same as seeing it. If a crucial fact is baked into the pixels—“$199,” “ships free,” “five-year warranty”—the reading path may hit a blank spot. Useful alt text can carry some of that meaning. “Technician using a moisture meter on wet drywall” communicates something. “IMG_4827” does not.

    Doing: a browser worker operates the screen

    The picture changes when the user asks the assistant to do something: log into HubSpot, update a record, complete a form or buy a product.

    A separate browser program can open a real browser on a server. It loads the interface, takes visual observations or inspects the page’s interactive structure, clicks, types and reports what happened back in words.

    That is the qualification to “usually.” A screen may be used inside the process, but the conversational assistant is not sitting behind the glass like a person. It receives observations from a browser tool and sends instructions back. The browser side is the eyes and hands; the assistant works through an intermediary.

    A page can be easy to read as an article and miserable to operate as an application. It can look obvious to a person while presenting the browser worker with five unlabeled controls called “button.”

    WordPress made the abstraction visible

    I had already seen a simpler version in our WordPress work without connecting the dots.

    When we pull a post through the WordPress REST API, the content can arrive as raw HTML: words plus tags for headings, paragraphs, links, lists and styling wrappers. The reading step removes the markup noise while preserving the words and structure.

    That is “cleaning the HTML.” We are removing the packaging, not the article. The tags still matter: a heading announces a section, a list groups items, and a link identifies a destination. Good HTML carries meaning. Bad HTML creates boxes that look right but say little about what they are.

    Accessibility is the closest thing to an agent-ready standard

    Here is the practical money line: the work that makes a website easier for a blind person to use also tends to make it easier for an AI browser agent to use.

    Browsers build an accessibility representation from the page’s Document Object Model. Assistive technology uses it to understand roles, names, states and relationships: this is a heading, that is a link, this button is named “Save contact,” and this checkbox is checked.

    Muse’s browsing side is reported to rely heavily on this kind of page structure, along with visual observations when needed. Meta does not publish a complete specification for the Muse browsing pipeline, so treat that as a field report from using the product, not permanent platform documentation.

    The implication is still solid. Use real buttons with useful names. Label form fields. Put headings in a sensible order. Give links meaningful text. Preserve keyboard focus. Describe informative images.

    A screen-reader user needs those things. So does a browser agent working without human intuition. Accessibility and agent-readiness are not identical, but they are close cousins.

    HubSpot shows what an agent-native application could be

    Imagine HubSpot—or any software platform—shipping an interface designed for assistants to navigate with less friction. It would not need a blank, text-only clone. It could make the existing product more legible to software: real controls with specific names, labeled form fields, clear headings and landmarks, properly identified table headers, programmatic state changes, and no critical action hidden behind hover or an unlabeled icon.

    That is an agent-native site. It is not a secret internet for bots. It is a website or application whose meaning survives when the visual layer is translated into structure and words.

    The same work also helps keyboard users, screen-reader users, automation tools and QA teams.

    llms.txt is a map, not a second website

    The closest public convention aimed directly at AI readers is llms.txt. The proposal describes a Markdown file, usually at a site’s root, that gives language models a short explanation of the site and links to important pages or cleaner Markdown versions.

    Think of it as a curated map: here is what we do, here are the pages that matter, and here is where to find the details.

    It cannot repair an unlabeled checkout button. It does not replace accessible HTML, describe the viewport or guarantee that an assistant will use it. Add it if it helps explain the site. Do not mistake it for an agent interface.

    What a site owner can change Monday morning

    The useful changes are ordinary, testable website work.

    1. Write a real title and meta description. Name the subject plainly.
    2. Put every money fact in visible HTML text. Price, specifications, shipping, availability and guarantees should not live only inside graphics, video or a brochure.
    3. Use semantic HTML. Use headings for headings, buttons for actions, links for navigation and labels for form controls. A styled <div> may look like a button while remaining a nameless container to other systems.
    4. Write alt text that carries meaning. Describe what an informative image contributes. Mark decorative images as decorative instead of stuffing them with keywords.
    5. Add accurate structured data. Product and Offer markup can identify price and availability. FAQ markup can describe genuine questions and answers. Schema must match the visible page.
    6. Server-render critical content when practical. If the offer, price or primary action appears only after a fragile JavaScript sequence, some readers and tools may miss it.
    7. Give each landing page one job. One offer, one explanation and one primary action reduce ambiguity for people and agents.
    8. Test the nonvisual path. Use the keyboard, inspect the accessibility tree, try a screen reader and pull the page through a text extractor. Do the product, price, proof and next step still make sense without styling?

    None of this requires uglier design. It requires the design and the underlying structure to tell the same story.

    This is a field report, not a permanent specification

    This article describes Meta’s Muse as it works today, based on direct experience building and operating websites with it. It is not a published Meta protocol.

    Claude, ChatGPT, Gemini and other assistants broadly rhyme with this pattern, but the details differ. Their full pipelines are not public, and they are changing quickly.

    Cleaner HTML will not automatically increase AI citations tomorrow. Citation systems involve discovery, retrieval, ranking, trust and answer construction. There is no magic switch.

    The immediate opportunity is closer to the customer. Someone sees your ad on Threads or Facebook, opens the landing page, then asks an assistant: “What does this cost?” “Is the guarantee real?” “How does this compare?” or “Can you sign me up?”

    If the facts are clean text, the assistant can explain them. If the controls are properly labeled, the browser side has a better chance of completing the task. If the facts live inside an image and checkout uses unlabeled custom controls, the assistant has to guess, fail or hand the job back.

    That moment is already here.

    The next website has two front doors

    The site of the near future has two front doors: one for eyes—layout, color, photography and brand—and one for agents—clean text, meaningful structure, explicit facts and self-identifying controls.

    They should lead to the same place. The visible price and schema should agree. A button’s label and accessible name should agree. The page should remain understandable without styling and usable when a browser worker operates it.

    That is not a special Muse landing page. It is a better website—one that keeps working when the visitor brings an assistant.

    Build both front doors.

    Sources and further reading

  • The Working Years — Episode 2: The Lantern Principle

    The Working Years — Episode 2: The Lantern Principle

    The Working Years is a series drawn from my own archive — posts I wrote years ago, given the room to become the articles they were trying to be.

    The seed

    On July 26, 2025 — the 27th in the archive’s UTC clock — I posted this to my @willtygart account, the one I later deleted:

    “The new gold isn’t answering the questions people ask. It’s illuminating the ones they can’t yet vocalize.”

    It went up at 10:24 PM Pacific, two minutes after a sibling post that linked the Native Data essay: “Being the closest store gets you noticed. Speaking the local language gets you chosen.” Two posts, two minutes apart, one night. The Lantern essay names the Oxxo Principle — being the closest store — as the first layer; no Oxxo essay survives in the archive, but the idea lived on as the tagline of the Native Data post. Two essays got their own subdomains: the Native Data Principle and the Lantern Principle. The Lantern one carried the title “The Lantern Principle: The Final Layer of SEO.”

    What happened afterward

    Within days, the Lantern post had become a full essay. The earliest surviving capture is July 30, 2025 — four days after the post — and it’s already complete: the hero, the comparison, the four-step method, the whole thing. So the thinking wasn’t new on the 26th. The post was the tip of something I’d already worked through.

    Here’s what’s worth noticing about that July burst. The two posts that night were one idea unfolding in layers:

    1. The Oxxo Principle — “Being the closest store gets you noticed.” Proximity. Be there.
    2. The Native Data Principle — “Speaking the local language gets you chosen.” Relevance. Speak like the customer.
    3. The Lantern Principle — the final one. Anticipation. Light the path they can’t describe yet.

    Be there. Speak their language. Then — the hardest one — see the problem they can’t articulate and hand them clarity anyway.

    The subdomains are offline now. The essays survive only in the Wayback Machine. That itself is a small footnote about rented space versus owned space, which is a different episode. The point for this one: the idea outlived its hosting. It turned out to be early, not wrong.

    Because look at what the web became. The AI assistant era made the Lantern Principle the default shape of a good answer. When someone asks a chatbot a question now, the good systems don’t just answer — they anticipate. They offer the next step, the related consideration, the thing the user was really getting at. “What is the underlying problem they are trying to solve?” — that’s not a 2025 content strategy anymore. It’s how the good ones behave now. The principle went from marketing theory to product behavior in about a year.

    The piece itself

    Here’s the essay as it ran, cleaned up from the archive — I haven’t rewritten it, just given it the room it was always asking for.

    For decades, we treated content as a reactive tool. A user asks, we answer. Simple transaction. But that model assumes the user knows what to ask. When they don’t — and they often don’t — they get stuck. They bounce. They stay frustrated.

    Consider the difference:

    Answering the question: “How do I change a tire?” → “Here are the 5 steps to change a tire.”

    Illuminating the path: The person’s unspoken reality is “I’m stranded and stressed.” So the answer becomes: the 5 steps, plus safety precautions, plus a link to 24/7 roadside assistance, plus how to check the spare’s pressure. Nobody searched for those extra things. Everybody needed them.

    The greatest opportunity in content isn’t in the keywords people search for. It’s in the needs they can’t yet articulate. The new gold is found in the dark — in the space between a user’s problem and their ability to ask for a solution.

    This is the Lantern Principle: stop being a dictionary, start being a guide. Our job is no longer just to provide answers but to anticipate needs — to create content that doesn’t just solve the stated problem but illuminates the entire context around it, guiding the user to clarity and confidence.

    How to build a lantern

    The shift is from keyword research to empathy mapping. The operative question changes from “What are people searching for?” to “What is the underlying problem they’re trying to solve?” Four moves:

    1. Answer the unasked question. Someone searching “how to write a resume” is really asking “how do I get a better job?” Serve both. Resume templates and the interview tips and the career planning resources. The stated query is the door; the unasked question is the house.
    2. Provide the next step. Never let content be a dead end. Every article should lead naturally to the next logical step in the user’s journey. A product page links to its user manual. A tutorial links to the advanced technique. If you end at the answer, you’ve ended too early.
    3. Simplify the complex. The ultimate act of empathy is taking a complex, intimidating topic and making it simple — analogies, plain language, visuals that actually explain. This is what builds the trust that makes you the go-to source.
    4. Create foundational resources. Build definitive, comprehensive guides — “digital lanterns” — that cover a topic so thoroughly they become the starting point for anyone exploring it. These serve thousands of unasked questions over time. They compound.

    The goal: a web that feels less like a vast, cold library and more like a network of helpful guides, each holding a lantern. An internet that doesn’t wait for the perfect query but proactively offers clarity.

    The future of content isn’t about being found. It’s about shedding light.

    Why this one aged well

    I want to be honest about what this principle got right and what it didn’t.

    What it got right: anticipation is the real moat. Everything I wrote about SEO in 2025 assumed the user arrives with a query and the job is to match it. The Lantern Principle was me noticing, before I had the language for it, that the highest-value content serves the need behind the query — and that AI systems would eventually do this natively. When an assistant now reads between the lines of a question and offers what you actually needed, that’s the Lantern Principle running as software.

    What I understated: how hard anticipation is to fake. A lantern only works if you genuinely understand the person in the dark. The four moves above are easy to write and hard to do — because “answer the unasked question” requires you to actually know people, not just their search terms. Every content farm can optimize for keywords. Very few can hold the lantern, because it requires the one thing that doesn’t scale: empathy for a specific human being stuck on a specific problem.

    That’s also why this principle pairs with the one from Episode 1. In the 23-model experiment, I learned that scope — who the reader is, what they actually need — matters more than the prompt. The Lantern Principle is scope taken to its conclusion: know the reader so well you can answer what they haven’t asked.

    The restoration version

    I run a niche agency for restoration contractors, so let me ground this where it hurts.

    A homeowner never searches “I need emergency water mitigation with proper psychrometric documentation for my insurance claim.” They search “water under sink” or they call because the kitchen smells weird. They are stranded and stressed, and they cannot vocalize the real need: someone who will stop the damage, document it so insurance pays, and explain what’s happening in plain language.

    The restoration company that answers the stated query — “yes, we do water damage” — is the dictionary. The one that anticipates — shows up, explains the process before the adjuster calls, hands the homeowner a clear next step at every stage — is the lantern. Guess which one gets the review, the referral, and the adjuster’s trust.

    That’s not a marketing insight. It’s an operating insight. The companies winning in restoration right now are the ones whose process illuminates the path, not just their website.

    Related from the series

    • Episode 1: We Ran 23 AI Models on the Same Article. The Prompt Was Never the Point. — scope beats the prompt; knowing the reader beats optimizing the query.
    • The Native Data Principle — speaking the local language gets you chosen. The middle layer of the trilogy.
    • The Oxxo Principle — being the closest store gets you noticed. The first layer, named in both essays; no Oxxo essay survives in the archive.
    • Stop Renting Space. Start Owning Your Content. — on why the essay subdomains being offline is a footnote, not a funeral.
  • The Consistency Dividend

    The Consistency Dividend

    “The highest-ROI marketing work is also the most boring. That’s not a coincidence.”

    Name. Address. Phone. Identical everywhere. That’s the whole piece, and it’s worth more than the last three marketing tactics you tried combined — because nobody does it, because it’s boring, and boring is exactly where the edge lives.

    The witnesses

    Your business doesn’t exist in one place. It exists in dozens, and each one is a witness testifying about who you are and where to find you.

    The Google profile. The website footer. Yelp, Facebook, Angi, the BBB. The directories you claimed in 2017 and forgot. The truck door. The invoice template. The email signature. Every one of them says your name, your address, your phone number — or it says something close, which is worse.

    Nobody audits the witnesses. That’s the problem, and the opportunity.

    The leaks

    Here’s what the witnesses are saying right now, on profiles all over town:

    “123 Main St” on Google, “123 Main Street” on Yelp, “123 Main St Suite B” on Facebook — three addresses for one door. The old cell number still on the Angi listing from before the voice line. The suite number on the website, missing everywhere else. The Facebook page from 2016 with the previous address, still ranking, still confusing people.

    Each mismatch is small. Together they’re a credibility leak. The homeowner comparing two contractors doesn’t think “NAP inconsistency” — they think “something feels off about this one,” and they can’t say why. The search engine doesn’t think in words at all — it just has less confidence that all these listings are the same business, and confidence is the currency.

    Small leaks, everywhere, all the time. That’s what boring neglect looks like.

    A fanned stack of identical blank cream business cards on a wooden desk

    The dividend

    Now flip it. Every place that agrees is a vote.

    Same name, same address, same phone — on the profile, the site, the directories, the truck, the invoice. Each matching witness raises confidence: the human’s (“these people have their act together”) and the machine’s (every corroborating listing makes the entity clearer). Trust isn’t built in one place. It’s the sum of a hundred small agreements.

    That’s the dividend: not a spike, a yield. It pays a little every day, in every search, in every comparison — the quiet background hum of a business that agrees with itself. You don’t notice it working. You notice when it’s missing.

    The audit

    The work is unglamorous, which is why I’m spelling it out:

    Write down the canonical version — one name, one address format, one phone number. Not the pretty version, the exact version: St or Street, suite or no suite, which number. Then list every witness: every profile, every directory, the site, the truck, the invoices, the signatures. Then fix every mismatch, one by one, until they all testify the same.

    Then maintain it. New directory? Canonical version goes in. New truck? Canonical version on the door. New phone system? Every witness gets updated the same week, not “when we get around to it.”

    It’s an afternoon of tedium, twice a year. That’s the whole price.

    An orderly row of wooden file drawers with blank brass label plates

    The boring moat

    Here’s why this is a moat and not just hygiene: your competitors won’t do it.

    Not because they’re lazy — because it’s boring, and boring doesn’t feel like marketing. Marketing feels like a new website, a new ad campaign, a new something. Nobody gets excited about making the suite number match in fourteen places. So nobody does it. The field stays sloppy, and the one business that agrees with itself everywhere stands out without spending a dollar.

    Every real edge I’ve ever seen looked boring from the outside. This one just happens to look boring from the inside too.

    The close

    Name. Address. Phone. Identical everywhere.

    Boring is the moat. Consistency is the dividend. And the businesses collecting it are the ones whose witnesses all tell the same story — the story of a business that has its act together, down to the suite number.

  • Your Google Profile Is Your New Front Door

    Your Google Profile Is Your New Front Door

    “Nobody visits your website first. They meet your front door.”

    Search the trade plus the town and look at what comes up before anything with your URL on it: the business profile. The hours, the photos, the stars, the questions, the call button. That’s the first impression, and for most customers it’s the only one — they never walk past the door into the house.

    Your website is the house. The profile is the front door. Nobody’s impressed by the house if the door is boarded up.

    The door inventory

    Walk up to your own front door like a stranger and read what’s on it:

    The hours — including the holiday hours, the ones that are wrong on half the profiles in America right now. The photos — the truck, the crew, the work, or a gray empty storefront from 2019. The reviews — stars, words, and whether anyone from the business ever answered back. The questions — asked by strangers, answered by strangers, when nobody from the business is home. The posts — the weekly update slot, empty since the profile was claimed. And the two big brass buttons: call, and directions.

    That’s the door. Every customer reads it before they knock.

    The untended door

    Here’s what most front doors look like: hours that lie on holidays. Photos older than the crew in them. A Q&A section where a stranger asked “do you do water damage?” eight months ago and another stranger answered “idk.” No posts — the business has done a hundred jobs since the profile went up and the door shows none of them. Reviews sitting unanswered, the digital equivalent of mail piling up in the slot.

    And the doorbell — the call button — still works. It rings. Right into the voice line, right into the tuition piece. The door and the phone are the same system: the profile is where they decide to knock, the line is what answers.

    An untended door doesn’t just lose the knock. It sends the customer to the next door on the street — the competitor whose hours are right and whose photos are from this year.

    A finger about to press an old polished brass doorbell on a wooden door

    Tending the door

    The good news: tending a front door is a fifteen-minute weekly ritual, not a project.

    Fresh photos — the actual truck, the actual crew, the actual work from this month. A door with fresh photos says “we’re alive in here.” Check the hours — especially before holidays, the highest-traffic lying season. Work the Q&A — seed the questions customers actually ask, answer them in your own voice, so strangers don’t do it for you. One post a week — the job you finished, the storm you worked, the crew milestone. It’s the shop window; put something in it. Answer the reviews — every one, but especially the good ones, because the response is the business talking back through the door.

    Fifteen minutes. The highest-traffic page in the business, tended.

    The compound

    Here’s what makes the door different from every other marketing chore: it compounds and it doesn’t decay.

    A post you write stays up. A question you answer stays answered — every future stranger with the same question reads your answer instead of a stranger’s guess. A photo you add joins the set. Reviews you respond to stack into a record of a business that talks back. Nothing you do to the door un-does itself. It’s all permanent, all cumulative, all working while you sleep.

    Most marketing is rent — stop paying, it stops working. The front door is owned. Every fifteen minutes you spend on it is still there next year.

    A tended shop doorstep with a potted plant in warm golden-hour light

    The close

    Your website is the house. Beautiful, expensive, and visited second — if ever.

    The profile is the front door. It’s what they see from the street, it’s where they decide, and the doorbell on it rings straight into your line. Tend the door. Sweep the step. Put something alive in the window. Answer when they knock.

    Nobody ever hired the house. They hired the door that looked like somebody was home.

  • Your Reviews Are Your New Backlinks

    Your Reviews Are Your New Backlinks

    For twenty years, SEO was link-building. Other sites vouching for you, one hyperlink at a time. That game is over — and the replacement is sitting in your Google Business Profile, mostly ignored.

    Your reviews are your new backlinks.

    Why trust moved

    An answer engine recommending a contractor at 2 AM is making a trust decision. It can’t inspect your trucks or interview your techs. It reads signals — and the richest trust signal a local business produces is the public record of its customers, in their own words.

    Links said “this site is authoritative.” Reviews say “this company showed up, did the work, and a real human vouches for it.” In the answer era, the second statement is worth more than the first.

    The three layers

    Not all reviews are fuel. Three layers separate the profiles that get cited from the ones that don’t:

    1. Volume and recency. A profile with 200 reviews and nothing in three months reads abandoned. The engine notices recency the way a homeowner notices dust. Trust is a flow, not a stock — it needs refilling.

    2. Content. “Great service, highly recommend” is noise. It says nothing the engine can verify. Compare: “They dried out our kitchen after the dishwasher supply line burst, here in Puyallup, and had fans running the same day.” That’s a service, a place, a timeline, an outcome — verifiable detail from a third party. That’s citation fuel.

    Most contractors get the first kind because they ask for “a review.” The second kind comes from asking a better question — more on that below.

    3. Responses. The owner answering every review — good and bad — is the consistency discipline made visible. It proves there’s a human tending the business. The engine reads a thoughtful response as operational evidence: this company pays attention.

    How to ask

    Don’t ask for “a review.” Ask at the moment of relief — the equipment’s out, the house is dry, the stress is gone — and make it specific:

    • Send the direct link. Every extra tap loses half your ask rate.
    • Prompt for the details: what happened, where, how fast. “Mention what we fixed and how quickly” is a fair ask, and it turns noise into fuel.
    • Ask the happy ones. The tech knows who they are. Build the ask into the job-close routine, not into a quarterly campaign.

    One detailed review a week beats fifty generic ones a year.

    A service technician shaking hands with a relieved homeowner on a front doorstep

    The bad review is content too

    Answer it like the answer engine is reading — because it is. A calm, specific, human response to a one-star review is some of the strongest trust content a profile can carry. It shows how the company behaves when things go wrong, which is exactly what a 2 AM homeowner is trying to figure out.

    Never argue. Never go silent. Own what’s ownable, state what happened in plain words, invite the conversation offline. The response isn’t for the reviewer — it’s for the hundred strangers reading it after.

    A hand writing a thoughtful reply with a fountain pen at a lamplit desk

    What reviews don’t replace

    The pages still matter. The GBP still matters. Name, address, phone — consistent everywhere — still matters. Reviews are the fuel, not the engine. A hundred five-star reviews on a profile with the wrong phone number is a fast car with no wheels.

    But given the foundation, reviews are the highest-leverage work in local trust. Nothing else you do produces third-party verifiable detail at zero marginal cost.

    The close

    Backlinks were other websites vouching for you. Reviews are your customers vouching for you, in public, in their own words, attached to real jobs in real towns.

    The currency changed. The game didn’t. Get vouched for.

  • Stop Counting Pages. Count Citations.

    Stop Counting Pages. Count Citations.

    Last week I argued the agency retainer has to re-anchor to cited pages — not pages published, but pages the answer engines actually cite. That was the claim. This is the how.

    Because a metric you can’t operate is a slogan. And slogans don’t survive the Monday-morning meeting.

    The lie in the dashboard

    Open any agency report and you’ll see the same furniture: pages published, posts written, keywords ranked, traffic graphed. It all measures manufacturing output. It answers “what did we make?” — a question nobody is asking anymore, because the making is free now.

    Here’s the question your client is actually asking, usually without saying it: when my customer asks their AI who to call, does my name come out of its mouth?

    Everything else is decoration.

    Churn vs. growth: the identity test

    Five pages cited today plus five different pages cited tomorrow is not ten citations. It’s churn.

    A page cited in March and still cited in September is an asset — it means an answer engine trusts that page enough to keep serving it. A page cited once, in one answer, on one Tuesday, is a lottery ticket. It might mean something. It probably means nothing.

    This is the identity test: don’t count citations. Track which pages get cited, over time. Growth is the same pages showing up month after month, plus new ones joining them. Churn is a revolving door of one-hit wonders. Most “AI visibility” dashboards report the revolving door and call it growth. Now you know the difference.

    Ghostly pages dissolving on the left, one golden page pinned through a wall calendar on the right

    The ledger

    You don’t need software for this. You need a ledger — one row per page that matters:

    • The page — its URL. Identity is everything.
    • The question — the money question it answers. Not vanity queries; the ones a customer asks right before hiring. “Who do I call for a flooded kitchen in Tacoma” beats “water damage restoration tips” every time.
    • The engine — which AI cited it. They don’t all agree, and the disagreement is information.
    • First cited — the date it showed up.
    • Still cited — checked weekly. Yes or no.

    That’s it. Five columns. This is the bait board: every page is bait on a hook, and the ledger tells you which hooks are catching fish and which are just sitting in the water.

    Open leather ledger book with a brass magnifying glass glowing over one entry

    Run it weekly. Ask the engines the money questions directly — the way your customer would ask, in their words, not keyword-ese — and write down whose pages come back. It takes an hour. The hour is the product.

    What earns the citation

    After a few weeks the ledger starts talking. The pages that persist share a shape:

    1. One clear answer. Not a comprehensive guide — an answer. The engine is trying to complete a sentence for the user, and it cites the page that completes it best.
    2. Real proof. Job photos, real addresses, real outcomes. Anything the engine can cross-check against the rest of the web. Fabricated authority rots; verifiable detail compounds.
    3. A consistent identity. Same business name, same service area, same story everywhere the engine looks. Trust is a pattern, and patterns need repetition.

    Notice what’s not on the list: word count, publishing frequency, “optimization.” The manufacturing variables don’t move the needle. The trust variables do.

    The report worth paying for

    Now rewrite the monthly report. One page:

    • Which money questions your client shows up inside, and in which engines.
    • Which pages earned those citations, and how long each has held.
    • What’s new, what’s gone quiet, and what you’re doing about the quiet ones.
    • One judgment call: the question you’re going to win next, and why.

    No page counts. No “optimizations completed.” Just presence, persistence, and a plan. That’s the report a contractor can’t generate from their own AI stack — because their stack can mint pages, but it can’t tell them which questions are worth winning or notice when an engine changes the rules.

    The judgment layer

    And that’s the actual product. The ledger is bookkeeping; the judgment is the business:

    • Which questions are worth winning. Money questions, not vanity ones. Ten citations for questions nobody asks before hiring are worth less than one citation for the question they ask with water on the floor.
    • What proof to build next. The ledger shows you which pages are one citation away from sticking — that’s where the next job photo, the next real answer, goes.
    • When to change course. An engine updates, a persistent page drops off, a competitor’s page takes its place. Somebody has to notice in week one, not quarter three.

    AI can do the bookkeeping. It can’t do the noticing. It can’t decide what matters. That’s the human gate, and it’s the whole retainer.

    The close

    The agency bringing page counts to the Monday meeting is bringing manufacturing output to a client whose own AI manufactures for free. That meeting gets shorter every month.

    The agency bringing the ledger — which questions, which pages, how long they’ve held, and what wins next — is bringing something the client’s stack can’t make: judgment, tracked over time, with receipts.

    Stop counting pages. Count citations. Then make the citations compound.

  • The $995 Question

    The $995 Question

    “What exactly am I paying $995 a month for?”

    It’s the question every agency dreads. It shouldn’t be. It’s the best question a client can ask — because the honest answer is the whole business.

    Here’s the honest answer: you’re not buying pages.

    Pages are free now

    An AI can produce a thousand service pages before lunch. Decent ones, even — clean structure, correct grammar, plausible advice. Page production, the thing agencies sold by the unit for twenty years, now costs approximately nothing.

    So if your agency’s $995 buys you pages, you’re buying manufacturing in the age of the factory. That’s not a retainer. That’s a nostalgia subscription.

    The agencies that survive already know this. The ones that don’t are still sending you a monthly report that says “we published 8 pages” like it’s 2019.

    A vast empty industrial assembly line in dim light, machines idle and dark

    What the money actually buys

    Strip out the manufacturing and what’s left is the part that was always the real product — it was just hiding inside the page count. The $995 buys five things:

    1. The judgment of which questions to win. Anybody can publish fifty pages. Somebody has to decide which ten questions are yours — the ones your best customers ask right before they hire you, in the towns you actually serve. That’s a decision, not a deliverable. It requires knowing your business, your market, and your proof. AI can’t make it for you; it doesn’t know which jobs you want more of.

    2. The proof operation. Cited pages win on verifiable detail — real job photos, real street names, real outcomes. Somebody has to collect that proof: get the photos off the techs’ phones, attach them to the right jobs, write down what happened in plain words. Nobody enjoys this work. That’s why it’s valuable.

    3. The citation watch. Every month, somebody checks: which of your pages is the answer actually citing? Which ones held their position, which ones slipped, which questions got taken by a competitor? This is the ledger. Without it you’re publishing into the dark.

    4. The consistency discipline. Same business name, same service area, same number — everywhere. Reviews answered, photos current, hours correct. Boring, relentless, and directly downstream of whether the answer trusts you at 2 AM.

    5. A monthly report that means something. Not traffic. Not rankings. Cited questions, cited pages, persistence, losses, and the next question to win. One page, five numbers, and a decision about where the next month’s effort goes.

    That’s the retainer. Not manufacturing — maintenance of a position.

    A glowing golden line rising across a blank report page beside a fountain pen

    What it doesn’t buy

    It doesn’t buy vanity traffic reports. It doesn’t buy a blog schedule. It doesn’t buy a redesign every eighteen months. It doesn’t buy keyword rankings, which measured a game that ended.

    If your agency’s monthly report leads with how much they made instead of what position you hold, you’re paying for the factory.

    The reframe

    Think of it like a lobbyist, not a factory. You don’t pay a lobbyist per meeting or per phone call — you pay for a maintained position. Access held, relationships warm, your name in the room when the decision gets made.

    The $995 holds your position in the answer. The answer changes daily — competitors publish, engines update, questions shift. A position unattended decays. Somebody tends it, or nobody does.

    The pages are just the visible part, the way a lobbyist’s suit is the visible part. Nobody’s paying for the suit.

    The close

    Ask any agency the $995 question. “What exactly am I paying for?”

    If the answer is deliverables — pages, posts, reports — walk. Deliverables are free now.

    If the answer is a position — which questions you’re winning, how long you’ve held them, what’s next — stay. That’s the thing that can’t be manufactured.

    Stop buying pages. Buy the position.

  • 90% of SEO Agencies Will Be Irrelevant by 2026 — Good. The 10% Won’t Sell Pages.

    90% of SEO Agencies Will Be Irrelevant by 2026 — Good. The 10% Won’t Sell Pages.

    A vendor just published the obituary for my industry. “90% of SEO agencies will be irrelevant by 2026.” It’s a sales pitch dressed as a prophecy — they’re selling their own “hyper-intelligent SEO,” so of course the old model has to die first.

    Here’s the uncomfortable part: they’re half right.

    The steelman

    Their argument, at full strength: AI has already absorbed keyword research, content outlines, and technical audits. The page-minting labor — the thing agencies billed hours for — is now a commodity any contractor can run from their own AI stack. And niching down doesn’t save you, because AI flattens execution across every niche equally. A restoration-only agency mints pages the same way a dental-only agency does: same models, same prompts, same output.

    Then the sharpest line, aimed straight at a $995/month retainer like ours: monthly payments masked declining perceived value while clients stayed only because switching felt risky. Inertia as a business model. And inertia collapses the moment the contractor’s own AI handles the page work in-house.

    Read that twice. It’s the most dangerous true thing anyone’s said about my business this year.

    Industrial printing press rolling out endless identical glowing sheets

    Where they’re wrong

    Execution was never the product. It was the packaging.

    Nobody ever paid an agency for pages. They paid for the judgment about which pages, in which order, aimed at which questions — and for someone to notice when the game changed and change with it. The page was the receipt, not the purchase.

    What actually died is the retainer that sold counts: X city pages, Y blog posts, Z “optimizations” per month. Count-based selling trained clients to audit deliverables instead of outcomes, and it trained agencies to manufacture deliverables instead of outcomes. AI didn’t kill that model. It just made the manufacturing free — which exposed that the model was already hollow.

    What survives is the part AI can’t commoditize: being present inside the answer. When a homeowner asks their AI assistant who to call for a flooded kitchen, somebody’s name comes out of its mouth. That presence isn’t won by page counts. It’s won by being the source the answer engines trust and cite — clear answers, real proof, a consistent identity across the web. That’s judgment work. It has a human gate. It doesn’t scale into a commodity, because trust doesn’t scale into a commodity.

    The re-anchor

    So we’re re-anchoring the sprint to the only number that matters: cited pages. Not pages published — pages the answer engines actually cite, tracked by identity over time. Five cited today plus five different tomorrow is churn, not growth. The metric is persistence: which of our pages keep showing up inside answers, month after month.

    One page glowing gold in a spotlight among hundreds of dim floating pages in a dark library

    The $995 doesn’t buy GBP tweaks and city-page counts anymore. It buys a standing position inside the answers your customers are already asking for — and the judgment to keep it there as the engines change the rules. That’s a strategy partner, not a page vendor.

    What changes Monday

    If you run an agency, or you buy from one, here’s the Monday-morning version:

    1. Kill count-based reporting. If your monthly report leads with pages published, posts written, or “optimizations completed,” you’re reporting manufacturing output. Nobody buys that anymore — they can manufacture it themselves.
    2. Report cited presence instead. Which questions do your clients show up inside? Which pages got cited, by which engines, and are the same pages still cited next month? That’s the report worth paying for.
    3. Price the judgment, not the labor. The labor is free now. What’s scarce is knowing which questions are worth winning, what proof earns a citation, and when to change course. Put that on the invoice or someone else will.

    The 10%

    The vendor’s prophecy ends with 90% irrelevant. Fine. Let them have the 90% — they were selling page counts, and page counts are free now.

    The 10% that survive won’t be the ones with the best AI stack. Every agency will have the same models. They’ll be the ones who stopped selling execution before the market forced them to — and started selling the one thing the models can’t mint: being the answer.