SaaS & Web Apps

Compare SaaS websites by AI visibility score. Review access to public product pages and look for readable workflows, plan differences and help documentation.

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.txt4A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt5The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap5A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt3The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages1The 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 negotiation1Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules5The 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-LD4Structured 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 HTML4The 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 navigation5Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons5Links 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 states4Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links1The 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 URL5Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links3Links 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.

Clear signals

Filters · 3 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.txt4A short guide to the site written for AI models: what it is and which pages matter most.
robots.txt5The file that tells crawlers where they may go. Every other rule a site gives to bots starts here.
Sitemap5A list of the site's pages, so a bot sees everything that exists instead of guessing from links.
Descriptive llms.txt3The llms.txt describes what is behind each link, so a model knows which pages are worth reading.
llms-full.txt or .md pages1The 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 negotiation1Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts.
AI crawler rules5The 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-LD4Structured 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 HTML4The 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 navigation5Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check.
Named links and buttons5Links 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 states4Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available.
Typed links1The 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 URL5Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL.
Working section links3Links 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.

Clear signals

5 sites

Next.js AI crawler rules

Websites in the directory, with their Good for Bots score. Column headers sort the list.
Site	Category	Score
BulkShare bulkshare.cloud Branded file delivery on custom domains for agencies and freelancers	SaaS & Web Apps	View report for BulkShare:
Mantis Ai mantisai.in Local lead intelligence and website gap detection for agencies and sales teams	SaaS & Web Apps	View report for Mantis Ai:
Baiivo baiivo.com Client work and payment software for freelancers and small studios	SaaS & Web Apps	View report for Baiivo:
Relanco relanco.ca Automated bilingual SMS and email payment reminders for Canadian contractors	SaaS & Web Apps	View report for Relanco:
Bidcraftr bidcraftr.com Proposal software with e-signatures and payment collection for freelancers	SaaS & Web Apps	View report for Bidcraftr:

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 SaaS & Web Apps

Most of a web app's value is behind a login. That is expected. The public website still needs to explain what the product does, who it serves, and where its limits lie. An assistant comparing products can only work with the material it is allowed to read.

A useful SaaS site makes its workflows concrete. It describes the objects a user works with, the integrations that connect them, and the differences between plans. A wall of interface screenshots may communicate the visual design while leaving the actual behaviour difficult to extract.

We scan public pages without entering customer workspaces. The findings describe that website evidence; they do not rate the application or show whether private records are exposed.

What to look for

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

Workflows in words: Look for an explanation of what a user can accomplish, with examples that make sense without opening a trial account.
Plan differences that can be read: Limits and included features should be text, with enough context to distinguish the plans. Check the provider's current terms before buying.
Public help material: Accessible guides let readers investigate an unfamiliar feature before signing up. A help centre that requires login cannot serve that public discovery role.
Clear access boundaries: The site should separate public product information from private customer work. Readability is not a reason to publish workspace data.

Frequently asked questions

Does a login hurt a site's score?

Having accounts is not itself a penalty. Our scan examines the public URLs it fetches; content that those URLs expose only through JavaScript or an access barrier can limit the evidence available.

Do you inspect the application after signing in?

No. We do not create accounts or enter private workspaces. The report describes the public website and the discovery signals observed during the scan.

Is this a ranking of the best SaaS products?

No. The order reflects our machine-readability score, not product quality, value for money or suitability for a particular team.

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