A magazine put a paywall in front of its journalism to stop AI reading it. I tested what that paywall actually checks. It reads one line of your request, the name you type in yourself, and compares it against a list. Say who you are and you get a bill. Make something up and you walk straight in. Then I asked two assistants to read the article anyway. Both got charged, both answered, and neither had read a word of it. It keeps going after the sign-off, about where this podcast is headed.

Chapters

• 00:00 - A story, and a bill instead of a page
• 02:19 - What a 402 is, and who sells it
• 04:02 - What the wall checks, and the name I made up
• 06:46 - robots.txt says one thing, the server does another
• 08:08 - Googlebot walks in free while Penske sues Google
• 10:08 - Is anybody actually paying
• 12:13 - I asked Claude and ChatGPT to read it
• 15:22 - Being read or being cited
• 17:42 - Ask your chatbot where it got the facts
• 19:17 - After the episode: where this is headed

Key Numbers

• 402 Payment Required has been in the web standards since 1992 and almost nothing ever used it
• robots.txt has been a convention since 1994, and nothing makes a robot obey it
• 6,000 or 8,000 or 9,500 websites, depending which of TollBit's own pages you read
• 25 robots named in Variety's robots.txt, 24 of them blocked
• 3 crawlers get charged that the file never names at all
• 0 AI companies named on TollBit's page aimed at AI companies
• 1 paying customer ever named publicly, a news reader app

Key Takeaways

1. The paywall checks a name, not a robot. Every crawler that identified itself honestly got a bill. A name I invented, belonging to no company on earth, got the whole page one second later.
2. Your server sets your policy and your robots.txt only describes it. Variety's two disagree right now, and three crawlers the file permits are charged anyway.
3. Blocking the machine does not block the answer. It decides who gets credited when the machine repeats you. Two assistants credited a search engine and a podcast directory.

What to Do

• Request a page from your own website with a crawler name in the user agent, then with a name you invent, and compare
• Read your robots.txt beside what your server actually returns, line by line
• Check what Google-Extended covers before you rely on it, because it has never covered AI Overviews
• Ask your assistant whether it read the page or searched around it
• Every link and every check I ran is in the newsletter, nohacks.co/subscribe

Sources & Links

• No Hacks website
• Variety's robots.txt
• The article

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

On August 5 Shopify switched on a second way into every store on its platform, built for AI agents instead of people. Nothing to install, no merchant asked. I opened three unrelated stores, Allbirds, Brooklinen and Partake Foods, and asked each what it could do for a machine. All three answered with the same roughly 800 words, identical character for character, and no merchant wrote a syllable of it. What those words say, and what it costs a brand when the visitor has no eyes.

Chapters

• 00:40 Thirty years of every shop trying to sound different
• 02:13 What Shopify switched on, overnight, on every store
• 03:19 Three stores, one identical answer
• 05:06 The tools are stage direction for a machine
• 08:13 Nobody is using any of it yet
• 13:45 Your voice does not transmit, your data does

Key Numbers

• Three unrelated stores returned the same ~800 words of tool text, identical character for character
• The adapter file is version 0.1.0
• Etsy put AI agent platform traffic under 1% of its total in Q2 earnings
• Shopify reports AI-referred orders tripled, which is referred traffic, not agents buying
• Shopify reports over a million merchants on the platform

Three Takeaways

1. Shopify wrote what your store says to machines, and every other store says it too. These are instructions, not descriptions. The checkout tool tells the agent to "follow it." Another tells it not to ask the shopper about missing options when it decides they only want to look. Someone chose when the customer gets consulted, and it was not the customer or the merchant.
2. This is the right way to build it, which is separate from whether anyone noticed. The tools read the same database as the storefront people see, so the two cannot drift apart. One good default beats a million bad ones. It is still worth knowing a default was set for you.
3. If the machine is the visitor, your voice does not transmit and your data is what is left. The photography, the badges, the reviews, the copy someone agonised over: none of it survives the call. Back comes a title, a price, a size run, availability. What is left to compete on is whether your prices are right and your stock is accurate. That work pays off whether or not the agents arrive.

