No Hacks with Slobodan Manic

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

In 2009, Luke Wroblewski's "mobile first" changed how every website gets built. Start with the harder constraint, and the rest gets better. Now the harder constraint is not a small screen. It's no screen at all. Sani introduces Machine First Architecture, a four-pillar framework covering everything from how you define your business to how machines interact with your website. Identity, structure, content, interaction. In that order.

Chapters

• 00:00 - Introduction: The Mobile First Parallel
• 01:24 - Why Machine First Follows the Same Pattern
• 05:09 - Pillar 1: Identity
• 08:05 - Pillar 2: Structure
• 12:34 - Pillar 3: Content
• 15:20 - Pillar 4: Interaction
• 19:29 - Why This Matters Now
• 22:30 - One Action Per Pillar
• 24:30 - Closing

Key Stats

• Brands on 4+ platforms are 2.8x more likely to appear in ChatGPT responses, but only with consistent identity (Digital Bloom)
• 70%+ of Google's first page results use schema markup
• Pages with 19+ verifiable data points averaged 5.4 AI citations vs 2.8 for pages with minimal data (SE Ranking, ~130K domains)
• 96% of AI Overview content comes from sources with verified E-E-A-T signals
• AI browser traffic to US retail sites increased 4,700% YoY in July 2025 (Adobe Analytics)

Key Takeaways

1. Machine first is the new mobile first. What works for a parser works for humans. The reverse is never true.
2. Identity comes before optimization. You need a canonical, structured definition of your business before you touch anything else.
3. Your website is a data model, not a wireframe. The page is a rendering of structured data. Machine-critical info goes at the top.
4. Content must be answer-first and verifiable. Machines evaluate the first few hundred words. Vague marketing copy is invisible.
5. Machines are not just reading your site, they're using it. Agents shop, book, and fill out forms. Visual-only confirmations and modal pop-ups break them silently.
6. Every agent failure is invisible. The agent moves to a competitor. You never see the lost transaction.

What to Do (One Action Per Pillar)

• Identity: Write your canonical definition as fields. Google your business name. Fix every platform that tells a different story.
• Structure: Disable JavaScript and visit your site. If content disappears, you're invisible to most AI crawlers.
• Content: Read the first paragraph of your key pages. If it doesn't state what the page is about, rewrite it.
• Interaction: Complete a core action on your site using only a screen reader. If you can't finish the flow, an agent can't either.

Links

• Machine First Architecture: machinefirstarchitecture.com
• Subscribe: 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

Google was granted patent US 12536233B1 in January 2026, describing a system that scores your landing page and, if it falls below a quality threshold, replaces it with an AI-generated version personalized to each searcher. This episode breaks down how the patent works, how the industry reacted, and what website owners should do to prepare.

Chapters

• 00:00 - Introduction
• 01:24 - How the Patent Works, Step by Step
• 04:26 - How the Industry Reacted
• 06:46 - What This Actually Means
• 07:57 - Ads First, Everything Else Later
• 08:58 - Google's Data Advantage
• 10:13 - Your Website Is Becoming a Warehouse
• 11:10 - The Measurement Problem
• 12:28 - Connection to Agentic Browsers and Web MCP
• 13:38 - What You Can Do About It
• 15:19 - Closing

Key Statistics

• Patent US 12,536,233 B1 approved January 2026, priority date July 2024 (USPTO)
• Patent filed by six Google engineers: Karen Zhang, IL Grover, Timothy Benjamin Wallen, Lauren Marjorie Bedford, Avi Sadan, and Ethan Milo
• Landing page score based on conversion rate, bounce rate, click-through rate, and design/content quality assessments
• AI pages can include product feeds, CTA buttons, chatbot functionality, personalized headlines, filters, and suggested products

Key Takeaways

