Start
On this page

Can AI see my website? Lighthouse agentic browsing explained

Use Lighthouse and Layzr's free agentic audit to check whether AI agents and AI crawlers can read your website, find your sitemap, and understand your pages.

Updated May 25, 2026

Lighthouse has an experimental category called Agentic Browsing. The plain question is the one website owners actually ask: can AI see my website and use it without getting stuck?

This is early. Chrome's own Lighthouse agentic browsing scoring docs say the category and WebMCP support are experimental and based on proposed standards. That makes the feature worth watching, but it also means you should not treat the score like a final ranking system.

If you want a quick answer before installing anything, run Layzr's free agentic audit. Paste a website URL and it checks the files AI crawlers look for first: robots.txt, sitemap.xml, llms.txt, AI bot rules, link headers, and whether the page can return markdown.

Use both if you care about answer engine optimization, AI visibility, and whether AI agents can actually read and move through your website.

What is Lighthouse agentic browsing?

Lighthouse agentic browsing is an experimental Lighthouse category for checking whether a website is built in a way AI agents can read and use. It looks at technical signals, not whether a real customer would finish a task.

DebugBear's agentic browsing article notes that the category started appearing with Lighthouse 13.3 and includes checks around the accessibility tree, content shifts, WebMCP, and llms.txt. That matches the direction in Chrome's docs: agents need clean structure, stable pages, and clear instructions.

How the agentic browsing score works

The first thing to know: the agentic browsing score is not a normal Lighthouse score. Chrome says the category does not use a weighted 0 to 100 average. It reports a fractional pass ratio, pass or fail audit status, and informational counts.

  • A fractional score shows how many agentic readiness checks passed.
  • Individual audits can show pass, fail, warning, or informational results.
  • The category is meant to provide signals while standards are still forming.
  • Results can move if your WebMCP tools register at different times, the accessibility tree changes, or layout shifts affect interaction targets.

That matters if you already use PageSpeed Insights or Lighthouse for performance work. A 100 Performance score and a clean agentic browsing report are measuring different things. One asks whether the page loads well. The other asks whether an AI agent can read and use enough of the page.

What Lighthouse checks for agents

The category mixes newer AI agent checks with older website quality signals. The old stuff matters more now because AI agents read pages differently from humans.

WebMCP checks

WebMCP is a proposed way for a website to expose actions and form intent to AI agents. Chrome says Lighthouse monitors WebMCP tool registration through the Chrome DevTools Protocol and checks both declarative tools in HTML and imperative tools registered with JavaScript.

One current audit looks for forms that do not include both `toolname` and `tooldescription`. Chrome marks that specific audit as informational for now, so it can tell you what is missing without failing the whole page.

Accessibility tree checks

AI agents often rely on the accessibility tree because it gives them roles, names, states, and relationships without making them parse every visual detail. If your buttons are unlabeled, your custom controls hide their state, or a clickable `div` has no role, the agent has to guess.

  • Use real buttons and links when the element is interactive.
  • Give form fields attached labels.
  • Make names and states programmatic rather than just visual.
  • Avoid hiding interactive elements from the accessibility tree.

Layout stability checks

Layout shift is already part of Core Web Vitals, but it has a different cost for agents. If an agent identifies a button and the page moves before the click, the action can hit the wrong target.

This is why the new category pays attention to CLS. The fix is the same as normal page speed work: reserve image and embed space, avoid injecting banners above content, load fonts carefully, and keep important controls stable.

llms.txt checks

The llms.txt Lighthouse audit checks for a Markdown file at `/llms.txt`. Chrome says a missing file returns N/A for now because llms.txt is optional, while server errors can be flagged.

If you add one, keep it useful. A good llms.txt file should explain what the website does and link to important pages. For Layzr, that connects directly to AI brand visibility: AI systems need a clean version of your brand story before they can repeat it accurately.

How to check your Lighthouse agentic browsing score

Because this category is still rolling out, you may not see it in every Lighthouse surface yet. DebugBear reported that PageSpeed Insights and Chrome DevTools were still using older Lighthouse versions in mid-May 2026. If your report does not show Agentic Browsing yet, use the latest Lighthouse CLI or a tool that exposes the new category.

  1. Install the latest Lighthouse CLI with `npm install -g lighthouse@latest`.
  2. Run `lighthouse --view https://example.com/` against a page you care about.
  3. Open the report and look for the Agentic Browsing category.
  4. Read the fractional pass ratio first, then open each audit.
  5. Separate informational checks from problems that would break a real agent task.

Can AI agents see my website? Run the free check

Lighthouse answers part of the question inside Chrome. Layzr's free agentic audit answers the crawler side: can AI crawlers reach the basic files they usually check before they read or cite your website?