Mentioned

• My WebMCP reference guide: https://nohacks.co/blog/what-is-webmcp
• What I found on day one: https://nohacks.co/blog/shopify-gave-every-store-an-agent-api
• Shopify's docs for building the buyers: https://shopify.dev/docs/agents
• Talia Wolf and the Emotional Targeting Framework
• Episode 229, llms.txt against 137,000 domains

Newsletter, one a week: https://nohacks.co/subscribe
Say hello: [email protected]

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

Most of what's sold as AI search optimization has never been tested by the people selling it, and this episode is me checking the biggest one against server logs. Ahrefs looked at 137,000 domains in June: 97% of llms.txt files got zero requests in May, and the biggest readers of the rest were SEO audit tools. I also lay out the line I use to sort every pitch: a hack tries to influence what the machine says about you, architecture changes what a machine can read and do on your website.

Chapters

00:00 The AI optimization economy and its zero evidence
02:50 llms.txt checked against 137,000 domains
06:00 The main readers of llms.txt are SEO audit tools
08:53 Why this market keeps producing hacks
10:23 Visibility scores and the prompt problem
12:43 Every generation of hacks dies the same way
15:08 What survives model updates
18:39 The mirror: fix what the internet thinks you are

Key Numbers

• 137,000 domains in Ahrefs' June 2026 server-log study
• 28% had a valid llms.txt file, and that number is the ceiling, their customers skew technical
• 97% of those files got zero requests in May, not low traffic, zero
• Of the 3% that got fetched, around 22% of the readers were SEO audit tools, the tools that flag you for not having the file
• My own Cloudflare logs at nohacks.co show the same thing, nobody fetches it

Three Takeaways

1. The pitch is a screenshot, the truth is in the logs. Before you pay for any AI visibility work, ask for evidence at the level of server logs, and watch what happens.
2. A hack tries to influence what the machine says about you. Architecture changes what a machine can read and do on your website. The first is rented and dies at the next model update, the second is owned.
3. LLMs are a mirror of everything happening online. If ChatGPT doesn't call you the best X for Y, the honest question is whether the internet agrees you are, and that's the problem worth fixing.

What to Do

• Sort anything you bought or got pitched this quarter with one question: does it change what a machine can read and do on the website, or what the machine says about it?
• Ask any vendor for their evidence before money leaves your account. Logs, tests, a mechanism, the same bar you'd use for anyone touching revenue.
• Check your own server logs for who actually fetches your llms.txt, it takes five minutes
• Try this: open free ChatGPT logged out of search, type "what is [your name] known for," and send me the screenshot at [email protected]. I want to see what you get.

Sources

• Ahrefs llms.txt server-log study (June 2026): https://ahrefs.com/blog/llmstxt-study/
• My identity-vs-capability piece: https://nohacks.co/blog/agentic-web-identity-vs-capability
• Weekly newsletter: https://nohacks.co/subscribe

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

I came back from a month off the grid to find OpenAI had killed Atlas, its most glamorously launched product, nine months after the keynote. It barely matters, though. The automated, non-human visitor Atlas was sending to your website is still coming, through whatever shell comes next. Build for the visitor, not the browser.

Timestamps

• 00:00 - Back from break, and the bad news
• 01:17 - Atlas: the most hyped browser ever launched
• 02:27 - Watching it work is a demo, not a workflow
• 03:29 - Killed with no keynote: the browser was never the product
• 04:35 - The visitor isn't dead, so build for it
• 05:24 - The real agentic web: background agents you don't watch
• 07:52 - Silent failure: a human recovers, an agent doesn't
• 09:41 - OpenAI's side quests, and the name that gave it away
• 12:48 - My Cloudflare data: AI traffic is 5-10x human
• 14:24 - What No Hacks is now

Key Numbers

• AI assistant traffic (ChatGPT and Claude users) is running 5-10x my human traffic on nohacks.co (my own Cloudflare AI analytics)
• Atlas: launched October 2025, shuts down August 9, 2026, nine months old
• Eight months in, Atlas never shipped beyond macOS, no Windows, iOS, or Android

