Requested https://belgium.be/, graded at the address above. 1 redirect followed.

Not your site? See what AI can read on yours. Scan your site free

ChatGPT sees none of the words on this page.

AI Visibility Score Not judged

34/ 100, grade F

We scored this page by our old rules, used before 13 November 2026. A new scan judges it by today's rules.

Your next move

Do this first

Here are the 2 things to do, in order.

  1. Ask whoever built your site to send all the words with the page, not add them later.

    See the details

  2. Check the web address, since it sends people to a different site.

    See the details

Show the details How we got this: the score, the bots we checked, and the proof for each fix.

Where this score comes from

Four weighted parts, and the arithmetic is on the page. This report was scored before 13 November 2026, when the score was these four parts; it is shown by that rule so its numbers add up. Nothing here is rounded in your favour, and anything the scan could not measure says so rather than being folded in as a guess.

ChatGPT sees 0% of this page

AI crawlers see little of what your visitors see.

A critical issue is holding this page back. The grade above does not tell the whole story: start with the critical item below.

Part Weight Measured Points
Prose Parity 50% 0% 0
Crawler access 25% 90% 22.5
Structure 15% 77% 11.5
Structured data 10% 0% 0
0 + 22.5 + 11.5 + 0 34 Read the methodology

Retrievability, measured at 0%, sits beside the score rather than inside it: it checks whether the rendered words can be recovered from the crawler's HTML at all, including from JSON data blocks, and it informs the findings below without adding points.

This page scores higher than 5% of the 1,182 sites we have measured. That puts it in the bottom 10 percent. See the index.

What to know about this measurement 2 notes on what was and was not measured

  • The page has no semantic main content containers; parity was measured on all visible text.
  • server-level blocking observed for ClaudeBot, Bytespider, Amazonbot: -0.10 (confidence-scaled)

The rendered page No screenshot: this report is past the image retention window

No screenshot: images are kept for 24 hours and this report is older than that. Re-scan the page for a fresh one. The text comparison above is kept for the life of the report and is unaffected.

Bot access matrix 3 of 15 AI crawlers blocked in a way that costs you

Every AI crawler we track, and what your site does when it asks for this page. Turning a model training crawler away is a choice, not a fault, so those are marked apart from the blocks that cost you score.

  • 3 blocked in a way that costs you
  • 12 can reach this page

3 of 15 AI crawlers were turned away in a way that costs you: ClaudeBot, Bytespider, Amazonbot. All were refused only in our test, and the real crawler may pass. Start there.

  • 15 / 15 named crawler tokens allowed in robots.txt
  • 9 / 12 live probes got the page (HTTP 2xx)
  • 3 rule-only or not probed, so no server response to read

Reaching a page is not the same as reading it. The crawlers marked allowed here are let in and receive the same HTML a browser gets. On this page that HTML is almost empty: the words only appear once code runs in a visitor's browser. What they can actually read is scored separately: see Main content is invisible to AI crawlers below.

Bot access matrix: the AI crawlers your robots.txt or your server treats differently.
Crawler Purpose Status robots.txt Server response
ClaudeBot Anthropic Purpose Training Refused in our test robots.txtallowed Server responseblocked at the server (HTTP 520)
Bytespider ByteDance Purpose Training Refused in our test robots.txtallowed Server responseblocked at the server (HTTP 520)
Amazonbot Amazon Purpose Training Refused in our test robots.txtallowed Server responseblocked at the server (HTTP 520)
12 other crawlers reach this page normally. Show them
The AI crawlers that reach this page normally.
Crawler Purpose Status robots.txt Server response
GPTBot OpenAI Purpose Training Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
OAI-SearchBot OpenAI Purpose AI search Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
ChatGPT-User OpenAI Purpose Assistant Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
Claude-SearchBot Anthropic Purpose AI search Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
Claude-User Anthropic Purpose Assistant Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
anthropic-ai Anthropic Purpose Training Allowed robots.txtallowed Server responseno request user agent exists to test
PerplexityBot Perplexity Purpose AI search Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
Perplexity-User Perplexity Purpose Assistant Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
Google-Extended Google Purpose Training Allowed robots.txtallowed Server responseno request user agent exists to test
Applebot-Extended Apple Purpose Training Allowed robots.txtallowed Server responseno request user agent exists to test
Meta-ExternalAgent Meta Purpose Training Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
CCBot Common Crawl Purpose Training Reaches your page robots.txtallowed Server responsesame page served (HTTP 200)
  • Refused in our test

    Your robots.txt welcomes this crawler, but your server answered its user agent with a block. Nothing in your rules asked for that, so this may be blanket bot defense reacting to our test request rather than a rule aimed at this crawler. The scan records it at low confidence and counts it at reduced weight, but it still costs Access score: if the real crawler is refused too, it cannot read your page. Servers that verify crawler IPs will block a spoofed user agent from any scanner; the real crawler may pass.

  • Reaches your page

    Your robots.txt allows this crawler and your server returned it the same page it returns to a browser. This measures access, not content: whether that HTML is readable without JavaScript is a separate check, scored as retrievability when the page can be graded.

  • Allowed

    Your robots.txt allows this token. It is a robots.txt token only: it sends no user agent of its own, so there is no server response to test and none is implied.