Paste your website URL and you get a simple pass/fail report. No login. No database. The result stays in the browser tab.

  • Can AI crawlers read my robots.txt?
  • Do I have a sitemap.xml file AI crawlers can find?
  • Do I have an llms.txt file?
  • Am I blocking GPTBot, ClaudeBot, PerplexityBot, or other AI crawlers?
  • Can an AI agent find useful links and markdown?

Where Layzr goes further

Lighthouse is useful for browser checks. It can tell you if a label is missing, if CLS is bad, or if a WebMCP annotation is invalid. It cannot tell you whether the page explains the product well, whether the next step is obvious, or whether a task reaches the right outcome.

Layzr gives you two paths. The free agentic audit answers the quick crawler question: can AI crawlers reach the right files? The full Layzr audit looks at the live page and shows what hurts SEO, clarity, trust, UX, and conversions.

  • Use Lighthouse for page-level browser checks.
  • Use the free agentic audit to check robots.txt, sitemap.xml, llms.txt, AI crawler rules, and markdown access.
  • Use the full Layzr audit when you want the SEO, copy, UX, trust, and conversion issues behind the page.
  • Use Layzr's AI visibility and brand mention checks when you need to know whether ChatGPT, Claude, Gemini, Perplexity, Grok, DeepSeek, Google AI Overviews, or Bing Copilot mention you.

Agent-friendly website checklist

This is the practical version. If you want to prepare for agent-friendly websites, start with the boring fixes. They help agents, but they also help people.

  • Use semantic HTML for buttons, links, forms, navigation, and headings.
  • Give every meaningful form control a label.
  • Make important states visible and programmatic.
  • Reserve space for images, embeds, ads, and late-loading UI.
  • Avoid transparent overlays and ghost elements that cover interactive controls.
  • Keep targets large enough to detect and click.
  • Make sure robots.txt does not block important AI crawlers by accident.
  • Publish a sitemap.xml and reference it in robots.txt.
  • Add llms.txt only if it gives agents a useful summary and real links.
  • Use WebMCP carefully when you have forms or actions agents should understand.
  • Run PageSpeed Insights for CLS and loading issues.
  • Run Layzr's free agentic audit to check robots.txt, sitemap.xml, llms.txt, AI crawler rules, and markdown access.
  • Run the full Layzr audit to catch the design, copy, SEO, and conversion problems Lighthouse misses.

How agentic browsing connects to AEO

Agentic browsing and answer engine optimization are not the same thing, but they are getting closer. AEO asks whether AI systems mention and describe your brand correctly. Agentic browsing asks whether an AI agent can read and act on the page once it arrives.

If an AI crawler cannot reach your website files, AEO starts with a crawl problem, not a content problem. Use the free agentic audit first, then use a full audit to see whether the page is clear enough to deserve a mention.

The overlap is practical: clear content, stable layouts, semantic HTML, useful summaries, and visible proof all make the page easier for AI systems to understand. That is also why Google Search Console still matters. You need to know which pages already have search demand before you decide which pages deserve agent-ready cleanup first.

References

FAQ

How do I check if AI can see my website?

Run Layzr's free agentic audit. It checks robots.txt, sitemap.xml, llms.txt, AI crawler rules, link headers, and markdown access so you can see whether AI crawlers can reach the basics.

What is Lighthouse agentic browsing?

Lighthouse agentic browsing is an experimental Lighthouse category that checks whether a page is built in a way AI agents can read and use. It looks at signals like WebMCP, accessibility tree quality, layout stability, and llms.txt.

How is the agentic browsing score calculated?

Chrome says the category does not use a weighted 0 to 100 score. It shows a fractional pass ratio, audit pass or fail status, warnings, and informational counts.

Does PageSpeed Insights show agentic browsing?

The feature is still rolling out across Lighthouse surfaces. If PageSpeed Insights does not show Agentic Browsing yet, run the latest Lighthouse CLI or use a tool that exposes Lighthouse 13.3 or newer.

What is WebMCP in Lighthouse?

WebMCP is a proposed way for websites to expose forms and actions to AI agents. Lighthouse can detect registered WebMCP tools and check whether forms have declarative metadata like toolname and tooldescription.

Does llms.txt affect the agentic browsing score?

The llms.txt audit is part of Lighthouse's agentic browsing discoverability checks. Chrome says a missing llms.txt file is marked N/A for now because the file is optional, while server errors can be flagged.

How is Layzr different from Lighthouse agentic browsing?

Lighthouse checks technical browser signals. Layzr's free agentic audit checks AI crawler access, and the full Layzr audit reviews SEO, copy, UX, trust, conversions, AI visibility, and brand mentions.

Check if AI can see your website

Paste your URL into the free agentic audit. It checks robots.txt, sitemap.xml, llms.txt, AI crawler rules, link headers, and markdown access.

Run free agentic audit