Baiivo

baiivo.com

Client work and payment software for freelancers and small studios

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

Baiivo scores 76 of 100: the whole readable base, 26 of the 50 agent-layer points, no penalties.

Earned

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

3 prompts away

Copy them below ↓

Still open

Behind the checks below, with prompts in Pro.

Penalties0

How scoring works · current methodology →

Through a bot’s eyes

“Baiivo is a client work and payment workspace for freelancers and small studios that connects quotes, contracts, deliverables, invoices, and follow-ups into a single record.”

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

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns about Baiivo's core offerings, target audience, and workflows through the homepage text, an llms.txt file, and embedded JSON-LD blocks. The homepage details the five-station job rail covering quotes, e-sign contracts, client portals, invoicing, and payment follow-ups. The llms.txt file outlines the site structure, primary pages, audience guides for designers and developers, comparison pages against alternatives like HoneyBook and FreshBooks, and free tools. The JSON-LD structured data supplies clear software application details, including exact pricing tiers such as the Free tier, Pro at thirty-nine dollars per month, Growth at one hundred nineteen dollars per month, and a contact-based Agency plan. Contact information including a support email and founder details are also fully provided.

What is Baiivo?

Baiivo is a client work and payment software designed for freelancers, solo studios, consultants, developers, designers, and small agencies. It provides a connected workspace that manages quotes, signed contracts with cryptographic audit trails, project deliverables through branded client portals, invoices processed over Stripe, and automated follow-up sentinel sequences that pause upon payment.

The platform aims to keep all client interactions and financial records unified under a single client profile. Additionally, it offers free tools such as rate calculators and payment term generators, and includes an MCP server for scoped AI agent interactions. The product is independently built by founder Jesús Mendoza and features multiple subscription tiers alongside a free plan.

3 prompts, 20 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

+10

Serve Markdown when asked for it

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

Read prompt

My website baiivo.com scored 76/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: serve markdown through content negotiation on all public HTML routes.

The check it fails is "Serves markdown when asked for it", worth 10 points. What the scanner saw: None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

The scan checked a sample of 4 pages. It does not establish which other pages have the same issues. Use the findings below to locate the responsible templates, components or configuration, and apply the fix wherever the same issue occurs. Pages in the sample with findings:
- https://baiivo.com/: Asking the homepage for markdown still returns text/html.
- https://baiivo.com/cashflow-tracking-for-freelancers: Asking the page at /cashflow-tracking-for-freelancers for markdown still returns text/html.
- https://baiivo.com/pricing: Asking the page at /pricing for markdown still returns text/html.
- https://baiivo.com/guides: Asking the page at /guides for markdown still returns text/html.

Implement content negotiation across all public HTML routes, including page types
outside the scan's sample. Put it in the shared response handling or the handlers
for each page type, so new pages receive it too. Agents need the content of any
page they follow, including pages the report did not name.

When a request arrives with `text/markdown` in its `Accept` header, the same URL that
serves HTML to a browser should return a markdown rendering of that page's content.
Requests without that header must keep getting the HTML exactly as they do now.

The response must:

- set `Content-Type: text/markdown; charset=utf-8`;
- include `Accept` in the `Vary` header, so shared caches never serve the markdown to a
  browser or the HTML to an agent (RFC 9110 says a server SHOULD send `Vary` whenever
  the representation depends on a request header);
- contain real markdown, not HTML with a different header on it;
- drop `ETag` and `Last-Modified` for the converted response, since a conditional request
  cannot be honoured against a body generated on the fly.

Work out how to do this in whatever stack this project uses. If the site is behind
Cloudflare on a paid plan, the "Markdown for Agents" zone setting does all of the above
and is the least invasive option. Otherwise implement it in the framework: middleware
inspecting the `Accept` header, a route handler that returns the markdown source, or
whatever fits the architecture here.

Strip navigation, headers, footers and cookie banners from the markdown. The point is the
content, without the page furniture around it.

Verify HTML and Markdown responses for each public page type, including URLs
outside the reported sample. Check that each Markdown response contains that
page's content and that ordinary browser requests still receive HTML.

The whole report, as markdown, is at https://goodforbots.com/r/baiivo.com.md?scan=cmushcsz300pv01o0ns6lgzij. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

+6.3

Serve Markdown at its own URL

Only 1 markdown link in llms.txt, too few to be a convention.

Read prompt

