Directory · AI visibility monitoring
Brand24 — what a crawler receives from brand24.com
Website measurement, not a product review. This page records what machine clients received from brand24.com. It does not evaluate Brand24 software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 80/100, measured 2026-10-09 19:21 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.
4
findings
✓
llms.txt on its host
✗
entity map on its host
8
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.
The stage to fix first is quote, because the three run in order.
What to fix
4 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 1 Note
1Links on this site point at pages that do not answer1 of 18 sampled internal links are gone: /faq (404, linked from /).MediumContent
What we saw
1 of 18 sampled internal links are gone: /faq (404, linked from /).
Why it matters
A link on this site was followed and the target answered 4xx or 5xx. A crawler spends budget on every one of these and learns nothing; a reader following one gets an error page. The usual causes are a route renamed without updating the links to it, and a nav or footer that renders links to authenticated-only routes for everyone — those answer 404 when signed out, which is what a crawler always is. Only 404 and 410 count here. A link answering 401, 403 or 429 means something declined to answer CrawlCheck — bot protection, a login wall, a rate limit — which is a fact about the request, not about the link, so those are counted and never reported as broken. Links are sampled rather than exhaustively crawled, so this is a floor and not a full link audit.
How to fix it
Fix or remove the internal links that return 404 so crawlers and visitors are not sent to dead pages.
Content: words, markup or images on a page — no deploy
Why this was decided
| Rule | BROKEN_INTERNAL_LINK · rule pack sv28 · scope core |
|---|---|
| Evaluated | 2026-10-09 19:21:26 UTC |
| Decision | d1:f880cfbe3c38cffff7c1 · finding f1:247e628d29c74f92242b resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 154cdfd3 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 130,801 | 6dd70093b396 | kept |
21 more in the manifest.
Artifacts: manifest:4140ed7b19a4309f9fab2a1471d2c47e4e74cffacdeaad1fc092f7956f71c5d2
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 BROKEN_INTERNAL_LINK under scoring rules v31 · fingerprint BROKEN_INTERNAL_LINK|/ · persisting (9 scans)
Verify the fix Re-scan after the change. This finding is cleared when BROKEN_INTERNAL_LINK is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
BROKEN_INTERNAL_LINK · full transcript
Open the other 3
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 4 findings on brand24.com. $749, once.
2 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 sitemap. 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 130,792 decompressed bytes the homepage delivers, 4.4% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 4.4% · 5,703 B
- Markup & attributes 53.6% · 70,105 B
- Structured data (JSON-LD) 2.6% · 3,337 B
- Inline CSS 23.5% · 30,784 B
- Inline JavaScript 3.4% · 4,437 B
- Inline SVG 12.6% · 16,426 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 20,393 B (15.6%) — Elementoropens
body{padding-top:90px}@media(min-width: 992px){body{padding-top:80px}} - Inline CSS · 10,069 B (7.7%) — unnamedopens
.grecaptcha-badge{bottom:100px !important}.single-case-study .main-foo - JSON-LD · 3,337 B (2.6%) —
.aioseo-schemaopens{"@context":"https:\/\/schema.org","@graph":[{"@type":"BreadcrumbList" - Inline SVG · 3,073 B (2.3%) — unnamedopens
<path d="M6.15796 9.37546C6.15796 7.64955 7.48313 6.25006 9.11827 6.25 - Inline SVG · 2,916 B (2.2%) — unnamedopens
<path d="M11.0687 9.75576V9.68992C13.4552 9.11683 14.639 7.43159 14.63
What changed
- 2026-10-01a declared sitemap listed no URLsappeared
- 2026-09-24the sitemap no longer returned HTMLresolved
- 2026-09-18score moved 71 → 69score-down
8 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 brand24.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If brand24.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 visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.