Marketplaces & Booking

Explore AI visibility reports for marketplaces and booking sites. Check crawler access and review how listings describe sellers, prices and availability.

How websites are scored

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt1The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap1A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD0Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML0The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation1Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons1Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields1Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states1Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL0Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links1Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

Filters · 1 active

Signals

Each one you pick narrows the list: a site must have them all.

Agent capabilities

API catalog0Lists the site's public APIs in one standard place, so an agent can find and use them without reading the docs. A bonus: it earns a badge and never costs points.
auth.md0A simple file that tells AI agents how to sign in and get access. A bonus: it earns a badge and never costs points.
A2A agent card0Describes the site's own AI agent in the A2A format, so other agents can find it and hand it work. A bonus: it earns a badge and never costs points.
Agent Skills index0Lists reusable instructions the site publishes for AI agents, with descriptions and download locations. The index earns a badge; the skill downloads themselves are not verified.
Web Bot Auth0Publishes the keys the site's own bots sign their requests with, so other websites can verify them. The badge checks the keys; the bots' requests are not observed.
ACP commerce0Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested.

Standards

llms.txt0A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt1The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap1A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt0The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages0The content is also available as plain Markdown, in one llms-full.txt file or as separate .md pages. Models can read it without the HTML.
Markdown negotiation0Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules0The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice.
Content Signals0The site says how its content may be used: for search, in AI answers or to train AI. Any mix of yes and no counts.
schema.org JSON-LD0Structured data on the homepage says what the site is, such as a company, a product or an article, so machines don't have to guess.
Semantic HTML0The page has a clear structure: a main content area, headings in order, a header and a footer. A bot can tell the content from the rest.
Crawlable navigation1Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons1Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls.
Named form fields1Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested.
Control roles and states1Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links0The page links to versions made for machines, such as a Markdown copy or an API description, so an agent can go straight to them.
Canonical URL0Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links1Links to part of a page, such as a table of contents or a skip link, lead to that section instead of the top of the page.

1 site

Websites in the directory, with their Good for Bots score. Column headers sort the list.
Site	Category	Score
Growth Bounties growthbounties.com Marketplace for independently verified Ahrefs Domain Rating growth outcomes	Marketplaces & Booking	View report for Growth Bounties:

Promarks a Pro listing, in gold. Pro never changes a score or a place in the order.What Pro includes

Through a bot’s eyes

About Marketplaces & Booking

A marketplace page often describes several things at once: the platform, the seller, the item and the terms of a particular offer. Booking adds another moving part, because availability depends on dates, location and party size. A useful page keeps those relationships clear instead of presenting a price without its assumptions.

This category includes platforms connecting buyers and sellers, service marketplaces and booking websites. Public listings should explain who supplies the offer and what the platform contributes. Stable listing addresses help a reader return to the same item, while accessible policy pages give cancellation rules and fees somewhere to live outside the checkout flow.

A report covers the public pages fetched during the scan. It cannot confirm a booking or test every date and location. Check availability and fulfilment terms with the marketplace.

What to look for

Use these questions when reading the sites themselves. They are guidance for this category, not additional scoring checks.

The seller and platform distinguished: Readers should be able to identify who provides the item or service and which responsibilities belong to the platform.
Availability with assumptions: Dates, location and quantity give an offer meaning. A starting price should not be mistaken for a confirmed offer for a particular request.
Reachable listing pages: Individual URLs make it possible to inspect and revisit an offer. A map or search interface should not be the only public description.
Fees and cancellation terms: Conditions should be available before committing to a booking. The directory's score does not verify that those policies are fair or enforced.

Frequently asked questions

Do you test reservations or payments?

No. The scanner does not make bookings, submit payments or contact sellers. The report describes public web access and detected signals.

How is a marketplace different from a directory?

A marketplace centres on connecting supply and demand for a transaction or booking. A directory primarily helps readers discover other destinations. The category does not change the score.

Is listed availability verified?

No. Availability can depend on the requested dates and other choices. Confirm it directly with the marketplace before relying on an offer.

Questions about scores, scans and listings in general are answered in the FAQ.