CrawlCheck

Directory · Agent and orchestration frameworks

AutoGPT — what a crawler receives from autogpt.net

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

87
Agrade

Answer engines can reach and read this site. It needs more it can quote.

AI visibility 87/100, measured 2026-10-06 02:17 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.

Open the full report autogpt.net ↗

2

findings

✓

llms.txt on its host

✗

entity map on its host

4

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.

92

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.

80

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, because the three run in order.

What to fix

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

2 Note

1HTTPS is served without a Strict-Transport-Security headerThe homepage answered over HTTPS (200) with no Strict-Transport-Security header.NoteSetting

What we saw

The homepage answered over HTTPS (200) with no Strict-Transport-Security header.

Why it matters

Strict-Transport-Security tells a browser that has visited once to use HTTPS for every later request without trying HTTP first. Without it, a typed or linked http:// address makes one plaintext request before the redirect. It does not change what crawlers receive or how the site ranks; it is a small, reversible hardening step, and it is listed at the lowest severity for that reason.

How to fix it

Send Strict-Transport-Security: max-age=15552000; includeSubDomains on HTTPS responses (Cloudflare: SSL/TLS, Edge Certificates, HSTS). Leave preload off unless you intend a change that takes months to undo.

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

Why this was decided
RuleHSTS_MISSING · rule pack sv27 · scope core
Evaluated2026-10-06 02:17:38 UTC
Decisiond1:9a4f9c6338ac65bcfb56 · finding f1:96362122116393b286ff resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 71386c1f · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /200541,591185bb35b9317kept

5 more in the manifest.

Artifacts: manifest:294d6626a4ac9571a35e43facca0efa8ecdaa97e02f9e75bc854433260984685

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 HSTS_MISSING under scoring rules v28 · fingerprint HSTS_MISSING|/ · persisting (5 scans)

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

HSTS_MISSING · full transcript

2The machine files cost more than the page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 1

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

Get this fixed — $749

What changed

No change recorded between the readings on file yet.

4 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 autogpt.net

Is this your company?

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