Same category
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Chrome extension to control YouTube captions and detect burned-in subtitles
subtitle.im is a Chrome browser extension designed for desktop YouTube users who want to control video captions automatically. The extension detects burned-in subtitles locally using optical character recognition and manages switchable YouTube captions based on user preferences. It offers global settings alongside channel and video rules to automatically open, close, or follow YouTube captions, and provides handling options when burned-in subtitles and switchable captions appear in different languages. The tool is available with a free tier covering a limited number of successful video handling instances, as well as paid annual and lifetime Pro subscriptions.
“subtitle.im is a Chrome extension that automatically controls YouTube captions and detects local burned-in subtitles.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
The input provides detailed homepage text and an llms.txt file covering the product features, installation context, privacy practices, and pricing plans. A language model reading the text learns how the extension detects burned-in subtitles locally without uploading video frames, how caption controls operate at global, channel, and video levels, and how different language conflicts are resolved. The homepage explicitly details pricing, offering a free tier with ten successfully handled videos, a Pro annual subscription priced at seventeen dollars and ninety-nine cents per year, and a Pro Lifetime option priced at twenty-nine dollars and ninety-nine cents. It also outlines clear documentation references through the llms.txt file, detailing links to setup guides, FAQs, privacy policies, terms of service, and translated versions. Visitor questions regarding allowances, refunds, and manual overrides are comprehensively answered in the text.
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 72 URLs.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 5 of 5 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 190 of 190 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 199 of 200 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 2 section links, and every one reaches an element on the page.
Describes itself to machines with schema.org JSON-LD. 1 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa. +8.3 with its prompt.
llms.txt is present and well formed. /llms.txt is well formed: 13 links across 2 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is partly descriptive: only 38% of links carry a description. +3.8 with its prompt in Pro.
Serves markdown at its own URL. llms.txt points at 5 markdown versions of pages.
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 in Pro.
Advertises machine-readable resources with typed links. 2 of 4 pages read pass. The page at /blog/smart-auto-toggle-youtube-subtitles/'s links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
40 of the 50 base points above the line, 28 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 subtitle.im
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
40.4 / 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 72 URLs.
0 of 8.3 points.
1 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.2 of 4.2 points.
190 of 190 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
1.3 of 2.5 points.
199 of 200 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 2 section links, and every one reaches an element on the page.
Agent layer
27.5 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 13 links across 2 sections.
3.8 of 7.5 points.
/llms.txt is partly descriptive: only 38% of links carry a description.
12.5 of 12.5 points.
llms.txt points at 5 markdown versions of pages.
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.
2 of 4 pages read pass. The page at /blog/smart-auto-toggle-youtube-subtitles/'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 1171 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 111 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://subtitle.im/
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://subtitle.im/
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://subtitle.im/
https://subtitle.im/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://subtitle.im
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://subtitle.im/
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://subtitle.im/
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://subtitle.im/
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://subtitle.im/
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://subtitle.im/
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://subtitle.im/
In its category
The prompts in the owner view would take subtitle.im to 91, 4th in its category.
To the prompts →Category average 63. 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 subtitle.im:Developer Tools & APIsProductivityWeb DevelopmentFreemium
Same category
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Same category
ihateimg.cv
Free browser-based image conversion, compression, and editing tools with zero server uploads
Same category
sshflow.com
SSH client built for developers providing workspaces for terminals, SFTP, and code editing
Same category
timestamp.rocks
Free tool to generate localized Discord timestamp codes and manage timezones
Same category
emailyy.online
Free browser-based email tools for signatures, subject lines, HTML previews, and header analysis
Same category
burntop.dev
Full-stack template with strict end-to-end tests for AI coding agents
Do you run subtitle.im? Open the owner view → Removing the listing is free. Remove →