How does a platform stay visible when the first reader is a machine?

Increasingly, a buyer meets you through an AI answer before they meet your site. ChatGPT, Perplexity, Google's AI Overviews and the assistants built on the same models read your platform, extract what survives, and quote it whether you are in the room or not. These pages are the working standards TBSCG applies to every page it ships, published in full so anyone can adopt them. Not marketing. Standards.

Published to be adopted.

Practical articles on enterprise content platforms, alongside our published standards and the live machine-readable layer. Take what is useful.

The standard

The Scrape-Bias Page Standard

Eight rules for building a page so machines quote it correctly: question-shaped headings, answer-first openings, visible FAQs, valid structured data, entity consistency. The standard behind every page on this site.

The field guide

AEO for Enterprise platforms

How answer engines read a platform, what actually moves visibility, what does not, how to measure presence in AI answers, and where regulated platforms need extra care.

The machine layer

llms.txt, live

A plain-text index at the domain root that tells AI crawlers what this firm is and where the canonical pages sit. This card links to the real file, not a description of one. Readable in thirty seconds.

.NET 8 End of Support: What It Means for Your CMS

.NET 8 and .NET 9 support ends 10 November 2026. What owners of Optimizely CMS 12, Umbraco 13 and Kentico Xperience 13 should check and decide.

Who actually builds your platform?

Why the people who scope enterprise platform work should be the people who build it, and what changes when they are.

Why do digital platforms lose value without anyone noticing?

How workarounds, unused capabilities and operational drag erode a platform’s value long before anything triggers an alert.

What does spreadsheet translation really cost?

The full cost of translating web content through spreadsheets, once language lag, errors, uneven campaigns and coordination are counted.

Can AI assistants read your website?

Whether an assistant can read, quote and recommend a site is increasingly decided by how its content is structured inside the CMS.

Getting your content platform ready for AI agents

What agent-ready means for an enterprise CMS and DAM: content models, metadata, permissions, APIs, audit trails and retrieval, and what to fix first.

The cost of standing still on a content platform

Why no decision is the most common outcome for an underperforming CMS or DAM, what to measure, and how to present the case for change to a CFO.

Standards work better in the open.

We would rather the pages machines quote, ours and everyone else's, be built to answer correctly. Publication also keeps us honest: every claim on this site can be checked against the rules on these pages.

01 The first reader changed

Buyers ask an assistant before they search, and often instead of searching. The answer is assembled from whichever pages extract cleanly. Visibility is now decided before anyone reaches your site.

02 Extraction has a bias

Answer engines favour pages that answer first, structure cleanly and mean one thing. Ambiguity is a tax: every place a page makes the machine guess is a place the answer can come out wrong.

03 Principles over tricks

The channels are young and they change monthly. The principles underneath, clear answers, clean structure, consistent identity, are stable. We publish the principles, not the tricks.

04 We apply it first

These are not aspirations. Each rule in the standard is in force on this platform: question-shaped headings, visible FAQs, JSON-LD on every page, llms.txt at the root. The proof is in the source.

Freshly printed newspapers stacked at the end of a press line
A standard only does its work once it leaves the building.

Put the standards to work.

Machine visibility is one property of a healthy platform, not a separate project. Here is where this work most often joins the rest.

Frequently asked questions.

What is answer engine optimisation (AEO)?

AEO is the practice of building pages so that AI answer engines, such as ChatGPT, Perplexity and Google's AI Overviews, can extract, attribute and quote them correctly. Where SEO optimises for a ranked list of links, AEO optimises for being the answer itself.

How is AEO different from SEO?

SEO earns a position on a results page that a person scans. AEO earns a place inside a machine-written answer. The disciplines overlap, clean structure and structured data help both, but AEO rewards answer-first writing and entity consistency far more heavily than rank ever did.

What is llms.txt?

A plain-text file at the domain root that gives AI crawlers a curated index of the site: what the organisation is, in one line, and where the canonical pages sit. It is a convention rather than a formal standard, and it costs almost nothing to publish. Ours is live at /llms.txt.

Does structured data still matter?

Yes, more than before. Valid JSON-LD such as Service, Product, TechArticle and FAQPage gives answer engines unambiguous facts to extract instead of prose to interpret. Schema that was once a rich-snippet tactic is now a primary machine-reading surface.

Where should an enterprise start with AEO?

With measurement, then the basics. Find out whether the platform appears in AI answers for the queries that matter, then fix the foundations: one question-shaped h1 per page, answer-first openings, visible FAQs, valid JSON-LD and an llms.txt index. The Health & Value Assessment scores this as part of its AI-readiness dimension.

Find out what the machines see.

The Health & Value Assessment includes an AI-readiness dimension: whether your platform is structured for machine readers and visible in the answers your buyers already read. Five days, led by senior consultants.