Proof, not promises

We scored our own site — then fixed it

The Answer Engine makes your site the one ChatGPT, Gemini and Google's AI Overviews recommend. Before we sold it, we ran it on ourselves. Here's the whole scorecard — every signal, before and after, including the ones we haven't finished.

out of 100 — AI-search readiness

The scorecard

Ten signals, one hundred points

We fetch a site the way an AI crawler does — raw HTML, no JavaScript — and score ten signals that decide whether a model can find, read, trust and quote it. Here's how our own site moved.

SignalWhat it measuresMaxBeforeAfter
Structured dataSchema.org JSON-LD — Organization, Service, FAQ, Person — present, valid and cross-linked15014
AI-crawler accessrobots.txt welcomes GPTBot, ClaudeBot, PerplexityBot and Google-Extended; sitemap present12212
Answer-format contentFAQ blocks and concise, quotable sentences a model can lift verbatim121011
Server-rendered factsKey facts in the initial HTML, readable without running JavaScript121212
llms.txtAn /llms.txt manifest declaring the site's purpose and key pages10010
MetadataUnique title and description per page, canonical URL, hreflang, OpenGraph10510
Semantic HTML & headingsOne h1, logical heading order, landmarks, descriptive links977
Entity clarityConsistent name, address and contact — a clear who, what and where847
AccessibilityAlt text, ARIA, language and contrast — which also help machines read it755
FreshnessVisible and structured last-updated dates; sitemap lastmod513
Total1004691

We scored our sister company justidosolutions.com the same way and got about 83 — independently reconstructing its published 84/100. That tells us the rubric is honest, not flattering.

What we changed

How we got from 46 to 91

  • Structured data (0 → 14): Organization and WebSite schema across the whole site, plus FAQ, Service and founder Person data — all cross-linked so a model reads one connected entity.
  • AI-crawler access (2 → 12): a robots file that welcomes the AI crawlers by name, and a full sitemap with language alternates.
  • llms.txt (0 → 10): a plain-language manifest at /llms.txt telling AI tools what we do and where the key pages are, in English and German.
  • Metadata (5 → 10): a canonical URL and hreflang on every page, and proper page-specific social cards.
  • Entity clarity (4 → 7): both our legal entities and our contact details now sit in the structured data.
  • Freshness (1 → 3): real last-modified dates in the sitemap.
Still improving

What we haven't finished

We'd rather show you this than hide it. Three signals are still short of full marks on our own site:

  • Headings (7/9): one demo mock-up on our homepage adds a heading our outline doesn't need — a quick clean-up.
  • Accessibility (5/7): a pass to label every inline icon for screen readers is still on the list.
  • Freshness (3/5): we put last-updated dates in the sitemap, but not yet inside the structured data.
Method

How we measured

Each site is fetched as raw HTML — no JavaScript run — along with its robots.txt, sitemap and llms.txt, then scored signal by signal against the rubric above. The 'after' score is measured on the live, deployed site. Anyone can reproduce it by re-fetching the page and re-applying the same ten checks.