Key Takeaways

1. The visitor outlives the shell. Browser, app, extension, cloud: the wrapper keeps changing, but the automated visitor arriving at your website is the same one every time. Build for the visitor, not the browser.
2. Watch-it-work AI browsers were always a demo. If you have to sit and watch it, it is not a workflow. The real agentic web runs in the background, which means its failures are silent, and you never see the lost signup or sale.
3. Being cited is not the whole game. The agent does not only mention you, it comes to your website and tries to act. Optimizing to appear in a prompt misses the harder work: a website a machine can actually use.

What to Do

• Simplify the paths a human muscles through but an agent will not: coupon-box bugs, cookie banners, console errors. The agent hits the wall and leaves, silently.
• Check your own logs and bot analytics for AI-assistant traffic. You are probably getting more than you think.
• Stop optimizing only to be discovered. Make the website something an agent can finish a task on.
• More on this every week in the No Hacks newsletter: nohacks.co/subscribe

Sources & Links

The story

• OpenAI is shutting down Atlas (TechCrunch)

My companion take and data

• AI Browsers Are Backward Because Agents Never Needed the Visual Layer
• Cloudflare Radar: bot and AI traffic

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

I sat down with Malte Landwehr, who left VP of SEO at Idealo to become CPO and CMO at Peec AI, the platform that tracks what ChatGPT, Claude, Gemini, and Google AI Overviews actually cite. We open on the strangest finding of the year. GummySearch, a Reddit analytics tool that shut down last November, now sits behind about 0.1% of all ChatGPT citations. From there we get into why clicks are the wrong way to measure AI search, why your local brand keeps losing to US ones, why scaled AI content rockets then crashes, and why Malte says SEO is dead as a default growth channel.

Guest Profile

Malte Landwehr is CPO and CMO at Peec AI, an AI search visibility platform that runs daily prompts across ChatGPT, Perplexity, Gemini, Google AI Overviews, Claude, and Grok. He spent more than twenty years in search and product, including five years as VP of SEO at Idealo and five years as VP of Product at Searchmetrics. In his first six months at Peec AI, the company grew from roughly $500K to $5M in ARR.

Chapters

• [0:00] Intro
• [1:15] Leaving one of Europe's best SEO jobs for AI search
• [5:07] Why clicks are the wrong way to measure ChatGPT
• [8:22] Which answer engines actually matter
• [12:34] GummySearch: a dead product winning ChatGPT citations
• [18:33] Listicles and the English-language fan-out bias
• [23:48] Advertorials, local results, and Mount AI content
• [33:50] Digital PR over technical SEO
• [36:27] ChatGPT Shopping is scraped Google Shopping, and the MCP contest
• [42:16] SEO is dead as a default channel, and the chunking move

Key Takeaways

1. Stop measuring AI search by clicks. In an LLM, clicking is optional, so ChatGPT can look like 1% of your traffic while shaping most of your buying journeys. Measure the influence on the decision, not the visit.
2. What gets written about you offsite now matters more than your own technical SEO. Grounding pulls from Reddit, G2, Wikipedia, YouTube, and news, so digital PR is the bigger lever for how AI describes and recommends you.
3. One citable paragraph beats a chunked article. Put your main claim near the top in two or three declarative, self-contained sentences that name the entities. Do not shred a whole article into one-line bullets.

Notable Quotes

"In a web search, clicking is part of the intended user journey. In an LLM, clicking is completely optional." Malte Landwehr

"They didn't gain visibility as a brand. They now have power over what brands are recommended by LLMs." Malte Landwehr, on GummySearch

Resources

• Peec AI: https://peec.ai
• Peec AI research blog: https://peec.ai/blog
• Malte Landwehr's website: https://www.maltelandwehr.de
• Future of AI Shopping webinar with Malte Landwehr (Peec AI): https://peec.ai/webinars/future-of-ai-shopping

Connect

