Brandon Lazovic

Pulse · September 22, 2026

Confirmed

Lighthouse 13.5 Ships an Audit for AI Agent Resource Catalogs

Lighthouse 13.5, released September 18, added an 'ard-schema' audit under a new 'Agent Discoverability' heading. It validates Agentic Resource Discovery (ARD), a proposed spec for how AI agents find an organization's tools and services: check robots.txt for an Agentmap directive, then a link tag with the ai-catalog relation, then an HTTP Link header, defaulting to /.well-known/ai-catalog.json. It fails only on a schema error or an unloadable file; a missing catalog scores Not Applicable, and PageSpeed Insights follows within two weeks.

In plain termsThe ai-catalog.json file this audit checks for is a JSON manifest, a structured text file, listing what an AI agent can do on a site, like a menu built for machines instead of people; Lighthouse is the audit tool already built into Chrome that scores a page's speed and accessibility.

Why it mattersA site's agent catalog now feeds a mainstream audit tool millions of developers already run, so a missing or malformed one becomes a visible score hit instead of an invisible gap.

Our takeI found the same gap by hand in "I passed every agent-readiness check while three statements in my own metadata were false": a check that verifies a catalog exists and parses says nothing about whether its claims are true. Lighthouse's new audit is that same shape check running at far larger scale, and it will reward a schema-valid catalog full of stale or invented values exactly as it rewards an honest one.

Confirmed

Google Merchant Center Documents New Eligibility Thresholds for Store Ratings

Google's Merchant Center help page for Store ratings now spells out eligibility math that was previously vaguer: a store generally needs at least 100 eligible, unique reviews and an average of 3.5 out of 5 stars to qualify for paid text and Shopping ads, calculated from a rolling 24-month review window. Ratings are geo-segmented, scored separately per country rather than pooled globally, so a merchant can qualify in one market and not another.

In plain termsA 'rolling 24-month window' means Google only counts reviews from the last two years counting back from today, so old feedback ages out automatically as new reviews come in, rather than counting every review a store has ever received.

Why it mattersA merchant chasing a store rating badge needs to clear that 100-review, 3.5-star bar inside each country's own rolling 24-month window, not as one global total, which changes where review-generation effort should go first.

Our takeA documented threshold is a compliance target, not a new bar Google invented today, since most merchants already near or past 100 reviews were effectively meeting it already. The thing to check next is whether the same reorganized help page changed anything about how an ineligible country's badge displays, since the geo-segmentation rule is the easiest part to miss.