Directory · Site crawler
Seobility — what a crawler receives from seobility.net
Website measurement, not a product review. This page records what machine clients received from seobility.net. It does not evaluate Seobility software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 82/100, measured 2026-10-18 18:08 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.
7
findings
✓
llms.txt on its host
✗
entity map on its host
24
scans on record since 2026-09-01
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?
The facts an assistant is asked for are declared and consistent.
The stage to fix first is reach, because the three run in order.
What to fix
7 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 Medium 1 Low 3 Note
1robots.txt rules do not apply to named agents15 named User-agent groups (15 agents) do not repeat 16 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignoreMediumSetting
What we saw
15 named User-agent groups (15 agents) do not repeat 16 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: `googlebot` bypasses /wp-admin/, /*/keywordcheck/check/*, /*/keywordchecker/check/*, /*/seocompare/check/*, /*/comparador-web-seo/check/*, /*/rankingcheck/check/*, /*/serpchecker/check/*, /*/seocheck/pdfexport*, /*/seochecker/pdfexport*, /*/seocheck/check*, /*/seochecker/check*, /en/keyword-research-tool/check, /de/keyword-recherche-tool/check, /es/buscador-palabras-clave/check, /pdfexample/, /docs/ai/. This includes a SEARCH crawler (googlebot) — the bypassed paths are being crawled and can enter the index. /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
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.
Paste this
Each crawler obeys only its own group, so a named group must repeat the rules you want. The corrected file below copies them in for you.
The whole corrected robots.txt for seobility.net · built from the live file, every change listed at the top.
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 seobility.net. 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: robots.txt rules do not apply to named agents (ROBOTS_RULES_SHADOWED, medium severity) Page: https://seobility.net/robots.txt What was measured: 15 named User-agent groups (15 agents) do not repeat 16 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: `googlebot` bypasses /wp-admin/, /*/keywordcheck/check/*, /*/keywordchecker/check/*, /*/seocompare/check/*, /*/comparador-web-seo/check/*, /*/rankingcheck/check/*, /*/serpchecker/check/*, /*/seocheck/pdfexport*, /*/seochecker/pdfexport*, /*/seocheck/check*, /*/seochecker/check*, /en/keyword-research-tool/check, /de/keyword-recherche-tool/check, /es/buscador-palabras-clave/check, /pdfexample/, /docs/ai/. This includes a SEARCH crawler (googlebot) — the bypassed paths are being crawled and can enter the index. 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. Detected platform: WordPress. Make the change where this platform controls it. Rule and examples: https://crawlcheck.io/rules/ROBOTS_RULES_SHADOWED Full report (markdown): https://crawlcheck.io/r/btnqqrmr80.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=seobility.net . The fix counts when ROBOTS_RULES_SHADOWED is gone from the new report.
Why this was decided
| Rule | ROBOTS_RULES_SHADOWED · rule pack sv32 · scope core |
|---|---|
| Evaluated | 2026-10-18 18:08:09 UTC |
| Decision | d1:7e1944d974dc91a5e86d · finding f1:d1611563e7121774a281 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: /robots.txt | 200 | 4,800 | 24073c63ae46 | write_unconfirmed |
23 more in the manifest.
Artifacts: manifest:a3907185e41f26ebe3c42a15c95297a3abc2c902ed5f1c3a93bf277e56f1666f
Grade effect Caps the letter at C together with 2 other medium-severity findings; the letter rises only when all of them are gone. Moves no points.
Rule ROBOTS_RULES_SHADOWED under scoring rules v32 · fingerprint ROBOTS_RULES_SHADOWED|/robots.txt · persisting (25 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 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 seobility.net. $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 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 249,592 decompressed bytes the homepage delivers, 3.5% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 3.5% · 8,808 B
- Markup & attributes 32.4% · 80,910 B
- Structured data (JSON-LD) 1.9% · 4,633 B
- Inline CSS 36.2% · 90,396 B
- Inline JavaScript 19.3% · 48,239 B
- Inline SVG 4.5% · 11,234 B
- HTML comments 2.2% · 5,372 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline CSS · 83,893 B (33.6%) — WordPress theme or block stylesopens
img:is([sizes=auto i],[sizes^="auto," i]){contain-intrinsic-size:3000p - Inline JavaScript · 14,571 B (5.8%) — unnamedopens
(()=>{class RocketLazyLoadScripts{constructor(){this.v="2.0.5",this.us - Inline JavaScript · 12,711 B (5.1%) — unnamedopens
const rocket_pairs = [{"selector":".third-section","style":".third-sec - Inline CSS · 5,773 B (2.3%) —
#wpr-lazyload-bg-nostyleopens.third-section::before{--wpr-bg-c70033f9-6040-4cd8-a578-c4d8aedd915a: - JSON-LD · 4,633 B (1.9%) —
.yoast-schema-graphopens{"@context":"https:\/\/schema.org","@graph":[{"@type":"TechArticle","@
What changed
- 2026-10-18the homepage date moved with no change to its wordsappeared
- 2026-10-18an answer engine was refused againreturned
- 2026-10-15the homepage began taking more than one redirect to reachappeared
- 2026-10-01score moved 82 → 85score-up
- 2026-10-01a stale edge copy was served againreturned
- 2026-09-24score moved 81 → 82score-up
- 2026-09-24resolved: www and the apex both serve the site instead of one redirectingresolved
- 2026-09-24the stale edge copy clearedresolved
- 2026-09-20no answer engine was refusedresolved
- 2026-09-20a stale edge copy was served againreturned
- 2026-09-18the stale edge copy clearedresolved
- 2026-09-18an answer engine was refused againreturned
24 scans on record, first 2026-09-01. 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 seobility.netIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If seobility.net 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 “Site crawler” is our label for what the product is primarily sold as; it is not scored. Back to the directory.