Directory · Inference and GPU compute
Paperspace — what a crawler receives from paperspace.com
Website measurement, not a product review. This page records what machine clients received from paperspace.com. It does not evaluate Paperspace software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 71/100, measured 2026-10-11 20:05 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.
3
findings
✗
llms.txt on its host
✗
entity map on its host
5
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; one that cannot read it never quotes it. That is why reach is a ceiling and not just a weight.
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.
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?
An assistant would have to paraphrase your page instead of quoting a fact.
- Structured data25
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals50
- Linked datan/a
- Quotable content60
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, because the three run in order.
What to fix
3 findings on this site. 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.
3 Note
1The homepage is reached through a chain of redirectshttp://paperspace.com/ takes 2 redirects to reach the page: 301 permanent (http→https) → 301 permanent (apex→www) → https://www.paperspace.com/ (200). Point theNoteSetting
What we saw
http://paperspace.com/ takes 2 redirects to reach the page: 301 permanent (http→https) → 301 permanent (apex→www) → https://www.paperspace.com/ (200). Point the first redirect straight at the final address.
Why it matters
Reaching the homepage takes more than one redirect, for example http to https and then the domain to www. Each hop is another request and round trip before a crawler or visitor gets the page, temporary hops (302, 307) tell search engines to keep the old address, and Google stops following after ten.
How to fix it
Send every old address straight to the final one in a single permanent (301 or 308) redirect: in the host, CDN or plugin rules, redirect http://domain and http://www straight to the final https address instead of chaining scheme, host and path fixes.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | REDIRECT_CHAIN · rule pack sv31 · scope core |
|---|---|
| Evaluated | 2026-10-11 20:05:27 UTC |
| Decision | d1:8c1c70ec6f18a10f9435 · finding f1:5f6932d6ea30d7a37d79 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build a0b27a0e · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| crawlcheck | 200 | 79,634 | f1b1e10e816c | already_held |
| anon | 200 | 79,634 | f1b1e10e816c | already_held |
| gptbot | 200 | 79,634 | f1b1e10e816c | already_held |
| claudebot | 200 | 79,634 | f1b1e10e816c | already_held |
| oaisearch | 200 | 79,634 | f1b1e10e816c | already_held |
| claudesearch | 200 | 79,634 | f1b1e10e816c | already_held |
| perplexity | 200 | 79,634 | f1b1e10e816c | already_held |
| googlebot | 200 | 79,634 | f1b1e10e816c | already_held |
16 more in the manifest.
Artifacts: manifest:d0b34840e9c60c8bd465393c79da5671fe0d1b7af032bcccb3b5c8a4968e1ca5
Grade effect Does not cap the letter: only medium, high and critical findings do. Moves no points either; the score is built from the measured rows.
Rule REDIRECT_CHAIN under scoring rules v31 · fingerprint REDIRECT_CHAIN|/ · new on this scan (1 scan)
Verify the fix Re-scan after the change. This finding is cleared when REDIRECT_CHAIN is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
REDIRECT_CHAIN · full transcript
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 findingsOr 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 — $749The main product
We fix the 3 findings on paperspace.com. $749, once.
One site. You keep the grade for free — this is the part where the list stops being a list.
- Every finding implemented on the site itself: machine files, schema, NAP, the lot
- An entity map authored for your business, not a template with the name swapped
- Measured again afterwards — the before and the after, sealed, so it is evidenced rather than claimed
- Thirty days of monitoring included
- Work starts within two business days
What it covers · one payment, nothing recurring
The chain a crawler follows
The chain breaks at llms.txt. Everything after that point is only reachable by a crawler guessing the conventional path.
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 79,586 decompressed bytes the homepage delivers, 8.7% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 8.7% · 6,933 B
- Markup & attributes 74.1% · 58,995 B
- Inline CSS 2.5% · 1,993 B
- Inline JavaScript 12.6% · 10,040 B
- HTML comments 2% · 1,625 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline JavaScript · 2,110 B (2.7%) — unnamedopens
!function(){var analytics=window.analytics=window.analytics||[];if(!an - Inline JavaScript · 2,063 B (2.6%) — unnamedopens
// scrambled text snippet class TextScramble { constructor(el) { this.
What changed
- 2026-10-11the homepage began taking more than one redirect to reachappeared
- 2026-09-18a stale edge copy was servedappeared
5 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 paperspace.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If paperspace.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 “Inference and GPU compute” is our label for what the product is primarily sold as; it is not scored. Back to the directory.