CrawlCheck

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.

82
Cgrade

AI assistants like ChatGPT can read your site, but find little to quote about your product.

AI visibility 82/100, measured 2026-11-02 00:06 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.

Open the full report wordlift.io ↗

901. ReachCan a named answer-engine crawler get your pages at all?792. ReadOnce it has the bytes, can it find the words?753. QuoteIs there a specific fact it can state and attribute?

3

findings

✓

llms.txt on its host

✗

entity map on its host

9

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, and one that cannot read it never quotes it.

90

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.

79

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.

75

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, the lowest of the three.

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 223 hours 16 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 223 hours 16 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,566 bytes cached vs 194,488 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

On WordPress (detected)

  1. Purge the server cache first (your host's Varnish or page cache), then the caching plugin, then the CDN; purging in the other order lets the CDN refill from the stale layer.
  2. Give robots.txt, sitemaps and llms.txt a short cache lifetime.

In Cloudflare (this site is behind it)

  1. Caching → Configuration → Purge Cache (custom purge for the exact URLs) after each change.
  2. Caching → Cache Rules: bypass the cache or set a short edge TTL for robots.txt, sitemaps and llms.txt.

All WordPress fixes

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 wordlift.io. 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: Visitors and crawlers are being served an old copy of this page (STALE_CACHE_SERVED, medium severity)
Page: https://wordlift.io/
What was measured: the copy served to us was built 223 hours 16 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,566 bytes cached vs 194,488 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.
Detected platform: WordPress. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/STALE_CACHE_SERVED
Full report (markdown): https://crawlcheck.io/r/q17wzp5yp6.md

Evidence (bytes the crawler received):
```
served to us: /script>
	
	<title>Home - AI-Powered SEO • WordLift</title>
<link crossorigin data-rocket-preconnect href="https://www.redditstatic.com" rel="preconnect">
<link crossorigin data-ro
fresh read: /script>
	
	<title>Home - AI-Powered SEO • WordLift</title>
	<meta name="description" content="WordLift is the AI-powered tool that revolutionizes your SEO. Get more organic traffi
```

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=wordlift.io . The fix counts when STALE_CACHE_SERVED is gone from the new report.
Why this was decided
RuleSTALE_CACHE_SERVED · rule pack sv34 · scope route
Evaluated2026-11-02 00:06:16 UTC
Decisiond1:18bd8cffc07103d3fe26 · finding f1:63ae4b1b351ded0c7250 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 93b7dbda from SIN · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /200195,5664cdb8197bd8ealready_held
read: /200194,488dabb41ab2f48kept
read: /200194,48811c7a8ff56c5kept

22 more in the manifest.

Artifacts: manifest:1ce88a902978a03f1a5e27a1bb09ce1e889712b8992c0e9575cfdd381299dc08

Evidence bytes
served to us: /script>
	
	<title>Home - AI-Powered SEO • WordLift</title>
<link crossorigin data-rocket-preconnect href="https://www.redditstatic.com" rel="preconnect">
<link crossorigin data-ro
fresh read: /script>
	
	<title>Home - AI-Powered SEO • WordLift</title>
	<meta name="description" content="WordLift is the AI-powered tool that revolutionizes your SEO. Get more organic traffi

Grade effect Caps the letter at C. Without it the letter would be B (score 82). Moves no points; the score is built from the measured rows.

Rule STALE_CACHE_SERVED under scoring rules v34 · fingerprint STALE_CACHE_SERVED|/ · persisting (9 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

2HTTPS is served without a Strict-Transport-Security header🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note
3A missing agent file answers with a full page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

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 findings

Or have them fixed

We implement the list on your site and re-measure, with a sealed before and after. One site, $100 once.

Get this fixed — $100

Sites like yours that fixed the same problem

Matched on WordPress + Cloudflare + Kinsta. A fix counts once two readings confirm it; sites are not named. Read from the technology record of 2026-10-25.

serves no /agents.md (optional)

9 sites on a stack like yours have made this fix (Published agents.md); 9 still hold it. 15 on any stack.

  • similar site A (WordPress + Cloudflare + Cloudflare Bot Management; shares platform, CDN): fixed 2026-10-31, still fixed today
  • similar site B (WordPress; shares platform): fixed 2026-10-30, still fixed today
  • similar site C (Cloudflare; shares CDN): fixed 2026-11-01, still fixed today

serves no /entitymap.json (optional)

2 sites on a stack like yours have made this fix (Published an entity map); 2 still hold it.

  • similar site A (WordPress + Cloudflare; shares platform, CDN): fixed 2026-10-29, still fixed today
  • similar site B (Cloudflare; shares CDN): fixed 2026-10-15, still fixed today

The signed answer lists every match.

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.

✓robots.txtEvery crawler reads this first
✓sitemapNamed in robots.txt and resolves
✓llms.txtPoints onward, links stay on this host
✗entity graphParses as JSON and points home

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,455 decompressed bytes the homepage delivers, 8.9% is text a reader or a model can actually use. Most of what a crawler downloads here is not words.

  • Readable text 8.9% · 17,329 B
  • Markup & attributes 49.9% · 97,587 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
Section average over 2 scans on this score version · held at 82 since 2026-11-02
0501002026-10-25 17:05 · 82/100 · 3 findings2026-11-02 00:06 · 82/100 · 3 findings2026-10-252026-11-02

What changed

  1. 2026-11-02score moved 80 → 81score-up
  2. 2026-10-02score moved 78 → 80score-up

9 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.io

Is 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.