Tag: SEO

  • How to Get Cited in ChatGPT Search in 2026: The Bing Index, OAI-SearchBot, and the 15% Citation Cliff

    How to Get Cited in ChatGPT Search in 2026: The Bing Index, OAI-SearchBot, and the 15% Citation Cliff

    ChatGPT Search cites 15% of the pages it retrieves. The other 85% get pulled into the model’s context window, evaluated, and silently discarded — no visibility, no referral, no trace. If you are doing GEO work and your pages keep getting retrieved but never quoted, you are losing at the second filter, not the first.

    This is the 2026 implementation guide for surviving both filters: getting retrieved by ChatGPT Search, then getting cited once you are there.

    How ChatGPT Search Actually Builds an Answer

    ChatGPT Search runs a three-stage pipeline. Each stage kills most candidates.

    1. Retrieval — ChatGPT Search is powered by Bing’s index for real-time web retrieval. Seer Interactive’s analysis found 87% of SearchGPT citations match Bing’s top results, with the bulk in positions one through ten and a long tail in positions eleven through twenty. AirOps research separately put ChatGPT-to-Bing overlap at 73%. If you are not in Bing’s top 20 for a query, you almost certainly are not in ChatGPT’s candidate set.
    2. Crawlability check — OpenAI’s OAI-SearchBot is the user agent that builds the index used for ChatGPT’s search features. It is separate from GPTBot (training) and ChatGPT-User (browsing). Block OAI-SearchBot in robots.txt and you remove yourself from ChatGPT Search entirely, even if Bing has you ranked.
    3. Citation selection — Of the pages retrieved, AirOps found ChatGPT cites only 15%. The model picks what to quote based on structure, freshness, authority signals, and whether the page directly answers the query.

    Step 1: Verify You Are Indexed by Bing

    Most sites optimized for Google have never logged into Bing Webmaster Tools. Fix that first. Three checks before anything else:

    • site:yourdomain.com in Bing — confirms basic indexing.
    • Bing Webmaster Tools → URL Inspection — confirms the specific pages you want cited are indexed and have no crawl errors.
    • Bing rankings for your target queries — if you are not in the top 20 in Bing, ChatGPT will not see you.

    If pages are missing, submit a sitemap via Bing Webmaster Tools and request URL inspection on any priority page. Bing typically reflects changes within 24–72 hours, faster than Google.

    Step 2: Allow OAI-SearchBot in robots.txt

    The single most-skipped step in GEO work. Add this block to your robots.txt:

    # Allow ChatGPT Search to retrieve and cite this site
User-agent: OAI-SearchBot
Allow: /

# Optional: allow on-demand browsing for ChatGPT users
User-agent: ChatGPT-User
Allow: /

