Directory · SEO suite
Similarweb — what a crawler receives from similarweb.com
Website measurement, not a product review. This page records what machine clients received from similarweb.com. It does not evaluate Similarweb software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 74/100, measured 2026-10-18 16:11 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 C A medium-severity finding sets the letter.
3
findings
✓
llms.txt on its host
✗
entity map on its host
24
scans on record since 2026-09-02
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.
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
3 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 Note
1Two business records on this page claim the same identity1 identity collision in this page's structured data: two nodes share the same url.MediumDeveloper
What we saw
1 identity collision in this page's structured data: two nodes share the same url.
Why it matters
A system resolving which business this page is about has more than one candidate for one identity. Two LocalBusiness or Organization nodes sharing a phone number, an @id or a coordinate pair give a retrieval system no way to decide which record is the entity, so it may pick either or neither. This reads only what the page declares - it does not assert the business is duplicated or wrongly located.
How to fix it
Merge the duplicate business nodes into one, keep a single @id, and remove any plugin that emits a second empty LocalBusiness record.
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 similarweb.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: Two business records on this page claim the same identity (ENTITY_COLLISION, medium severity) Page: https://similarweb.com/ What was measured: 1 identity collision in this page's structured data: two nodes share the same url. Why it matters: A system resolving which business this page is about has more than one candidate for one identity. Two LocalBusiness or Organization nodes sharing a phone number, an @id or a coordinate pair give a retrieval system no way to decide which record is the entity, so it may pick either or neither. This reads only what the page declares - it does not assert the business is duplicated or wrongly located. How to fix it: Merge the duplicate business nodes into one, keep a single @id, and remove any plugin that emits a second empty LocalBusiness record. Rule and examples: https://crawlcheck.io/rules/ENTITY_COLLISION Full report (markdown): https://crawlcheck.io/r/hks67t4bz6.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=similarweb.com . The fix counts when ENTITY_COLLISION is gone from the new report.
Why this was decided
| Rule | ENTITY_COLLISION · rule pack sv32 · scope route |
|---|---|
| Evaluated | 2026-10-18 16:11:39 UTC |
| Decision | d1:9ce52f2cfc7b99d1b01a · finding f1:b9527c6f0fce651b4625 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build b3cf8c17 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 918,017 | a0039dc7b5c1 | write_unconfirmed |
21 more in the manifest.
Artifacts: manifest:dc1ee21e3aa1dc3860e60d68f75f28c86917e3e0cf89326b777f4d57764799d5
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 ENTITY_COLLISION under scoring rules v32 · fingerprint ENTITY_COLLISION|/ · persisting (28 scans)
Verify the fix Re-scan after the change. This finding is cleared when ENTITY_COLLISION is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
ENTITY_COLLISION · full transcript
Open the other 2
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 3 findings on similarweb.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 entity graph. 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 917,453 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% · 12,486 B
- Structured data (JSON-LD) 0.5% · 4,453 B
- Inline JavaScript 56.3% · 516,203 B
- Inline SVG 77.6% · 712,395 B
- HTML comments 0% · 8 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline JavaScript · 512,521 B (55.9%) — a framework state payloadopens
window.__APP_DATA__ = {"header":{"identity":null,"swUrls":{"logoutEndp - Inline SVG · 442,429 B (48.2%) — unnamedopens
\\n <path d=\\\"M8 3.2002C8.34292 3.2002 8.67909 3.22184 9.00879 3.262 - Inline SVG · 56,663 B (6.2%) — unnamedopens
<g clip-path="url(#redarbor_svg__clip0_10782_15717)" fill="#fff"><path - Inline SVG · 15,801 B (1.7%) — unnamedopens
<g clip-path="url(#slide4-logo_svg__clip0_10755_11259)" fill="#fff"><p - Inline SVG · 11,549 B (1.3%) — unnamedopens
<g clip-path="url(#best-relationship_svg__a)"><path fill="#fff" d="M0
What changed
- 2026-10-04score moved 73 → 74score-up
- 2026-10-04score moved 74 → 73score-down
- 2026-09-22score moved 73 → 72score-down
- 2026-09-17a new finding appeared: the machine files cost more than the pageappeared
- 2026-09-15score moved 73 → 74score-up
- 2026-09-13score moved 75 → 73score-down
- 2026-09-08score moved 75 → 74score-down
- 2026-09-07score moved 74 → 75score-up
- 2026-09-05score moved 75 → 74score-down
- 2026-09-04score moved 76 → 75score-down
24 scans on record, first 2026-09-02. 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 similarweb.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If similarweb.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 “SEO suite” is our label for what the product is primarily sold as; it is not scored. Back to the directory.