Skip to content
Good for Bots

Second-pass editing tool that checks existing transcripts against their audio to fix errors

Good for Bots: Fair, 55 of 100Get this badge →

On your homepage, it turns this report’s link to verbaia.com dofollow.

Scanned

What is Verbaia?

Verbaia is a second-pass editing and audio playback tool for transcripts. A user brings in their text and, where available, the matching audio, and Verbaia goes over them a second time, reading the words against the sound to catch garbled words, wrong names, numbers and other transcription errors. The homepage says it is built for content creators and lists doctors, researchers, lecturers, students and videographers among those it is for. The PC version is described as available now, and a Mac version as coming soon. The llms.txt file adds that the software runs on Windows 10 or 11 (64-bit) and is sold as a one-time purchase with no subscription, with a free 7-day trial.

Through a bot’s eyes

“Verbaia is a second-pass editing and audio playback tool that goes over an existing transcript and its matching audio a second time to catch wrong words, names and numbers, and returns a corrected text copy.”

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 a second-pass tool for correcting transcripts, the kinds of errors it catches, the accessibility reasons for accurate transcripts, a cited 2025 audit figure on transcription errors for deaf and hard-of-hearing speakers, and a list of intended users. It also states the one-time payment with no subscription, the free 7-day trial, the PC and Mac availability, and a support email address. The homepage gives no price amount and no system requirements. The llms.txt file adds those details: a $149 introductory price and a $250 list price, Windows 10 or 11 (64-bit) as the platform, trial and license terms, and links to a technical support document, a blog index and an agent purchase page. The JSON-LD blocks name the organization and website and give a one-sentence description of the product.

What stays hidden

The input does not say which audio or text file formats are accepted, how the second pass works step by step, or when the Mac version will ship, since the homepage says shipping soon and llms.txt says in test. The company behind Verbaia is not named, and no address or contact is given beyond the support email. The linked pages on how it works, the user guide and the support pages were not read, so detailed workings and trial limits are not in this input.

Good for Bots report

Verbaia scores 55 of 100: 37 of the 50 base points, 19 of the 50 agent-layer points, no penalties.

Earned

37 of the 50 base points above the line, 19 of the 50 agent-layer points below it.

55

Taken back

Earned, then taken back by penalties.

1

Still open

Behind the checks below, with prompts in Pro.

13
Penalties0
How scoring works · current methodology →

For the owner of verbaia.com

3 prompts, 31 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

36.7 / 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 25 URLs.

Fails.

0 of 8.3 points.

2 of 4 pages read pass. The page at /verbaia-download.html publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Half passes.

5 of 10 points.

2 of 4 pages read pass; 2 partly. The page at /verbaia-download.html is partly structured: No <h1>, so nothing says what the page is about.

Prompt in Pro →
Passes.

8.3 of 8.3 points.

8 of 8 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

2.5 of 2.5 points.

25 of 25 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

18.8 / 50

Passes.

11.3 of 11.3 points.

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

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

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.

Prompt in Pro →
Fails.

0 of 2.5 points.

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

Prompt in Pro →

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 459 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 127 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
Detected
A sign-in form
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://verbaia.com/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

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

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (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)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • 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)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://verbaia.com/

    https://verbaia.com/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
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

54th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 54Verbaia · this reportverbaia.com

The prompts in the owner view would take Verbaia to 86, 8th in its category.

To the prompts →

Category average 58. 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
9 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
657.2 KB
Took
16.8 s
Homepage
127 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
  • /verbaia-download.htmllinked from the homepage · from the sitemap · read
  • /verbaia-signup.htmllinked from the homepage · from the sitemap · read
  • /what-is-verbaia.htmllinked from the homepage · from the sitemap · read

Do you run verbaia.com? Open the owner view → Removing the listing is free. Remove →