My website baiivo.com scored 76/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: serve the content as markdown at its own URLs.

The check it only partly passes is "Serves markdown at its own URL", with 6.25 points of it still on the table. What the scanner saw: Only 1 markdown link in llms.txt, too few to be a convention.

`/llms.txt` lists a markdown mirror or two, so the mechanism works; there are not enough
of them to be a convention on this site rather than an accident. Generate a `.md`
twin for every page worth reading and list them all in the index. If the pages come from
markdown already, this is usually a matter of exposing the source rather than converting
anything.

A model that can only reach this site's content through HTML pays to parse markup and
loses structure doing it: navigation, cookie banners and script tags arrive alongside
the prose, and headings, tables and code blocks come out flattened. Markdown at its own
address removes HTML from the path entirely: what is fetched is the content and nothing
else.

Two routes satisfy this, and it is worth being clear about which one the specification
asks for. llmstxt.org asks for a markdown version of each page **at the same URL as the
original**, either with `.md` appended (`page.html.md`) or with the extension replaced
(`page.md`). `llms-full.txt`, the single bundle holding everything, does not appear in
the specification at all. It is a community convention that grew up around it and is
now widespread. Both are accepted here. The per-page form is the one the document
asks for.

Either of these passes:

- **The bundle.** `/llms-full.txt`, one document, real markdown rather than HTML,
carrying the site's actual content rather than a placeholder.
- **Per-page mirrors.** A markdown twin for each page at `page.md` or `page.html.md`,
**and linked from `/llms.txt`**. That second half is load-bearing: mirrors are counted
from the links in the index, so twins that nothing points at are invisible to this scan
and, more to the point, to anything crawling the site.

For the mirror route, the index carries them as ordinary link lines:

```markdown
## Docs

- [Quickstart](/docs/quickstart.md): create an account and take a first payment
- [Concepts](/docs/concepts.md): customers, subscriptions, invoices and proration
- [Webhooks](/docs/webhooks.md): events, signature verification, retry schedule
```

Both `/docs/quickstart` and `/docs/quickstart.md` have to answer 200: the HTML for
people, the markdown for everything else.

Serving markdown through content negotiation does **not** satisfy this, and that is
deliberate rather than an oversight. A negotiated response only exists for a client that
knows to send `Accept: text/markdown`, and most crawlers send no preference at all. A
`.md` address sits in the open: it is found by ordinary crawling, it can be linked to,
and it can be cited. If this site already negotiates markdown, the report says so in
these words: *"Markdown is served on request, but not at any URL a crawler would find on
its own"*. That is a different check passing on its own terms, not a contradiction.

Four things about how this is measured. The bundle is judged by size, by being markdown
rather than a page or JSON, and by not merely repeating `llms.txt`; its content is never
sampled beyond that, so a couple of kilobytes of boilerplate would pass. Do not take that
as permission, since the point of the file is the content in it. `.mdx` counts as markdown
although the specification names only `.md`, because excluding it would punish a large
part of the documentation ecosystem for its toolchain. The number of mirrors we want
before calling it a convention on this site is our judgement, not the specification's.
And the mirror URLs listed in the index are counted, never fetched, so a list of `.md`
addresses that 404 passes this check and helps nobody at all.

The whole report, as markdown, is at https://goodforbots.com/r/baiivo.com.md?scan=cmushcsz300pv01o0ns6lgzij. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

+3.8

Add descriptions to llms.txt

/llms.txt is partly descriptive: it has no summary blockquote under the title.

Read prompt

My website baiivo.com scored 76/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: describe the links in llms.txt and open the file with a summary.

The check it only partly passes is "llms.txt is descriptive, not a bare link list", with 3.75 points of it still on the table. What the scanner saw: /llms.txt is partly descriptive: it has no summary blockquote under the title.

The links carry notes, and the file never says what this project is. A reader arriving at
it has to infer the subject from the titles of pages it has not fetched. Add a `>`
blockquote directly beneath the H1: two or three sentences covering what this is, who it
is for, and anything needed to make sense of the sections below (a version, a scope, a
deprecation date).

A file made of `- [Docs](/docs)` and thirty more like it tells a model that this site has
pages, which it already knew. What a model needs from an index is the thing that lets it
choose: what is behind each address, and whether fetching it is worth the tokens. That is
what a note after the link does, and it is the difference between an index and a table of
contents nobody asked for.