• Malte Landwehr on LinkedIn: https://www.linkedin.com/in/landwehr/
• Peec AI: https://peec.ai

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

This week I welcome Alisa Scharf, Chief AI Officer at Seer Interactive, to the podcast, to ask the question she fires back at every client who walks in wanting to "win at AI visibility." Her answer flips the whole project: fix what the models get wrong about you before you chase the category terms. We got into her research on why lower-authority websites earn more citations, why LLMs recommend a brand only 2.3% of the time, and the gap nobody is tooling for: getting an agent to actually use your website, not find it.

About the Guest

Alisa Scharf is Chief AI Officer at Seer Interactive, where she runs the AI practice across the agency's client accounts. Her team's research spans hundreds of thousands of pages and tens of thousands of prompts, and she argues that citations are a leading indicator, not a business outcome.

Chapters

• 00:00 - The first question Alisa asks a new client
• 04:08 - Brand accuracy: what models get wrong about you
• 06:57 - Defense wins championships
• 09:54 - The brand accuracy audit
• 13:12 - Why lower-authority websites get cited more
• 15:57 - Citations are page two of Google
• 19:37 - LLMs recommend a brand 2.3% of the time
• 21:49 - The agentic browsing tooling gap
• 28:13 - Losing 30-80% of organic traffic
• 37:31 - How a 15-year-old brand catches up
• 40:24 - What we will get wrong in 12 months
• 43:18 - Where to find Alisa

Key Takeaways

1. Defense before offense. Pick five factual prompts about your own company, founding, location, what you sell, who you compete with, and run them across ChatGPT, Claude, and Gemini. Fix what the models get wrong before you spend a dollar chasing category terms.
2. Citations are a leading indicator, not a result. They swing by month and by model. Real success shows up in direct traffic, branded search, and brand recognition, none of which sit neatly on a dashboard.
3. Visibility is not readiness. Getting cited and getting an agent to actually buy, book, or provision on a customer's behalf are two different problems. Most providers sell the first and call it the second.

Notable Quotes

Resources

• Seer Interactive: https://www.seerinteractive.com
• Seer insights and research: https://www.seerinteractive.com/insights
• No Hacks EP 222, Wil Reynolds, AI visibility is a vanity metric: https://nohacks.co/episode/222-ai-visibility-is-a-vanity-metric-with-wil-reynolds
• No Hacks EP 225, Matt Biilmann on agent experience: https://nohacks.co/episode/225-every-website-already-has-an-agent-experience-and-most-are-bad-with-netlify-ceo-matt-biilmann
• SparkToro: https://sparktoro.com

Connect with Alisa Scharf

• LinkedIn: https://www.linkedin.com/in/alisascharf/
• X: https://x.com/alisa_scharf
• Bio: https://www.seerinteractive.com/people/team/alisa-scharf

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

The user-agent string in the HTTP header has been there since the 1990s. The web was built with software navigating it on someone's behalf. For thirty years that someone was a human. That changes now. Matt Biilmann, CEO and co-founder of Netlify, was one of the first to take seriously what it means when the "user" navigating the web is an AI agent. 

He published the foundational essay on Agent Experience in January 2025, pivoted his entire company around it, and recently shipped netlify.ai as a separate entry point built for agents. We cover the four pillars of Agent Experience, why every product already has an agent experience whether you designed one or not, content negotiation as a way to tell agents to go to a different URL than humans, why SaaS is in real trouble (with a story from inside Netlify about ripping out vendor contracts), how the data-structure assumption that has defined software for fifty years is breaking, and the one thing every website owner should start doing this week.

About the Guest

Matt Biilmann is the CEO and co-founder of Netlify, the platform that started the Jamstack movement and is leading the shift from developer experience to agent experience. His January 2025 essay on Agent Experience is the foundational text for the discipline. 

Chapters