Page basics checklist 5 of 7 basics in place

Page basics, checked against what an AI crawler receives rather than the rendered page. This report was scored before 13 November 2026, when these fed the Structure part of the score above.

  • Title tag The page has a title in its HTML. Pass
  • Meta description No meta description. Search results can show it under your link; add one under 155 characters. Needs work
  • One H1 heading Exactly one main heading. Pass
  • Canonical URL A canonical link names the page's official address. Pass
  • Heading coverage Headings break up the text. Pass
  • No wall of text No single block of text is very long. Pass
  • llms.txt No llms.txt. It is informational only, a nice-to-have rather than a ranking factor. Needs work
  • Structured data No JSON-LD structured data found. Whether AI tools use it is not something we measure; the entity section below has a copy-paste starting point if you want to add it. Needs work

What is holding you back, worst first

Ranked by severity, worst first. Start at the top: fix the critical items and the rest compounds.

Estimated gain is the sub-score arithmetic applied to this page, not a prediction about citations. Clearing the first item alone would move this page from 34 to at most 84.

Critical

Main content is invisible to AI crawlers

csr_blank up to +50

AI assistants cannot see what you sell or say, so when a buyer asks about your kind of business they get told about competitors whose pages are readable and you are left out entirely.

What this means for you

When an AI crawler visits your page it receives a nearly empty shell, because your words only appear after a browser runs the site's code, which crawlers do not do.

The fix, technically

Server-side render or statically generate the page so the main content ships in the initial HTML.

Evidence from your pageOnly 0% of the rendered main content exists in the initial HTML (36 rendered tokens vs 28 raw tokens).

Fix the rendering gap. We move the content AI engines miss into the initial HTML: server rendering, static generation, or hydration restructuring, measured before and after with this scanner.

Get a rendering audit
Major

Server-level blocking of AI crawler user agents

ua_enforcement +2.5

If the real crawlers are turned away too, they cannot read your page, so none of it reaches the AI tools they collect for.

What this means for you

In our test, your security or hosting layer turned away the AI crawlers named here before they reached your page.

The fix, technically

Requests with AI crawler user agents get blocked at the edge. Review CDN/WAF bot rules if you want AI visibility.

Evidence from your pageClaudeBot got HTTP 520; Bytespider got HTTP 520; Amazonbot got HTTP 520. Servers that verify crawler IPs will block a spoofed user agent from any scanner; the real crawler may pass.

Review your crawler access policy. We map which AI systems you are blocking, deliberately or by accident, and align robots.txt, CDN rules, and directives with the visibility you actually want.

Get an access review
Major

No structured data in the initial HTML

no_schema up to +10

Google documents using structured data for richer search results; whether AI assistants use it is not something we measure.

What this means for you

The page has no structured data: a machine-readable label of facts such as your business name, address or prices.

The fix, technically

Add JSON-LD (Organization plus the types matching your content) server-side.

Evidence from your pageNo JSON-LD blocks in the initial HTML.

Ship structured data that parses. We add server-rendered JSON-LD with the required properties for your content types, validated by the same checker that graded this page.

Get schema implemented
Minor

No meta description in the initial HTML

missing_meta_description +2.3

Google documents that it may show this line in its results; whether AI tools use it is not something we measure.

What this means for you

The page has no meta description, the short summary line search results can show under your link.

The fix, technically

Add a server-rendered meta description.

Evidence from your pageNo meta description in the initial HTML.

Make the page extraction friendly. Titles, headings, and block structure decide how retrieval systems chunk and quote you. We restructure pages so the right passages surface.

Get a structure pass
Minor

No llms.txt

no_llms_txt +1.2

Independent studies found no measurable effect from llms.txt, and whether any AI tool reads yours is not something we measure.

What this means for you

Your site has no llms.txt, an optional guide file for AI tools.

The fix, technically

Informational only. Independent 2026 data (Ahrefs, SE Ranking, Google documentation) shows no measurable citation effect from llms.txt. It is checked because it costs nothing and some assistants read it, but it moves neither crawling nor ranking.

Evidence from your pageNo llms.txt at the site root.

Minor

URL redirects off the original domain

offsite_redirect

The scores here describe that other site, so your own page is not the one AI is reading about you.

What this means for you

The web address you entered sends visitors to a different website.

The fix, technically

The scanned URL redirects to a different domain; scores describe the final target.

Evidence from your pagebelgium.be redirected to www.belgium.be (1 hop(s)).

Two ways to fix what this found

You are not guessing at this. Across 1,182 sites in our live AI Visibility Index, the average score is 74/100. This report shows exactly where belgium.be stands.

Do it yourself

Get your whole site audited with a reviewed, ranked fix plan you can hand to your dev, plus 3 months of monitoring. Delivered in 3 business days.

Tell us you want this

We are finishing this service. Say the word and you go first when it opens.

Just want to keep an eye on this page? Starter, $59/mo.

Have us do it