# Optional: block training crawler if you want retrieval without training
User-agent: GPTBot
Disallow: /

    OpenAI publishes these three user agents and treats each independently. You can allow OAI-SearchBot for ChatGPT Search visibility and still disallow GPTBot from using your content for model training. The settings do not conflict. OpenAI’s systems typically recognize robots.txt changes within 24 hours.

    Step 3: Structure Pages for the Citation Filter

    Retrieval is necessary but not sufficient. Once your page is in the candidate set, the model decides whether to quote it. Pages that get quoted share a structural pattern.

    Direct answers in the first 100 words

    ChatGPT cites sources that answer the question fully. Partial answers lose to complete ones. Lead each page with a clean direct-answer paragraph: question implied or stated, answer in the next sentence, supporting detail after. This is the same pattern that wins featured snippets, which is not a coincidence — answer engines and snippet engines reward the same structure.

    JSON-LD schema

    An AirOps study of 548,534 pages found pages with JSON-LD markup posted a 38.5% citation rate versus 32.0% without it. Article, FAQPage, and HowTo schema are the highest-leverage types. Add them.

    Word count: 500–2,000

    Pages between 500 and 2,000 words performed best in the same AirOps study. Pages longer than 5,000 words were cited less often than pages under 500. The mechanism is mechanical: long pages overflow the retrieval context window, and the model defaults to shorter, denser sources it can quote in full.

    Freshness

    Content updated within 30 days received 3.2x more citations than older material. The fix is not faked freshness — it is genuine updates: a new stat, a new case, a corrected claim. Update the date when you update the content, not before.

    Step 4: Build the Authority Layer

    Structure gets you cited once. Authority gets you cited repeatedly. AirOps found sites with over 32,000 referring domains are 3.5x more likely to be cited by ChatGPT than sites with fewer than 200. You do not need 32,000 — you need to be in the upper band of your topical neighborhood.

    ChatGPT’s citation pattern leans heavily on Wikipedia (roughly 48% of top citations in multiple studies) and large news/media properties. The practitioner read on that: ChatGPT favors sources with multi-source third-party validation. Build the kind of citations on the open web that Wikipedia editors accept — peer-reviewed studies, primary sources, named author attribution, transparent methodology.

    Step 5: Track Your Citation Footprint

    You cannot manage what you do not measure. The minimum tracking stack for 2026:

    • Server log monitoring for OAI-SearchBot user agent — confirms OpenAI is actually crawling. If you allowed the bot in robots.txt three weeks ago and there are zero OAI-SearchBot hits in your logs, something is wrong (CDN block, IP firewall, misconfigured allow rule).
    • Manual citation audits — pick 10 priority queries, run them in ChatGPT with the Search toggle on, log which domains get cited. Repeat weekly. A spreadsheet beats no tracking.
    • Bing position tracking — because ChatGPT pulls from the Bing index, Bing rankings are a leading indicator. If your Bing position drops, ChatGPT visibility drops behind it.

    The Practitioner Summary

    Ranking in ChatGPT in 2026 is not mysterious. It is a four-gate funnel: Bing index → OAI-SearchBot crawl access → retrieval into the candidate set → citation selection. Most sites fail at gate one (not indexed in Bing) or gate two (OAI-SearchBot blocked or not addressed). Sites that clear those two gates and write pages that answer the question fully, with schema and a 500–2,000-word range, will land in the 15% that get quoted.

    Treat ChatGPT Search like a separate search engine that happens to share an index with Bing. Optimize for the index. Allow the crawler. Write the page. The rest follows.

  • Is Anything Actually Fetching Your llms.txt? A Server-Log Verification Method

    Is Anything Actually Fetching Your llms.txt? A Server-Log Verification Method

    You shipped an llms.txt file. You curated the links, you paired it with robots.txt, you validated the format. Now answer the only question that matters: is anything actually requesting it? Most site owners never check — and the data from 2026 suggests the honest answer, for most domains, is “almost nothing.” This is the verification step that turns llms.txt from an act of faith into a measurable signal. Here is how to read your own server logs and find out exactly what is fetching the file you published.

    Why verification matters more than the file itself

    The uncomfortable finding of the last year is that publishing llms.txt and benefiting from llms.txt are two different things. In OtterlyAI’s 90-day crawler study, only 0.1% of AI crawler requests touched /llms.txt at all — 84 requests out of 62,100 total AI bot visits — and the file received far fewer visits than the average content page (OtterlyAI GEO study). As of Q1 2026, no major AI company — OpenAI, Google, Anthropic, Meta, or Mistral — has publicly committed to reading or acting on llms.txt in production systems, though GPTBot does fetch the file occasionally (AEO Engine).

    That does not make the file worthless. It makes measurement the whole game. If you cannot tell whether a crawler ever requested the file, you cannot tell whether your time was wasted, whether a platform quietly started honoring it, or whether your file is returning a silent 404. Verification is the difference between strategy and superstition.

    The five-minute server-log check

    Every fetch of your llms.txt file leaves a row in your access log. The job is to isolate requests to that path, then filter by the user-agents that belong to AI systems. On any server with standard combined-format Apache or Nginx logs, this one-liner does the first pass:

    grep -E "/llms(-full)?\.txt" /var/log/nginx/access.log | \
  grep -E -i "GPTBot|OAI-SearchBot|ChatGPT-User|ClaudeBot|Claude-User|Claude-SearchBot|PerplexityBot|Perplexity-User|Google-Extended|Google-CloudVertexBot|Amazonbot|CCBot|Applebot|meta-externalagent|MistralAI-User|bingbot"

    The first grep narrows to requests for llms.txt or llms-full.txt. The second filters to the known AI crawler user-agent strings documented across 2026 reference work (No Hacks AI User-Agent Landscape 2026; Momentic crawler list). Each surviving line tells you three things: which bot, what time, and the HTTP status code it received.

    That status code is the part people skip. A 200 means the bot got your file. A 404 means you have been congratulating yourself over a file the crawler never actually reached — a misconfigured path, a redirect loop, or a build step that drops the file on deploy. A 301 or 302 means it is being redirected, and not every crawler follows redirects for this path. Read the status column before you read anything else.

    Turn the raw hits into a monthly cadence table

    One grep tells you whether the file is reachable. To know whether anything is changing, you need the same query run on a schedule and counted by bot. Extend the pipeline to a count:

    grep -E "/llms(-full)?\.txt" /var/log/nginx/access.log* | \
  grep -E -i -o "GPTBot|ClaudeBot|PerplexityBot|Google-Extended|bingbot|Amazonbot|CCBot|Applebot" | \
  sort | uniq -c | sort -rn

    This produces a leaderboard of which AI user-agents requested your llms.txt across all retained logs. Capture that number on the first of each month and you have a cadence series. The signal you are watching for is not the absolute count — it will be small — but the direction: a bot that appears for the first time, a bot whose hit count jumps, or a bot that goes silent. Those inflection points are the leading indicators that a platform has changed how it treats the file.

    What you see in the log What it means Action
    No requests to /llms.txt at all File may be unreachable, or simply not yet fetched — both are common Request the URL yourself; confirm a clean 200 before assuming neglect
    200 from GPTBot, low frequency Consistent with reported behavior — GPTBot fetches occasionally Log the cadence; treat as baseline, not a ranking signal
    404 or 301 on the path Crawler is not getting the file you think you published Fix the path/redirect today — this is a silent failure
    A new bot appears month-over-month A platform may have started fetching the file Note the date; correlate with any citation or referral changes

    Cross-check against your content fetches

    The llms.txt hit count means little in isolation. Compare it against how often the same bots fetch your actual content pages. If GPTBot pulls forty content URLs a day and never touches llms.txt, the file is not part of how that crawler discovers you — your content’s own structure and internal linking are doing the work. The practical monitoring approach documented for 2026 is exactly this: a server-log dashboard built against the major user-agents, watching cadence and path-preference shifts month over month (Digital Applied 30-day log study). The same study notes distinct personalities worth knowing — GPTBot crawls more aggressively than most assume, ClaudeBot is more patient than its volume suggests, and PerplexityBot is quieter than its share-of-voice would predict.

    What to do with the answer

    If your logs show the file is reachable and occasionally fetched, you are in the normal range for 2026 — keep the file current and keep measuring. If they show a 404, you found a real bug that no amount of curation would have fixed. And if they show a brand-new bot starting to request the path, you have spotted a platform behavior change before the blog posts catch up to it. That last case is the entire payoff: the practitioners who read their own logs will know the standard started mattering weeks before the ones who only read about it. Verification is not the boring final step of an llms.txt rollout. On a standard that nobody has formally committed to honoring yet, it is the only step that produces evidence instead of hope.

  • LSAs vs Google Ads vs SEO for Restoration Companies in 2026: The Channel Comparison Vendors Won’t Show You

    LSAs vs Google Ads vs SEO for Restoration Companies in 2026: The Channel Comparison Vendors Won’t Show You

    If you own a restoration company in 2026, your marketing budget is being eaten alive by three channels fighting for the same lead: Google Local Services Ads, Google Search Ads, and SEO. The owners I talk to are spending six figures a year and still can’t tell me, with a straight face, which channel is actually paying them. So let’s settle this with the numbers vendors don’t put in their pitch decks.

    The water damage CPC is the most expensive in home services

    Reported cost-per-click for top water damage restoration keywords has climbed as high as the $200–$250 range in competitive metros, with industry sources citing top-of-page bids reaching around $250 per click for terms like “water damage restoration [city].” Average emergency restoration keywords more commonly land in the $40–$100 CPC range depending on geography and time of day. That is not a typo. A single click — not a lead, not a job — can cost more than most contractors charge for a furnace tune-up.

    The reason owners keep paying it is simple. A water mitigation job typically prices in the $3,000–$15,000+ range depending on category and scope. At those ticket sizes, a $300 cost-per-lead and a 25% close rate still pencils out. But “pencils out” is doing a lot of heavy lifting in that sentence — and that’s where most owners stop running the math.

    The three channels, ranked by what they actually do

    Google Local Services Ads (LSA): the most consistent ROI lever right now

    LSA cost-per-lead in restoration is widely reported in the $80–$180 range for water damage, with mold remediation reported between roughly $60 and $250 depending on market. Conversion rates from lead to booked job tend to be reported around the 10–15% range — higher than standard Google Search Ads — because Google charges per qualified phone call or message, not per click.

    The bottom line on LSAs: if you do not have Google Guaranteed status set up and your service area dialed in, this is the first thing you fix this quarter. The catch nobody mentions: Google ended the credit policy for “job type not serviced” and “geo not serviced” disputes in 2025, meaning junk leads now come out of your pocket with no refund pathway. You have to dispute aggressively on the categories Google still credits, or your effective CPL drifts 15–25% higher than the platform number says it is.

    Google Search Ads (PPC): the channel you run when you have no other choice

    Average reported cost-per-lead for Google Search Ads in restoration falls in the $150–$400+ range, with the high end concentrated in metros with two or more national franchise advertisers bidding against you. Conversion from click to lead in well-managed accounts typically lands in the 5–10% range — half of what LSAs deliver.

    PPC has one thing LSAs don’t: control. You set the keywords, you set the geo, you set the ad copy, you decide whether you want commercial water damage leads or residential mold leads or fire restoration leads. If you are running a multi-location shop or chasing commercial work specifically, you cannot live on LSAs alone — the lead types are too restricted. But if you are a single-location residential operator, every dollar in PPC should be earning its keep against the LSA dollar, and most of the time it isn’t.

    SEO: the long-term asset everyone wants to own and almost nobody finishes building

    Cost-per-lead from established organic rankings is commonly reported in the $75–$150 range — roughly half the cost of paid channels at maturity. The trade-off is time. Restoration SEO in competitive metros typically takes 12–18 months of consistent investment before it produces meaningful lead flow, with initial signal in 3–6 months for low-competition local terms.

    The honest read: most restoration owners start SEO, get impatient at month four when paid channels are still doing all the work, and either fire the agency or stop publishing content. Then they restart 18 months later with a different vendor and the same outcome. SEO works. It works exactly the way the calendar says it will work. The companies that win with it are the ones who treat it like a 24-month commitment, not a 90-day experiment.

    What the channel mix should actually look like

    For a residential-focused restoration company doing $1M–$5M in revenue, a defensible channel mix in 2026 looks something like this:

    • LSA: 35–45% of paid budget. Highest reported ROI of any paid channel in restoration. Cap is the daily lead volume Google will give you, not the budget.
    • Google Search Ads: 25–35% of paid budget. Covers the lead types LSAs cannot serve — commercial work, specific service lines, and overflow when LSAs hit daily caps. Required for any multi-location shop.
    • SEO and content: 20–30% of total marketing budget. Treat as 18–24 month asset build. Tracked separately from paid CPL because the unit economics only stabilize at month 12+.
    • Referrals and direct outreach: ongoing, no fixed budget. Reported industry-wide as the lowest-CAC channel and the one with the shortest break-even window. Build a plumber/agent/property manager referral program before you spend another dollar on paid ads.

    The split that gets restoration owners in trouble is putting 80% into paid and 20% into “we’ll get to it” SEO. Two years later they are completely dependent on Google’s auction prices, and the auction prices have gone up every year of the last five.

    The metric that actually matters

    Cost-per-lead is the metric every vendor reports. It is the wrong number to optimize for. The number that matters is fully-loaded cost-per-acquired-job, which is CPL divided by your channel-specific close rate, plus the labor cost of the CSR who fielded the call, plus the credit card processing on whatever portion of the job is paid out-of-pocket, minus the franchise or TPA fee if applicable.

    Most restoration owners do not have this number for any of their channels. They have CPL from the platform dashboards, they have revenue from the job management software, and the two systems have never talked to each other. Fix that before you change a single bid. The owner who knows their fully-loaded acquired-job cost by channel makes better decisions in five minutes than the owner who doesn’t makes in a quarter.

    The bottom line

    LSAs are the highest-ROI paid channel in restoration in 2026 and should be the first lever you optimize. Google Search Ads are required for any operator chasing commercial work or running multiple locations, but they should never be your largest line item. SEO is the long-term insurance policy against rising auction prices, and the only restoration owners who get the payoff are the ones who treat it like a 24-month commitment and refuse to flinch at month six.

    If you are spending more than $5,000 a month on Google Search Ads and you do not yet have LSAs set up, you are leaving the most profitable channel in restoration on the table. Start there.

    Frequently Asked Questions

    What is the average cost per lead for water damage restoration in 2026?

    Reported cost-per-lead for water damage restoration in 2026 ranges from roughly $80–$180 on Google Local Services Ads, $150–$400+ on Google Search Ads, and $75–$150 from mature organic SEO. Actual costs vary significantly by metro, competition, and lead-type mix.

    Are Google Local Services Ads better than Google Ads for restoration?

    For most residential restoration operators, LSAs deliver a lower cost-per-lead and a higher reported lead-to-job conversion rate than standard Google Search Ads. LSAs charge per qualified call rather than per click, which is why the ROI tends to be more consistent. Multi-location shops and commercial-focused operators still need Google Search Ads to cover lead types LSAs do not serve.

    How long does SEO take to work for a restoration company?

    Restoration SEO in competitive metros typically takes 12–18 months of consistent investment before it produces meaningful lead flow. Initial ranking signal often appears in 3–6 months for low-competition local terms, but the cost-per-lead advantage versus paid channels only stabilizes after month 12.

    What percentage of a restoration marketing budget should go to paid ads?

    A common defensible split for a residential restoration company in 2026 is roughly 60–70% of total marketing budget on paid channels (LSA + Google Search Ads) and 20–30% on SEO and content, with referral programs running in parallel at minimal incremental cost. Going above 80% paid concentrates risk in the Google auction.

    📖 Recommended Reading in Restoration Intelligence

  • GEO Case Studies Teardown: What 5 Published Wins Reveal About Generative Engine Optimization in 2026

    GEO Case Studies Teardown: What 5 Published Wins Reveal About Generative Engine Optimization in 2026

    If you want to know whether generative engine optimization actually moves the needle, stop reading think pieces and look at what shipped. The case-study record from 2025 and early 2026 is now thick enough to draw practitioner conclusions: which interventions correlate with citation lift, how fast the curve bends, and what the conversion side of the funnel does once AI traffic shows up. This is a working teardown of the published case studies — what was done, what changed, and what the implementation pattern looks like underneath.

    Case 1: B2B SaaS — 575 to 3,500 AI-referred trials in roughly seven weeks

    A $30M+ ARR B2B SaaS company documented in Digital Agency Network’s GEO case study roundup moved from 575 AI-referred free trials per period to over 3,500 in about seven weeks. The intervention sequence was content restructuring for citability — clear one-sentence definitions at the top of each section, statistics and comparisons rendered as tables rather than buried in prose, and step-by-step frameworks that LLMs can extract verbatim. The first 40–60 words under every H2 carried the answer to that H2’s implicit question.

    The implementation pattern under this win is what matters: the company did not write new articles. It rebuilt existing articles to surface the answer first. That is the cheapest possible GEO intervention — restructure, do not republish.

    Case 2: B2B SaaS — citation rate from 8% to 12% in four weeks

    Discovered Labs documented a B2B SaaS case where ChatGPT citation rate on tracked queries moved from 8% to 12% by week four of an engagement, with the company’s VP of Marketing noting they had been “invisible for 18 months despite solid SEO work.” The 50% relative lift came from the same restructuring pattern plus aggressive entity-binding — explicit company name, product name, and category definition repeated in citation-friendly positions throughout each asset.

    The data point worth carrying: traditional SEO authority does not automatically translate to LLM citation. The two systems read pages differently, and the page-level rewrite is what closes the gap.

    Case 3: CloudEagle — 33 pages optimized, 33% increase in AI citations

    CloudEagle’s published GEO result, cited across multiple 2026 case study summaries including AlphaP’s real-world GEO examples, is one of the cleanest dose-response curves in the public record. Optimize 33 pages → 33% increase in AI citations. The ratio is suspicious as a coincidence but tells the practitioner the right thing: GEO is a per-page intervention, and aggregate lift scales roughly with how many pages you treat. There is no site-wide tag you can flip. Each asset gets its own restructure.

    Case 4: HubSpot — template rebuild, not content rebuild

    HubSpot’s internal AEO case study, summarized in HubSpot’s own AEO case study writeup, is the cleanest illustration of the structural fix. HubSpot already ranked for thousands of marketing queries — the volume was there. The barrier was that answers were buried multiple paragraphs deep, written in traditional long-form. The fix was a template rebuild: every article restructured so the first 40–60 words under each H2 or H3 directly answered the implicit question of that heading.

    This is the playbook to copy. If your site has any existing traffic, restructuring beats writing new content. The audit question is: under every H2 on every page, do the first three sentences answer the question that H2 raises?

    Case 5: Netpeak USA — 120% revenue lift, 693% AI traffic growth

    Stackmatix’s AEO case study compilation documents Netpeak USA’s conversational ecommerce GEO campaign producing +120% revenue and +693% AI traffic growth. The mechanism: product and category pages restructured around buyer questions (“what is the best X for Y?”, “X vs Y comparison”, “how do I choose X?”) with direct, hedged answers up top and detailed reasoning below. The pattern works because AI search engines synthesize buying decisions from extractable answer fragments, and ecommerce pages historically bury the answer under marketing copy.

    The structural pattern under every win

    Read the five cases together and one implementation discipline emerges. Every published GEO win in the public record traces back to the same physical change to the page:

    1. Answer first. The first 40–60 words under every H2 directly answer the question that heading raises. No setup, no transition paragraph, no scene-setting.
    2. Tables over prose for comparison data. Articles with 15+ data points receive measurably more AI citations than those with fewer than five, per the research synthesized in Marketing LTB’s 2026 GEO statistics roundup. Tables make those data points extractable.
    3. Entity binding. Company name, product name, and category definition explicitly stated in citation-friendly positions, not just implied through context.
    4. Stepwise frameworks. Procedural content rendered as numbered steps that LLMs can extract verbatim into responses.
    5. Citable sources inline. Authoritative external citations placed adjacent to claims, not banished to a references section at the bottom.

    What the cases do not prove

    The published record has selection bias the size of a building. Every case study you can read is a published win. The agencies and SaaS companies that ran a GEO campaign and got nothing are not writing blog posts about it. Read the cases for the structural patterns, not the percentage lifts — the lifts are a function of starting baseline, vertical, and how invisible the brand was before the intervention.

    Two other limits worth naming. First, conversion-rate claims about AI-referred traffic (“converts at a higher rate than organic” appears in over half of marketer surveys per the 2026 HubSpot State of Marketing report) come from self-reporting, not third-party measurement. The directional point is probably right — qualified intent behind an LLM query — but the magnitude is unverifiable. Second, AI citation rates are measured against the agencies’ own tracked query sets. Those sets are chosen for relevance to the client, which means baseline visibility is artificially low. The 8% → 12% case is real; whether it generalizes to a random query set is unknown.

    What to do tomorrow if you are starting from zero

    Pick ten pages on your site that already rank in positions 4–15 for queries with commercial intent. Open each one. Under every H2, rewrite the first 40–60 words so they directly answer the question that heading raises. Convert any prose comparison into a table. State your company name, product category, and the specific problem you solve in the opening paragraph. Add a sources list with authoritative citations.

    That is the intervention every published GEO case study reduces to. Ten pages, one week of writing work. The case study record suggests you will see citation movement in three to six weeks if the queries you care about already have AI Overview or LLM citation surface area at all. If they do not, the intervention is still right — you are positioning for when they do.

    FAQ

    How long until GEO interventions show measurable lift?

    Published cases show citation movement at the four-week mark (the 8% → 12% B2B SaaS case) and traffic movement at six to eight weeks (the 575 → 3,500 trials case at roughly seven weeks). Three months is the standard window quoted in agency case studies for material citation rate change.

    Does traditional SEO authority help GEO?

    Partially. Pages that already hold featured snippets are disproportionately pulled into Google AI Overviews, per multiple 2026 AEO summaries. But the B2B SaaS case where the company was “invisible for 18 months despite solid SEO work” shows that authority alone does not produce citations — page-level structural changes are the missing ingredient.

    How many pages do I need to optimize before I see results?

    CloudEagle’s case (33 pages → 33% citation lift) suggests the dose-response is roughly linear at small scale. Most published case studies show meaningful aggregate movement starting around 10–30 pages restructured. Below that, you are testing the methodology rather than expecting measurable lift.

    Is the citation rate lift actually translating to revenue?

    The published evidence says yes for ecommerce (Netpeak USA’s +120% revenue) and trial-driven SaaS (the 575 → 3,500 trials case). For brand and consideration-stage content the answer is murkier — AI citations probably influence brand recall and assisted conversion, but the attribution chain to revenue is harder to draw cleanly and the case study record is thin on this slice.

    What is the cheapest GEO intervention with the highest published return?

    Restructuring existing pages that already rank. The HubSpot template rebuild and the 575 → 3,500 trials case both used this approach. No new content, no new authority work, no link building — just rewriting the first 40–60 words under every H2 and converting prose comparisons into tables.

  • How to Measure LLM Visibility in 2026: The GA4 + Response-Side Stack

    How to Measure LLM Visibility in 2026: The GA4 + Response-Side Stack

    Traditional analytics platforms can’t see the most important impression you’re making in 2026. When a user asks ChatGPT, Perplexity, Gemini, or Claude about your category, your brand either shows up in the answer or it doesn’t — and your GA4 dashboard has no idea either way. This is the measurement blind spot at the center of generative engine optimization. If you can’t measure LLM visibility, you can’t optimize for it.

    This guide walks through the measurement stack that actually works in 2026: the GA4 channel grouping that catches AI referral traffic, the manual verification protocol that costs nothing, and the dedicated LLM visibility platforms that automate prompt monitoring at scale. By the end, you’ll have a measurement framework you can run starting today.

    Why GA4 alone is not enough

    Standard web analytics measures what happens after the click. LLM visibility is what happens before the click — or instead of one. According to widely cited industry reporting, a large share of AI search sessions end without the user ever clicking through to a source, which means the brand impression inside the AI response is often the only impression you get. GA4 cannot see that impression. It cannot see when ChatGPT recommends you in a comparison. It cannot see when Perplexity cites your article as a source for an answer.

    You still need GA4 — AI referral traffic is real, growing, and converts well — but you need it as one layer of a two-layer stack. Layer one is referral-side measurement, which captures the users who actually click through from AI platforms. Layer two is response-side measurement, which monitors what AI platforms are saying about you whether anyone clicks or not.

    Layer one: catching AI referrals in GA4

    GA4 does not have a built-in “AI” channel. By default, traffic from ChatGPT, Perplexity, Claude, and Gemini gets bucketed into the generic Referral channel, where it disappears next to social and partner sites. The fix is a custom channel group that uses a referrer regex to peel AI traffic out into its own bucket.

    In GA4, go to Admin → Data Settings → Channel Groups, create a custom channel group, and add a new rule above the default Referral rule. Set the conditions to Source matches regex and use a pattern like this:

    chatgpt\.com|openai\.com|perplexity\.ai|claude\.ai|anthropic\.com|gemini\.google\.com|copilot\.microsoft\.com|deepseek\.com|you\.com|meta\.ai|poe\.com

    The order matters. Your AI Traffic rule must sit above the Referral rule in the priority list, or AI traffic will be captured by Referral first and never reach your custom channel. Once the rule is live, you can build Explorations that segment AI traffic by source, page, conversion rate, and engagement time — and compare that segment against organic, direct, and social.

    The referrer attribution gap

    One caveat: not every AI click passes a referrer. ChatGPT’s free tier in particular has been reported to strip referrer headers in many configurations, meaning a meaningful share of ChatGPT traffic shows up as Direct in GA4 rather than as a chatgpt.com referral. This is a known limitation across the industry. Treat your AI referral numbers as a floor, not a ceiling, and use response-side monitoring to fill in the gap.

    Layer two: response-side monitoring

    This is the measurement that traditional SEO never needed. You’re no longer just asking “did anyone visit?” — you’re asking “what is the AI saying about me?” There are two ways to answer that question.

    The manual verification protocol

    The free, no-tool approach is a structured query log. Build a list of 15 to 25 prompts that a buyer in your category would realistically type into an AI assistant. Be specific. “Best CRM for small B2B teams” is a prompt. “What is a CRM” is not — that’s a research query, not a buyer query.

    Once a week, run every prompt through each AI platform you care about — typically ChatGPT, Perplexity, Gemini, and Claude — and record three things per query: whether your brand was mentioned, whether your domain was cited as a source, and what position your brand appeared in if it was named alongside competitors. A simple spreadsheet with prompt, date, platform, mention (yes/no), citation (yes/no), and position is enough to start. Week-over-week deltas on this sheet will tell you whether your GEO and AEO work is moving the needle.

    This is slow and manual but it’s the only method that gives you ground truth. The dedicated platforms below are essentially automating this protocol — running the same kind of prompt log against the same APIs on a daily schedule. If you’re under $1,000/month in marketing spend, run it manually. If you’re past that, automate it.

    Dedicated LLM visibility platforms

    A new category of tools emerged in 2025 and matured in 2026 specifically to monitor LLM responses. They all do roughly the same thing — run your target prompts daily across multiple AI engines, score visibility, track which sources the AIs cite, and surface competitor gaps — but they segment by price point.

    At the budget end, Otterly.AI offers monitoring plans starting around $29/month, with a Share of AI Voice metric and time-to-first-data of under ten minutes after signup. It’s the simplest entry point for teams that just want a citation-frequency dashboard. In the mid-market, Peec AI starts around €89/month and emphasizes multilingual coverage and actionable recommendations — it doesn’t just tell you you’re invisible, it suggests what to change. At the enterprise tier, Profound starts around $499/month and adds Prompt Volumes, which estimates real AI search demand by topic with demographic breakdowns. SOC 2 compliance and dedicated onboarding generally start at the $1,000+ enterprise tiers across this category.

    Other platforms in active use this year include Semrush’s AI Toolkit, SE Ranking’s SE Visible, Goodie AI, Rankscale, Nightwatch, AirOps, and Searchable. The category is moving fast — pricing and features change quarterly — so verify the current state of any platform before committing.

    The six KPIs to track

    Whatever measurement stack you use, the same handful of metrics will tell you whether GEO is working. Organize them into leading and lagging indicators:

    Leading indicators (response-side, change first):

    • Mention Rate — the percentage of monitored prompts where AI responses mention your brand name. This is the broadest signal.
    • Citation Rate — the percentage of monitored prompts where your domain is cited as a source, not just named. Citation is stronger than mention because it implies the AI is treating your content as authoritative.
    • Position — when your brand is named alongside competitors, where in the list does it appear. First-named brands get disproportionate attention.

    Lagging indicators (referral and revenue-side, change later):

    • AI Referral Sessions — total sessions from your AI Traffic channel group in GA4.
    • AI Referral Engagement — engagement rate and average engagement time for the AI segment, compared to organic. Strong AI referral traffic typically engages longer because the user arrived with intent already framed by the AI.
    • AI-Influenced Conversions — conversions where AI was part of the attribution path, even if not the last touch.

    Tier-one metrics move first because content changes affect what AIs say within days to weeks. Tier-two metrics lag because they require enough traffic to be statistically meaningful, which can take a quarter or more to develop.

    The minimum viable setup

    If you do nothing else this week, do these three things:

    1. Add the AI Traffic channel group to GA4 using the regex above and move it above Referral in priority.
    2. Build a 15-prompt spreadsheet of buyer-intent queries for your category and run them once across ChatGPT, Perplexity, Gemini, and Claude. Record mention, citation, and position.
    3. Set a calendar reminder to repeat step two every Friday for four weeks. After four weeks you’ll have a real trendline.

    That setup costs nothing and produces the measurement layer that lets you tell whether your GEO, AEO, and LLMs.txt work is actually compounding — or whether you’re guessing. Once the trendline is stable, evaluate whether automating with Otterly, Peec, or Profound is worth the spend. For most operators, the manual protocol gets you 80% of the insight at 0% of the budget.

    Frequently Asked Questions

    What is LLM visibility?

    LLM visibility is the measurement of how often, and how prominently, a brand or website appears in responses generated by large language models like ChatGPT, Perplexity, Gemini, and Claude. It is the response-side counterpart to traditional search ranking — instead of measuring where you appear in a results page, you’re measuring whether AI assistants mention or cite you when answering questions in your category.

    Can GA4 track AI traffic from ChatGPT and Perplexity?

    GA4 can track AI referral clicks if you create a custom channel group with a referrer regex matching AI domains and place it above the default Referral rule. It cannot track impressions inside AI responses where the user doesn’t click through, and ChatGPT’s free tier often strips referrers entirely, so a portion of AI traffic still lands in Direct. Treat GA4 numbers as a floor.

    What is the difference between mention rate and citation rate?

    Mention rate measures the percentage of monitored AI prompts where your brand name appears anywhere in the response. Citation rate measures the percentage where your specific domain or URL is referenced as a source. Citation is a stronger signal because it indicates the AI is treating your content as authoritative, not just naming you in passing.

    Which LLM visibility tool should I use in 2026?

    For budget-conscious teams, Otterly.AI starts around $29/month and gets you to first data in minutes. For mid-market needs with multilingual coverage and recommendations, Peec AI starts around €89/month. For enterprise teams that need prompt-volume demand data and SOC 2 compliance, Profound starts around $499/month. Verify current pricing before purchasing — the category moves quickly.

    How often should I check my LLM visibility?

    For manual tracking, weekly is the right cadence — frequent enough to catch movement, infrequent enough to avoid noise. Dedicated platforms typically run automated checks daily and let you review weekly. Don’t expect day-to-day stability; AI responses have inherent variance, so look at week-over-week and month-over-month trends rather than single data points.

  • Google AI Overviews After the May 2026 Update: What Changed and the New Citation Playbook

    Google AI Overviews After the May 2026 Update: What Changed and the New Citation Playbook

    Google shipped one of the most consequential AI Overviews updates of the year on May 6, 2026 — and most SEO teams still have not adjusted their content templates to match. The update changed what gets cited, where citations are drawn from, and how users decide which links to actually click. This is the practitioner walkthrough: what shifted, the data behind it, and the on-page changes that move the needle in the new system.

    What Google Actually Changed on May 6, 2026

    Google’s own announcement (How AI Mode and AI Overviews help you explore the web) named five shifts to the Overviews surface:

    1. Forum and social perspective blocks — Overviews now embed direct quotes from Reddit, WordPress blogs, and public forums in a dedicated “perspectives” section.
    2. Subscription-aware citation highlights — links from news outlets the searcher is logged in to are visually flagged. Google’s internal test data showed those flagged links were “significantly more likely” to be clicked.
    3. Suggested exploration topics — bulleted follow-up queries now render at the end of many AI responses, which means downstream traffic flows depend on whether your domain ranks for the fan-out queries, not just the head term.
    4. Further Exploration section — a bulleted-link cluster plus an “Expert Advice” snippet pulling from articles, reviews, and forum threads.
    5. Hover-to-preview link cards — hovering a citation now triggers a card showing site name, page summary, and metadata before the click.

    Two of those five — perspectives blocks and Further Exploration — are net-new citation slots. The other three change which citations users actually convert on.

    The Citation Math Has Shifted

    The most important measurement from the last 60 days: in March 2026, the share of AI Overview citations pulled from pages ranking in Google’s organic top 10 dropped to 38%, down from 76% in July 2025 (500M-keyword analysis). 31% of cited sources now rank in positions 11–100, and another 31% rank outside the top 100 entirely for the query they get cited on.

    Translation for practitioners: Overviews are no longer a rank-amplifier. They are an independent retrieval layer. A page that ranks #47 with the right passage structure can outcompete a page that ranks #3 with the wrong structure. Domain Authority correlation with citation selection is now r=0.18 — effectively noise. Semantic completeness correlation is 0.87.

    The Passage That Gets Cited

    AI Overview extracts cluster tightly around 134–167 words per passage, with 62% of featured content falling in the 100–300 word range. Position inside the article matters: 44.2% of citations are pulled from the first 30% of the body, 31.1% from the middle, 24.7% from the conclusion (Wellows ranking factor study). Lead-heavy structure is no longer a copywriting preference — it is the extraction surface.

    The structural pattern that wins, repeatable across H2 sections:

    <h2>[Specific question phrased as a noun phrase]</h2>
