Directory · AI visibility monitoring
Mentionlytics — what a crawler receives from mentionlytics.com
Website measurement, not a product review. This page records what machine clients received from mentionlytics.com. It does not evaluate Mentionlytics software, features, pricing or support.
Answer engines are being served something other than this site.
AI visibility 80/100, measured 2026-10-04 04: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.
Held at D A high-severity finding sets the letter.
5
findings
✗
llms.txt on its host
✗
entity map on its host
6
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 read, because the three run in order.
What to fix
5 findings on this site, 3 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.
3 High 1 Low 1 Note
1robots.txt is unreadableHTTP 403.HighSetting
What we saw
HTTP 403. /robots.txt
Why it matters
A 5xx on robots.txt tells a standards-following crawler to treat the whole site as disallowed (RFC 9309). A 401 or 403 is a 4xx, which the standard treats as no file and so allows everything, though some crawlers read it as a refusal. Either way the rules you wrote are not the rules a crawler read. This is the single most expensive file on the site to get wrong.
How to fix it
robots.txt could not be fetched. Allow it through the security layer; it is the one file every crawler reads first.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
On WordPress (detected)
- WordPress serves a virtual robots.txt. Edit it in your SEO plugin: Yoast SEO → Tools → File editor; Rank Math → General Settings → Edit robots.txt; All in One SEO → Tools → Robots.txt Editor.
- A real robots.txt file in the site root (the folder with wp-config.php) overrides every plugin. If one exists, edit that file instead, through your host's file manager or SFTP.
- Keep one group per crawler: a crawler that has its own User-agent group ignores the * group entirely, so repeat any Disallow lines it still needs.
Why this was decided
| Rule | ROBOTS_BLOCKED · rule pack sv27 · scope core |
|---|---|
| Evaluated | 2026-10-04 04:17:30 UTC |
| Decision | d1:0e249670b25e40f80b2d · finding f1:a4e1cbececd64f7e3dbc resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build a06ac9d9 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /robots.txt | 403 | 75,193 | ac4f780358ba | already_held |
21 more in the manifest.
Artifacts: manifest:e85f6930a264561f6643af37c202e7556ed82938ae6fa29bf6e337a3bc0c2c80
Grade effect Caps the letter at D together with 2 other high-severity findings; the letter rises only when all of them are gone. Moves no points.
Rule ROBOTS_BLOCKED under scoring rules v31 · fingerprint ROBOTS_BLOCKED|/robots.txt · persisting (5 scans)
Verify the fix Re-scan after the change. This finding is cleared when ROBOTS_BLOCKED is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.
ROBOTS_BLOCKED · full transcript
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 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 5 findings on mentionlytics.com. $749, once.
3 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 232,864 decompressed bytes the homepage delivers, 5% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 5% · 11,631 B
- Markup & attributes 35.5% · 82,702 B
- Structured data (JSON-LD) 1.7% · 3,860 B
- Inline CSS 48.4% · 112,821 B
- Inline JavaScript 8.7% · 20,357 B
- HTML comments 0.6% · 1,493 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 69,074 B (29.7%) — WordPress theme or block stylesopens
@font-face { font-family: 'Titillium Web'; src: url('https://www.menti - Inline CSS · 24,273 B (10.4%) —
#azoom-style-inline-cssopens.padding{padding:15px;}.padding-2x{padding:30px;}body,html,p{color:#f6 - Inline CSS · 9,380 B (4%) — WordPress theme or block stylesopens
:root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio - Inline JavaScript · 5,455 B (2.3%) —
#vwoCodeopenswindow._vwo_code || (function () { var w=window, d=document; var accou - Inline CSS · 4,321 B (1.9%) — WordPress theme or block stylesopens
:root{--wp-block-synced-color:#7a00df;--wp-block-synced-color--rgb:122
What changed
- 2026-10-01score moved 76 → 77score-up
- 2026-10-01the homepage no longer read as mostly markupresolved
- 2026-09-22resolved: whether a sitemap exists could not be determined — every path was refusedresolved
- 2026-09-18resolved: this origin refused crawlcheck, so the site was never measuredresolved
- 2026-09-18a new finding appeared: whether a sitemap exists could not be determined — every path was refusedappeared
- 2026-09-18a new finding appeared: the sitemap is refusedappeared
- 2026-09-18a new finding appeared: robots.txt is unreadableappeared
- 2026-09-18the homepage read as mostly markupappeared
- 2026-09-18no llms.txt was foundappeared
- 2026-09-18a new finding appeared: the hsts header asks for browser preloading but does not qualify for itappeared
6 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 mentionlytics.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If mentionlytics.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.