CrawlCheck

Directory · Video and image generation

Playground — what a crawler receives from playground.com

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

60
Dgrade

AI assistants are being shown something other than your site.

AI visibility 60/100, measured 2026-10-19 03:02 UTC from outside its network, as each named AI and search crawler and as a browser. An engine can technically reach this site and would struggle to get anything quotable out of it.

Held at D A high-severity finding sets the letter.

Open the full report playground.com ↗

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

8

findings

✗

llms.txt on its host

✗

entity map on its host

9

scans on record since 2026-09-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.

75

Stage 1 · 40% of the score

Reach

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

At least one answer engine was refused, challenged or served less than a browser.

40

Stage 2 · 30% of the score

Read

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

The content is buried in markup, or the files that guide a crawler are missing.

—

Stage 3 · 30% of the score

Quote

Is there a specific fact it can state and attribute?

Not measured on this scan; left out rather than counted as zero.

  • Structured datan/a
  • Local presence & NAPn/a
  • Claim consistencyn/a
  • Authors & trust signalsn/a
  • Linked datan/a
  • Quotable contentn/a
  • Entity corroborationn/a
  • Page subjectn/a

The stage to fix first is read, the lowest of the three.

What to fix

8 findings on this site, 4 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.

4 High 2 Low 2 Note

1robots.txt is unreadableHTTP 403.HighSetting

What we saw

HTTP 403. /robots.txt

Why it matters

A 5xx on robots.txt tells a standards-following crawler to treat the whole site as disallowed (RFC 9309). A 401 or 403 is a 4xx, which the standard treats as no file and so allows everything, though some crawlers read it as a refusal. Either way the rules you wrote are not the rules a crawler read. This is the single most expensive file on the site to get wrong.

How to fix it

robots.txt could not be fetched. Allow it through the security layer; it is the one file every crawler reads first.

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

Site deployed from GitHub

  1. Add this workflow file as .github/workflows/crawlcheck.yml (change robots-path if robots.txt lives elsewhere).
  2. Run it from the Actions tab: it opens one pull request with the corrected robots.txt, every change listed. Review, merge, deploy.

How the action works

Paste this

A minimal valid file. Serve it at https://playground.com/robots.txt as text/plain with a 200, and let it through any bot or firewall rule (use your sitemap’s real address if it is not /sitemap.xml).

User-agent: *
Disallow:

Sitemap: https://playground.com/sitemap.xml

The whole corrected robots.txt for playground.com · 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 playground.com. 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 is unreadable (ROBOTS_BLOCKED, high severity)
Page: https://playground.com/robots.txt
What was measured: HTTP 403.
Why it matters: A 5xx on robots.txt tells a standards-following crawler to treat the whole site as disallowed (RFC 9309). A 401 or 403 is a 4xx, which the standard treats as no file and so allows everything, though some crawlers read it as a refusal. Either way the rules you wrote are not the rules a crawler read. This is the single most expensive file on the site to get wrong.
How to fix it: robots.txt could not be fetched. Allow it through the security layer; it is the one file every crawler reads first.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/ROBOTS_BLOCKED
Full report (markdown): https://crawlcheck.io/r/7eek19vgnh.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=playground.com . The fix counts when ROBOTS_BLOCKED is gone from the new report.
Why this was decided
RuleROBOTS_BLOCKED · rule pack sv32 · scope core
Evaluated2026-10-19 03:02:38 UTC
Decisiond1:ec8fac106de69d2334a9 · finding f1:8a0a21d99cc32c313414 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 6929574e · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /robots.txt403134c996c0469ef0already_held

5 more in the manifest.

Artifacts: manifest:4e86216befd2b13a771c185eefcb857a33871af521fe5c1d5753c552cc02759c

Grade effect Caps the letter at D together with 3 other high-severity findings; the letter rises only when all of them are gone. Moves no points.

Rule ROBOTS_BLOCKED under scoring rules v34 · fingerprint ROBOTS_BLOCKED|/robots.txt · new on this scan (1 scan)

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

ROBOTS_BLOCKED · full transcript

2The sitemap is refused/sitemap.xml🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.High
3The sitemap is refused/sitemap_index.xml🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.High
4The sitemap is refused/wp-sitemap.xml🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.High
5The site refuses plain automated requests; it was measured through a real browser🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Low
6Whether a sitemap exists could not be determined — every path was refused🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Low
7No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
8HTTPS is served without a Strict-Transport-Security header🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 7

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, $100 once.

Get this fixed — $100

What changed

  1. 2026-10-19resolved: the homepage and robots.txt both refused this client, so the site was never measuredresolved
  2. 2026-10-19a new finding appeared: whether a sitemap exists could not be determined — every path was refusedappeared
  3. 2026-10-19a new finding appeared: the sitemap is refusedappeared
  4. 2026-10-19a new finding appeared: the site refuses plain automated requests; it was measured through a real browserappeared
  5. 2026-10-19a new finding appeared: robots.txt is unreadableappeared
  6. 2026-10-19no llms.txt was foundappeared
  7. 2026-10-19a new finding appeared: https is served without a strict-transport-security headerappeared
  8. 2026-10-18the homepage no longer redirected off its own hostresolved
  9. 2026-10-18resolved: this domain is an alias: every path redirects to another siteresolved
  10. 2026-10-18a new finding appeared: the homepage and robots.txt both refused this client, so the site was never measuredappeared
  11. 2026-10-04resolved: this origin refused crawlcheck, so the site was never measuredresolved
  12. 2026-10-04the homepage redirected off its own host againreturned

9 scans on record, first 2026-09-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 playground.com

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If playground.com 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 “Video and image generation” is our label for what the product is primarily sold as; it is not scored. Back to the directory.