<p><strong>[One-sentence direct answer with a named entity or number.]</strong></p>
<p>[Supporting detail with verifiable source attribution.]</p>
<p>[Nuance, caveat, or contrast — kept under the 167-word ceiling.]</p>

    Each H2 block becomes a standalone extractable unit. If your article only answers the headline question, you compete for one citation. If five H2 blocks each answer a distinct fan-out question, you compete for five.

    Schema That Earns Citations Now

    Properly marked-up pages show 73% higher selection rates in AI Overviews versus unmarked content. The three schema types doing the most work in the May 2026 surface:

    • FAQPage — feeds the Further Exploration section directly. Each Question/Answer pair is treated as a passage candidate.
    • Article with author and datePublished — freshness is now a citation factor. Content under three months old is 3× more likely to be cited.
    • HowTo with step-level markup — extracted into the Expert Advice snippet when the query is procedural.

    A minimal Article block that hits the freshness and authorship signals Google’s extractor now reads for:

    {
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "...",
  "author": { "@type": "Person", "name": "...", "url": "..." },
  "datePublished": "2026-05-14",
  "dateModified": "2026-05-14",
  "publisher": { "@type": "Organization", "name": "...", "logo": {...} }
}

    How to Show Up in the New Perspectives Block

    The forum-quote section is the biggest opportunity nobody is optimizing for yet. Reporting from TechCrunch’s coverage of the rollout confirmed Google is pulling from Reddit, public forums, and WordPress blogs explicitly tagged as personal perspective.

    Three practitioner moves:

    1. Author bylines with first-person framing on at least one article per topic cluster. Personal-perspective phrasing (“In our deployment of …”, “What surprised us was …”) signals firsthand experience to the extractor.
    2. Engage in the relevant subreddit with substantive comments under your real handle, then link your bylined article from your profile. Reddit threads are now a primary retrieval source for perspectives blocks.
    3. Tag personal-perspective posts with Person schema alongside Article schema. The Person entity is what Google ties to the firsthand-experience signal.

    What to Measure Starting This Week

    Citation share by query is the only metric that matters in this surface, and traditional analytics will not give it to you. Two practitioner approaches:

    • Manual citation logging — pull your 20 highest-value head terms and 50 fan-out queries, query them weekly in an incognito session, log whether your domain appears in the Overview, the perspectives block, or the Further Exploration list. Track citation share, not just rank.
    • Server-log analysis — Google’s Overview generator hits your pages with a distinct user agent and crawl signature. Filtering for those signatures gives you a leading indicator: pages getting hit by the extractor are pages being evaluated for citation.

    Cited pages earn 35% more organic clicks and 91% more paid clicks than uncited peers (Averi.ai citation study). Uncited pages on triggering queries lose 61% of their normal CTR. The gap between cited and uncited is now wider than the gap between position #1 and position #5 in classical SEO. Treat citation as the primary KPI.

    The Update in One Sentence

    Google has decoupled AI Overview citation from organic rank, opened two new citation slots (perspectives and Further Exploration), and is now rewarding firsthand-experience signals at the page and author level — the practitioners who restructure for passage-level extraction and earn citation in the new slots will pick up the traffic that used to flow to position-#1 pages.

  • Restoration Company Marketing in 2026: LSA vs Google Ads vs SEO — Real CAC Numbers

    Restoration Company Marketing in 2026: LSA vs Google Ads vs SEO — Real CAC Numbers

    Restoration company marketing is one of the most expensive paid-search categories in the United States. “Water damage restoration” keywords routinely clear $60–$85 per click in competitive markets, with reported outlier bids running well over $200 in metros like New York, Houston, and South Florida. Industry tracking has flagged some emergency-restoration terms breaking $500 per click in specific moments. Meanwhile, the average home-services lead via Google Local Service Ads (LSA) is roughly $53 — but water damage restoration sits at the premium end, with reported LSA cost-per-lead ranges of approximately $80–$180 depending on market.

    If you run a $3M–$15M restoration company, this is the single biggest line item that nobody on your team is staring at correctly. Owners hear “marketing” and think website. The real fight in 2026 is channel allocation: how much should you spend on LSA, how much on Google Search Ads, and how much on owned SEO — and at what point does each one stop scaling? Here is the honest breakdown a $5M owner needs before their next marketing budget meeting.

    The three channels that actually matter

    For commercial water and fire restoration in 2026, three channels do the heavy lifting: Google Local Service Ads (the LSA “Google Guaranteed” boxes at the very top of the SERP), Google Search Ads (the paid text ads below LSA), and organic SEO (the map pack plus blue links). Everything else — Yelp, Angi, HomeAdvisor, Facebook, programmatic display, lead-broker buys — is either supplemental, declining, or actively cannibalizing your margin. The first decision is choosing where the bulk of your new-customer budget goes among those three.

    Local Service Ads (LSA) — the default starting point in 2026

    LSA is the highest-real-estate placement on a phone screen, period. For emergency-driven categories like water damage and mold, that real estate matters more than anything else. Reported 2026 cost-per-lead for water damage restoration through LSA generally falls in the $80–$180 range, with some markets reporting averages closer to $100 in stable competitive conditions. On a $6,000 average ticket, even a $150 LSA lead at a 25–35% close rate produces a customer acquisition cost (CAC) of roughly $450–$600 — which is workable on jobs that gross $1,800–$2,400.

    The catch: Google removed credits for “job type not serviced” and “geo not serviced” leads in 2025, meaning every junk lead now hits your card with no recourse. You have to dispute leads inside Google’s dispute window and you have to answer your phone in under 30 seconds. LSA also weights reviews more heavily than any other channel — a 4.6 average will visibly underperform a 4.9 in the same zip code. If your review velocity is under 8 per month, fix that before you scale LSA spend.

    Google Search Ads — the diminishing-returns layer

    Below LSA, traditional Google Search Ads remain expensive and uneven. Reported 2026 average CPC for water damage restoration keywords falls into bands: bottom-of-funnel emergency keywords like “emergency water damage [city]” run $60–$85; less-direct terms like “water damage cleanup near me” run $40–$65; awareness-stage keywords like “what to do after a flood” run $20–$40. The trap is that close rates on Search Ads have been compressing for three reasons: LSA is taking the highest-intent clicks, AI Overviews are stealing informational queries, and click fraud from competitor bots remains nontrivial.

    For most restoration owners, Search Ads should be a defense-and-coverage play, not a primary growth channel. Bid on your own brand name to keep TPA programs and franchise competitors from arbitraging your traffic. Bid on the keywords LSA does not cover well (commercial, mold remediation, biohazard, contents pack-out). Cap monthly spend. Watch the CAC, not the CPC.

    SEO — the compounding asset that owners under-invest in

    Owned SEO — Google Business Profile plus a real content engine on the company website — is where the math eventually breaks in your favor. Multiple cross-industry benchmarks in 2025–2026 put the cost-per-lead delta between SEO and paid search at roughly 4x–6x lower for SEO once a site is mature (typically 12–18 months in). One widely cited cross-industry benchmark places SEO CPL near $31 versus paid search closer to $181. Restoration-specific tracking from agencies serving the category has reported organic CPL well under $50 in established markets after 18+ months of investment, while paid CPL stays in the $150+ band.

    The painful truth: SEO has a CAC of essentially zero on the marginal lead, but you cannot start it in January and expect leads in March. The owners who win SEO in restoration started 24 months ago, publish 6–12 useful pieces a month, and have a Google Business Profile with 500+ reviews and weekly post activity. If you have not started, your starting line is today — not next quarter.

    The honest allocation for a $5M restoration company in 2026

    A defensible 2026 marketing budget for a $5M residential and small-commercial restoration company, assuming 60% TPA-fed and 40% self-generated, looks roughly like this on the self-gen side:

    • LSA: 45–55% of self-gen ad spend. Highest immediate ROI. Cap by service area until close rate clears 30%.
    • Google Search Ads: 15–20%. Brand defense plus commercial, mold, and biohazard keywords LSA underweights.
    • SEO and Google Business Profile: 25–35%. This is content, on-site technical work, review-generation systems, and GBP weekly posts. Treat it as an asset, not a cost.
    • Everything else (Yelp, Angi, Nextdoor, paid social): under 5% combined, and only with tracked phone numbers per channel.

    If your current mix is 80%+ LSA and 0% SEO, you are renting your customer pipeline from Google at a rate that will keep rising. If your current mix is 80%+ SEO and 0% LSA, you are leaving the highest-intent emergency calls on the table for competitors who will outbid you for them.

    What to measure, not what to chase

    CPC, CPL, and CAC are not the same number. Restoration owners chase CPC because Google Ads dashboards make it visible. The metric that should sit on your monitor is blended CAC by channel, calculated quarterly: total channel spend divided by booked jobs from that channel. Track three more numbers next to it — close rate from lead to booked job, average ticket size by channel, and lifetime value adjustments for repeat and referral. A $180 LSA lead with a 35% close on $7,000 average ticket is a different business than a $40 organic lead with a 12% close on $2,200 average ticket — even though the CPL looks better in column B.

    Bottom line

    In 2026, LSA pays the bills, Search Ads defends the perimeter, and SEO is the only channel that compounds. The restoration owners who will be writing larger checks to their estimators in 2028 are the ones who fund all three this year — and the ones who refuse to pay $150 for a water damage lead because “that’s expensive” will keep watching franchise competitors and out-of-town aggregators win the calls that finance their own retirement. The expensive lead is the one you didn’t bid on at 2 a.m. when the house was actively flooding.

    Frequently Asked Questions

    What is a good cost per lead for a water damage restoration company in 2026?

    Reported 2026 ranges put water damage LSA cost-per-lead at roughly $80–$180, with some stable markets averaging closer to $100. Google Search Ads CPL is generally higher and more volatile. Organic SEO CPL trends well under $50 in mature programs after 12–18 months. Evaluate against your average job size and close rate, not against a flat industry number.

    Are Google Local Service Ads still worth it for restoration companies?

    Yes, for emergency categories LSA remains the most cost-efficient paid channel in 2026 because of its top-of-screen placement and pay-per-lead structure. The caveats: Google removed credit for off-service-area and wrong-job-type leads, review velocity matters more than ever, and you have to answer the phone in under 30 seconds to keep ranking.

    How long until SEO produces restoration leads?

    Plan on 9–12 months for a Google Business Profile and review-driven program to generate meaningful local-pack volume, and 12–18 months for content-driven organic leads to show up in any volume. Owners who treat SEO as a 6-month sprint nearly always abandon it 30 days before it would have started working.

    Should I use a marketing agency or build in-house?

    Under $3M revenue, hire one credible local agency for LSA plus GBP and own SEO with a part-time writer. From $3M–$10M, split LSA/Search Ads with an agency and bring SEO content in-house under a marketing coordinator. Above $10M, build the function internally with a director-level hire — at that size your marketing spend funds a salary and the data needs to live on your side of the firewall.

    📖 Recommended Reading in Restoration Intelligence

  • LLMs.txt in 2026: The 4-Element Spec, The Robots.txt Pairing, and How to Verify Crawlers Are Reading It

    LLMs.txt in 2026: The 4-Element Spec, The Robots.txt Pairing, and How to Verify Crawlers Are Reading It

    If you publish an llms.txt file this week, no major model is going to fetch it tonight. That is the honest 2026 read on the spec — and yet the file is still worth shipping for narrow, specific reasons. This guide covers the 4-element specification published at llmstxt.org, the robots.txt pairing that actually controls AI crawler behavior right now, and a server-log filter you can run to verify whether anyone is reading the file you just shipped.

    What llms.txt actually is (and what it isn’t)

    llms.txt is a Markdown file served at the site root — /llms.txt — proposed by Jeremy Howard of Answer.AI on September 3, 2024. The spec at llmstxt.org defines four elements: a required H1 with the project or site name; a blockquote summary; zero or more Markdown content sections (no headings); and zero or more H2-delimited file-list sections containing annotated Markdown links to deeper content. That is the entire specification. There is no header convention, no schema requirement, no robots-style allow/deny syntax.

    What llms.txt is not: it is not a substitute for robots.txt, it is not an access-control mechanism, and as of May 2026 it is not consumed at inference time by ChatGPT, Claude, Gemini, Perplexity, or Copilot in any documented production system. Server-log audits across multiple independent practitioners show GPTBot, ClaudeBot, and Google-Extended do not request /llms.txt in meaningful volume during routine crawls.

    The realistic 2026 use case is developer tooling. AI coding assistants and IDE agents — Cursor, GitHub Copilot, Claude Code, and similar tools — retrieve docs in real time, and a curated llms.txt cuts token waste by pointing them at canonical Markdown sources instead of HTML-rendered pages bloated with nav and tracking. Companies like Anthropic, Stripe, Cursor, Cloudflare, Vercel, Mintlify, Supabase, and LangGraph ship llms.txt for that reason.

    The 4-element template — a working example

    Here is a real, valid llms.txt for a hypothetical SaaS docs site. Copy this structure, change the project name, and you have a shippable file in under 30 minutes:

    # Acme Analytics