• 00:00 Every product has an agent experience (cold open)
• 00:35 The architectural question
• 01:46 Welcome Matt to No Hacks
• 02:15 When AX became a design constraint, not a concept
• 06:44 The January 28 2025 essay and who got it first
• 10:22 Why netlify.ai was built as a separate website
• 12:44 Content negotiation: telling agents to go to a different URL
• 13:54 Qualitative data and the Axis eval framework
• 17:12 Does AX apply to e-commerce and content websites?
• 20:59 The cumulative media argument (TV did not kill radio)
• 25:00 User-agent in HTTP and Al Gore-era agent commerce laws
• 26:33 SaaS business model is dead: build-vs-buy is shifting
• 30:44 The end of structured content as a hard constraint
• 40:25 One thing every website owner should do now
• 43:08 Where to find Matt online

Key Takeaways

1. Every website already has an agent experience. Agent Experience is how AI agents currently interact with your product, whether through computer use, fetching, or working around the barriers you put up. It is not a feature you add. The only question is whether the experience is good or bad.
2. The four pillars: Access, Context, Tools, Orchestration. Matt's framework for thinking about AX systematically. Access answers whether agents can reach your product at all. Context is the prompt-engineering equivalent for agents. Tools are the concrete capabilities you expose. Orchestration covers how agents string those tools together inside your product.
3. Build a separate entry point for agents. netlify.ai is purpose-built for agents while netlify.com remains the human entry point. Content negotiation tells agents to go to one URL, humans see the other. The blessed-path approach beats trying to make one URL serve both.
4. SaaS economics are shifting structurally. The build-vs-buy floor is dropping fast as AI lowers the cost of software. Traditional 90%-margin seat-based SaaS is in real trouble. Dev tool companies have upside because companies need more tools. Everyone else is going to be ripping out vendor contracts and building internally.
5. The data-structure paradigm is breaking. Software engineering has operated on the Linus Torvalds principle that data structures matter more than code. LLMs are not built around data structures. Building software around LLMs means rethinking the assumption that drove fifty years of computer science.

Notable Quotes

What To Do Next

• Open your website in Claude Code or ChatGPT and ask the agent to complete a real task. Watch where it stalls. That is your AX baseline.
• Check your traffic logs for AI assistant visitors (ChatGPT-User, Claude-Web, PerplexityBot, GPTBot). The number is rising whether you measure it or not. Cloudflare reports AI assistants are now 5.5% of all internet traffic, up from 3.9% six months ago.
• Read Matt's January 28 2025 essay on Agent Experience at biilmann.blog as the starting point. Then read the one-year retrospective for the four pillars framework.
• If you operate a developer tool or any product with a clear automation surface, start a simple eval scenario: take a fresh agent, give it a task, score whether it succeeds. Axis from Netlify will give a proper framework when it ships open source.

Resources Mentioned

• netlify.ai (the agent-built entry point Matt and team shipped recently)
• netlify.com (the human entry point)
• Matt's original Agent Experience essay, January 28 2025: biilmann.blog
• Matt's "AI in the CLI: The Humanoid Robot of the Web" (August 2025)
• 
  
• Claude Code (the agent that flipped broad accessibility for CLI coding agents)

Connect with Matt Biilmann

• Blog: biilmann.blog
• LinkedIn: linkedin.com/in/mathias-biilmann-christensen-a5a3805
• Twitter/X: @biilmann (x.com/biilmann)
• Bluesky: bsky.app/profile/did:plc:grjr4il5dredrsuj7nosb4pq
• Mastodon: mastodon.social/@biilmann
• Netlify: netlify.com and netlify.ai

Connect with No Hacks

• Website: nohacks.co
• Subscribe to the newsletter: nohacks.co/subscribe
• Machine-First Architecture: machinefirstarchitecture.com

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

We are significantly closer to movie Her than we were just 6 months ago.

Most coverage reads Google's last six months as a string of independent product updates. They aren't. Read together, they're the whole agentic-web stack closing one component at a time. Tuesday's Gemini Intelligence on Android announcement named the keystone - the first OS-level web-agent integration any company has built. Chrome auto-browse lands on Pixel 10 and Galaxy S26 in late June.

