FlowiseAI

Last scanned docs.flowiseai.comGitBook15 pages tested

AI agents can find, read and use these docs well. FlowiseAI scores 94 out of 100 (grade A), passing 21 of 27 checks. 6 still need work.

Fix it with Documentation.AI

Get this report by email

We send the full report to your inbox. Nothing on this page needs an email.

Use your work email. We only send what you asked for, and every email has an unsubscribe link.

Developer docs

Kind of site

21/27

Checks passed

5

Partly passed

1

Failed

Access

Content discoverability4 passed3 partly
  • llms.txt follows the standard structure

    llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.flowiseai.com/llms.txt: No blockquote summary found

    Your llms.txt contains parseable links but doesn't follow the standard structure. Add an H1 title as the first line and a blockquote summary (lines starting with >) to improve agent parsing.

    Check your fix: llms.txt starts with a # Title, then a > summary line, then ## sections of links.

  • llms.txt fits in an agent's context

    llms.txt is 98,573 characters (between 50,000 and 100,000; consider splitting)

    Your llms.txt is 98,573 characters, which may be truncated on some agent platforms. If it grows further, split into nested llms.txt files with a root index under 50,000 characters.

    Check your fix: curl -s https://docs.flowiseai.com/llms.txt | wc -c prints less than 50000.

  • Pages point agents to llms.txt

    llms.txt directive found in HTML of 15 of 15 sampled pages, but buried deep in the page (past 50%)

    An llms.txt directive was found in the HTML of some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every documentation page.

    Check your fix: curl -s https://docs.flowiseai.com/api-reference | grep -n llms.txt finds the link near the top of the HTML.

  • llms.txt exists

    llms.txt found at https://docs.flowiseai.com/llms.txt

  • llms.txt links work

    All 15 same-origin sampled links resolve (653 total links)

  • llms.txt links point to Markdown

    15/15 same-origin sampled links point to markdown content (100%)

  • Markdown pages point agents to llms.txt

    llms.txt directive found in markdown of all 15 sampled pages, near the top of content

Markdown availability2 passed
  • Pages are available as Markdown

    15/15 sampled pages support .md URLs (100%)

  • Server returns Markdown when asked

    15/15 sampled pages support content negotiation (100%)

Page size and truncation3 passed1 failed
  • Content starts near the top

    14 of 15 sampled pages have content starting past 50% (worst 100%)

    14 of 15 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.

  • Content is in the HTML without JavaScript

    All 15 sampled pages contain server-rendered content

  • Markdown pages fit in context

    All 15 pages under 50K chars (median 1K, max 4K)

  • HTML pages fit in context

    All 15 sampled pages under 50K chars (median 571K HTML โ†’ 8K markdown (99% boilerplate))

Content structure3 passed
  • Tabs don't bloat the page

    No tabbed content detected across 15 sampled pages

  • Headings inside tabs name their variant

    No tabbed content found; header quality check not applicable

  • Code blocks are well-formed

    All 2 code fences properly closed across 16 pages

URL stability2 passed
  • Missing pages return a real 404

    All 15 sampled pages return proper error codes for bad URLs

  • Redirects stay on the same host

    No redirects detected across 15 sampled pages

Content health2 passed1 partly
  • Markdown matches the HTML page

    2 of 15 pages have minor content differences between markdown and HTML

    2 pages have minor content differences between their markdown and HTML versions.

  • llms.txt covers the whole site

    llms.txt covers 100% of 653 sitemap doc pages; 2 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)

  • Cache headers allow timely updates

    All 16 endpoints have appropriate cache headers

Authentication and access1 passed
  • Gated docs offer another way in

    All docs pages are publicly accessible; no alternative access paths needed

  • Docs are readable without logging in

    All 15 sampled pages are publicly accessible

Crawler access2 passed
  • Crawlers and AI assistants may read the docs

    robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.

  • Sitemap lists the docs pages

    The sitemap at https://docs.flowiseai.com/sitemap.xml lists 653 of the 655 docs pages found through llms.txt and page links.

Freshness