> Acme Analytics is a self-hosted product analytics platform for SaaS teams. This file points AI assistants and IDE agents at canonical Markdown documentation, not the rendered HTML.

Authoritative Markdown sources for product, API, and SDK documentation. Use the `.md` variant of any docs page (append `.md` to the URL) for a clean, agent-friendly version.

## Getting Started

- [Quickstart](https://acme.example/docs/quickstart.md): 10-minute setup, install through first event.
- [Concepts](https://acme.example/docs/concepts.md): events, properties, identities, sessions — definitions and examples.

## API Reference

- [REST API Reference](https://acme.example/docs/api/rest.md): every endpoint, request/response schema, rate limits.
- [Webhook Reference](https://acme.example/docs/api/webhooks.md): payload contracts and retry behavior.

## SDKs

- [JavaScript SDK](https://acme.example/docs/sdk/js.md): browser and Node, including server-side rendering notes.
- [Python SDK](https://acme.example/docs/sdk/python.md): server-side ingestion patterns.

## Optional

- [Changelog](https://acme.example/docs/changelog.md): version history, breaking changes flagged inline.

    Two practitioner notes. First, the spec uses an “Optional” H2 as a soft signal — links under that heading can be skipped by aggressive token budgets. Second, the file is most useful when every linked URL has a parallel .md Markdown version. If your site is pure HTML, llms.txt without paired Markdown does little.

    The robots.txt pairing — this is what actually controls AI bots today

    The lever that meaningfully controls AI crawler behavior in 2026 is robots.txt with user-agent–specific rules. Anthropic publishes official documentation for three bots — ClaudeBot for training, Claude-User for user-initiated fetches, and Claude-SearchBot for search indexing — and confirms all three honor robots.txt. OpenAI runs GPTBot (training) and OAI-SearchBot (live ChatGPT search). Google’s AI training opt-out is the Google-Extended user-agent. Perplexity uses PerplexityBot.

    The two-bucket pattern most practitioner sites should ship: block training-only crawlers, allow search and user-initiated retrieval so your content can still be cited in answers.

    # Allow AI search and user-fetch traffic (citations, attribution)
User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

# Block training-only crawlers
User-agent: ClaudeBot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

# Standard search crawler — leave open
User-agent: Googlebot
Allow: /

Sitemap: https://example.com/sitemap.xml

    One operational caveat: robots.txt is policy, not enforcement. Anthropic, OpenAI, and Google have all publicly committed their named bots to compliance, but unnamed scrapers and residential-IP harvesters routinely ignore it. For sites with sensitive content, pair robots.txt with WAF or Cloudflare bot-management rules at the edge.

    Structured data still does more heavy lifting than llms.txt

    If your goal is AI citation rather than IDE-agent retrieval, structured data on the page itself moves the needle more than llms.txt. The minimum stack for any article you want cited: Article schema with named author and publisher, FAQPage schema on any post that answers a discrete question, and speakable markup on the answer paragraphs. These get parsed during normal HTML fetches by every major AI crawler — no separate file required.

    How to verify your llms.txt is actually being read

    Ship the file, then run this server-log filter weekly for 30 days. On any standard access-log format (nginx, Apache, or a Cloudflare log push), grep for requests to /llms.txt and break them down by user-agent:

    grep "GET /llms.txt" /var/log/nginx/access.log \
  | awk -F\" '{print $6}' \
  | sort | uniq -c | sort -rn

    What you will almost certainly see in May 2026: a steady trickle of human curl requests, the occasional IDE agent fetch tagged with a Cursor or VS Code user-agent, and effectively zero hits from GPTBot, ClaudeBot, or Google-Extended. That null result is itself the measurement — it tells you llms.txt is a developer-experience asset right now, not an AI-citation asset, and your investment should match that reality.

    The recommended 2026 rollout

    For most sites, the right sequence is: ship the robots.txt user-agent rules above first, because those are enforceable today and shape every AI crawler interaction. Add structured data to every article that competes for AI citation. Then publish llms.txt — under 30 minutes of work — for the IDE-agent and dev-tooling upside, with no expectation of immediate search lift. When OpenAI, Anthropic, or Google publicly confirm production llms.txt consumption, you are already in position.

  • How Claude Cowork Trains Content and SEO Agency Teams to Think in Systems

    How Claude Cowork Trains Content and SEO Agency Teams to Think in Systems

    Last refreshed: May 15, 2026

    Content and SEO agencies sell a service that is, at its core, orchestration. A client says “get me more traffic” and the agency decomposes that into keyword research, content briefs, writer assignments, editorial review, optimization passes, publishing workflows, reporting cadences, and strategic adjustments. The people who do that decomposition well run profitable agencies. The people who do not burn hours and bleed margin.

    That orchestration skill — the ability to take a vague client goal and turn it into a sequenced, dependency-aware production plan — is the skill most agency employees never formally learn. They learn their lane: the writer writes, the SEO specialist optimizes, the account manager manages the client relationship. But nobody shows them the full system.

    Claude Cowork shows the full system. And it does it in a way that every person on an agency team can watch, absorb, and eventually replicate.

    The short answer: Claude Cowork decomposes complex tasks into parallel workstreams with visible progress and dependency tracking. For a content or SEO agency, that means watching the exact orchestration process that turns a client goal into a sequenced production plan — the skill that determines whether an agency scales or stays stuck.

    The Agency Scaling Problem

    Most content and SEO agencies hit a ceiling. That ceiling is not about talent or clients. It is about the number of people who can orchestrate. Usually it is one person — the founder or a senior director — who holds the operational logic: how work gets planned, how production gets sequenced, how quality gets maintained across concurrent client workstreams.

    Every other team member is a specialist executing within their lane. They are good at what they do. But they cannot plan a full campaign, sequence a production sprint, or manage the dependencies between research, creation, optimization, and publishing. So every new client adds load to the one person who can.

    Cowork does not solve that by doing the work. It solves that by making the orchestration visible so more people can learn it.

    How Cowork Maps to Agency Roles

    The SEO Strategist

    Give Cowork: “A new client in the commercial roofing space wants to rank for twenty target keywords within six months. They have an existing site with thin content and no internal linking strategy. Build me the complete SEO campaign plan from audit through month-six reporting.”

    Cowork decomposes this into audit, keyword clustering, site architecture recommendations, content production sequencing (which topics first based on difficulty and business value), technical optimization tasks, internal linking plan, external authority building, and a reporting cadence with milestone checkpoints. The strategist sees the full lifecycle — not just “here are keywords, go write content.”

    The Content Writer

    Writers at agencies typically receive a brief and deliver a draft. Give Cowork: “Build me the complete workflow for taking a content brief from assignment through published, optimized, and internally linked article — including all the steps the writer touches and the steps that happen around the writer.”

    Cowork shows the writer that their draft is one step in a longer chain: the brief was informed by keyword research and competitive analysis, the draft gets an editorial pass and an SEO optimization pass, the optimized piece gets schema markup and internal links before publishing, and after publishing it gets tracked for ranking performance that informs future briefs. The writer sees that their work quality affects every downstream step — and that understanding the system makes them a better writer, not just a faster one.

    The Account Manager

    Give Cowork: “We have eight active clients, each with a monthly content deliverable and a quarterly strategy review. Two clients just requested scope changes. One client’s site had a traffic drop that needs diagnosis. Build me the account management plan for this month.”

    Cowork shows the account manager how to triage and sequence: which clients need immediate attention (the traffic drop diagnosis), which scope changes affect production timelines and need to be surfaced to the production team, where monthly deliverables can be batched for efficiency, and how to structure the quarterly reviews so they generate upsell opportunities rather than just recapping metrics. The account manager sees that client management is resource orchestration — not just relationship maintenance.

    The Agency Founder

    This is the meta-level. Give Cowork: “We want to onboard three new clients next month while maintaining quality for our existing eight clients. Our team is two strategists, three writers, one SEO specialist, and one account manager. Build me the capacity plan.”

    Cowork exposes the capacity constraints and sequencing decisions that the founder usually does intuitively: which roles are at capacity, where onboarding tasks can be parallelized, which existing client work can be batch-processed to free up bandwidth, and what the risk profile looks like if one of those three new clients has a larger scope than estimated. The founder sees their own decision-making process externalized — and can use it to train their team lead or operations manager to make the same calls.

    The Meta-Training Layer

    Here is what makes this particularly powerful for agencies: the skill Cowork trains is the skill that agencies sell. A content agency does not sell writing. It sells the orchestration of research, creation, optimization, and distribution into a system that produces results. The better every team member understands that system, the better the agency performs — and the less dependent it is on one person holding the whole thing together.

    Cowork makes the system visible. And visible systems are learnable systems.

    Frequently Asked Questions

    How does Claude Cowork help content and SEO agencies specifically?

    Cowork decomposes agency workflows — campaign planning, content production, client management, capacity planning — into visible workstreams with dependencies. That orchestration visibility teaches every team member how the full system works, not just their individual lane.

    Can Cowork help with agency scaling challenges?

    Yes. The primary scaling bottleneck for agencies is that orchestration knowledge is trapped in one or two people. Cowork makes that orchestration visible and teachable, so more team members can learn to plan and sequence work — reducing the dependency on the founder or a senior director.

    Is Cowork a replacement for agency project management tools?

    No. Cowork trains the planning and decomposition skill. Use your existing tools — Asana, Monday, ClickUp, Notion — to execute and track the work. Cowork is the thinking layer that shows how plans should be structured before they go into your PM tool.

    Which agency role benefits most from Cowork training?

    Account managers and junior strategists benefit most. They are the roles most likely to be promoted into orchestration responsibilities without formal training in how to plan and sequence multi-track production work.


  • Replace Your SEO Agency Kit — SpyFu + Claude + DataForSEO

    Replace Your SEO Agency Kit — SpyFu + Claude + DataForSEO

    $130/month of tools doing $2,000/month of agency work. This kit documents and delivers the complete stack — configured, connected, and ready to run.

    What Small SEO Agencies Actually Do

    A $2,000/month SEO retainer typically covers: weekly competitive keyword monitoring, monthly rank tracking, keyword gap analysis against 3-5 competitors, content brief creation, and a monthly report. That’s the job. SpyFu handles the data layer. Claude handles the interpretation and content strategy. DataForSEO handles rank tracking. This kit wires them together into a system you run yourself in about 45 minutes per week.

    The Stack

    • SpyFu Pro ($79/mo) — competitor keyword intelligence, PPC ad history, 10+ years of historical data, API access
    • Claude Pro ($20/mo) — interprets the data, writes content briefs, identifies opportunities, generates competitive analysis narratives
    • DataForSEO (~$30/mo) — automated weekly rank tracking for your target keywords, stored in Notion

    Total: ~$130/month. Everything a boutique SEO agency provides, run by you.

    What’s Included

    • Complete stack setup guide — SpyFu + Claude + DataForSEO configured, authenticated, and connected to Notion
    • Weekly competitive audit workflow — 45-minute documented process from SpyFu data pull to prioritized action list
    • Keyword gap analysis workflow — identify and prioritize the keywords your top 3 competitors rank for that you don’t. Includes SpyFu Kombat tool tutorial and Claude prompt for interpreting the gap list
    • Content brief generator — SpyFu competitor data → Claude → a complete, publishable content brief in 10 minutes
    • Rank tracking setup — DataForSEO automated weekly rank pulls stored in Notion with trend visualization
    • Monthly competitive report template — client-ready or internal presentation format, auto-populated from Notion data
    • Python scripts for all automated data pulls — SpyFu domain overview, keyword rankings, DataForSEO rank checks

    Who This Is For

    Business owners who are paying $1,500-$3,000/month for SEO services and want to understand whether they’re getting value — and potentially do it themselves. In-house marketers who want a structured competitive intelligence system that doesn’t require an agency. Agencies who want to build this workflow into their own client delivery at scale.

    Replace Your SEO Agency Kit

    $97

    Delivered to your inbox within 24 hours

    Buy Now →

    Secure checkout via Square — all major cards

    Want this customized for your stack? Email will@tygartmedia.com

    FAQ

    Is this actually a replacement for a good SEO agency?

    For most small businesses: yes. A good boutique SEO agency at $2,000/month is doing exactly what this kit documents. For enterprise sites with complex technical SEO needs, active link building campaigns, and large content programs — no, you need dedicated resources. But for a local business, a growing ecommerce store, or a service business with 5-50 pages, this stack covers the core work.

    How much time does the weekly workflow take?

    About 45 minutes once set up. Data pulls are automated. The human time is reviewing the Notion dashboard, running the Claude keyword gap analysis, and deciding which actions to take.

    Do I need technical skills to set this up?

    Basic comfort with running Python scripts and following a setup guide. The initial setup takes 3-4 hours. After that it runs automatically and the weekly workflow is mostly reviewing dashboards and running Claude prompts.

    How is this delivered?

    To your inbox within 24 hours. ZIP file with all Python scripts, the Notion template duplicate link, Claude prompt library, and the complete setup guide.