There is nothing normative to cite here, and saying so is the honest opening move. The
llms.txt specification makes the note after a link optional and says nothing about how
many links should carry one. This is our judgement about what makes such a file
worth retrieving, and the report says as much.

The file must:

- open with a `>` blockquote summary directly under the H1, before the first `##` heading
and before the first link line. A summary written lower down is not read as the
summary, by this scan or by anything skimming the file top-down;
- give each link a `:` followed by a note, on the same line as the link;
- describe what is behind the link rather than restating its name. `Pricing: pricing`
costs a line and conveys nothing.

Before and after, on the same file:

```markdown
# Acme

## Docs

- [Quickstart](/docs/quickstart.md)
- [Concepts](/docs/concepts.md)
- [Webhooks](/docs/webhooks.md)
```

```markdown
# Acme

> Acme is a hosted billing API for subscription businesses. Everything below is written
> against the v2 API; v1 reaches end of life in March.

## Docs

- [Quickstart](/docs/quickstart.md): create an account and take a first payment in about
ten minutes, with a runnable curl example
- [Concepts](/docs/concepts.md): customers, subscriptions, invoices and proration, and
how the four objects relate
- [Webhooks](/docs/webhooks.md): the event list, signature verification, and the retry
schedule
```

The second file is not longer for the sake of it. A model reading it can answer "where do
I find the retry schedule" without fetching anything, and then fetch exactly one page.

One caution. The summary has to sit above everything else. A blockquote placed after the
first heading, or after the first link, reads as a note about that section rather than
about the project, and is not counted as the file's summary.

Two things about how this is measured, both of which are limits rather than rules. The
thresholds are ours and are judgement, not measurement (a quarter of the links carrying
a note starts earning credit, three in five passes), so treat them as a floor and write a
note wherever a reader would want one. And only the presence of a note is detected, never
its quality: `: docs` counts the same as a sentence that says something. Writing `: docs`
on every link would clear the check and defeat the purpose of doing it, since the file is
for a model and not for us.

One last thing about order. A site with no `/llms.txt` at all fails this check too, and
that is deliberate: marking it inapplicable would drop it out of the denominator and
quietly reward a site for having done nothing. If both this and the llms.txt check are
outstanding, do that one first. There is nothing to describe until the file exists.

The whole report, as markdown, is at https://goodforbots.com/r/baiivo.com.md?scan=cmushcsz300pv01o0ns6lgzij. Read it first: this prompt covers one finding, and the report has everything the scan saw.

Pro

12 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for Baiivo from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

All 35 checks

Evidence for each, in Markdown →

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

Readable base

50 / 50

3.5 of 3.5 points.

robots.txt is valid, with 13 user-agent groups.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 39 URLs.

8.8 of 8.8 points.

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

10.5 of 10.5 points.

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

4.4 of 4.4 points.

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

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

2.6 of 2.6 points.

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

1.8 of 1.8 points.

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

0.9 of 0.9 points.

3 of 4 pages read pass. The page at /pricing has 1 of 2 section links pointing at no element on the page.

Agent layer

26.3 / 50

11.3 of 11.3 points.

/llms.txt is well formed: 31 links across 5 sections.

3.8 of 7.5 points.

/llms.txt is partly descriptive: it has no summary blockquote under the title.

6.3 of 12.5 points.

Only 1 markdown link in llms.txt, too few to be a convention.

0 of 10 points.

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

5 of 5 points.

States a position on 9 AI crawlers, across 2 purposes (search, training).

0 of 2.5 points.

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

Prompt in Pro →

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.

Prompt in Pro →

Penalties

− 0

Penalty: 0 of 15 points.

Penalty: 0 of 20 points.

Penalty: 0 of 25 points.

Penalty: 0 of 10 points.

Penalty: 0 of 3 points.

Agent capabilities

0 of 10 · no points

Each one found adds +1 to the badge.

Adds +1 to the badge when found.

What we found

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

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

Passes: Homepage
The homepage marks its content root, its heading outline and its landmarks.
Passes: /cashflow-tracking-for-freelancers
The page at /cashflow-tracking-for-freelancers marks its content root, its heading outline and its landmarks.
Passes: /pricing
The page at /pricing marks its content root, its heading outline and its landmarks.
Passes: /guides
The page at /guides marks its content root, its heading outline and its landmarks.

Extracted words: 2,317
Headings: 31
H1 headings: 1

Content and navigation

