CrawlCheck

Directory · Search and discovery infrastructure

Lucidworks — what a crawler receives from lucidworks.com

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

83
Cgrade

AI assistants like ChatGPT can read your site, but find little they can quote from your pages.

AI visibility 83/100, measured 2026-10-30 18:34 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 lucidworks.com ↗

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

4

findings

✓

llms.txt on its host

✗

entity map on its host

11

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.

79

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.

88

Stage 2 · 30% of the score

Read

Once it has the bytes, can it find the words?

The delivered HTML is mostly content, and the machine files point at the rest.

84

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

What to fix

4 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 Note

1The homepage depends on files this site's own robots.txt disallows1 render resource referenced by the homepage is disallowed to every crawler by this site's own robots.txt: /wp-content/cache/min/1/forms/embed/developer/2449519MediumSetting

What we saw

1 render resource referenced by the homepage is disallowed to every crawler by this site's own robots.txt: /wp-content/cache/min/1/forms/embed/developer/244951955.js (*/embed/). A crawler that obeys robots.txt will not fetch these, so it renders the page without them. /robots.txt

Why it matters

Googlebot renders pages, and a stylesheet or script it is forbidden to fetch is rendered without. Layout, visibility and any content a script inserts are then judged from a page the site never intended to show. Only rules in the * group count here - a rule aimed at one named crawler is a narrower question.

How to fix it

Allow crawlers to fetch the CSS and JavaScript the page depends on. Remove the Disallow rules covering those paths, or serve the content without them.

Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing

On WordPress (detected)

  1. 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.
  2. 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.
  3. 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.

In Cloudflare (this site is behind it)

  1. 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.
  2. Robots.txt is cached at the edge: purge it (Caching → Configuration → Custom purge → the robots.txt URL) after you change it.

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 lucidworks.com. 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: The homepage depends on files this site's own robots.txt disallows (RENDER_RESOURCE_BLOCKED, medium severity)
Page: https://lucidworks.com/robots.txt
What was measured: 1 render resource referenced by the homepage is disallowed to every crawler by this site's own robots.txt: /wp-content/cache/min/1/forms/embed/developer/244951955.js (*/embed/). A crawler that obeys robots.txt will not fetch these, so it renders the page without them.
Why it matters: Googlebot renders pages, and a stylesheet or script it is forbidden to fetch is rendered without. Layout, visibility and any content a script inserts are then judged from a page the site never intended to show. Only rules in the * group count here - a rule aimed at one named crawler is a narrower question.
How to fix it: Allow crawlers to fetch the CSS and JavaScript the page depends on. Remove the Disallow rules covering those paths, or serve the content without them.
Detected platform: WordPress. Make the change where this platform controls it.
Rule and examples: https://crawlcheck.io/rules/RENDER_RESOURCE_BLOCKED
Full report (markdown): https://crawlcheck.io/r/lsvjkath8a.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=lucidworks.com . The fix counts when RENDER_RESOURCE_BLOCKED is gone from the new report.
Why this was decided
RuleRENDER_RESOURCE_BLOCKED · rule pack sv34 · scope route
Evaluated2026-10-30 18:34:25 UTC
Decisiond1:786a95978ed26b42af68 · finding f1:a22bf6650bef449c3bc8 resolve either at /api/graph/<id> with a key
Observercrawlcheck-worker build 48134344 from LAX · audit v4

What it rests on

IdentityStatusBytessha256Kept
read: /200276,971eb52ff6d2ae0kept
read: /robots.txt200585c7b2cc58033dalready_held

22 more in the manifest.

Artifacts: manifest:7a91ab1f9435eeab7e5ff33026cf33db95c47ec50237918bfda0254f4ed1e43c

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 RENDER_RESOURCE_BLOCKED under scoring rules v34 · fingerprint RENDER_RESOURCE_BLOCKED|/robots.txt · new on this scan (2 scans)

Verify the fix Re-scan after the change. This finding is cleared when RENDER_RESOURCE_BLOCKED is no longer reported at /robots.txt; if it comes back after clearing, it is marked a regression, not a new finding.

RENDER_RESOURCE_BLOCKED · full transcript

2Almost nothing a machine receives from this page is readable text🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
3Visitors and crawlers are being served an old copy of this page🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Medium
4The homepage is reached through a chain of redirects🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Note

Open the other 3

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

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

  • Readable text 3.3% · 9,016 B
  • Markup & attributes 17.1% · 47,217 B
  • Structured data (JSON-LD) 0.7% · 1,811 B
  • Inline CSS 64.2% · 177,679 B
  • Inline JavaScript 11.3% · 31,241 B
  • Inline SVG 3.4% · 9,417 B
  • HTML comments 0.2% · 529 B

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

  • Inline CSS · 177,068 B (63.9%) — #wpr-usedcssopens img:is([sizes=auto i],[sizes^="auto," i]){contain-intrinsic-size:3000p
  • Inline JavaScript · 14,571 B (5.3%) — unnamedopens (()=>{class RocketLazyLoadScripts{constructor(){this.v="2.0.5",this.us
  • Inline SVG · 7,832 B (2.8%) — unnamedopens <g clip-path="url(#clip0_4481_54935)"> <path d="M868.014 149.789C877.3
  • Inline JavaScript · 3,533 B (1.3%) — #rocket-preload-links-js-afteropens (function() { "use strict";var r="function"==typeof Symbol&&"symbol"==
Section average over 2 scans on this score version · held at 83 since 2026-10-30
0501002026-10-23 11:34 · 80/100 · 3 findings2026-10-30 18:34 · 83/100 · 4 findings2026-10-232026-10-30

What changed

  1. 2026-10-30score moved 77 → 80score-up
  2. 2026-10-30resolved: the machine files cost more than the pageresolved
  3. 2026-10-30a render resource was blocked to crawlers againreturned
  4. 2026-10-30the homepage read as mostly markupappeared
  5. 2026-10-23the blocked render resource clearedresolved
  6. 2026-10-23a stale edge copy was servedappeared
  7. 2026-10-21resolved: this origin refused crawlcheck, so the site was never measuredresolved
  8. 2026-10-21a render resource was blocked to crawlersappeared
  9. 2026-10-21the homepage began taking more than one redirect to reachappeared
  10. 2026-10-21a new finding appeared: the machine files cost more than the pageappeared

11 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 lucidworks.com

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If lucidworks.com 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 “Search and discovery infrastructure” is our label for what the product is primarily sold as; it is not scored. Back to the directory.