qibbopress.com

No JSON-LD and no microdata anywhere on the page.

Structured data is the only part of your page an agent can consume without interpretation. Everything else it has to infer, and inference is where it invents facts about you.

Copy<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your company",
  "url": "https://example.com",
  "description": "One sentence an assistant can quote.",
  "sameAs": ["https://x.com/you", "https://github.com/you"]
}
</script>

The page contains no <a href> elements at all.

An agent moves through a site by following hrefs. With none, this page is a dead end and everything behind it is undiscoverable.

No /llms.txt or /llms-full.txt at https://qibbopress.com.

Without it, an assistant deciding what your site is about crawls whatever it happens to find. llms.txt is the cheapest way to control that first impression, and today most of your competitors do not have one either.

Copy# Example Inc

> One paragraph an assistant can quote verbatim about what you do and who it is for.

## Docs
- [Quickstart](https://example.com/docs/quickstart): Get running in five minutes.
- [API reference](https://example.com/docs/api): Every endpoint with examples.

## Product
- [Pricing](https://example.com/pricing): Plans, limits and exact prices.
- [Changelog](https://example.com/changelog): What shipped, newest first.

## Policies
- [Terms](https://example.com/terms)
- [Contact](https://example.com/contact): support@example.com

No sitemap found at https://qibbopress.com/sitemap_index.xml or in robots.txt.

Without a sitemap, discovery depends entirely on crawlable links. Any page not reachable by a plain <a href> is invisible.

CopySitemap: https://example.com/sitemap.xml

The page has no <title> element, or it is empty.

The title is the label an assistant uses when it lists you among its sources. Without one you are cited as a bare URL, which almost nobody clicks.

Copy<title>Agent Experience Scanner - AXRAY</title>

Only 0 words of readable text reached the agent.

There is not enough here for an assistant to build an answer from, so it will use someone else as the source.

The raw HTML contains 0 words of text.

This is the single most expensive AX failure. To a crawling agent the page is blank, so it cannot be summarised, cited or ranked at all.

The page has no headings at all.

Without an h1 the agent has no anchor for the document topic and falls back to the title tag or the URL slug.

No <meta name="description"> on the page.

It is the one sentence you get to write yourself. Without it the assistant summarises you from whatever text it happened to read first, which is often your cookie banner.

Copy<meta name="description" content="Scan any URL and see exactly what an AI agent can read, understand and act on. Get an AX score and a prioritised fix list.">

Only 0 internal links on the page.

A page with no onward links is a cul-de-sac. Everything you publish that is not linked from a crawlable page effectively does not exist.

0.0% of the payload is readable text.

The document is almost entirely machinery. An agent truncating this page will likely truncate before reaching any of your content.

Missing: og:title, og:description, og:type, og:url, og:image.

When a page is JavaScript-heavy or truncated, Open Graph tags are frequently the only clean summary an agent gets.

Copy<meta property="og:title" content="Page title">
<meta property="og:description" content="One sentence.">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/page">
<meta property="og:image" content="https://example.com/og.png">

The request failed: fetch failed

Agents fetch with a short timeout and no retry budget. A request that fails once is a page that does not exist as far as they are concerned.

No well-known agent manifest, no OpenAPI reference and no developer docs link found.

This is the frontier of AX: sites that publish a machine-callable surface get used by agents directly instead of being scraped approximately.

Copy{
  "name": "Example",
  "description": "What an agent can do with this service.",
  "documentation": "https://example.com/docs",
  "endpoints": [
    { "type": "openapi", "url": "https://example.com/openapi.json" }
  ]
}

No mailto, tel, contact link or contactPoint data found.

"How do I get in touch with them" is one of the most common agent-mediated questions about a company. Make the answer machine-readable.

Copy{"@type":"Organization","contactPoint":[{"@type":"ContactPoint","contactType":"customer support","email":"support@example.com","url":"https://example.com/contact"}]}

Only 0 headings on the page.

Agents chunk long pages by heading. A page with no outline is chunked arbitrarily and quoted out of context.

No <main> element. Landmarks present: none.

Without a main landmark an extractor has to guess your content boundary heuristically, and on marketing pages it usually guesses the header.

Copy<main>
  <article>
    <h1>…</h1>
    …
  </article>
</main>

The <html> element has no lang attribute.

Without it an assistant guesses the language, and guesses wrong on short or mixed-language pages, producing garbled quotes.

Copy<html lang="en">

No /.well-known/mcp.json and no ai-plugin.json.

This is the highest-leverage unclaimed slot on the web right now. The sites that publish a callable surface get used directly instead of guessed at.

Copy{
  "schema_version": "2025-06-18",
  "name": "example",
  "description": "Search the catalogue and check availability.",
  "documentation": "https://example.com/docs",
  "servers": [
    { "type": "http", "url": "https://mcp.example.com" }
  ],
  "contact": "support@example.com"
}

No Last-Modified, ETag, dateModified or <time> element anywhere.

Agents deprioritise content they cannot date, and re-fetch undated pages more often, which costs you bandwidth for nothing.

Copy{"@type":"Article","datePublished":"2026-01-15","dateModified":"2026-08-01"}

No Organization structured data on the page.

Entity resolution is how assistants decide two mentions are the same company. Unresolved entities get merged with, or mistaken for, someone else.

Copy{"@context":"https://schema.org","@type":"Organization","name":"Example Inc","url":"https://example.com","logo":"https://example.com/logo.png","sameAs":["https://x.com/example","https://github.com/example","https://www.linkedin.com/company/example"]}

robots.txt has no per-agent AI groups, and there is no TDM reservation or noai directive anywhere.

With no explicit policy, every operator applies its own default to you and you have no documented position if you later object.

Copy# Answer engines: allowed, they cite and link us.
User-agent: OAI-SearchBot
User-agent: PerplexityBot
User-agent: Claude-SearchBot
User-agent: DuckAssistBot
Allow: /

# User-triggered fetches: allowed, a person is waiting.
User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Perplexity-User
Allow: /

# Training crawlers: your call. This example allows them.
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Google-Extended
Allow: /

No <link rel="canonical"> on the page.

Agents dedupe sources by canonical URL. Without one, the same content behind different query strings competes with itself and dilutes every citation.

Copy<link rel="canonical" href="https://qibbopress.com/">

No crawlable GET search form and no SearchAction.

Without a GET-addressable search, an agent looking for one specific page on your site has to fetch dozens of pages to find it, and usually gives up first.

No rel="license" link and no license or copyright fields in structured data.

If you care how your content is reused, say so where machines can read it. A footer copyright line is not machine-readable.

Copy<link rel="license" href="https://example.com/terms">

No /.well-known/security.txt.

It is the standard machine-readable place to say who to contact. Agents and researchers both look there first.

CopyContact: mailto:security@example.com
Expires: 2027-01-01T00:00:00.000Z
Preferred-Languages: en

No twitter:* card tags.

Several agents fall back to card metadata when they cannot extract the body reliably.

Copy<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Page title">
<meta name="twitter:description" content="One sentence.">

No robots.txt served (HTTP 0).

Without a robots.txt every crawler applies its own defaults and you have no way to express a preference. It is also the file most agents read first.

CopyUser-agent: *
Allow: /

Sitemap: https://example.com/sitemap.xml

No Content-Type header was returned.

Agents use the header to decide whether to parse the body as HTML at all.

The response body was the real page, not a challenge or block screen.

Bot protection that cannot tell a shopping assistant from a scraper silently removes you from AI answers, with no error anyone on your team will ever see.

No robots.txt, so nothing is disallowed by default.

These crawlers are the ones that put your link inside an AI answer. Blocking them removes the referral traffic, not just the training use.

No robots.txt, so nothing is disallowed by default.

These fetches happen because a human just pasted your link into an assistant. A block here fails in front of a real person who wanted to read you.

No robots.txt, so nothing is disallowed by default.

AI Overviews and Copilot answers are grounded on the classic search index. Blocking Googlebot or Bingbot now also removes you from AI surfaces.

No robots meta tag or X-Robots-Tag header.

noindex and nosnippet remove you from the surfaces that would otherwise quote and link you.

The URL served content directly with no redirect.

Every hop costs latency and some agents cap redirects at two or three.

Full response in 12 ms.

Agents fetch many pages per answer and drop the slow ones. Speed is a ranking input you control.

0 KB of HTML, 0% of it inline script.

Agents truncate long documents. Anything past the cut simply is not read.

Site root.

Assistants show the URL next to the citation, and readable URLs get clicked more than opaque ids.

Live user-agent probing was not run for this scan.

Some sites answer 200 to a generic client and 403 to a named AI crawler. Only a live probe finds that.

No content images on this page.

Agents cannot see images. Alt text is the only description they get.

Too few structural elements to judge.

Not needed: the page already server-renders its content.

No JSON-LD to validate.

No JSON-LD to evaluate.

No prices detected in the page text.

Top-level page; breadcrumbs are not expected.

No microdata; JSON-LD is the preferred format anyway.

Too few links to judge.

No interactive form fields on this page.

No interactive form fields on this page.

No text-like fields on this page.

No button-like controls detected.

No llms.txt to evaluate.