CrawlCheck

Directory · Inference and GPU compute

Scaleway — what a crawler receives from scaleway.com

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

64
Dgrade

AI assistants are being shown something other than your site.

AI visibility 64/100, measured 2026-11-01 02:04 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 scaleway.com ↗

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

5

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.

67

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.

60

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

5 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 High 1 Low 2 Note

1The sitemap is refusedHTTP 403, 2,183 bytes.HighSetting

What we saw

HTTP 403, 2,183 bytes. /sitemap_index.xml

Why it matters

SAME LIMIT AS ABOVE: if a named application firewall appears in the response, this may be blocking CrawlCheck's IP rather than crawlers. Confirm in server logs grouped by source IP. Otherwise: the server refuses this sitemap rather than returning it or a clean 404. Crawlers cannot enumerate the site and fall back to link-following, so deep and newly published pages go undiscovered.

How to fix it

Allow the sitemap URL through the security layer so crawlers can read it.

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

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 scaleway.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: The sitemap is refused (SITEMAP_BLOCKED, high severity)
Page: https://scaleway.com/sitemap_index.xml
What was measured: HTTP 403, 2,183 bytes.
Why it matters: SAME LIMIT AS ABOVE: if a named application firewall appears in the response, this may be blocking CrawlCheck's IP rather than crawlers. Confirm in server logs grouped by source IP. Otherwise: the server refuses this sitemap rather than returning it or a clean 404. Crawlers cannot enumerate the site and fall back to link-following, so deep and newly published pages go undiscovered.
How to fix it: Allow the sitemap URL through the security layer so crawlers can read it.
Detected platform: Next.js. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/SITEMAP_BLOCKED
Full report (markdown): https://crawlcheck.io/r/y856mydfl6.md

Evidence (bytes the crawler received):
```
<!DOCTYPE html>
<html>
<head>
    <title>Establishing a secure connection ...</title>
    <meta name="viewport" content="width=device-width, initial-scale=0.8">
    <link href="/.bunny-shield/assets/challenge-styles.css" rel="stylesheet" />
    <script src="/.bunny-shield/assets/shield-challenge.js"></script>
    <style>
        * { margin: 0; padding: 0; box-sizing: border-box; }
        html, body { width: 100%; height: 100%; overflow: hidden; display: flex; flex-direction: column; font-family: Inter, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif; }
        iframe { flex: 1; widt
```

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=scaleway.com . The fix counts when SITEMAP_BLOCKED is gone from the new report.
Why this was decided
RuleSITEMAP_BLOCKED · rule pack sv34 · scope core
Evaluated2026-11-01 02:04:36 UTC
Decisiond1:6736830833a552a8e52a · finding f1:37da7df292651694b93c resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build f2e0ba88 from LAX · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /sitemap.xml2000—no_body
read: /sitemap_index.xml4032,183fe7499d8971akept
read: /wp-sitemap.xml4032,183f6d9eeaeedafkept

3 more in the manifest.

Artifacts: manifest:ff49c7e74bb1746aec5840f31e8825a574d7f56b67d13124eed47da8419482aa

Evidence bytes
<!DOCTYPE html>
<html>
<head>
    <title>Establishing a secure connection ...</title>
    <meta name="viewport" content="width=device-width, initial-scale=0.8">
    <link href="/.bunny-shield/assets/challenge-styles.css" rel="stylesheet" />
    <script src="/.bunny-shield/assets/shield-challenge.js"></script>
    <style>
        * { margin: 0; padding: 0; box-sizing: border-box; }
        html, body { width: 100%; height: 100%; overflow: hidden; display: flex; flex-direction: column; font-family: Inter, -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif; }
        iframe { flex: 1; widt

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

Rule SITEMAP_BLOCKED under scoring rules v34 · fingerprint SITEMAP_BLOCKED|/sitemap_index.xml · new on this scan (1 scan)

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

SITEMAP_BLOCKED · full transcript

2The sitemap is refused/wp-sitemap.xml🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.High
3The 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
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
5No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 4

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
Section average over 2 scans on this score version · held at 64 since 2026-11-01
0501002026-10-24 16:05 · 86/100 · 4 findings2026-11-01 02:04 · 64/100 · 5 findings2026-10-242026-11-01

What changed

  1. 2026-11-01score moved 84 → 67score-down
  2. 2026-11-01the homepage no longer read as mostly markupresolved
  3. 2026-11-01resolved: the machine files cost more than the pageresolved
  4. 2026-11-01a new finding appeared: the sitemap is refusedappeared
  5. 2026-11-01a new finding appeared: the site refuses plain automated requests; it was measured through a real browserappeared
  6. 2026-10-12the homepage began taking more than one redirect to reachappeared

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 scaleway.com

Is this your company?

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