AI Readiness Assessment
64 judgements need a named person in the organisation to confirm, because they turn on what you know to be true rather than anything measurement can settle: whether a claim is supported, whether a page is still current, which of two versions is the one to quote. In order, they cover: who is answerable for this content; is it still true today; can each claim be backed; does our published content agree; will the right meaning come across; can someone reach it and act on it. An answer recorded against each, with a name and a date, is what turns published content into governed content.
Once the foundations are sound and the content is governed, the visibility stage measures how AI systems and agents actually find the estate: which pages they reach, how often, and how the organisation is represented when they answer questions about it, tracked over time. Building visibility on unconfirmed foundations only amplifies whatever is wrong, which is why it comes last.
How much of your content is reachable and readable, rather than blocked, buried or missing. Higher is better.
Where your content could lead an AI system to state something incorrect. Only direct routes to a wrong answer count here.
Anyone asking for this site, a person on a phone or an AI system building an answer, is either let in or turned away, in milliseconds, by machinery most organisations never see. An AI system refused here gets nothing at all: to that system the organisation simply does not answer.
The door changes without notice: a security setting, a network change or a new crawler policy can close it silently. It is measured live on the day of assessment, and it is worth watching continuously rather than once.
3 of the 4 people are served, and so are the 15 AI systems.
Whether the estate can be reached and read at all: access rules, links, redirects, sitemap, transport.
| Check | Result | Evidence | |||||||
|---|---|---|---|---|---|---|---|---|---|
| DS01 | warning | robots.txt returns 404; no directives served; crawlers assume allow-all | |||||||
What we check The site publishes a robots.txt file and it can be fetched and read. What good looks like The site publishes a robots.txt that can be fetched and read. Why it matters A missing or broken robots file leaves the rules of access undefined, and access decisions then get made without them. What we found on this page robots.txt returns 404; no directives served; crawlers assume allow-all The evidence, taken from the page as served The access-rules file, as the site answered for it
The address robots.txt was asked for. It is the file a site uses to tell automated readers what they may read.
| |||||||||
| DS23 | warning | sitemap.xml not found (status=404); discovery relies on links alone | |||||||
What we check The site publishes a sitemap at the standard address and it returns successfully. What good looks like The site publishes a sitemap at the standard address and it returns successfully. Why it matters Without one, discovery of the site rests on links alone, so anything poorly linked is easy to miss entirely. What we found on this page sitemap.xml not found (status=404); discovery relies on links alone The evidence, taken from the page as served The sitemap, as the site answered for it
The address sitemap.xml was asked for. It is the file a site uses to list its own pages.
| |||||||||
Passing checks are omitted here; the full record is in the exports.
The highest-priority pages, chosen from the site's own signals of importance.
| Check | Result | Evidence | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DS17 | fail | the page states no preferred address for itself, so duplicate copies compete to be the one cited | |||||||||||
What we check Each page names one preferred address for itself, its canonical link. What good looks like Each page names one preferred address for itself. Why it matters With no preferred address stated, duplicate copies compete and the version that ends up cited is arbitrary. What we found on this page the page states no preferred address for itself, so duplicate copies compete to be the one cited The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a tag naming the page's preferred address. <head> <meta charset="utf-8"/> <title>Unceasing Digital</title> <meta name="viewport" content="width=device-width, initial-scale=1"/> <link rel="stylesheet" href="style.css"/> </head> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: each page names one preferred address for itself. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 3 out of a possible 5, because it is one of the checks that decide how cleanly content can be read once reached, so it carries a middle weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| CT31 | warning | the page carries no description of itself in its head | |||||||||||
What we check The page provides a meta description, the short summary offered alongside its title. What good looks like The page provides a meta description. Why it matters Absent, the page gives up its one documented summary field, though Google rewrites these freely anyway. What we found on this page the page carries no description of itself in its head The evidence, taken from the page as served The head of this page, as served
The head of the page was read for a description tag. <head> <meta charset="utf-8"/> <title>Unceasing Digital</title> <meta name="viewport" content="width=device-width, initial-scale=1"/> <link rel="stylesheet" href="style.css"/> </head> | |||||||||||||
| CT16 | warning | the page carries no structured data block stating what it is (not required; a hygiene signal) | |||||||||||
What we check The page carries structured data, the machine-readable summary of what it describes. What good looks like The page carries structured data summarising what it describes. Why it matters Vendors document this as optional rather than required, so its absence is a small forfeit and no more. What we found on this page the page carries no structured data block stating what it is (not required; a hygiene signal) The evidence, taken from the page as served The head of this page, as served
The page was read for a structured data block describing what the page is. <head> <meta charset="utf-8"/> <title>Unceasing Digital</title> <meta name="viewport" content="width=device-width, initial-scale=1"/> <link rel="stylesheet" href="style.css"/> </head> | |||||||||||||
| CT04 | warning | the page carries no date, so there is nothing on it saying how current its content is | |||||||||||
What we check The page carries a date, ideally written into the markup rather than sitting only in the text. What good looks like The page carries a date, ideally written into the markup rather than sitting only in the text. Why it matters An undated page gives nothing to weigh its age against, so old and new material are treated alike. What we found on this page the page carries no date, so there is nothing on it saying how current its content is The evidence, taken from the page as served The head of this page, as served
The head of the page and the page's own text were read for a date. <head> <meta charset="utf-8"/> <title>Unceasing Digital</title> <meta name="viewport" content="width=device-width, initial-scale=1"/> <link rel="stylesheet" href="style.css"/> </head> | |||||||||||||
| AR13 | warning | only 72 characters of this page read as its own content, so either the page is thin or its own words cannot be told apart from the parts repeated across the site | |||||||||||
What we check Whether the page's main content is marked off from the navigation and footer around it. What good looks like A main or article region marks the primary content off from the navigation and footer around it. Why it matters Pulling the page's text returns menus and legal footers mixed with the substance, so the answer arrives buried in noise. What we found on this page only 72 characters of this page read as its own content, so either the page is thin or its own words cannot be told apart from the parts repeated across the site The evidence, taken from the page as served The main text extracted from the page, as served
Unceasing Digital provides software development and IT support services. | |||||||||||||
| CT35 | warning | the page carries no copyright line in the content as served, so there is nothing on it to date it by, and an absent copyright line is one of the marks of a copied template | |||||||||||
What we check The copyright line at the foot of the page, and the year it states. What good looks like The copyright line states the current year. Why it matters A copyright year in the past reads as a page nobody has attended to, and it is the usual sign of a template copied from somewhere else. Either way an AI treats the content as stale and can present old material as current. What we found on this page the page carries no copyright line in the content as served, so there is nothing on it to date it by, and an absent copyright line is one of the marks of a copied template The evidence, taken from the page as served The foot of this page, as served
The foot of the page was read for a copyright line. <footer> Unceasing Digital Ltd, company number 11883080 registered in England and Wales at 66 Paul Street, London EC2A 4NA<br/> Unceasing Digital (EU) Oร, registry number 16059662 registered in Estonia at Sakala tn 7-2, Kesklinna linnaosa, Harju maakond, EE10141 Tallinn </footer> | |||||||||||||
| CT24 | warning | the page's own content runs to 72 characters | |||||||||||
What we check The page holds enough main text to be substantive, measured against a 400 character floor. What good looks like The page holds enough main text to be substantive. Why it matters A page of a few sentences offers almost nothing to quote, so it adds little beyond its own existence. What we found on this page the page's own content runs to 72 characters The evidence, taken from the page as served How much of this page is its own content
Counted from the page as served, before any script runs. The page's own content is the part it marks out as its main content; where it marks out none, the whole of its text is counted.
| |||||||||||||
| CT13 | warning | main content is 20% of the page's text; the shared furniture around it dominates what is read out | |||||||||||
What we check How much of the page's text sits in the main content region rather than in surrounding furniture. What good looks like Most of the page's text sits in its main content region rather than in the surrounding furniture. Why it matters When the main region is a small slice of the page, what is pulled out is mostly menus and boilerplate. What we found on this page main content is 20% of the page's text; the shared furniture around it dominates what is read out The evidence, taken from the page as served How much of this page is its own content
Counted from the page as served, before any script runs. The rest is the menus, header and foot-of-page text that appear on other pages of the site as well.
| |||||||||||||
| CT14 | fail | the page does not mark out its navigation, so the menu links run into the page's own words when it is read | |||||||||||
What we check Navigation is marked as navigation, so its links separate cleanly from the body text. What good looks like Navigation is marked as navigation, so its links separate cleanly from the body text. Why it matters Unmarked menus read as ordinary sentences once the page is extracted, padding each passage with link text. What we found on this page the page does not mark out its navigation, so the menu links run into the page's own words when it is read The evidence, taken from the page as served The blocks this page marks out, as served
The page was read for the block that marks out its navigation. <header> <main> <footer> Why it reads as a failure The result is set by what was measured on this item, quoted above, and not by an opinion of it. It reads as a failure because the standard was not met: navigation is marked as navigation, so its links separate cleanly from the body text. What it does to the figure This check counts toward the readiness figure for this item, at a weight of 1 out of a possible 5, because it is one of the supporting checks, so it carries the lightest weight in the figure for this item. Why it moves the misinformation reading This failure could contribute to a wrong answer in some cases, so it raises the misinformation reading for this item. Where an item carries more than one such failure, the readings compound and the item moves up the scale. What this result does not say This says what was found on this item at the time of assessment, and nothing beyond it: it is not a statement about the rest of the estate, and it does not judge the quality of the content itself. | |||||||||||||
| AJ05 | warning | no site-search control detected on this page | |||||||||||
What we check Whether a search box for the site is present in the page as it is served. What good looks like A search box is present in the served markup, so the site's own content can be queried directly. Why it matters With no search box on the page, its links are the only route from here into the rest of the site. What we found on this page no site-search control detected on this page The evidence, taken from the page as served The head of this page, as served
The page was read for a search box: a search form, a control named for search, or a box labelled as one. <head> <meta charset="utf-8"/> <title>Unceasing Digital</title> <meta name="viewport" content="width=device-width, initial-scale=1"/> <link rel="stylesheet" href="style.css"/> </head> | |||||||||||||
No PDF documents were part of this assessment.
This report is Stage 1, Foundations: each automated test the engine can run without human input, so there is a usable result at the first stage. Governance (owner-confirmed truth) and Visibility (how AI agents find the estate) are later stages and are shown greyed above.
What was assessed. 1 pages were assessed, selected from 1 reviewed using the site's own signals of importance (its navigation, homepage links, most-linked pages, sitemap, and any llms.txt file), and the first 0 PDF documents found were assessed separately. The industry in the header is classified from the site's own content. The traffic classification comes from a recognised top-sites list or a connected traffic provider; it reads NA when the domain is not connected to a traffic source.
Header identity signals. The regulated sector and listed company values are inferred from the same crawled content, and shown here so the header can stay to the answer alone. Regulated sector reads “None found”: no regulator statements, and the established sector carries no statutory regulator. Listed company reads “Not established”: no clear public-listing indicators in the sampled pages.
AI readiness is the weighted share of checks that passed, reported separately for pages and for PDF documents because each is reached and corrected differently. Grade A checks decide whether content can be reached and read at all; grade B whether it is understood correctly; grade C support reliability. A measured score is scaled into a ceiling when an access gate binds it (for example the site blocking AI crawlers at its edge): content that cannot be reached is not partially ready. Scores never read exactly 25, 50, 75 or 100, because those are buckets, not measurements.
Likelihood of misinformation is a band, given as a worst case (the highest any single item or estate-wide finding reaches) and a typical position across the pages or documents. Only checks whose failure is a direct route to a wrong answer carry a band; the rest affect readiness only.
| Band | Range | Meaning |
|---|---|---|
| Likely zero | 0-5% | No failing misinformation-bearing checks. |
| Very little | 6-25% | Unlikely to cause wrong information. |
| Likely | 26-50% | Could contribute to wrong information in some cases. |
| Very likely | 51-75% | A real and common route to wrong information. |
| Extremely likely | 76-100% | A frequent and direct cause of wrong information. |
Of the register's 187 checks, 63 ran automatically in this Foundations stage. 64 are governance questions for the next stage. The remainder need organisation-supplied data or an external service; each check that did not run is listed in the exports.
About us
We have been doing this for 25 years. For the last two years, we have been training AI to understand and map AI Readiness (fundamentals, governance, visibility), against our unique dataset of more than 3.7 trillion data points.
Who’s talking about us