1. The patent is real, and the scope is clear - Google has patented a system to score landing pages and replace underperforming ones with AI-generated versions personalized to each user's search history and context.
2. It starts with ads, but that's the playbook - The patent explicitly references sponsored content items. Google has a history of introducing features in ads first, then expanding (see: Google Shopping's evolution from free to paid).
3. Google has a data advantage no one can match - The system uses full search history, previous queries, click behavior, location, and device data. No advertiser has access to that level of personalization.
4. Your website is shifting from storefront to warehouse - Brands become suppliers of data while Google owns the customer experience. Your product feed and structured data become the front door to your business.
5. The technology is category-agnostic - The patent focuses on shopping today, but scoring a page and replacing it with an AI version is a technique that applies to any content type. The question is when it expands, not whether.

Action Items Checklist

• Treat your product feed like your homepage: accurate, complete, detailed specs, pricing, stock levels, high-quality images
• Invest in structured data and machine-readable content so AI-generated pages based on your data are correct
• Build direct audience relationships: email lists, community, direct traffic, brand reputation
• Monitor your landing page quality scores in Google Ads
• Read the patent yourself to understand exactly what Google is describing
• Listen to the Browser Wars episode for context on agentic browsers and Web MCP
• Listen to the Duane Forrester episode on trust as the most important signal for AI

Sources & Links

The Patent

• US Patent 12,536,233 B1 - AI Generated Content Page Tailored to a Specific User

Episode URL: https://www.nohackspod.com/episode/220-google-patented-replacing-your-landing-page-with-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

Rand Fishkin, co-founder of SparkToro and one of the most influential voices in digital marketing history, shares research proving that AI brand recommendations are wildly inconsistent. You'd need to ask ChatGPT 1,500 times to get the same brand list in the same order twice. We discuss why AI ranking tools are selling metrics that don't exist, why Google is still 210x bigger than ChatGPT, and why brand building (not digital marketing tricks) is the real lever for AI visibility.

About the Guest

Rand Fishkin - Co-founder & CEO of SparkToro, co-founder of Moz and Alertmouse, author of "Lost and Founder"

Chapters

• 00:00 - Intro
• 01:04 - The best thing AI has brought online
• 02:51 - The AI inconsistency research: 1,500 prompts for the same list
• 06:17 - Why AI tracking tools give you a false sense of visibility
• 09:16 - Is AI search actually better than Google?
• 11:34 - Kung Pao Chicken vs Peanut Butter: prompt variability
• 16:26 - What AI tracking should actually measure
• 20:16 - Why the best brands weren't built on digital marketing
• 22:43 - AI as "Spicy Autocomplete": where the hype exceeds reality
• 25:17 - Why AI cannot be creative
• 28:58 - Google is still 200x bigger than ChatGPT
• 31:28 - Two ways to show up in AI: base models and RAG
• 34:34 - Brand mentions as the real lever for AI visibility
• 38:10 - Zero-click marketing and the death of traffic as a metric
• 41:47 - Why SEO careers are more important than ever
• 44:39 - What brands should actually do first in March 2026
• 48:10 - The one thing about AI that should be killed today
• 52:02 - Where to find Rand

Key Takeaways

1. AI rankings don't exist
2. Visibility percentage is the real metric
3. Brand mentions drive AI visibility 
4. The best brands weren't built on digital marketing
5. Your homepage is not your homepage anymore
6. SEO is more important than ever, but the metric changed

RESOURCES:

• Rand's AI Inconsistency Research: https://sparktoro.com/blog/new-resear...
• SparkToro (audience research): https://sparktoro.com
• Alertmouse (brand mention monitoring, free): https://alertmouse.com
• Connect with Rand on LinkedIn: https://linkedin.com/in/randfishkin

Episode URL: https://www.nohackspod.com/episode/219-your-homepage-is-not-your-homepage-anymore-with-rand-fishkin

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

Five years. 218 episodes. 110 hours of content. To celebrate, five returning guests flip the script and interview Sani about the agentic web, the future of web optimization, and what makes this podcast tick. Kelly Wortham, Iqbal Ali, Talia Wolf, Jon MacDonald, and Shiva Manjunath each bring their own questions, their own perspectives, and a few personal ones too.

Chapters

