CrawlCheck

Directory · AI visibility monitoring

Evertune — what a crawler receives from evertune.ai

Website measurement, not a product review. This page records what machine clients received from evertune.ai. It does not evaluate Evertune software, features, pricing or support.

85
Agrade

Answer engines can reach and read this site. It needs more it can quote.

AI visibility 85/100, measured 2026-10-06 17: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.

Open the full report evertune.ai ↗

1

finding

✓

llms.txt on its host

✗

entity map on its host

6

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; one that cannot read it never quotes it. That is why reach is a ceiling and not just a weight.

93

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.

76

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.

82

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 read, because the three run in order.

What to fix

1 finding on this site. Every one is named below; the top one is shown in full, free. Want it fixed for you? We implement it and re-measure.

1 Note

1Visitors and crawlers are being served an old copy of this pagethe copy served to us was built 20 hours 56 min ago, and identical to a fresh read once per-request tokens (nonces, CSRF tokens, our own cache-buster) are set aNoteSetting

What we saw

the copy served to us was built 20 hours 56 min ago, and identical to a fresh read once per-request tokens (nonces, CSRF tokens, our own cache-buster) are set aside, so the cache is old but not wrong

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 Webflow (detected)

  1. Republish the site; Webflow clears its CDN on publish. If Cloudflare is in front, purge there too.

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 Webflow fixes

Why this was decided
RuleSTALE_CACHE_SERVED · rule pack sv27 · scope route
Evaluated2026-10-06 17:18:02 UTC
Decisiond1:b46c0af8b1e8d7e99cc3 · finding f1:21831c2b5625444204a2 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 087699c7 · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /200103,71115bb0424fbb3kept
read: /200103,71144843fbdaa17write_unconfirmed
read: /200103,711d47a6e68c9e2write_unconfirmed

21 more in the manifest.

Artifacts: manifest:743e18d3391fe9c50f99592fc15df440dc0ab6381040e2af779f704c6466c192

Grade effect Does not cap the letter: only medium, high and critical findings do. Moves no points either; the score is built from the measured rows.

Rule STALE_CACHE_SERVED under scoring rules v31 · 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

Or 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 — $749

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

  • Readable text 7.9% · 8,226 B
  • Markup & attributes 44.7% · 46,331 B
  • Structured data (JSON-LD) 1.3% · 1,327 B
  • Inline CSS 9.4% · 9,748 B
  • Inline JavaScript 24.8% · 25,688 B
  • Inline SVG 6.7% · 6,962 B
  • HTML comments 5.2% · 5,365 B

The individual blocks that weigh the most, so the fix is a search rather than a hunt:

  • Inline CSS · 3,452 B (3.3%) — unnamedopens @keyframes nav-acc-in { from { opacity: 0; transform: translateY(-6px)
  • Inline SVG · 3,348 B (3.2%) — .cta-swoosh-svg-mopens <defs> <linearGradient id="cta-swoosh-gradient-m" gradientUnits="userS
  • Inline JavaScript · 3,192 B (3.1%) — unnamedopens document.addEventListener('DOMContentLoaded', function () { var row =
  • Inline JavaScript · 3,167 B (3.1%) — unnamedopens document.addEventListener('DOMContentLoaded', function () { if (typeof
  • Inline SVG · 3,150 B (3%) — .cta-swoosh-svgopens <defs> <linearGradient id="cta-swoosh-gradient" gradientUnits="userSpa

What changed

  1. 2026-10-01score moved 82 → 83score-up
  2. 2026-10-01a stale edge copy was served againreturned
  3. 2026-09-24the stale edge copy clearedresolved

6 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 evertune.ai

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If evertune.ai 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 “AI visibility monitoring” is our label for what the product is primarily sold as; it is not scored. Back to the directory.