Directory · Inference and GPU compute

Baseten — what a crawler receives from baseten.co

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

Cgrade

AI assistants like ChatGPT can read your site, but find little to quote about your product.

AI visibility 76/100, measured 2026-10-26 13:35 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 baseten.co ↗

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

findings

✓

llms.txt on its host

✗

entity map on its host

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.

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.

What each crawler gets100
Crawler permissions100
Machine-file chain71
Speed78
Server & hosting100
Internal links80
Mobile100
exposure100

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.

Page weight & text20
Machine files60
Sitemap83
Crawl waste100
Accessibility structure90
Image signals60
Instructions for agents100
URL naming100
errpages67

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 data50
Local presence & NAPn/a
Claim consistencyn/a
Authors & trust signals50
Linked datan/a
Quotable content67
Entity corroborationn/a
Page subjectn/a

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

What to fix

7 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 Low 4 Note

1The homepage depends on files this site's own robots.txt disallows46 render resources referenced by the homepage are disallowed to every crawler by this site's own robots.txt: /_next/static/css/75e3f2fdd99f66d9.css (/_next/), MediumSetting

What we saw

46 render resources referenced by the homepage are disallowed to every crawler by this site's own robots.txt: /_next/static/css/75e3f2fdd99f66d9.css (/_next/), /_next/static/css/0f041f2cae6d6ac2.css (/_next/), /_next/static/css/3f611c6be6f58721.css (/_next/), /_next/static/css/734bc25898615c74.css (/_next/). A crawler that obeys robots.txt will not fetch these, so it renders the page without them. /robots.txt

Why it matters

Googlebot renders pages, and a stylesheet or script it is forbidden to fetch is rendered without. Layout, visibility and any content a script inserts are then judged from a page the site never intended to show. Only rules in the * group count here - a rule aimed at one named crawler is a narrower question.

How to fix it

Allow crawlers to fetch the CSS and JavaScript the page depends on. Remove the Disallow rules covering those paths, or serve the content without them.

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

On Next.js (detected)

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/.
Ship one of the two, not both: the route handler and a public/robots.txt collide.

All Next.js fixes

Site deployed from GitHub

Add this workflow file as .github/workflows/crawlcheck.yml (change robots-path if robots.txt lives elsewhere).
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

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 baseten.co. 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: The homepage depends on files this site's own robots.txt disallows (RENDER_RESOURCE_BLOCKED, medium severity)
Page: https://baseten.co/robots.txt
What was measured: 46 render resources referenced by the homepage are disallowed to every crawler by this site's own robots.txt: /_next/static/css/75e3f2fdd99f66d9.css (/_next/), /_next/static/css/0f041f2cae6d6ac2.css (/_next/), /_next/static/css/3f611c6be6f58721.css (/_next/), /_next/static/css/734bc25898615c74.css (/_next/). A crawler that obeys robots.txt will not fetch these, so it renders the page without them.
Why it matters: Googlebot renders pages, and a stylesheet or script it is forbidden to fetch is rendered without. Layout, visibility and any content a script inserts are then judged from a page the site never intended to show. Only rules in the * group count here - a rule aimed at one named crawler is a narrower question.
How to fix it: Allow crawlers to fetch the CSS and JavaScript the page depends on. Remove the Disallow rules covering those paths, or serve the content without them.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/RENDER_RESOURCE_BLOCKED
Full report (markdown): https://crawlcheck.io/r/5nkh5k62cm.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=baseten.co . The fix counts when RENDER_RESOURCE_BLOCKED is gone from the new report.

Why this was decided

Rule	`RENDER_RESOURCE_BLOCKED` · rule pack `sv34` · scope route
Evaluated	2026-10-26 13:35:58 UTC
Decision	`d1:b98192545a6a43924adb` · finding `f1:6c9bde7869f0394995e4` resolve either at `/api/graph/<id>` with a key
Observer	crawlcheck-worker build `2144844c` from SIN · audit v4

What it rests on

Identity	Status	Bytes	sha256	Kept
read: /	200	471,257	`10ea0ef5350e`	write_unconfirmed
read: /robots.txt	200	140	`bc7a1a0739d8`	already_held

22 more in the manifest.

Artifacts: manifest:0f7693bb75bd2cebb5ae559ea24883207a54f2d348011bc4ec4a265e754c6e34

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 RENDER_RESOURCE_BLOCKED under scoring rules v34 · fingerprint RENDER_RESOURCE_BLOCKED|/robots.txt · persisting (9 scans)

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

RENDER_RESOURCE_BLOCKED · full transcript

2Almost 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

3robots.txt keeps Google's image crawler off the site's images/_next/image/🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Low

4The 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

5Images are not the format their file names say🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

6A 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

7Visitors and crawlers are being served an old copy of this page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 6

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 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 471,217 decompressed bytes the homepage delivers, 1.8% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

Readable text 1.8% · 8,288 B
Markup & attributes 40% · 188,617 B
Inline JavaScript 49.4% · 232,604 B
Inline SVG 8.7% · 41,124 B
HTML comments 0.1% · 584 B

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

Inline JavaScript · 29,840 B (6.3%) — unnamedopens self.__next_f.push([1,"f:[\"$\",\"$L55\",null,{\"isDraftModeEnabled\":
Inline JavaScript · 21,289 B (4.5%) — unnamedopens self.__next_f.push([1,"57:[\"$\",\"section\",null,{\"ref\":\"$undefine
Inline JavaScript · 15,100 B (3.2%) — unnamedopens self.__next_f.push([1,"63:[\"$\",\"section\",null,{\"ref\":\"$undefine
Inline JavaScript · 13,151 B (2.8%) — unnamedopens self.__next_f.push([1,"6f:[\"$\",\"$1\",\"H0lQ-saLQdKKdE5dV5Taaw\",{\"
Inline JavaScript · 10,648 B (2.3%) — unnamedopens self.__next_f.push([1,"6c:[\"$\",\"$1\",\"KnYC6gWtS_qSTI_yIND_Hw\",{\"

What changed

2026-10-22score moved 77 → 78score-up
2026-10-15a stale edge copy was served againreturned
2026-10-15the homepage began taking more than one redirect to reachappeared
2026-10-15homepage images stopped matching their file namesappeared
2026-10-15robots.txt began keeping Googlebot-Image off homepage imagesappeared
2026-10-06the stale edge copy clearedresolved
2026-10-02score moved 76 → 77score-up

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 baseten.co

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If baseten.co 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.