Maintenance2 passed1 partly
  • Links and section anchors work

    1 of 52 references checked on the sampled pages are broken: 1 link. 1 more could not be verified (timeouts or blocked requests) and is not counted.

    Fix or remove the broken links, redirect moved pages to their new address, and restore or retarget section anchors. Agents follow links to gather context, and a dead link ends that path.

    Check your fix: Every link on https://github.com/FlowiseAI/FlowiseDocs/blob/main/esp/contributing/README.md (404) linked from https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/cache/redis-embeddings-cache returns 200, and every #section link points at an element with that id.

  • Pages say when they were last changed

    15 of 15 sampled pages state when they were last changed.

  • Sitemap entries still exist

    All 10 sitemap entries sampled still exist.

Consistency with the API specNot applicable
  • Endpoints in the docs exist in the API spec

    No OpenAPI description was found, so the docs could not be compared with a spec.

CurrencyNot applicable
  • Deprecated operations are marked as such

    No OpenAPI description was found, so deprecation notices could not be compared with a spec.

Additional checks

Not part of the score: optional extras that help agents use your docs.

  • MCP server is discoverable

    An MCP server is described at https://docs.flowiseai.com/.well-known/mcp/server-card.json.

  • llms-full.txt is available

    llms-full.txt found at https://docs.flowiseai.com/llms-full.txt (618,567 characters).

  • Agent skills are published

    No agent skills index was found at /.well-known/agent-skills/index.json.

    Publish an Agent Skills index at /.well-known/agent-skills/index.json with a SKILL.md for your main tasks, so agents can load task instructions without reading every page.

About this scan

Scanned
Oct 21, 2026
Pages tested
15 of 653 found
Platform
GitBook
Kind of site
Developer docs
AFDocs score, on its own
93 (A), 17 of 23 checks pass
  • Based on 15 sampled pages, chosen deterministically from the sitemap and llms.txt. Pages outside the sample were not read.
  • Pages were fetched without running JavaScript, the way most AI agents read the web.
  • robots.txt stopped the scanner from reading 1 URL; checks that needed them are unverified.
  • Answerability, where an AI agent answers real questions written from these pages, runs in the open-source scanner with your own API key. This web score is made of Access and Freshness.

Methodology 2026-09.6 ยท AFDocs 0.20.0

Pages we sampled (15)
  • https://docs.flowiseai.com/api-reference
  • https://docs.flowiseai.com/espanol/documentacion-oficial/configuracion/autorizacion/nivel-chatflow
  • https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/cache/redis-embeddings-cache
  • https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/document-loaders/file-loader
  • https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/llms/replicate
  • https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/langchain/tools
  • https://docs.flowiseai.com/espanol/documentacion-oficial/integraciones/llamaindex/agents/openai-tool-agent-1
  • https://docs.flowiseai.com/espanol/documentacion-oficial/referencia-api/feedback
  • https://docs.flowiseai.com/espanol/partes/parte-7-multi-agentes
  • https://docs.flowiseai.com/integrations/langchain/chains/conversational-retrieval-qa-chain
  • https://docs.flowiseai.com/integrations/langchain/document-loaders/folder
  • https://docs.flowiseai.com/integrations/langchain/llms/huggingface-inference
  • https://docs.flowiseai.com/integrations/langchain/text-splitters/markdown-text-splitter
  • https://docs.flowiseai.com/integrations/langchain/vector-stores/pinecone
  • https://docs.flowiseai.com/integrations/utilities/if-else

Show your score

Add the badge to your docs or README. It updates each time the site is scanned.

Agent Readiness Score badge

Markdown

[![Agent Readiness Score: 94 (A)](https://documentation.ai/agent-score/badge/flowiseai.svg)](https://documentation.ai/agent-score/flowiseai)

HTML

<a href="https://documentation.ai/agent-score/flowiseai"><img src="https://documentation.ai/agent-score/badge/flowiseai.svg" alt="Agent Readiness Score: 94 (A)" height="20"></a>

Agent-ready docs by default

Documentation.AI sites ship with llms.txt, Markdown pages, a sitemap and an MCP server, and our agent keeps the content current.

Live in under 5 min ยท No credit card required