Also AI & Machine Learning
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric

Open-source project workspace for teams and AI agents
Tale is an open-source project workspace designed for teams and AI agents. It allows users to plan projects, delegate tasks to agents, and review results within a shared environment that combines task boards, agent sandboxes, shared knowledge, and workflows. Built for collaborative teams such as software development, marketing, and operations, Tale supports multiple runtimes and model providers including Claude, Codex, Gemini, Cursor, and OpenAI. The platform can be self-hosted using Docker on user infrastructure or used via cloud options.
“Tale is an open-source project workspace for teams and AI agents that combines task boards, agent sandboxes, shared knowledge, and workflows.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model reading the provided inputs learns that Tale is an open-source project workspace published by Ruler GmbH in Spiez, Switzerland. The homepage and llms.txt provide comprehensive details about platform features, including shared task boards, agent sandboxes, automations, and knowledge management. The text covers supported agent runtimes, connected tool integrations like GitHub and Slack, use cases for marketing and engineering, and extensive frequently asked questions addressing self-hosting, air-gapped deployments, and model choices. Pricing details are fully articulated across the homepage, llms.txt, and JSON-LD blocks, stating that the Community edition is free and open source, while the Enterprise edition costs 12 CHF or 14 EUR per user per month. The embedded JSON-LD provides structured organization and software application data, while the llms.txt file supplies a complete directory of platform pages and comparison articles.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing at least 400 URLs.
Describes itself to machines with schema.org JSON-LD. 3 of 4 pages read pass; 1 partly. The page at /contact declares BreadcrumbList but names none of them, so the markup asserts that something exists without saying what.
Content is marked up so a reader can find it. 3 of 4 pages read pass; 1 partly. The page at /contact is partly structured: The outline jumps from h1 to h3, which the standard forbids.
Navigation links expose usable destinations. 24 of 24 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 66 of 66 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 74 of 77 assessed homepage controls and role declarations meet the static role, state and relationship checks. +1.3 with its prompt in Pro.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 78 links across 3 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 96% of links.
Serves markdown at its own URL. /llms-full.txt serves the site's content as markdown (at least 64 KB).
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
49 of the 50 base points above the line, 31 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of tale.dev
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
48.8 / 50
3.3 of 3.3 points.
robots.txt is valid, with 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing at least 400 URLs.
8.3 of 8.3 points.
3 of 4 pages read pass; 1 partly. The page at /contact declares BreadcrumbList but names none of them, so the markup asserts that something exists without saying what.
10 of 10 points.
3 of 4 pages read pass; 1 partly. The page at /contact is partly structured: The outline jumps from h1 to h3, which the standard forbids.
4.2 of 4.2 points.
66 of 66 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.
1.3 of 2.5 points.
74 of 77 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
Agent layer
31.3 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 78 links across 3 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 96% of links.
12.5 of 12.5 points.
/llms-full.txt serves the site's content as markdown (at least 64 KB).
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 971 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 76 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
Adds +1 to the badge when found.
No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://tale.dev/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://tale.dev/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://tale.dev/
https://tale.dev/robots.txt
User-agent: * allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://tale.dev
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://tale.dev/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://tale.dev/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://tale.dev/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://tale.dev/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://tale.dev/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://tale.dev/
In its category
The prompts in the owner view would take Tale to 98, first in its category.
To the prompts →Category average 60. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.
More like Tale:AI Products & AgentsProject ManagementAI & Machine LearningOpen Source
Also AI & Machine Learning
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Same category
chatmizer.com
Omnichannel AI messaging platform for customer support, sales, and bookings
Same category
snappchart.app
AI chart analysis tool that grades trade setups from uploaded screenshots
Same category
pathnovo.com
AI agents that parse engineering documents into structured data for enterprise systems
Same category
aipicturesque.com
Freemium AI creative studio combining image, video, audio, and motion models in one workspace
Do you run tale.dev? Open the owner view → Removing the listing is free. Remove →