Directory · SEO suite
Moz — what a crawler receives from moz.com
Website measurement, not a product review. This page records what machine clients received from moz.com. It does not evaluate Moz software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 83/100, measured 2026-10-04 04:52 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
22
scans on record since 2026-08-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?
Every named crawler was served the same page a browser gets.
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 2 Note
1robots.txt rules do not apply to named agents1 named User-agent group (3 agents) do not repeat 19 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `MediumSetting
What we saw
1 named User-agent group (3 agents) do not repeat 19 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `*` entirely, so those rules do not apply to any of the named agents (some declare their own, different rules). Worst group: `rogerbot, ahrefsbot, gptbot` bypasses /products/content/, /local/enterprise/confirm, /researchtools/ose/, /page-strength/*, /thumbs/*, /api/user?*, /checkout/*, /purchase/*, /local/search/, /local/details/, /messages/, /content/audit/*, /content/search/*, /marketplace/, /cpresources/, /vendor/, /community/q/questions/*/view_counts, /admin-preview/*, /community/q/socket.io/*. /robots.txt
Why it matters
A crawler reads only the User-agent group that matches it best and ignores every other group, including `*`. Naming an agent and giving it only `Allow: /` therefore deletes all of your `*` Disallow rules for that agent. The file still parses and the agent still reaches your homepage, so this is invisible on inspection — but the paths you meant to keep out of search are open, and search engines will crawl and may index them.
How to fix it
Every User-agent group that names a crawler must repeat the Disallow rules you want applied. A named group with no rules means 'allow everything' for that crawler.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | ROBOTS_RULES_SHADOWED · rule pack sv27 · scope core |
|---|---|
| Evaluated | 2026-10-04 04:52:47 UTC |
| Decision | d1:cd442830ce3e3f42c6a6 · finding f1:47a37b59f21a49a1803e resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build e0a45003 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /robots.txt | 200 | 1,207 | 79bb8772fcda | already_held |
23 more in the manifest.
Artifacts: manifest:d3474bc344d46cc5af2224ec33b7e42223a02e747c4a32c64aeb0cfcde2b2ad2
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 ROBOTS_RULES_SHADOWED under scoring rules v28 · fingerprint ROBOTS_RULES_SHADOWED|/robots.txt · persisting (31 scans)
Verify the fix Re-scan after the change. This finding is cleared when ROBOTS_RULES_SHADOWED is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.
ROBOTS_RULES_SHADOWED · 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 moz.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 llms.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 166,531 decompressed bytes the homepage delivers, 10.1% is text a reader or a model can actually use. Workable, with room to trim.
- Readable text 10.1% · 16,878 B
- Markup & attributes 81.5% · 135,773 B
- Structured data (JSON-LD) 1.5% · 2,571 B
- Inline JavaScript 2.4% · 4,066 B
- Inline SVG 4.3% · 7,243 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- JSON-LD · 2,571 B (1.5%) — unnamedopens
{"@context":"https://schema.org","@graph":[{"@type":"WebPage","author" - Inline JavaScript · 2,165 B (1.3%) — unnamedopens
var _mgn = _mgn || {}; _mgn = Object.assign(_mgn, { env: "production",
What changed
- 2026-10-04score moved 82 → 83score-up
- 2026-10-04score moved 83 → 82score-down
- 2026-10-04score moved 82 → 83score-up
- 2026-09-20the shared schema identifier clearedresolved
- 2026-09-17a new finding appeared: the machine files cost more than the pageappeared
- 2026-09-15score moved 85 → 86score-up
- 2026-09-08score moved 85 → 83score-down
- 2026-09-07score moved 83 → 85score-up
- 2026-09-02score moved 85 → 83score-down
- 2026-09-02score moved 83 → 85score-up
- 2026-09-01a named-agent group shadowed the wildcard rulesappeared
- 2026-09-01two schema nodes shared one identifierappeared
22 scans on record, first 2026-08-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 moz.comIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If moz.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.