This episode walks through the six-month assembly (Chrome auto-browse, AppFunctions, AI Mode in Chrome, "Ask Google", web.dev agent-friendly guidance, Gemma 4 + Gemini Nano 4, UCP, A2A, Gemini Intelligence Android, DeepMind AI Pointer), the durability question I can't fully answer yet (five-year moat or six-month head start before Apple closes it), and the audit any website needs to pass once an agent can operate it on a user's phone.

Timestamps:

• 00:00 - 10 Google moves in six months
• 04:53 - Walking the six-month assembly, January through this week
• 06:51 - The full stack: action, agent-to-app, transaction, identity, distribution, input
• 09:01 - Late June: what changes for a salon owner with a booking website
• 10:32 - The durability question: Apple's six-month gap, not a five-year moat
• 15:47 - Machine-First Architecture: three visitor classes you have to design for
• 16:19 - Google's seven rules. nohacks.co passed six. Tailwind 4 broke one.
• 17:32 - The test you can run today: disable JavaScript, try to complete a booking
• 20:53 - A few days to fix it. The cost of waiting is unknown.

Weekly breakdown of how the agent-web is assembling, every Wednesday: https://nohacks.co/subscribe

The Machine-First Architecture framework: https://machinefirstarchitecture.com

Sources mentioned in this episode:

• DeepMind AI Pointer (May 13): https://deepmind.google/blog/ai-pointer/
• Gemini Intelligence Android (May 12): https://blog.google/products-and-platforms/platforms/android/gemini-intelligence/
• Chrome auto-browse preview (January): https://blog.google/products-and-platforms/products/chrome/gemini-3-auto-browse/
• AppFunctions for Android (February): https://developer.android.com/ai/appfunctions
• Google web.dev - "Build agent-friendly websites" (April): https://web.dev/articles/agent-friendly-websites
• Universal Commerce Protocol: https://ucp.dev/

Related reading on No Hacks:

• Selling to AI: The Complete Guide to Agentic Commerce - https://nohacks.co/blog/agentic-commerce
• Google's Agent-Friendly Checklist Has 7 Rules. Tailwind v4 Breaks One. - https://nohacks.co/blog/google-agent-friendly-checklist
• Amazon v. Perplexity: The CFAA Case That Decides Whether AI Agents Can Visit Your Website - https://nohacks.co/blog/amazon-perplexity-cfaa-agent-visitor-rights

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

I ran the Cloudflare Agent Readiness scanner on nohacks.co, got 33 out of 100, and felt insulted. One toggle later the score was 67. That gap is where this episode starts. My case: the web is splitting into two economies. A retailer-friendly agentic web where AI-referred traffic now converts 42 percent better than human traffic. And a page-view-driven publisher web losing 20 to 90 percent of its Google traffic in a year. This split is structural, not a rebalancing.

Chapters:

• 00:00 Opening
• 00:41 The 33, then 67 score on nohacks.co
• 02:46 The thesis: the web is becoming two webs
• 03:55 Cloudflare Agents Week: 28 shipments in five days
• 05:35 The data stack: Adobe 393%, the conversion inversion, publisher declines
• 10:08 The mobile-first parallel
• 11:21 Why this split is permanent
• 13:12 The "publishers will adapt" and licensing-deal rebuttals
• 17:02 Three sector-specific moves
• 19:34 Closing: run the scanner, reply with your score

Key Numbers

• Cloudflare shipped 28 agent-infrastructure pieces during Agents Week (April 13 to 17, 2026)
• AI traffic to US retailers grew 393 percent year over year in Q1 2026 (Adobe)
• AI-referred traffic converted 42 percent better than non-AI in March 2026, after converting 38 percent worse in March 2025
• Google traffic to publishers down 33 percent globally; some local publishers down 25 to 90 percent
• Automated traffic growing 8× faster than human traffic year over year

Three Takeaways

1. The split is structural, not a rebalancing. Retailers fit the agentic web because agents complete the same action the website wants. Page-view publishing does not, because the agent summarizes instead of sending a human to see an ad.
2. The composite score is a trigger, not a target. Ignore the number. Read the per-check list and fix the signals that ship against real agent runtimes today.
3. Watch the infrastructure before the mainstream catches up. The mobile-first rebuild shipped years before the indexing caught up. This is the same gap, different shape.

