CrawlCheck

Directory · Content and GEO

Frase — what a crawler receives from frase.io

Website measurement, not a product review. This page records what machine clients received from frase.io. It does not evaluate Frase software, features, pricing or support.

79
Cgrade

Answer engines can reach and read this site. It needs more it can quote.

AI visibility 79/100, measured 2026-10-15 04:05 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can reach and read this site. What is left is giving it something specific to say.

Held at C A medium-severity finding sets the letter.

Open the full report frase.io ↗

931. ReachCan a named answer-engine crawler get your pages at all?852. ReadOnce it has the bytes, can it find the words?543. QuoteIs there a specific fact it can state and attribute?

3

findings

✓

llms.txt on its host

✗

entity map on its host

17

scans on record since 2026-08-18

The three stages, in the order an engine hits a site

Each stage gates the next: an engine that cannot reach a page never reads it, and one that cannot read it never quotes it.

93

Stage 1 · 40% of the score

Reach

Can a named answer-engine crawler get your pages at all?

Every named crawler was served the same page a browser gets.

85

Stage 2 · 30% of the score

Read

Once it has the bytes, can it find the words?

The delivered HTML is mostly content, and the machine files point at the rest.

54

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

An assistant would have to paraphrase your page instead of quoting a fact.

The stage to fix first is quote, because the three run in order.

What to fix

3 findings on this site, 2 of them scored serious. Every one is named below; the top one is shown in full, free. What we saw, why each matters, how to fix it and the bytes behind it are what a licence buys — or we implement the whole list for you.

2 Medium 1 Note

1robots.txt rules do not apply to named agents11 named User-agent groups (11 agents) do not repeat 1 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignoresMediumSetting

What we saw

11 named User-agent groups (11 agents) do not repeat 1 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `*` entirely, so those rules do not apply to any of the named agents. Worst group: `gptbot` bypasses /sentry-test. This includes a SEARCH crawler (applebot-extended) — the bypassed paths are being crawled and can enter the index. /robots.txt

Why it matters

A crawler reads only the User-agent group that matches it best and ignores every other group, including `*`. Naming an agent and giving it only `Allow: /` therefore deletes all of your `*` Disallow rules for that agent. The file still parses and the agent still reaches your homepage, so this is invisible on inspection — but the paths you meant to keep out of search are open, and search engines will crawl and may index them.

How to fix it

Every User-agent group that names a crawler must repeat the Disallow rules you want applied. A named group with no rules means 'allow everything' for that crawler.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

On Next.js (detected)

  1. App Router: add app/robots.ts that returns a MetadataRoute.Robots object (rules per userAgent, sitemap URL). Pages Router or static export: put robots.txt in public/.
  2. Ship one of the two, not both: the route handler and a public/robots.txt collide.

All Next.js fixes

Paste this

Each crawler obeys only its own group, so a named group must repeat the rules you want. The corrected file below copies them in for you.

The whole corrected robots.txt for www.frase.io · built from the live file, every change listed at the top.

Fix it with a coding agent

Paste into Claude Code, Cursor or Codex, opened on the code that serves this site.

Show prompt
You are working in the codebase (or server/CDN configuration) that serves frase.io. A crawler audit found the problem below. Fix it at the source, keep the change as small as possible, and do not change anything a visitor sees unless the fix requires it.

Finding: robots.txt rules do not apply to named agents (ROBOTS_RULES_SHADOWED, medium severity)
Page: https://frase.io/robots.txt
What was measured: 11 named User-agent groups (11 agents) do not repeat 1 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `*` entirely, so those rules do not apply to any of the named agents. Worst group: `gptbot` bypasses /sentry-test. This includes a SEARCH crawler (applebot-extended) — the bypassed paths are being crawled and can enter the index.
Why it matters: A crawler reads only the User-agent group that matches it best and ignores every other group, including `*`. Naming an agent and giving it only `Allow: /` therefore deletes all of your `*` Disallow rules for that agent. The file still parses and the agent still reaches your homepage, so this is invisible on inspection — but the paths you meant to keep out of search are open, and search engines will crawl and may index them.
How to fix it: Every User-agent group that names a crawler must repeat the Disallow rules you want applied. A named group with no rules means 'allow everything' for that crawler.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/ROBOTS_RULES_SHADOWED
Full report (markdown): https://crawlcheck.io/r/0c46m79vqr.md

