AI on your content

Machine-readability assessment.

Find out what crawlers and assistants get from your site today, then decide what they should get.

Why it matters

A growing share of questions now goes to an assistant before a search engine. The assistant answers from what its crawler could fetch and read. If product data appears only after scripts run, if the edge turns the crawler away, or if two pages state two prices, the answer is wrong or missing, and you usually do not find out.

The assessment shows what those machines receive from your site today, measured on your pages.

What we assess

Discoverable

Robots rules, edge and bot settings, sitemaps, canonical addresses, and what your logs show about who reads the site.

Renderable

What a crawler receives without running scripts, on the pages that matter to your business.

Structured

Headings, structured data, tables and text alternatives: whether a machine can tell what each part means.

Addressable

Stable addresses, redirects, feeds and APIs, and whether permissions hold in every place content is copied to.

The full list of questions is public in the machine-readability checklist.

What you receive

  • A written report with a score from 0 to 100 for each of the four areas.
  • For every number, how and where it was measured, so your team can repeat it.
  • A short list of changes in order of impact, each with the effort we expect.
  • A walk-through of the findings with your team.

See the format on a real site: our own assessment of contentplane.net, with every check and every gap.

How it runs

  1. Scope.We agree which sites, languages and page types are in scope. Price and timing are fixed in writing before we start.
  2. Measure.We fetch your pages the way crawlers do and read your robots rules, sitemaps and markup. With your permission we also read edge and server logs.
  3. Report.You receive the report and we go through it with you.

What we need from you

The site addresses in scope and a contact who knows the platform. Read access to CDN or server logs makes the "Discoverable" score more precise, but it is optional.

After the report

Fix the findings yourselves, or ask us to. Most fixes fall under headless delivery or cloud, edge and pipelines. The assessment does not commit you to anything else.

The checks are made from the outside, the way a crawler sees your site, so any platform works. Where a fix sits inside the CMS, we are deepest on Optimizely and also work on Umbraco, Contentful and Strapi.

Start with the site address

Tell us which site, why the question came up, and when you need an answer.