• 00:00 - Five years of No Hacks
• 01:33 - Kelly Wortham: Why the shift to the agentic web?
• 05:17 - Kelly Wortham: The secret to being a great podcast host
• 08:57 - Iqbal Ali: Why Web MCP is a big deal
• 12:23 - Iqbal Ali: What excites you about 2026?
• 13:58 - Talia Wolf: What everyone misses about optimizing for AI agents
• 15:33 - Talia Wolf: The misleading advice in the industry
• 18:19 - Jon MacDonald: Why brands need agentic web data now
• 25:38 - Jon MacDonald: NBA All-Star Weekend hot takes
• 29:22 - Shiva Manjunath: The skeptic's case against agentic web hype
• 37:56 - Shiva Manjunath: If you were a meme
• 38:37 - What's next for No Hacks

Key Takeaways

1. AI middleware is coming to every interaction - Chrome has 3 billion browsers, Apple is putting AI into Siri across every device. There will be an AI layer between every user and every website. This is not five years away. It is happening now.
2. Web MCP could make the agentic web actually work - Current AI agents take 3-5 minutes to fill a basic form on well-coded pages. Web MCP provides a standard interface between your front end and AI agents, making interactions reliable regardless of your HTML quality.
3. Optimizing for AI agents is not a separate discipline - A fully functional website built for humans gets you 80-90% there. Accessibility, semantic HTML, schema markup, fast load times. All the basics you felt bad about skipping? They matter now more than ever.
4. Citation tracking in LLMs is misleading - Prompting an LLM 100 times and averaging your position to 4.7 is not useful data. The rankings model does not translate to AI. Bing Webmaster Tools just launched AI tracking in beta, and Google will have to follow. That is when real measurement begins.
5. Getting ready for AI agents means making your website better for humans- There is not a single reason not to do it. Better technical health, better standards compliance, better user experience. The work is the same.
6. This is not about websites going away - Stores did not go away when e-commerce arrived. Websites will not go away when AI agents arrive. But there is a new channel, and if your site is not ready for it, you can disappear from discovery entirely.

Guest Hosts

Kelly Wortham

Founder of the Test and Learn Community (TLC). Asked about the shift to the agentic web and what makes a great podcast interviewer.

Iqbal Ali

Experimentation and AI consultant, founder of Ressada. Asked about Web MCP and what excites Sani about 2026.

Talia Wolf

CRO expert, founder of GetUplift, author of "Emotional Targeting." Asked about what people miss when optimizing for AI agents and what common industry advice is wrong.

Jon MacDonald

Founder of The Good, author of three books on website optimization. Asked about why agentic web data matters for brands and shared NBA All-Star Weekend hot takes.

Shiva Manjunath

Host of the From A to B podcast. Brought the skeptic's perspective on agentic web hype and asked what meme Sani would be.

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

In the 1990s, Microsoft and Netscape fought for control of the browser, the gateway between humans and the internet. Netscape went from 90% market share to zero in five years. Now, with over 30 agentic browsers launching in under 18 months, the same war is playing out again, only this time the stakes are higher. This episode breaks down the 90s browser wars, compares the tactics to what's happening today, and explains what website owners should do about it.

Key takeaways

1. The playbook hasn't changed - Bundling, free products, proprietary lock-in, and distribution deals decided the 90s browser wars. The same tactics are playing out with agentic browsers today.
2. Google is running Microsoft's 1995 playbook - Microsoft embedded IE into Windows to protect its OS monopoly. Google is embedding Gemini into Chrome to protect its search monopoly. The browser is the defensive weapon, not the product.
3. The Chromium trap is deeper than IE bundling ever was - Most agentic browsers (Comet, Atlas, Neon) run on Google's Chromium engine. Even competitors are built on Google's foundation.
4. The prize shifted from attention to transactions - The 90s fight was about what people see. The agentic browser fight is about what AI agents buy, book, and do on your behalf.
5. Your website is the new Netscape - If AI agents mediate every user interaction, your site risks becoming invisible infrastructure rather than a destination.
6. Regulation will be too late - The DOJ took 6 years to settle with Microsoft. Netscape was already dead. The same timeline is playing out with Google's antitrust case.

