Two-sided platforms with separate buyer and seller flows. Agents read marketplace pages to compare listings, surface sellers, and route shoppers to the right SKU.
Marketplaces have two distinct user populations (buyers and sellers), and agents need to identify both flows. The well-implemented marketplace declares Product schema for listings, exposes seller / vendor metadata, and ships separate /sell and /buy entry points the agent can route to.
When the catalogue is JS-paginated, agents reading SSR HTML see the first page only. Use real /page/N URLs.
Without Organization or Person schema on the seller, agents cannot quote who is offering the product.
No /sell entry point means agents cannot route prospective sellers to onboarding.
/listings#filter=… loses the filter state on agent fetch. Use real query params.
Each row is the latest completed public scan for one domain. Composite is a 0–100 weighted average of five sub-scores; grade is bound to a published band table. The rubric (current and prior versions) is at /rubric.
Every score is the output of the public AgentSpeed rubric. The full check list, weights, and grade bands are at /rubric. New scans use the current active rubric; historical scans render against their original rubric.
Visit the scanner and submit a URL to generate a score. Every completed public scan creates a permanent score page and makes the domain eligible for ranking. There’s no application process and no editorial gate.
Add User-agent: AgentSpeedBot / Disallow: / to your robots.txt. On the next scan we honour it automatically and the public score page is replaced with a removal notice. See /bot.
Scan your marketplace to see how agents read your listings + seller flows.
Side-by-side composite, sub-scores, and per-category winner. Permanent shareable URL.
Every check in the rubric has a remediation page with paste-ready snippets.
Crawler matrix, llms.txt analyzer, structured-data validator, and seven more.