Skip to content
Good for Bots

Study app that links notes into a map of what you know and schedules spaced reviews

Good for Bots: Good, 81 of 100Get this badge →

On your homepage, it turns this report’s link to breef.app dofollow.

Scanned

What is Breef?

Breef is a study app for notes. Users write or record what they learn, and their notes link into a map of what they know. The input describes it as built for students, researchers and lifelong learners who bring their own material, such as lecture notes, slides, books and papers. The homepage lists features including voice notes that write up a lecture as a study note, spaced reviews that bring each note back before it is forgotten, quizzes on notes, exam dates that schedule final reviews, a question feature that answers from the user's notes, and sharing notes on the web. A free plan is offered, with a Pro plan at €6 a month or €48 a year.

Through a bot’s eyes

“Breef is a study app that turns notes and lectures into linked notes, with spaced reviews, quizzes and exam prep. It is free to start, with a Pro plan at €6 a month or €48 a year.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

The homepage text covers note-taking and studying in English, with examples about photosynthesis, chlorophyll, sound waves and musical intervals, and describes the app's features in headings and short paragraphs. The facts a visitor would look for are present as text: the Free plan at €0 with its listed allowances, the Pro plan at €48 a year or €6 a month with its extra allowances, and a sign-up link to /auth. The homepage text does not name a company or give a contact address. The llms.txt file adds a product summary, a list of main pages, the Model Context Protocol server address for connecting AI apps, privacy statements, the operator's name and country, and a long list of free study tools and guides. It is cut off before its list ends. The JSON-LD adds an Organization entry with a support email address, a country code, supported languages and three priced offers. Both files repeat pricing and features from the homepage and add details the homepage text does not contain.

What stays hidden

A model reading only the homepage text would not learn the operator's name, the support address, the languages the app runs in, or where data is stored; these appear only in the llms.txt or JSON-LD. Because llms.txt is cut off, the pages and study tools it lists after the cut are not visible, and the input does not show what the Free plan's limits mean in daily use.

Good for Bots report

Breef scores 81 of 100: the whole readable base, 31 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 31 of the 50 agent-layer points below it.

81

Still open

Behind the checks below, with prompts in Pro.

1
Penalties0
How scoring works · current methodology →

For the owner of breef.app

3 prompts, 18 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

50 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, Person, PostalAddress in valid schema.org JSON-LD.

Passes.

10 of 10 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.3 of 8.3 points.

64 of 64 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

169 of 169 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

2 of 2 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

178 of 178 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

31.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 43 links across 6 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 86% of links. 12 of 37 descriptions follow the link with something other than ":", the separator the format specifies (`- [name](url): notes`).

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (at least 64 KB).

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1200 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 305 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

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.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://breef.app/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

https://breef.app/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://breef.app/

    robots.txt is present and valid

  • Observed · Direct request

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    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://breef.app

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://breef.app/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

3rd of 16 in Education & Learning

  1. 1Unrustunrust.dev
  2. 2Xue Chinesexuechinese.yudis.dev
  3. 3Breef · this reportbreef.app

The prompts in the owner view would take Breef to 99, first in its category.

To the prompts →

Category average 66. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
11 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
4.3 MB
Took
16.4 s
Homepage
305 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

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.

  • Homepagealways read
  • /for/lifelong-learnerslinked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · read
  • /alternatives/ankifrom the sitemap · read

More like Breef:Education & LearningProductivityStudentsFreemium

Also Freemium

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Freemium

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also Good

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Also Freemium

brivoy.com

Community site where makers launch new products and early adopters discover them

Also Freemium

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Do you run breef.app? Open the owner view → Removing the listing is free. Remove →