--- title: "Documentation: AI visibility reports" description: "Compare documentation websites by AI visibility score. Read crawler findings and look for accessible guides, versioned references and code examples in text." url: "https://goodforbots.com/directory/category/documentation" --- # Documentation Compare documentation websites by AI visibility score. Read crawler findings and look for accessible guides, versioned references and code examples in text. [How websites are scored](https://goodforbots.com/standards#scoring) Search by name or domain: https://goodforbots.com/directory/category/documentation.md?q={query}, at most 120 characters. 0 sites. Sorted by best score first. Also: [worst score first](https://goodforbots.com/directory/category/documentation.md?sort=score-asc) · [site name, A–Z](https://goodforbots.com/directory/category/documentation.md?sort=host). No sites match these filters. “(Pro)” marks a Pro listing. Pro never changes a score or a place in the order. [What Pro includes](https://goodforbots.com/pricing#pro). Every report is also available as Markdown at https://goodforbots.com/r/{host}.md. ## Categories - [All sites](https://goodforbots.com/directory.md): 117 sites - Software & Tools - Documentation: 0 sites (this page) - [Developer Tools & APIs](https://goodforbots.com/directory/category/developer-tools.md): 24 sites - [SaaS & Web Apps](https://goodforbots.com/directory/category/saas.md): 34 sites - [AI Products & Agents](https://goodforbots.com/directory/category/ai-products.md): 20 sites - Content & Knowledge - [Blogs & Newsletters](https://goodforbots.com/directory/category/blogs.md): 2 sites - [Education & Learning](https://goodforbots.com/directory/category/education.md): 7 sites - [Research & Reference](https://goodforbots.com/directory/category/research-reference.md): 5 sites - [Directories & Aggregators](https://goodforbots.com/directory/category/directories.md): 11 sites - Commerce & Services - [E-commerce Stores](https://goodforbots.com/directory/category/ecommerce.md): 1 site - [Marketplaces & Booking](https://goodforbots.com/directory/category/marketplaces.md): 1 site - [Local Businesses & Services](https://goodforbots.com/directory/category/local-business.md): 1 site - Organizations & People - [Companies & Agencies](https://goodforbots.com/directory/category/companies.md): 3 sites - [Communities & Forums](https://goodforbots.com/directory/category/communities.md): 1 site - Misc - [Other](https://goodforbots.com/directory/category/other.md): 1 site ## Platforms Match any selected platform. Counts show sites using each one. - Astro: 0 sites - Lovable: 0 sites - Next.js: 0 sites - Nuxt: 0 sites - SvelteKit: 0 sites - WordPress: 0 sites ## Signals Each one you pick narrows the list: a site must have them all. ### Agent capabilities - API catalog: 0 sites. Lists 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.md: 0 sites. A 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 card: 0 sites. Describes 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 index: 0 sites. Lists 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 Auth: 0 sites. Publishes 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 commerce: 0 sites. Publishes how agents can connect to its Agentic Commerce Protocol integration. The badge confirms discovery metadata; purchases are not tested. ### Standards - llms.txt: 0 sites. A short guide to the site written for AI models: what it is and which pages matter most. - robots.txt: 0 sites. The file that tells crawlers where they may go. Every other rule a site gives to bots starts here. - Sitemap: 0 sites. A list of the site's pages, so a bot sees everything that exists instead of guessing from links. - Descriptive llms.txt: 0 sites. The llms.txt describes what is behind each link, so a model knows which pages are worth reading. - llms-full.txt or .md pages: 0 sites. The 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 negotiation: 0 sites. Pages come back as clean Markdown when a bot asks for it: just the content, without menus, styling and scripts. - AI crawler rules: 0 sites. The site says which AI bots may visit, for training, search or answering questions. Blocking some is fine; what counts is making a choice. - Content Signals: 0 sites. The 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-LD: 0 sites. Structured 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 HTML: 0 sites. The 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 navigation: 0 sites. Observed homepage navigation exposes usable page addresses and section targets in HTML. Destinations are not fetched by this check. - Named links and buttons: 0 sites. Links and buttons in the collected homepage HTML have names recoverable from text, labels or native alternatives, including icon controls. - Named form fields: 0 sites. Observed homepage fields have recoverable names and recognizable input semantics. Submission behavior is not tested. - Control roles and states: 0 sites. Homepage controls meet static checks for roles, required states and relationship targets, using native HTML semantics where available. - Typed links: 0 sites. The 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 URL: 0 sites. Each page names the one address that should be indexed and cited, so an agent quoting it links to the right URL. - Working section links: 0 sites. Links 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. ## About Documentation A documentation site is often where an assistant goes after the marketing page stops being useful. The question has become specific: which parameter is optional, which version introduced a feature, or why an example fails. A page that hides those answers behind an interactive shell leaves the reader with a title and a guess. Useful documentation gives each topic an address, keeps examples beside their explanations, and makes the supported version clear. A [Markdown representation](https://goodforbots.com/standards#llms-full-txt) can make that material easier to extract; an [llms.txt file](https://goodforbots.com/standards#llms-txt) can point a reader towards the right starting places. Neither replaces the documentation itself. The report covers fetched URLs, not every guide or code sample. For an integration, open the reference for your version and test the example against the product you use. ## What to look for Use these questions when reading the sites themselves. They are guidance for this category, not additional scoring checks. ### A route to the answer Look for links to individual guides and reference pages. A search box is useful for people, but should not be the only way to reach the content. ### Version context Examples should identify the release they apply to. An old answer with a clear version is more useful than one that silently mixes several releases. ### Examples available as text Commands, parameters and expected output should survive extraction from the page. Screenshots alone leave an assistant unable to inspect the details. ### A readable alternative Check whether Markdown pages or a useful llms.txt guide lead to the actual reference material, rather than repeating the homepage description. ## Frequently asked questions ### Does llms.txt replace a documentation site? No. It is a guide to material the publisher wants to make discoverable. The linked pages still need to be accessible and contain enough context to answer the question. ### Does a high score mean every code example works? No. The score concerns machine readability and the signals collected during a scan. We do not run a site's examples or verify every documented behaviour. ### Where do API providers belong? A dedicated documentation site fits here. A site primarily presenting an API or developer product belongs in Developer Tools & APIs. The distinction describes the site, not a different scoring tier. Questions about scores, scans and listings in general are answered in [the FAQ](https://goodforbots.com/faq). ## Explore related categories - [Developer Tools & APIs](https://goodforbots.com/directory/category/developer-tools.md) - [Open Source Projects](https://goodforbots.com/directory/category/open-source.md) - [Research & Reference](https://goodforbots.com/directory/category/research-reference.md) ## Structured data ```json { "@context": "https://schema.org", "@graph": [ { "@type": "CollectionPage", "@id": "https://goodforbots.com/directory/category/documentation#webpage", "url": "https://goodforbots.com/directory/category/documentation", "name": "Documentation: AI visibility reports", "description": "Compare documentation websites by AI visibility score. Read crawler findings and look for accessible guides, versioned references and code examples in text.", "inLanguage": "en", "isPartOf": { "@id": "https://goodforbots.com/#website" }, "breadcrumb": { "@id": "https://goodforbots.com/directory/category/documentation#breadcrumb" }, "mainEntity": { "@id": "https://goodforbots.com/directory/category/documentation#items" } }, { "@type": "BreadcrumbList", "@id": "https://goodforbots.com/directory/category/documentation#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://goodforbots.com/" }, { "@type": "ListItem", "position": 2, "name": "Directory", "item": "https://goodforbots.com/directory" }, { "@type": "ListItem", "position": 3, "name": "Documentation", "item": "https://goodforbots.com/directory/category/documentation" } ] }, { "@type": "ItemList", "@id": "https://goodforbots.com/directory/category/documentation#items", "name": "Documentation: AI visibility reports", "numberOfItems": 0, "itemListElement": [] }, { "@type": "FAQPage", "@id": "https://goodforbots.com/directory/category/documentation#faq", "name": "Frequently asked questions about Documentation", "isPartOf": { "@id": "https://goodforbots.com/directory/category/documentation#webpage" }, "mainEntity": [ { "@type": "Question", "name": "Does llms.txt replace a documentation site?", "acceptedAnswer": { "@type": "Answer", "text": "No. It is a guide to material the publisher wants to make discoverable. The linked pages still need to be accessible and contain enough context to answer the question." } }, { "@type": "Question", "name": "Does a high score mean every code example works?", "acceptedAnswer": { "@type": "Answer", "text": "No. The score concerns machine readability and the signals collected during a scan. We do not run a site's examples or verify every documented behaviour." } }, { "@type": "Question", "name": "Where do API providers belong?", "acceptedAnswer": { "@type": "Answer", "text": "A dedicated documentation site fits here. A site primarily presenting an API or developer product belongs in Developer Tools & APIs. The distinction describes the site, not a different scoring tier." } } ] }, { "@type": "Organization", "@id": "https://goodforbots.com/#organization", "name": "Good for Bots", "url": "https://goodforbots.com", "logo": "https://goodforbots.com/icon-512.png", "founder": { "@id": "https://goodforbots.com/#person-mateusz-pawlica" }, "contactPoint": { "@type": "ContactPoint", "contactType": "customer support", "email": "support@goodforbots.com", "url": "https://goodforbots.com/contact" } }, { "@type": "WebSite", "@id": "https://goodforbots.com/#website", "name": "Good for Bots", "url": "https://goodforbots.com", "description": "Check if AI crawlers can access and read your website, free. Get a score out of 100 with every finding and fix prompts, then browse reports in the directory.", "inLanguage": "en", "publisher": { "@id": "https://goodforbots.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://goodforbots.com/directory?q={q}" }, "query-input": "required maxlength=120 name=q" } }, { "@type": "Person", "@id": "https://goodforbots.com/#person-mateusz-pawlica", "name": "Mateusz Pawlica", "givenName": "Mateusz", "familyName": "Pawlica", "jobTitle": "Founder of Good for Bots", "description": "Web developer who builds directories and AI-powered products, and the founder of Good for Bots.", "url": "https://goodforbots.com/about#founder", "sameAs": [ "https://pl.linkedin.com/in/mateusz-pawlica-65238816b", "https://pawlicaweb.pl/o-mnie" ], "knowsAbout": [ "llms.txt", "robots.txt", "AI crawlers", "Markdown content negotiation", "Structured data", "Technical SEO", "Web directories", "Next.js", "TypeScript", "Generative AI" ], "worksFor": { "@id": "https://goodforbots.com/#organization" } } ] } ```