CrawlCheck

Directory · Model and API providers

Poe — what a crawler receives from poe.com

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

59
Fgrade

AI assistants are being shown something other than your site.

AI visibility 59/100, measured 2026-10-25 13:12 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 F A critical-severity finding sets the letter.

Open the full report poe.com ↗

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

8

findings

✗

llms.txt on its host

✗

entity map on its host

8

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.

69

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.

71

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.

32

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, the lowest of the three.

What to fix

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

1 Critical 1 High 3 Medium 3 Note

1robots.txt blocks every crawler it does not nameA User-agent: * group contains Disallow: / with no Allow overriding itCriticalSetting

What we saw

A User-agent: * group contains Disallow: / with no Allow overriding it /robots.txt

Why it matters

robots.txt instructs every crawler to stay off the entire site.

How to fix it

robots.txt disallows everything. Remove the blanket Disallow: / rule (or restrict it to the paths you actually mean).

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.

In Cloudflare (this site is behind it)

  1. If Cloudflare's managed robots.txt is on (Security → Bots, or AI Crawl Control → robots.txt), Cloudflare adds its own lines above yours. Turn it off, or keep it knowing those lines are there.
  2. Robots.txt is cached at the edge: purge it (Caching → Configuration → Custom purge → the robots.txt URL) after you change it.

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

An empty Disallow allows everything. Keep any narrower rules you meant, below the User-agent line.

User-agent: *
Disallow:

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

The whole corrected robots.txt for poe.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 poe.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 blocks every crawler it does not name (ROBOTS_DISALLOW_ALL, critical severity)
Page: https://poe.com/robots.txt
What was measured: A User-agent: * group contains Disallow: / with no Allow overriding it
Why it matters: robots.txt instructs every crawler to stay off the entire site.
How to fix it: robots.txt disallows everything. Remove the blanket Disallow: / rule (or restrict it to the paths you actually mean).
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/ROBOTS_DISALLOW_ALL
Full report (markdown): https://crawlcheck.io/r/w7bnynm3vg.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=poe.com . The fix counts when ROBOTS_DISALLOW_ALL is gone from the new report.
Why this was decided
RuleROBOTS_DISALLOW_ALL · rule pack sv34 · scope core
Evaluated2026-10-25 13:12:25 UTC
Decisiond1:9b1da6c44a182269c0ea · finding f1:ac5444787d59bf262c1b resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 0ffe94b9 from IAD · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /robots.txt20050915311f9ec76falready_held

21 more in the manifest.

Artifacts: manifest:92087af2eeccd406f314662328d800ae19582b07790df198388ffd078ba2c33d

Grade effect Caps the letter at F. Without it the letter would be D (score 59). Moves no points; the score is built from the measured rows.

Rule ROBOTS_DISALLOW_ALL under scoring rules v34 · fingerprint ROBOTS_DISALLOW_ALL|/robots.txt · persisting (9 scans)

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

ROBOTS_DISALLOW_ALL · full transcript

2No XML sitemap found🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.High
3robots.txt declares no sitemap/robots.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
4robots.txt rules do not apply to named agents/robots.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
5Almost nothing a machine receives from this page is readable text🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
6The 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
7No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
8A missing agent file answers with a full page🔒 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

The chain a crawler follows

The chain breaks at sitemap. 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 74,586 decompressed bytes the homepage delivers, 0.5% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 0.5% · 360 B
  • Markup & attributes 6.1% · 4,558 B
  • Inline CSS 77.8% · 58,023 B
  • Inline JavaScript 13.6% · 10,161 B
  • Inline SVG 1.9% · 1,450 B
  • HTML comments 0% · 34 B

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

  • Inline CSS · 58,023 B (77.8%) — unnamedopens @layer global{:root{--black:var(--neutral-12);--blue-1:#f8faff;--blue-
  • Inline JavaScript · 5,052 B (6.8%) — unnamedopens var _0x208d9b=_0x6795;(function(_0x280592,_0x54642a){var _0x236683=_0x
  • Inline JavaScript · 2,944 B (3.9%) — Google Tag Manager or gtagopens {"props":{"pageProps":{"data":{"mainQuery":{"viewer":{"uid":null,"logi
Section average over 2 scans on this score version · held at 59 since 2026-10-25
0501002026-10-24 02:05 · 59/100 · 8 findings2026-10-25 13:12 · 59/100 · 8 findings2026-10-242026-10-25

What changed

  1. 2026-10-25score moved 61 → 60score-down
  2. 2026-10-24the homepage no longer refused this clientresolved
  3. 2026-10-24the homepage read as mostly markupappeared
  4. 2026-10-12the homepage began taking more than one redirect to reachappeared

8 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 poe.com

Is this your company?

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