What to Do

• Run isitagentready.com on your website. Toggle the category, re-run, compare.
• Transaction-driven revenue: agent readiness is tied to revenue. Fix the checks that ship against real agent runtimes now.
• Page-view-driven revenue: model your P&L with 30 percent less traffic this quarter. If it breaks the business, start diversifying today.
• Reply to the newsletter with your score. I read every reply.

Sources

• Cloudflare Agent Readiness Score
• Adobe Q1 2026 AI Traffic Report via TechCrunch
• Publisher traffic drop (Press Gazette)
• What is the Agentic Web (nohacks.co)

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit

Wil Reynolds, founder of Seer Interactive, shares how losing 80% of organic traffic actually revealed that his team had been tracking the wrong metrics for years. We get into why AI visibility is a vanity metric, how 44% of LLM users include brand names in their prompts, the real security risks of wrong phone numbers in AI answers, and why trust (not visibility) is the only moat that matters.

Chapters

• 00:00 - 80% traffic drop, pipeline went up
• 06:43 - The pressure of experimental channels with real budgets
• 08:28 - AI visibility is a vanity metric
• 13:49 - People are tracking the wrong prompts
• 17:15 - AI is getting your phone number wrong (and scammers know it)
• 22:30 - Trust vs visibility: the real optimization target
• 30:26 - Trust is a moat, hacks mortgage your brand
• 32:20 - Be seen, be believed, be chosen
• 44:15 - What digital marketers should do right now
• 49:33 - Where to find Wil

Key Takeaways

1. Traffic is no longer the leading indicator - Seer lost 80% of their organic traffic over two years. Pipeline went up. Social converts at 5x organic. The correlation between search traffic and revenue has broken for many businesses
2. AI visibility is a vanity metric - When ChatGPT doubles the length of an answer, your "visibility" goes up without any more humans seeing you. If visibility grows but leads don't, you're the sucker. Track visibility against your pipeline, not in isolation
3. 44% of LLM users put brand names in their prompts - Wil's team watched real humans use LLMs and found nearly half include specific brands. Head-to-head brand comparisons are the prompts worth tracking, not generic category queries
4. Trust is the only real moat - Michelin built a restaurant guide in 1900 that still drives foot traffic and pricing power. RAMP launched 52 AI-generated restaurant pages in a day. One is rotisserie chicken made by a chef. The other is a chicken nugget. Both are chicken, but only one builds trust
5. Be seen, be believed, be chosen - Visibility gets you in the room. But if people Google your team and nobody shares their content, if you're not speaking at conferences, if your newsletter has no engaged readers, belief falls apart. Trust transfers from people, not listicles

Concepts Discussed

• Three Types of AI Search | Search-led (web index + AI), answer-led (hybrid with tool use), and fully generative (training data only). Each requires different optimization.
• Training Data Lag | Gemini 3.1 launched with training data from January 2025, a 16-month gap. Work done since then has zero provable impact on training-data-based answers.
• Brand-in-Prompt Behavior | 44% of observed LLM users include brand names in their prompts. Changes the optimization target from "show up for generic queries" to "win head-to-head comparisons".
• Phone Number Hallucination | LLMs serve wrong phone numbers for businesses, creating fraud exposure. Especially dangerous for financial services targeting elderly customers.
• Recommended Stack Visibility | AI coding tools recommend tech stacks from training data. Being the default recommendation in Claude Code or Codex creates durable, hard-to-displace visibility.

Connect with Wil Reynolds

• LinkedIn: linkedin.com/in/wilreynolds
• LinkedIn Newsletter: Thinking Out Loud
• Seer Interactive: seerinteractive.com

No Hacks runs no sponsorships and is funded by advisory and audit work. 

If your website needs to work for machines as well as people, start with a fixed-scope Machine-First Architecture audit: https://nohacks.co/audit