Directory · Design and interface generation
Lovable — what a crawler receives from lovable.dev
Website measurement, not a product review. This page records what machine clients received from lovable.dev. It does not evaluate Lovable software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 67/100, measured 2026-10-07 13:19 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.
3
findings
✓
llms.txt on its host
✗
entity map on its host
5
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.
- What each crawler getsn/a
- Crawler permissions100
- Machine-file chainn/a
- Speed0
- Server & hosting75
- Internal linksn/a
- Mobilen/a
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.
- Page weight & textn/a
- Machine files80
- Sitemapn/a
- Crawl wasten/a
- Accessibility structuren/a
- Image signalsn/a
- Instructions for agentsn/a
- URL namingn/a
Stage 3 · 30% of the score
Quote
Is there a specific fact it can state and attribute?
Not measured on this scan; left out rather than counted as zero.
- Structured datan/a
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signalsn/a
- Linked datan/a
- Quotable contentn/a
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is reach, because the three run in order.
What to fix
3 findings on this site, 1 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.
1 Medium 2 Low
1robots.txt rules do not apply to named agents2 named User-agent groups (8 agents) do not repeat 8 of the Disallow rules the `*` group carries. A crawler obeys only its own most-specific group and ignores `MediumSetting
What we saw
2 named User-agent groups (8 agents) do not repeat 8 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: `slackbot-linkexpanding, twitterbot, linkedinbot, facebookexternalhit, facebot` bypasses /templates&, /templates%26, /templates/*&, /templates/*%26, /*/templates&, /*/templates%26, /*/templates/*&, /*/templates/*%26. /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
In Cloudflare (this site is behind it)
- If Cloudflare's managed robots.txt is on (Security → Bots, or AI Crawl Control → robots.txt), Cloudflare adds its own lines above yours. Turn it off, or keep it knowing those lines are there.
- Robots.txt is cached at the edge: purge it (Caching → Configuration → Custom purge → the robots.txt URL) after you change it.
Why this was decided
| Rule | ROBOTS_RULES_SHADOWED · rule pack sv28 · scope core |
|---|---|
| Evaluated | 2026-10-07 13:19:05 UTC |
| Decision | d1:855f44041908c8bc1c23 · finding f1:7a6121a42ffe00dfdf88 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build f728f238 · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /robots.txt | 200 | 1,668 | 320e2cc26fde | already_held |
5 more in the manifest.
Artifacts: manifest:884e9df944952b99e607ce03196e0b05c00e102cb4ac73d6989cb73ce8e8c1e6
Grade effect Would cap the letter at C, but the score (67) already reads C, so the letter is the same without it. Moves no points.
Rule ROBOTS_RULES_SHADOWED under scoring rules v31 · fingerprint ROBOTS_RULES_SHADOWED|/robots.txt · persisting (8 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 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 lovable.dev. $749, once.
1 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
What changed
No change recorded between the readings on file yet.
5 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 lovable.devIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If lovable.dev 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 “Design and interface generation” is our label for what the product is primarily sold as; it is not scored. Back to the directory.