Directory · Web data and extraction
Oxylabs — what a crawler receives from oxylabs.io
Website measurement, not a product review. This page records what machine clients received from oxylabs.io. It does not evaluate Oxylabs software, features, pricing or support.
Answer engines can technically reach this site, but get little they can use.
AI visibility 70/100, measured 2026-10-11 19:06 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.
2
findings
✗
llms.txt on its host
✗
entity map on its host
6
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.
- What each crawler getsn/a
- Crawler permissions100
- Machine-file chainn/a
- Speed100
- 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 files40
- 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 read, because the three run in order.
What to fix
2 findings on this site. 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.
2 Low
1The cache is still serving a file the origin no longer hasThe bare URL and a cache-busted request to the same URL disagree: bare HTTP 200 [cf-cache-status: REVALIDATED], origin HTTP 429 (HTML). Whichever side is wrong,LowSetting
What we saw
The bare URL and a cache-busted request to the same URL disagree: bare HTTP 200 [cf-cache-status: REVALIDATED], origin HTTP 429 (HTML). Whichever side is wrong, what a crawler receives depends on cache state. /llms.txt
Why it matters
How to fix it
Give robots.txt, sitemap.xml and llms.txt a short cache lifetime (five minutes is plenty) so an edit reaches crawlers the same day.
Setting: a setting on the server, CDN, DNS or a plugin — no code and no writing
On Next.js (detected)
- Revalidate (revalidatePath / revalidateTag or a shorter revalidate time) and redeploy; on a CDN, purge the paths that changed.
In Cloudflare (this site is behind it)
- Caching → Configuration → Purge Cache (custom purge for the exact URLs) after each change.
- Caching → Cache Rules: bypass the cache or set a short edge TTL for robots.txt, sitemaps and llms.txt.
Why this was decided
| Rule | MACHINE_FILE_CACHE_STALE · rule pack sv31 · scope core |
|---|---|
| Evaluated | 2026-10-11 19:06:05 UTC |
| Decision | d1:567f7eb69cf982420141 · finding f1:0afa2c09a58fce024c4d resolve either at /api/graph/<id> with a key |
| Observer | crawlcheck-worker build a0b27a0e · audit v4 |
What it rests on
| Identity | Status | Bytes | sha256 | Kept |
|---|---|---|---|---|
| read: /robots.txt | 200 | 121 | 4eff0c58129f | already_held |
| read: /sitemap.xml | 404 | 199,647 | 7ddf5a8e4261 | kept |
| read: /sitemap_index.xml | 404 | 199,647 | 7ddf5a8e4261 | kept |
| read: /wp-sitemap.xml | 404 | 199,647 | 7ddf5a8e4261 | kept |
| read: /llms.txt | 200 | 4,354 | 3d38efd3a06b | already_held |
1 more in the manifest.
Artifacts: manifest:1bf59e60d9a071ced99fe44880b42af123938718d71eb1114d9d40ef69da353a
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 MACHINE_FILE_CACHE_STALE under scoring rules v31 · fingerprint MACHINE_FILE_CACHE_STALE|/llms.txt · new on this scan (1 scan)
Verify the fix Re-scan after the change. This finding is cleared when MACHINE_FILE_CACHE_STALE is no longer reported at /llms.txt; if it comes back after clearing, it is marked a regression, not a new finding.
MACHINE_FILE_CACHE_STALE · full transcript
Open the other 1
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 2 findings on oxylabs.io. $749, once.
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
- 2026-10-11resolved: the machine files cost more than the pageresolved
- 2026-10-11a new finding appeared: the cache is still serving a file the origin no longer has againreturned
- 2026-10-11a new finding appeared: the sitemap robots.txt declares refused this client againreturned
- 2026-10-07a new finding appeared: the machine files cost more than the pageappeared
- 2026-10-04resolved: the sitemap is refusedresolved
- 2026-10-04an llms.txt became readableresolved
- 2026-10-04resolved: the cache is still serving a file the origin no longer hasresolved
- 2026-10-04resolved: the sitemap robots.txt declares refused this clientresolved
- 2026-09-27resolved: whether a sitemap exists could not be determined — every path was refusedresolved
- 2026-09-27resolved: robots.txt does not return 200resolved
- 2026-09-27a new finding appeared: the cache is still serving a file the origin no longer hasappeared
- 2026-09-27a new finding appeared: the sitemap robots.txt declares refused this clientappeared
6 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 oxylabs.ioIs this your company?
This listing came from a fetch, not a submission, so nobody was asked. If oxylabs.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 “Web data and extraction” is our label for what the product is primarily sold as; it is not scored. Back to the directory.