We implement every fix above and re-scan to prove the gain. We scope it on a short call first, so we only take work we can deliver.

Work with us to fix this

See six real sites measured this way

Crawler-view structured data

Entity confidence

We parsed the JSON-LD in the HTML a no-JavaScript crawler receives and checked five properties of the identity it declares. This measures your markup, not any AI system's behavior: nobody outside those systems can observe what they do with a given property, so nothing here is a prediction. Scored separately from your 34/100 score.

0/100 Not declared No identity node in the HTML a crawler receives. 0 of 5 signals present
  • Missing: Identity declaredNo JSON-LD in the crawler-view HTML, so there is no identity node to read. Add an Organization block with a name and an absolute url.
  • Missing: External identifiers (sameAs)Measured on the identity node, and no identity node was found. Declare one first, then add sameAs URLs to it.
  • Missing: Stable identifier (@id)Measured on the identity node, and no identity node was found. Declare one first, then give it an absolute @id.
  • Missing: Logo declaredMeasured on the identity node, and no identity node was found. Declare one first, then add logo as a full https URL.
  • Missing: Category declaredMeasured on the identity node, and no identity node was found. Declare one first, then state a category as a specific type, a standard industry code, or a resolvable additionalType URL.

Starting point for your identity block

Built from this scan: the URL we resolved, plus one property for each signal above that we did not find. Every REPLACE_ value is a placeholder, so edit them before you ship this. We do not guess names, logos, profile links or categories, so nothing here is invented.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.belgium.be/#organization",
  "name": "REPLACE_WITH_YOUR_ORGANIZATION_NAME",
  "url": "https://www.belgium.be/",
  "logo": "REPLACE_WITH_AN_ABSOLUTE_HTTPS_URL_TO_YOUR_LOGO",
  "sameAs": [
    "REPLACE_WITH_A_URL_THAT_IDENTIFIES_THE_SAME_ENTITY"
  ],
  "additionalType": "REPLACE_WITH_A_CATEGORY_URL_OR_DELETE_THIS_LINE"
}
</script>

What each signal measures, the weights, and the sample behind them: the methodology page.

llms.txt This site serves none

This site serves no llms.txt. Informational only. Independent 2026 data (Ahrefs, SE Ranking, Google documentation) shows no measurable citation effect from llms.txt. It is checked because it costs nothing and some assistants read it, but it moves neither crawling nor ranking.

Keywords and prompts

Derive the questions people ask AI assistants where this page could be the answer, scored by how much of each the page actually covers, then test whether a named model brings the brand up at all. The scan you are reading is free and anonymous; this check asks a real model live, so it asks for an email.

Not indexed; share this link freely. Save it as a PDF with your browser's print (Cmd or Ctrl + P) for a client-ready copy.

This homepage is 46 points short of the 80 that unlocks a score badge. Do this first lists the quickest fixes; scan again once they are live.

See if AI recommends you

We ask one AI engine three questions a buyer would ask about your kind of business, and show you whether belgium.be is named, who is named instead, and the sources cited. Free, one per email.

We use the email only to send that one link and to keep it to one free check per address.

Fixed something? Prove it.

We re-measure this page now and show the before and after side by side, including the parts that did not move. One re-check per report.

See how you stack up: compare belgium.be against a competitor.

Not measured on this run

What a paid plan adds for this page

These four tools run on belgium.be on any paid plan. They are listed as capabilities, not as a preview: none of it has been measured for this report, so nothing is shown. Everything above stays free.

  • Locked

    Prompt tracking over time

    Your prompt set re-run every week with the history kept, the competitors models name instead, and 10 prompts per run.

  • Locked

    Score history

    Every past score for this page in one dated chart, linked back to the report behind each point.

  • Locked

    Whole-site audit

    Every page on belgium.be checked and ranked worst first, with a CSV.

  • Locked

    API and MCP

    Run this same check from your own code, or from Claude and ChatGPT.

Starter is $59/mo and watches 1,000 pages across 10 sites. Nothing on this report is withheld to sell it. See what a plan adds

Keep belgium.be readable to AI

This report is a snapshot. Parity regressions are silent, because nothing looks wrong in a browser, so the way they get caught is a re-check after every deploy rather than a person remembering to look.

Free: get told if it slips

AI visibility drops silently after a redeploy or a CDN tweak. Get one email if belgium.be drops, plus a weekly summary either way. No spam.

Free tier watches 25 pages across 3 sites, re-checked weekly, with a drift alert when a page drops more than 6 points.

Starter · $59/mo

Or find out before your customers do

  • We tell you what broke, and what it cost you. Not just that a number moved: the words that stopped reaching crawlers, the crawler that lost access, and the likely reason.
  • Every week, on this page and up to 1,000 more, with the history to show when it happened
  • See the AI prompts this page could answer, and the keyword angles you are missing
  • Audit your whole site: every page checked, worst first, with a CSV
  • Your API + MCP key for code, Claude, and ChatGPT
See plans and pricing

Keep this report

The link is the report; nothing is gated behind this. If you want it in your inbox to forward or find again, we will send it.