Share of extracted homepage words by marked region. Navigation inside a header, footer or main region is counted once, under navigation.

Extracted words and their share by page region
Region	Words	Share
Main region	2,235	96.46%
Navigation	48	2.07%
Page header	5	0.22%
Page footer	29	1.25%
Other text	0	0%

10 words appear before the first main-region text in HTML order.

Diagnostic only; it does not affect the score. Recognised hidden text and script payloads are excluded. Stylesheet visibility and repetition across pages are unknown. A large menu is not necessarily a problem.

Heading outline · first 4

H1Run every client project from quote to paid invoice.
H2What is Baiivo?
H2One job envelope, five stations down the rail.
H3The quote sets the terms, not just the price.

27 more headings recorded

Page landmarks

banner
contentinfo
navigation
region

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "gaps": [],
  "pages": [
    {
      "url": "https://baiivo.com/",
      "reason": "structured",
      "status": "pass",
      "summary": "The homepage marks its content root, its heading outline and its landmarks.",
      "homepage": true
    },
    {
      "url": "https://baiivo.com/cashflow-tracking-for-freelancers",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /cashflow-tracking-for-freelancers marks its content root, its heading outline and its landmarks.",
      "homepage": false
    },
    {
      "url": "https://baiivo.com/pricing",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /pricing marks its content root, its heading outline and its landmarks.",
      "homepage": false
    },
    {
      "url": "https://baiivo.com/guides",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /guides marks its content root, its heading outline and its landmarks.",
      "homepage": false
    }
  ],
  "roots": [
    {
      "words": 2257,
      "source": "element",
      "hierarchicallyCorrect": true
    }
  ],
  "reason": "structured",
  "h1Count": 1,
  "headings": [
    {
      "text": "Run every client project from quote to paid invoice.",
      "empty": false,
      "level": 1
    },
    {
      "text": "What is Baiivo?",
      "empty": false,
      "level": 2
    },
    {
      "text": "One job envelope, five stations down the rail.",
      "empty": false,
      "level": 2
    },
    {
      "text": "The quote sets the terms, not just the price.",
      "empty": false,
      "level": 3
    },
    {
      "text": "The signature carries its own evidence.",
      "empty": false,
      "level": 3
    },
    {
      "text": "Clients see the gallery, never the back room.",
      "empty": false,
      "level": 3
    },
    {
      "text": "The invoice already knows the whole story.",
      "empty": false,
      "level": 3
    },
    {
      "text": "Reminders chase the invoice, then stand down.",
      "empty": false,
      "level": 3
    },
    {
      "text": "The client portal is a gallery, not your back room.",
      "empty": false,
      "level": 2
    },
    {
      "text": "The sentinel chases invoices, then stands down.",
      "empty": false,
      "level": 2
    },
    {
      "text": "The scattered bench vs the shop.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Choose the payment workflow that needs a clearer next action.",
      "empty": false,
      "level": 2
    },
    "… 19 more items"
  ],
  "bodyWords": 2339,
  "landmarks": [
    {
      "role": "banner",
      "named": false,
      "source": "native",
      "element": "header"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "contentinfo",
      "named": false,
      "source": "native",
      "element": "footer"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    }
  ],
  "textRatio": 0.0944,
  "truncated": false,
  "articleCount": 15,
  "contentWords": 2257,
  "headingCount": 31,
  "headingSkips": [],
  "requirements": {
    "landmarks": true,
    "contentRoot": true,
    "headingOutline": true
  },
  "landmarkRoles": [
    "banner",
    "contentinfo",
    "navigation",
    "region"
  ],
  "hiddenMainCount": 0,
  "textComposition": {
    "words": {
      "main": 2235,
      "other": 0,
      "footer": 29,
      "header": 5,
      "navigation": 48
    },
    "shares": {
      "main": 0.96460940871817,
      "other": 0,
      "footer": 0.012516184721622789,
      "header": 0.0021579628830384117,
      "navigation": 0.020716443677168753
    },
    "version": 1,
    "truncated": false,
    "totalWords": 2317,
    "analysisLimited": false,
    "mainRegionCount": 1,
    "wordsBeforeMain": 10
  },
  "emptyHeadingCount": 0,
  "misnestedMainCount": 0
}

Related checks

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://baiivo.com/

Declared crawling rules

robots.txt refuses this URL for some listed identities. See the affected crawlers below.

