Directory · Content and GEO
WordLift — what a crawler receives from wordlift.io
Website measurement, not a product review. This page records what machine clients received from wordlift.io. It does not evaluate WordLift software, features, pricing or support.
Answer engines can reach and read this site. It needs more it can quote.
AI visibility 80/100, measured 2026-10-05 14:18 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.
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?
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.
- Structured data71
- Local presence & NAPn/a
- Claim consistencyn/a
- Authors & trust signals75
- Linked data100
- Quotable content50
- Entity corroborationn/a
- Page subjectn/a
The stage to fix first is quote, 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 Note
1Visitors and crawlers are being served an old copy of this pagethe copy served to us was built 551 hours 32 min ago, and two fresh reads agree with each other and both differ from the cached copy at byte 606 once per-requesMediumSetting
What we saw
the copy served to us was built 551 hours 32 min ago, and two fresh reads agree with each other and both differ from the cached copy at byte 606 once per-request tokens are set aside (195,540 bytes cached vs 194,076 fresh)
Why it matters
The page handed to us carried a cache age older than an hour. The detail says whether the copy still matches what the origin produces now: if it matches, nothing is broken today; if it differs, an edit is already waiting behind the cache. It matters the moment you change something: an edit, a new price, a corrected phone number stays invisible to every visitor and every crawler for about that long, and nothing in your dashboard says so.
How to fix it
Lower the cache lifetime on HTML (an hour or less), or purge the edge and origin caches after every publish so crawlers see the current copy.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
Why this was decided
| Rule | STALE_CACHE_SERVED · rule pack sv27 · scope route |
|---|---|
| Evaluated | 2026-10-05 14:18:05 UTC |
| Decision | d1:ffa0d9b021e206bad35e · finding f1:63ae4b1b351ded0c7250 resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build 71386c1f · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: / | 200 | 195,540 | 1865384fa70c | kept |
| read: / | 200 | 194,076 | aeae278ea450 | kept |
| read: / | 200 | 194,076 | ddd665c60fa5 | kept |
21 more in the manifest.
Artifacts: manifest:101708b07d72e0c89dda6c4add8d793420837e0945ac49293e56f864b972c00d
Evidence bytes
[object Object]Grade effect Caps the letter at C. Without it the letter would be B (score 80). Moves no points; the score is built from the measured rows.
Rule STALE_CACHE_SERVED under scoring rules v28 · fingerprint STALE_CACHE_SERVED|/ · persisting (5 scans)
Verify the fix Re-scan after the change. This finding is cleared when STALE_CACHE_SERVED is no longer reported at /; if it comes back after clearing, it is marked a regression, not a new finding.
STALE_CACHE_SERVED · 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 wordlift.io. $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
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 195,429 decompressed bytes the homepage delivers, 8.8% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.
- Readable text 8.8% · 17,254 B
- Markup & attributes 50% · 97,636 B
- Structured data (JSON-LD) 1.1% · 2,162 B
- Inline CSS 8.1% · 15,780 B
- Inline JavaScript 6.8% · 13,269 B
- Inline SVG 25% · 48,916 B
- HTML comments 0.2% · 412 B
The individual blocks that weigh the most, so the fix is a search rather than a hunt:
- Inline SVG · 16,893 B (8.6%) —
#blocksopens<g clip-path="url(#clip0_2279_4036)"> <rect width="1440" height="800" - Inline CSS · 10,317 B (5.3%) —
#global-styles-inline-cssopens:root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio - Inline SVG · 5,246 B (2.7%) — unnamedopens
<path d="M27.9711 20C23.7988 20 20.6763 16.7553 20.6763 12.633C20.6763 - Inline SVG · 5,246 B (2.7%) — unnamedopens
<path d="M27.9711 20C23.7988 20 20.6763 16.7553 20.6763 12.633C20.6763 - Inline SVG · 5,203 B (2.7%) — unnamedopens
<path d="M53.4057 40C46.1699 40 40.7431 33.7853 40.7431 25.3107C40.743
What changed
- 2026-10-02score moved 78 → 80score-up
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 wordlift.ioIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If wordlift.io 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 “Content and GEO” is our label for what the product is primarily sold as; it is not scored. Back to the directory.