Skip to content
Good for Bots

LyricFast

lyricfast.com

AI tool that times lyrics to a song and exports lyric videos for YouTube and TikTok

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

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

Scanned

What is LyricFast?

LyricFast is a web tool for making lyric videos from finished songs, named as LyricFast in the page title, the structured data and the llms.txt title. The homepage says it is for musicians and creators who have a track and want a video for YouTube, TikTok or Instagram-style feeds. A user uploads an MP3, WAV, M4A, OGG or FLAC file, optionally pastes original lyrics, and receives AI-timed word-level lyrics. The user can listen, correct uncertain words, preview the full song in the browser, choose a visual style and aspect ratio, then export a 1080p MP4 using credits.

Through a bot’s eyes

“LyricFast is an AI lyric video maker that times lyrics to an uploaded song, lets users correct words and preview the full track, and exports videos for YouTube, TikTok and other platforms.”

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 the lyric video workflow: uploading songs, AI word timing, correcting lyrics, previewing the full track, visual styles such as Film Lyrics, the 16:9, 9:16 and 1:1 ratios, and a page on Suno-made songs. Pricing appears as text: 10 credits per video minute, $9 for 100 credits, $24 for 300, and $19 per month for 600 per Creator period. The homepage also states that uploading and full-song preview are free, that sign-in is needed to upload, and that failed renders use no credits. Several linked pages on lyric animation, transcription, guides and comparisons are named. The llms.txt file, which was provided, describes pricing differently: $12 per song, a Creator plan at $19 per month for 20 songs, a free tier at 720p with a watermark, and SRT export for unlocked projects. No Markdown version was provided. The JSON-LD block contains only the name and URL.

What stays hidden

A model reading only this input cannot tell which pricing description is current, since the homepage and llms.txt give different plans and units. It cannot confirm whether a free export at 720p with a watermark exists, because only the llms.txt mentions it. The input gives no company name, contact address or support channel, and no detail on who operates the service or where it is based.

Good for Bots report

LyricFast scores 45 of 100: 39 of the 50 base points, 6 of the 50 agent-layer points, no penalties.

Earned

39 of the 50 base points above the line, 6 of the 50 agent-layer points below it.

45

Still open

Behind the checks below, with prompts in Pro.

24
Penalties0
How scoring works · current methodology →

For the owner of lyricfast.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

39.2 / 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 26 URLs.

Fails.

0 of 8.3 points.

1 of 4 pages read pass. The page at /guides/best-lyric-video-maker publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

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.

18 of 18 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Fails.

0 of 2.5 points.

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

Prompt in Pro →
Passes.

2.5 of 2.5 points.

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

5.6 / 50

Half passes.

5.6 of 11.3 points.

/llms.txt has a title but lists no links to follow.

Prompt in Pro →
Fails.

0 of 7.5 points.

/llms.txt lists no links, so there is nothing to describe.

Prompt in Pro →
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 1022 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 202 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://lyricfast.com/

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

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

    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

50th of 60 in AI Products & Agents

  1. 1Pixelropepixelrope.com
  2. 2Contents Pilotcontentspilot.com
  3. 50LyricFast · this reportlyricfast.com

The prompts in the owner view would take LyricFast to 76, 15th in its category.

To the prompts →

Category average 62. 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
16 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
1.9 MB
Took
16.3 s
Homepage
202 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
  • /guides/best-lyric-video-makerarticle · 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

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