# INGEST report — namesilo.com
> Machine comprehension measurement. Not an SEO score. UNKNOWN stays UNKNOWN.
- **URL:** https://namesilo.com
- **Report ID:** `c14806c1-5842-4e15-b0cc-aba164a8612c`
- **Tested:** 2026-09-30T13:14:10.906Z
- **Duration:** 4.5s
- **Contract:** 1.0.0
- **Coverage:** 10/13 measured
- **Composite:** 52 / 100
- **Critical:** 4 · **Warnings:** 6
## Question

Can a machine retrieve, parse, identify, extract, verify, relate, and trust the important facts on this page without unnecessary inference?

## Scorecard
| Component | Score |
| --- | --- |
| Fetch health | 0 |
| Crawler access | 0 |
| Raw HTML quality | 60 |
| JS dependency | 100 |
| Structured data | — |
| Fact parity | — (0/2 groups compared) |
| Fact recovery cost | 100 |
| Entity coherence | — |
| Provenance | 100 |
| Freshness | 20 |
| Salience | 57 |
| Indexability | 0 |
| Discovery | 84 |
| AI readiness | — |
| Search interpretation (v2) | — |
| Machine ingestion (composite) | 52 |
Unmeasured: Structured data, Fact parity, Entity coherence

## Critical findings

### Bot friction on fetch

Response looks like a challenge, WAF, or access wall

```
<!DOCTYPE html> <!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]--> <!--[if IE 7]> <html class="no-js ie7 oldie" lang="en-US"> <![endif]--> <!--[if IE 8]> <html class="no-js ie8 oldie" lang="en-US"> <![endif]--> <!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]--> <head> <title>Attention Required! | Cloudflare</title> <meta charset="UTF-8" /> <meta
```

### noindex present

noindex, nofollow

### Non-indexable HTTP state

BOT_CHALLENGE

### SALIENCE_CONFLICT

Title "Attention Required! | Cloudflare" vs H1 "Sorry, you have been blocked" vs body "Please enable cookies. Sorry, you have been blocked You are unable to access nam" (no schema)

```
Please enable cookies. Sorry, you have been blocked You are unable to access namesilo.com Why have I been blocked? This website is using a security service to protect itself from online attacks. The a
```

## Warnings

### No parseable JSON-LD graph

Structured identity is missing for machines

### Missing canonical

Page does not declare a canonical URL

### robots.txt missing or unreadable

HTTP 403 for https://namesilo.com/robots.txt

### Audited URL not in sitemap

https://namesilo.com missing from https://www.namesilo.com/sitemap.xml

```
https://www.namesilo.com/ https://www.namesilo.com/support/v2 https://www.namesilo.com/domain/search-domains https://www.namesilo.com/domain/transfer-domains https://www.namesilo.com/Marketplace https://www.namesilo.com/pricing https://www.namesilo.com/whois https://www.namesilo.com/discounts-and-promotions https://www.namesilo.com/hosting https://www.namesilo.com/ssl https://www.namesilo.com/support/v2/articles/domain-manager/whois-privacy https://www.namesilo.com/email
```

### Duplicate sitemap URLs

https://www.namesilo.com/pricing, https://www.namesilo.com/hosting, https://www.namesilo.com/account/billing-manager, https://www.namesilo.com/tld/biz

### Rendering errors

desktop: Failed to load resource: the server responded with a status of 403 (); stateless: Failed to load resource: the server responded with a status of 403 (); mobile: Failed to load resource: the server responded with a status of 403 ()

```
desktop: Failed to load resource: the server responded with a status of 403 () stateless: Failed to load resource: the server responded with a status of 403 () mobile: Failed to load resource: the server responded with a status of 403 () mobile: %c%d font-size:0;color:transparent NaN
```

## Crawler access

| Agent | HTTP | Robots | Usable | Blocked |
| --- | --- | --- | --- | --- |
| Default HTTP Client | 403 | — | no | yes |
| Googlebot | 403 | — | no | yes |
| Googlebot Smartphone | 403 | — | no | yes |
| Bingbot | 403 | — | no | yes |
| OAI-SearchBot | 403 | — | no | yes |
| GPTBot | 403 | — | no | yes |
| ClaudeBot | 403 | — | no | yes |
| Claude-User | 403 | — | no | yes |
| PerplexityBot | 403 | — | no | yes |
| Perplexity-User | 403 | — | no | yes |
| Applebot | 403 | — | no | yes |
| Applebot-Extended | 403 | — | no | yes |
| Common Crawl | 403 | — | no | yes |

## Rendering

