HAUSE

PAGES MACHINES CANNOT READ

A person sees the argument.
A machine gets the shell.

Strip a page to its text. If the answer disappears, the page never had one — it had a rendering of one.

Why can't answer engines read my beautifully designed page?

Because the meaning lives in the interaction. Canvas coordinates, animation states and content revealed only on click are invisible to a crawler, an answer engine or an agent browser: they get the chrome and none of the argument. HAUSE treats legibility as part of the grammar — an answer-first block with a stable anchor, structured data projected from the same records the page renders, ARIA state on every instrument, and a text fallback that survives the interaction being removed.

01 / EXPERIENCE THE DIFFERENCE

The meaning must survive the surface.

ONE FICTIONAL RECORD / THREE PROJECTIONS

Remove a layer. Check what survives.
01A02A03A04A05A06A07A08A09B10B

Did every listener prefer room A?

No. In this fictional ten-person listening study, eight listeners chose room A and two chose room B. The record supports a majority preference for A, but contradicts the claim that every listener preferred it.

QUESTION

Did every listener prefer room A?

No. In this fictional ten-person listening study, eight listeners chose room A and two chose room B. The record supports a majority preference for A, but contradicts the claim that every listener preferred it.

Responses: A, A, A, A, A, A, A, A, B, B

This is a text projection of the supplied record, not a live crawler or an extraction audit.

{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "Did every listener prefer room A?",
    "url": "https://hause.design/problems/pages-machines-cannot-read#reader-record",
    "answerCount": 1,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "No. In this fictional ten-person listening study, eight listeners chose room A and two chose room B. The record supports a majority preference for A, but contradicts the claim that every listener preferred it."
    }
  }
}

Generated by HAUSE’s qaLd helper from the same question and answer. This illustrative payload is displayed, not added as another claim to the page’s head.

The presentation changes. The question, the answer and its limits do not. This demonstrates consistency—not guaranteed indexing.

02 / HOW YOU MEET IT

Strip the page to text, and it should still answer the question it was designed to answer.

The page ranks for nothing it is actually about, and an answer engine quotes someone's thin paragraph over your interactive explanation. The paragraph was legible. The explanation was a canvas. Both were about the same thing; only one of them said so in a way a machine could carry away.

03 / BENEATH THE SURFACE

Why the failure keeps returning.

Design systems stop at the visual layer, so legibility is delegated to something bolted on afterwards that can only describe the page from outside — a meta description guessing at what the page argues. Meanwhile the best version of the page is the one a person operates, which is precisely the version a machine cannot follow. Nothing forces the two to be the same page, so they drift apart in the direction of whichever audience the team can see.

TAKE THE RESPONSE WITH YOU

Give it a form.

Answer

The question asked the way people ask it, answered first — one lift-able paragraph beneath the editorial surface, addressable by anchor.

Excerpt

Someone else's words, typeset — verbatim source material with its markdown rendered and its trims marked.

Snippet

A labeled block of code or terminal output, verbatim on the ink — the on-ramp form, promoted when two sites needed the same shape.

Lens

One concept at several depths — the explanation, the object, the clause — on one URL, with the reader's depth remembered.

PUBLISHED 31 AUG 2026 · REVISED 9 SEP 2026 · VERSION 1.1

CITE

site build fb3ec31 · built 2026-09-26

CITE THIS

Article · 1.1

Hay, C. (2026). Pages machines cannot read. In HAUSE — the problems (Version 1.1). hause.design. https://hause.design/problems/pages-machines-cannot-read

An argument is a published object: dated, versioned, and referenceable — which is the subject of one of these pages and the practice of all of them.

HAUSE · THE SPECIMEN BOOK / 2026

GITHUB →VINDEX3.ORG →CHRISHAYUK →