What to do today

• Don't optimize for one agentic browser. Build for web standards: semantic HTML, ARIA labels, structured data, server-side rendering.
• Build direct audience relationships (email, communities, subscriptions) so you're not dependent on browser intermediaries.
• Make your site worth visiting, not just worth scraping. Offer value an AI agent can't replicate.
• Treat accessibility as an agent strategy. Screen reader compatibility = AI agent compatibility.
• Test your site with an agentic browser to see what works and what breaks.

Read the full agentic browser landscape breakdown: nohackspod.com/blog/agentic-browser-landscape-2026

Chapters

• 00:00 - Introduction
• 01:34 - The First Browser War
• 09:15 - The Agentic Browser Explosion
• 12:48 - Why Is This Happening Now?
• 16:15 - Where the 2026 Version Gets Worse
• 21:27 - What This Means for Your Website
• 23:14 - What to Do About It
• 26:49 - Closing

Connect

Website: https://nohackspod.com

LinkedIn: https://www.linkedin.com/in/slobodanmanic/

Newsletter: https://nohackspod.com/subscribe

Episode URL: https://www.nohackspod.com/episode/217-the-browser-wars-are-back-this-time-with-ai-agents

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

Duane Forrester, 30-year search veteran who co-launched Schema.org and built Bing Webmaster Tools, explains why AI systems prioritize trust above all else. We discuss machine comfort bias, chunk-level content optimization, why SEO is now a multidisciplinary role, and how to prepare for a world where LLMs decide who gets cited.

About the Guest

Duane Forrester is the author of "The Machine Layer" and search industry pioneer

• 30 years in search and digital strategy
• Senior Product Manager at Microsoft - built Bing Webmaster Tools
• Co-launched Schema.org structured data standard
• Leadership roles at Bruce Clay Inc. and Yext
• Founder of Unbound Answers, creator of CitationIQ

Chapters

• 00:00 - Intro
• 01:01 - The biggest shift SEO has ever seen
• 03:30 - Machine Comfort Bias: the 5 layers of trust
• 09:19 - Chunking: writing for AI and humans
• 16:01 - Making content citation-ready
• 18:35 - Schema.org: the trust infrastructure
• 25:46 - Ironman vs Superman: AI as amplifier, not savior
• 32:28 - EEAT, Universal Verifiers, and why trust is everything
• 42:59 - Latent Choice Signals: the invisible metrics
• 52:35 - The Machine Layer book
• 57:53 - Emerging roles in AI discoverability
• 01:01:16 - Where to find Duane

Key Takeaways

1. Trust is the new algorithm - LLMs need multiple dimensions of verification before citing you. If you can provide everything they need without them having to guess, they'll lean into that "machine comfort bias"
2. Chunking matters, but not how you think - Don't reformat your entire page into 300-word blocks. Instead, put key facts, figures, and bullet points at the top. LLMs get "lost in the middle" of long-form content
3. Be the canonical source - Your goal isn't rankings, it's being seen as THE source of knowledge on your topic. If you haven't expanded the LLM's training data with net new information, you won't be cited
4. SEO is now multidisciplinary - Technical SEOs must understand branding, conversion, engagement, PR, and UX. Silos are killing companies in the AI discovery layer
5. AI is Ironman, not Superman - These systems amplify your skills but require you to drive them. Hope is not a strategy. Always ask self-referencing questions to verify outputs
6. LLMs want to save money - They won't waste tokens looking elsewhere if you provide everything they need. Consistency and trust reduce their computational costs

Resources Mentioned

Duane's Work

• Book: The Machine Layer - Available on Amazon (Kindle & Paperback)
• Website: duaneforrester.com - Free frameworks from the book available
• Substack: duaneforresterdecodes.substack.com
• LinkedIn: linkedin.com/in/dforrester

Connect with No Hacks

• Website: https://nohackspod.com
• Newsletter: Subscribe for weekly episodes

Episode URL: https://www.nohackspod.com/episode/216-the-machine-layer-building-trust-in-the-age-of-ai-search-with-duane-forrester

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