CrawlCheck

Directory · AI security and governance

Protect AI — what a crawler receives from protectai.com

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

67
Dgrade

AI assistants are being shown something other than your site.

AI visibility 67/100, measured 2026-10-27 10:34 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 protectai.com ↗

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

9

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.

79

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.

64

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.

54

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

9 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 High 4 Medium 4 Note

1No XML sitemap foundNo sitemap at any conventional path and none declared.HighDeveloper

What we saw

No sitemap at any conventional path and none declared.

Why it matters

Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.

How to fix it

Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.

Developer: a template, theme or application change — a developer touches it

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 protectai.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: No XML sitemap found (NO_SITEMAP_FOUND, high severity)
Page: https://protectai.com/
What was measured: No sitemap at any conventional path and none declared.
Why it matters: Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.
How to fix it: Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.

Rule and examples: https://crawlcheck.io/rules/NO_SITEMAP_FOUND
Full report (markdown): https://crawlcheck.io/r/gabvrvc6nk.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=protectai.com . The fix counts when NO_SITEMAP_FOUND is gone from the new report.
Why this was decided
RuleNO_SITEMAP_FOUND · rule pack sv34 · scope core
Evaluated2026-10-27 10:34:21 UTC
Decisiond1:b0c21de3f9414e7834db · finding f1:caa3f274d67494f735e3 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build c1d5ec39 · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /sitemap.xml404288,502ebc01b31df86kept
read: /sitemap_index.xml404288,502ebc01b31df86kept
read: /wp-sitemap.xml404288,502ebc01b31df86kept

19 more in the manifest.

Artifacts: manifest:19c317790b70e5af23697b089081fb0c02ee7eba8b1a5289cd846b422a741d6b

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

Rule NO_SITEMAP_FOUND under scoring rules v34 · fingerprint NO_SITEMAP_FOUND|/ · persisting (8 scans)

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

NO_SITEMAP_FOUND · full transcript

2robots.txt does not return 200/robots.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
3The homepage sends crawlers to a different hostname🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
4Almost 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
5The page’s content only exists after JavaScript runs🔒 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
7Images 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
8No llms.txt/llms.txt🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
9A 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 8

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 robots.txt. 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 1,524,752 decompressed bytes the homepage delivers, 0.6% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 0.6% · 9,662 B
  • Markup & attributes 4.7% · 72,348 B
  • Inline CSS 22.7% · 346,266 B
  • Inline JavaScript 71.2% · 1,086,041 B
  • Inline SVG 0.2% · 2,825 B
  • HTML comments 0.5% · 7,610 B

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

  • Inline JavaScript · 882,515 B (57.9%) — jQueryopens /* JavaScript Cookie v2.2.1 https://github.com/js-cookie/js-cookie Cop
  • Inline CSS · 307,266 B (20.2%) — unnamedopens \s*$/g;d.extend({htmlPrefilter:function(a){return a},clone:function(a,
  • Inline JavaScript · 93,959 B (6.2%) — jQueryopens /* jQuery v3.6.1 | (c) OpenJS Foundation and other contributors | jque
  • Inline JavaScript · 79,181 B (5.2%) — Google Tag Manager or gtagopens /* Video & Asset loader */ let compGatedModalForm = document.querySele
  • Inline CSS · 38,405 B (2.5%) — unnamedopens .coveo-visible-to-screen-reader-only { position: absolute; left: -1000

What changed

  1. 2026-10-17homepage images stopped matching their file namesappeared
  2. 2026-10-17a new finding appeared: the page’s content only exists after javascript runsappeared
  3. 2026-10-12the homepage began taking more than one redirect to reachappeared
  4. 2026-09-27robots.txt named a sitemapresolved
  5. 2026-09-27robots.txt no longer returned HTMLresolved
  6. 2026-09-27resolved: www and the apex both serve the site instead of one redirectingresolved
  7. 2026-09-27a new finding appeared: robots.txt does not return 200 againreturned
  8. 2026-09-27the homepage redirected off its own host againreturned
  9. 2026-09-22the homepage no longer redirected off its own hostresolved
  10. 2026-09-22resolved: this domain is an alias: every path redirects to another siteresolved
  11. 2026-09-22robots.txt no longer named a sitemapappeared
  12. 2026-09-22robots.txt returned HTMLappeared

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

Is this your company?

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