Sources and scope: declared crawling rules

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://baiivo.com/
robots.txt is present and valid
Declared allow · robots.txt
- goodforbotsbot (Site diagnostics)
- * (Default robots group)
- claude-searchbot (ai-search)
- mistralai-index (ai-search)
- kimi-searchbot (ai-search)
- amzn-searchbot (ai-search)
- meta-webindexer (ai-search)
- exasearchbot (ai-search)
- aiwebindex (ai-search)
- duckassistbot (ai-search)
- shapbot (ai-search)
- yandexadditional (ai-search)
- yandexadditionalbot (ai-search)
- mistralai-training (ai-training)
- kimibot (ai-training)
- ai2bot (Unknown)
- webzio-extended (ai-training)
- chatgpt-user (user-fetch)
- claude-user (user-fetch)
- perplexity-user (user-fetch)
- mistralai-user (user-fetch)
- kimi-user (user-fetch)
- amzn-user (user-fetch)
- diffbot-user (user-fetch)
- firecrawlagent (extraction)
- webzio (extraction)
- meta-externalfetcher (user-fetch, agent)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: *
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- oai-searchbot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: oai-searchbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- perplexitybot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: perplexitybot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- gptbot (ai-training)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: gptbot
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- claudebot (ai-training)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: claudebot
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- applebot-extended (ai-training)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: applebot-extended
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- google-extended (ai-training, grounding)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: google-extended
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- meta-externalagent (ai-training, product-improvement)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: meta-externalagent
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- amazonbot (ai-training, product-improvement)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: amazonbot
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- ccbot (open-dataset, ai-training)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: ccbot
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- googlebot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: googlebot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- bingbot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: bingbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared restriction · robots.txt
- bytespider (Unknown)
A matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://baiivo.com/
https://baiivo.com/robots.txt
```
User-agent: bytespider
disallow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access

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://baiivo.com
```
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://baiivo.com/
```
HTTP 200
Transport: direct
```
Serves the homepage over HTTPS with HTTP 200 Serves 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

4th of 34 in SaaS & Web Apps

Whole category →

1BulkSharebulkshare.cloud
2SoftSyncsoftsync.ai
4Baiivo · this reportbaiivo.com

The prompts above would take Baiivo to 96, 2nd in its category.

To the prompts ↑

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

Scanned: 3 Oct 2026
Category: SaaS & Web Apps
Tags: ProductivityB2BStartups

Site profile

Login: Detected; A sign-in or sign-up link
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.

Read this report as Markdown

Removing it is free. Remove →

Scan details

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

Scanned: 3 Oct 2026
Rubric: 0.9.0
Requests: 22
Fetched: 1.5 MB
Took: 16.5 s
Homepage: 1.5 s · 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
/cashflow-tracking-for-freelancersarticle · linked from the homepage · from the sitemap · read
/pricingpricing · linked from the homepage · from the sitemap · read
/guidescollection · linked from the homepage · from the sitemap · read

Similar reports

The whole directory →

More like Baiivo:SaaS & Web Apps Productivity B2B Startups

Good for Bots

goodforbots.com

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

Same category

Relanco

relanco.ca

Automated bilingual SMS and email payment reminders for Canadian contractors

Same category

NextFeed

nx-feed.com

Product feed management software that finds errors before channels reject them

Same category

SoftSync

softsync.ai

Flexible B2B CRM for startups with meeting notes and automated follow-ups

Same category

BulkShare

bulkshare.cloud

Branded file delivery on custom domains for agencies and freelancers

Same category

Wisegrid

wisegrid.co

Work-management spreadsheet with dashboards, automations, and in-cell AI formulas

Baiivo

Changed your site? Run a new scan.

Baiivo scores 76 of 100: the whole readable base, 26 of the 50 agent-layer points, no penalties.

Through a bot’s eyes

What a bot can read

What is Baiivo?

3 prompts, 20 points

Serve Markdown when asked for it

Serve Markdown at its own URL

Add descriptions to llms.txt

12 more prompts in Pro

Ready-made files

A ready-made llms.txt and robots.txt

All 35 checks

Who can read this page, and for what purpose?

Declared crawling rules

Observed access

Indexing directives

Search snippets

Search usage

AI input and use

AI training

4th of 34 in SaaS & Web Apps

Site profile

Scan details

Similar reports

Good for Bots

Relanco

NextFeed

SoftSync

BulkShare

Wisegrid