Directory · Content and GEO

Outranking — what a crawler receives from outranking.io

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

Fgrade

AI assistants are being shown something other than your site.

AI visibility 31/100, measured 2026-10-29 19:06 UTC from outside its network, as each named AI and search crawler and as a browser. An answer engine cannot use this site as it is served today.

Open the full report outranking.io ↗

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

findings

✗

llms.txt on its host

✗

entity map on its host

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.

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.

What each crawler getsn/a
Crawler permissionsn/a
Machine-file chainn/a
Speed0
Server & hosting50
Internal linksn/a
Mobilen/a
exposuren/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
errpagesn/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 reach, 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 High 1 Low 1 Note

1No XML sitemap foundNo sitemap at any conventional path and none declared.HighDeveloper

What we saw

No sitemap at any conventional path and none declared.

Why it matters

Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.

How to fix it

Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.

Developer: a template, theme or application change — a developer touches it

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 outranking.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: No XML sitemap found (NO_SITEMAP_FOUND, high severity)
Page: https://outranking.io/
What was measured: No sitemap at any conventional path and none declared.
Why it matters: Without a sitemap, discovery depends entirely on internal linking. Orphaned and recently published pages may never be found.
How to fix it: Publish a sitemap at /sitemap.xml (most CMSs generate one) and name it in robots.txt.

Rule and examples: https://crawlcheck.io/rules/NO_SITEMAP_FOUND
Full report (markdown): https://crawlcheck.io/r/wbbedvnga3.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=outranking.io . The fix counts when NO_SITEMAP_FOUND is gone from the new report.

Why this was decided

Rule	`NO_SITEMAP_FOUND` · rule pack `sv34` · scope core
Evaluated	2026-10-29 19:06:23 UTC
Decision	`d1:3f40cd324ac1af5d5749` · finding `f1:f715c9cb8ebe331b1d63` resolve either at `/api/graph/<id>` with a key
Observer	crawlcheck-worker build `dff9f519` from EWR · audit v4

What it rests on

Identity	Status	sha256	Kept
read: /sitemap.xml	—	`—`	no_body
read: /sitemap_index.xml	—	`—`	no_body
read: /wp-sitemap.xml	—	`—`	no_body

3 more in the manifest.

Artifacts: manifest:aad455343ed3840cadbf54c5f63f0846af2fe51e6436befdbb4749206cb519a0

Grade effect Would cap the letter at D, but the score (31) already reads F, so the letter is the same without it. Moves no points.

Rule NO_SITEMAP_FOUND under scoring rules v34 · fingerprint NO_SITEMAP_FOUND|/ · persisting (7 scans)

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

NO_SITEMAP_FOUND · full transcript

2The homepage refused this client, so every homepage section is unmeasured🔒 What we saw, why it matters, the fix and the evidence bytes are in the licensed report.Low

3No llms.txt/llms.txt🔒 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

What changed

2026-10-29resolved: this origin refused crawlcheck, so the site was never measuredresolved
2026-10-29no sitemap could be found againreturned
2026-10-29no llms.txt was found againreturned
2026-10-29the homepage refused this clientappeared
2026-10-22robots.txt named a sitemapresolved
2026-10-22resolved: robots.txt answers with the catch-all page - there is no robots.txtresolved
2026-10-22the homepage is reached in one redirect or noneresolved
2026-10-22a sitemap became readableresolved
2026-10-22an llms.txt became readableresolved
2026-10-22resolved: https is served without a strict-transport-security headerresolved
2026-10-22resolved: the page’s content only exists after javascript runsresolved
2026-10-22a new finding appeared: this origin refused crawlcheck, so the site was never measuredappeared

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

Is this your company?

This listing came from a fetch, not a submission, so nobody was asked. If outranking.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.