- **JS dependency:** LOW
- **Content added:** 0 chars
- **Content removed:** 0 chars
- **Schema injected:** no
- **Canonical changed:** no

## Fact parity

- Matched: 0
- Contradictory: 0
- Ambiguous: 0
- Stale: 0
- Human-only: 2
- Machine-only: 0

_Fact parity scores agreement across the 0 of 2 fact groups asserted in both layers. The other 2 are one-sided — a coverage gap, not a disagreement, and they do not move the score._

| Status | Visible | Machine |
| --- | --- | --- |
| HUMAN_ONLY | Attention Required! \| Cloudflare \| Sorry, you have been blocked |  |
| HUMAN_ONLY | what you were doing when this page came up and the Cloudflare Ray ID found at th… |  |

## Fact ledger

| Subject | Predicate | Object | Source | Provenance | Cost |
| --- | --- | --- | --- | --- | --- |
| https://namesilo.com | hasTitle | Attention Required! \| Cloudflare | visible_html | PROVENANCE_KNOWN | 0 |
| https://namesilo.com | hasHeading | Sorry, you have been blocked | visible_html | PROVENANCE_KNOWN | 0 |
| Please | include | what you were doing when this page came up and the Cloudflare Ray ID found at th… | visible_html | PROVENANCE_KNOWN | 0 |

## Indexability

- **State:** NOINDEX

## Tickets

### P0 — Bot friction on fetch on /

Response looks like a challenge, WAF, or access wall

- **Current:** <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]>    <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>
<title>Attention Required! | Cloudflare</title>
<meta charset="UTF-8" />
<meta
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check FETCH-CHALLENGE must not FAIL

### P2 — No parseable JSON-LD graph on /

Structured identity is missing for machines

- **Current:** (see evidence)
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check SCHEMA must not FAIL

### P2 — Missing canonical on /

Page does not declare a canonical URL

- **Current:** (see evidence)
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check CANONICAL-MISSING must not FAIL

### P2 — robots.txt missing or unreadable on /

HTTP 403 for https://namesilo.com/robots.txt

- **Current:** (see evidence)
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check ROBOTS-MISSING must not FAIL

### P2 — Audited URL not in sitemap on /

https://namesilo.com missing from https://www.namesilo.com/sitemap.xml

- **Current:** https://www.namesilo.com/
https://www.namesilo.com/support/v2
https://www.namesilo.com/domain/search-domains
https://www.namesilo.com/domain/transfer-domains
https://www.namesilo.com/Marketplace
https://www.namesilo.com/pricing
https://www.namesilo.com/whois
https://www.namesilo.com/discounts-and-promotions
https://www.namesilo.com/hosting
https://www.namesilo.com/ssl
https://www.namesilo.com/support/v2/articles/domain-manager/whois-privacy
https://www.namesilo.com/email
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check SITEMAP must not FAIL

### P2 — Duplicate sitemap URLs on /

https://www.namesilo.com/pricing, https://www.namesilo.com/hosting, https://www.namesilo.com/account/billing-manager, https://www.namesilo.com/tld/biz

- **Current:** (see evidence)
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check SITEMAP must not FAIL

### P0 — noindex present on /

noindex, nofollow

- **Current:** (see evidence)
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check INDEX-NOINDEX must not FAIL

### P0 — Non-indexable HTTP state on /

BOT_CHALLENGE

- **Current:** (see evidence)
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check INDEX-STATUS must not FAIL

### P0 — SALIENCE_CONFLICT on /

Title "Attention Required! | Cloudflare" vs H1 "Sorry, you have been blocked" vs body "Please enable cookies. Sorry, you have been blocked You are unable to access nam" (no schema)

- **Current:** Please enable cookies. Sorry, you have been blocked You are unable to access namesilo.com Why have I been blocked? This website is using a security service to protect itself from online attacks. The a
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check SALIENCE-CONFLICT must not FAIL

### P2 — Rendering errors on /

desktop: Failed to load resource: the server responded with a status of 403 (); stateless: Failed to load resource: the server responded with a status of 403 (); mobile: Failed to load resource: the server responded with a status of 403 ()

- **Current:** desktop: Failed to load resource: the server responded with a status of 403 ()
stateless: Failed to load resource: the server responded with a status of 403 ()
mobile: Failed to load resource: the server responded with a status of 403 ()
mobile: %c%d font-size:0;color:transparent NaN
- **Expected:** Machine-readable, consistent, first-HTML representation of the fact
- **Acceptance:** ingest audit https://namesilo.com — check RENDER-ERROR must not FAIL

---

Paste this into an editor or agent chat. Treat scores as measurement, not ranking.