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.
Answer engines are being served something other than this site.
AI visibility 62/100, measured 2026-10-12 02: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.
Held at D A high-severity finding sets the letter.
7
findings
✗
llms.txt on its host
✗
entity map on its host
7
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?
At least one answer engine was refused, challenged or served less than a browser.
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 data63
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals50
- Linked datan/a
- Quotable content40
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, because the three run in order.
What to fix
7 findings on this site, 4 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 3 Medium 3 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
Why this was decided
| Rule | NO_SITEMAP_FOUND · rule pack sv31 · scope core |
|---|---|
| Evaluated | 2026-10-12 02:05:18 UTC |
| Decision | d1:87459862a19d27daaf59 · finding f1:caa3f274d67494f735e3 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 |
|---|---|---|---|---|
| read: /sitemap.xml | 404 | 254,449 | ba7993cf3321 | already_held |
| read: /sitemap_index.xml | 404 | 254,449 | ba7993cf3321 | already_held |
| read: /wp-sitemap.xml | 404 | 254,449 | ba7993cf3321 | already_held |
19 more in the manifest.
Artifacts: manifest:89794071b5faa15b76170408fc86db7b984127d9606e48472c807d6bea53503a
Grade effect Caps the letter at D. Without it the letter would be C (score 62). Moves no points; the score is built from the measured rows.
Rule NO_SITEMAP_FOUND under scoring rules v31 · fingerprint NO_SITEMAP_FOUND|/ · persisting (6 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
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 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 7 findings on protectai.com. $749, once.
4 of them are scored serious. 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 robots.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 710,782 decompressed bytes the homepage delivers, 1.4% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 1.4% · 10,137 B
- Markup & attributes 9% · 63,842 B
- Inline CSS 45.2% · 321,042 B
- Inline JavaScript 25.8% · 183,730 B
- Inline SVG 16.9% · 120,193 B
- HTML comments 1.7% · 11,838 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 271,630 B (38.2%) — unnamedopens
\s*$/g;d.extend({htmlPrefilter:function(a){return a},clone:function(a, - Inline SVG · 119,060 B (16.8%) — unnamedopens
<defs><style> .cls-1 { fill: url(#linear-gradient-11); filter: url(#ou - Inline JavaScript · 93,959 B (13.2%) — jQueryopens
/* jQuery v3.6.1 | (c) OpenJS Foundation and other contributors | jque - Inline JavaScript · 46,887 B (6.6%) — jQueryopens
/* JavaScript Cookie v2.2.1 https://github.com/js-cookie/js-cookie Cop - Inline CSS · 26,204 B (3.7%) — unnamedopens
.coveo-visible-to-screen-reader-only { position: absolute; left: -1000
What changed
- 2026-10-12the homepage began taking more than one redirect to reachappeared
- 2026-09-27robots.txt named a sitemapresolved
- 2026-09-27robots.txt no longer returned HTMLresolved
- 2026-09-27resolved: www and the apex both serve the site instead of one redirectingresolved
- 2026-09-27a new finding appeared: robots.txt does not return 200 againreturned
- 2026-09-27the homepage redirected off its own host againreturned
- 2026-09-22the homepage no longer redirected off its own hostresolved
- 2026-09-22resolved: this domain is an alias: every path redirects to another siteresolved
- 2026-09-22robots.txt no longer named a sitemapappeared
- 2026-09-22robots.txt returned HTMLappeared
- 2026-09-22the homepage read as mostly markup againreturned
- 2026-09-22no sitemap could be found againreturned
7 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.comIs 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.