When you are done:
1. Tell me which files or settings you changed and why.
2. If the fix is a server, CDN or cache setting you cannot change from the code, say exactly where it is set.
3. After deploying, re-scan at https://crawlcheck.io/?url=frase.io . The fix counts when ROBOTS_RULES_SHADOWED is gone from the new report.
Why this was decided
RuleROBOTS_RULES_SHADOWED · rule pack sv32 · scope core
Evaluated2026-10-15 04:05:31 UTC
Decisiond1:f7c828b795cf7fd5a02a · finding f1:c36e21234c44583fe5e3 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 1c06d410 · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /robots.txt2001,14422464f905885already_held

25 more in the manifest.

Artifacts: manifest:2cd09f5e7b3b85bd86917b0783629697dd251250bb76905d639717465257bb3a

Grade effect Caps the letter at C together with 1 other medium-severity finding; the letter rises only when all of them are gone. Moves no points.

Rule ROBOTS_RULES_SHADOWED under scoring rules v32 · fingerprint ROBOTS_RULES_SHADOWED|/robots.txt · persisting (24 scans)

Verify the fix Re-scan after the change. This finding is cleared when ROBOTS_RULES_SHADOWED is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.

ROBOTS_RULES_SHADOWED · full transcript

2Two business records on this page claim the same identity🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
3The homepage is reached through a chain of redirects🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 2

What we saw, why it matters, how to fix it, and the evidence bytes for every finding — on this report and every re-scan. From $29 a month.

Unlock the findings

Or have them fixed

We implement the list on your site and re-measure, with a sealed before and after. One site, $749 once.

Get this fixed — $749

The chain a crawler follows

The chain breaks at entity graph. Everything after that point is only reachable by a crawler guessing the conventional path.

✓robots.txtEvery crawler reads this first
✓sitemapNamed in robots.txt and resolves
✓llms.txtPoints onward, links stay on this host
✗entity graphParses as JSON and points home

A machine file that does not parse is worth less than one that is absent, because it looks present. Rows behind this.

Where the bytes go

Of the 172,463 decompressed bytes the homepage delivers, 7.9% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 7.9% · 13,680 B
  • Markup & attributes 49.1% · 84,650 B
  • Structured data (JSON-LD) 3.1% · 5,354 B
  • Inline JavaScript 34% · 58,703 B
  • Inline SVG 5.7% · 9,784 B
  • HTML comments 0.2% · 292 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline JavaScript · 5,606 B (3.3%) — unnamedopens self.__next_f.push([1,"0:{\"P\":null,\"b\":\"PoHpDp1O6n3lGmLrj3orT\",\
  • Inline JavaScript · 4,808 B (2.8%) — unnamedopens self.__next_f.push([1,"e:[\"$\",\"div\",null,{\"data-home-v3\":true,\"
  • Inline JavaScript · 4,618 B (2.7%) — unnamedopens self.__next_f.push([1,"39:[\"$\",\"div\",null,{\"className\":\"lg:col-
  • Inline JavaScript · 4,494 B (2.6%) — unnamedopens self.__next_f.push([1,"21:[\"$\",\"section\",null,{\"id\":\"$undefined
  • Inline JavaScript · 4,376 B (2.5%) — Shopify runtimeopens self.__next_f.push([1,"37:[\"$\",\"$L34\",null,{\"delay\":0.3,\"childr

What changed

  1. 2026-10-15the homepage began taking more than one redirect to reachappeared
  2. 2026-10-02score moved 78 → 79score-up
  3. 2026-09-08score moved 82 → 83score-up
  4. 2026-09-01a named-agent group shadowed the wildcard rulesappeared
  5. 2026-09-01two schema nodes shared one identifierappeared

17 scans on record, first 2026-08-18. Score movements are shown only between readings taken under the same score version; finding codes are comparable across all of them.

Is this your site?

This listing reads the public record. Claim it and Watch keeps that record on your terms: every list this page holds back, finding age, and twice-daily re-measurement. Free for 30 days, no card.

Claim the record for frase.io

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If frase.io is yours you can prove it in a minute and for nothing — a DNS TXT record or one meta tag on the home page, both checkable by anyone.

Claiming marks you as the verified owner and lets you correct the category and the company name. It moves no score, no rank and no position.

Claim this listing — free or ask about a verified profile

Dispute or re-scan

If a reading here is wrong, it is our instrument that is wrong, and we want to know. Tell us what is wrong and the site is re-measured; the result is published as measured. Nothing about a listing, a payment or a request changes a number.

By email instead: hello@crawlcheck.io. Category “Content and GEO” is our label for what the product is primarily sold as; it is not scored. Back to the directory.