Home/News/Google Lighthouse 13.5 Adds Agent Resource Discovery Audit

SEO & GEO

Google Lighthouse 13.5 Adds Agent Resource Discovery Audit

2026-09-21 Search Engine Journal SEO & GEO
Google Lighthouse 13.5 Adds Agent Resource Discovery Audit
图:Search Engine Journal

Google Lighthouse 13.5 ships a new audit that checks whether a site exposes an Agent Resource Discovery (ARD) catalog, helping AI agents locate the tools and services a site offers — the audit doesn't affect search rankings yet.

Key facts

  • Timing: Released September 21, 2026 with Lighthouse 13.5; ships in Chrome 156 DevTools at release, reaches PageSpeed Insights within two weeks
  • Who's affected: Any independent store wanting to be discoverable by AI agents (shopping assistants, AI Overviews, etc.)
  • What to do: Not required yet — it's in the experimental "agentic browsing" category. Worth adding an Agentmap directive to robots.txt or a /.well-known/ard.json file per spec v0.91 as future-proofing

What happened

The new audit checks three locations for ARD catalog pointers: an Agentmap directive in robots.txt, an ai-catalog relation in an HTML link tag, and the same relation in an HTTP Link response header. If none are found, Lighthouse falls back to requesting the legacy path /.well-known/ai-catalog.json or the current spec's (v0.91, updated August 26, 2026) /.well-known/ard.json. Note that a site using only the new path without other pointers may get incorrectly flagged as "not applicable."

What this means for independent store owners

This is early infrastructure groundwork — the audit doesn't factor into Google search rankings, and Search Engine Journal classifies it as "experimental." But as AI shopping assistants and agentic tools increasingly access sites directly instead of through a human browsing session, exposing a machine-readable catalog of what your site offers under the ARD spec could help these agents find and cite you sooner. Most independent stores don't need to act immediately, but if your team already maintains robots.txt or structured data, adding an Agentmap directive is low-cost. The spec will likely keep evolving, so it's not worth a major rebuild right now.

Someone should be watching these changes for you

I run AI automation for independent stores — content, SEO/GEO, product listing, social, and keeping up with policy shifts like this one.

See how it works