The Machine That Visits Once

When a machine lands on your page, you don't know what it is. It might be a small model on someone's phone, working inside a tight memory budget. It might be a full-scale agent with browsing tools. It might be a plain scraper that never runs a model at all. It might be a language model that never saw your page, only a converted text copy with the layout and scripts stripped out. It might be a coding agent that fetches the page once and moves on.

Each of these reads something different. One sees your raw markup. One sees a text projection. One consults the accessibility tree. One parses your structured metadata. None of them see your visual design. The colour, the position, the size, the carefully weighted hero image: invisible to every single one.

And here's the part that changes how you design: it will visit once.

Humans Follow Journeys. Machines Don't

Your human visitors need guiding. People can't take in everything at once, so a good site walks them through it: a landing page, a benefits page, a pricing page, a form. That journey is real design work and it matters.

Machines are the opposite. A machine hits one page, takes what it can read, and leaves. It won't click through to the explainer or scroll back to the page where you defined your terms. If your meaning only emerges across the journey, a machine that lands mid-journey gets nothing.

So every page has to stand alone for the machine while the journey still works for the human. That's not a trade-off. They're complementary designs on the same pages, and the sites that get both right are the ones machines quote correctly.

Redundancy Is the Design Answer

You can't predict the visitor, so you stop trying. Carry the same meaning in several channels at once: in the page's semantic structure, in the accessibility tree, in the metadata, in plain text. Whichever channel a visitor can read, the meaning survives the trip.

A page that keeps its meaning in one channel fails every visitor that lacks that channel. Prices that live only in an image fail everyone who can't see pixels. A button that's really a styled box fails everyone who reads structure instead of looking at it. The fix is never exotic. It's redundancy.

What the Tree Shows That Your Eyes Don't

The accessibility tree is the version of your page that screen readers consume, and several kinds of machine visitor read it too. It's also where a visual review misses the most, because the page can look perfect while the tree is full of holes.

Our audit reads each page the way a tree consumer does. The same defects come up on site after site:

• Buttons that aren't buttons. A styled box wired to respond to clicks. It looks like a button and works fine for a mouse user, yet the tree holds nothing you can press.
• Links that all say the same thing. "Read more. Read more. Read more." Strip away the layout, as every machine does, and no one can tell where any of them go.
• Form fields labelled by their placeholder. The hint vanishes the moment someone types, and in a text projection it was never a label at all.
• Data locked inside images. The price list, the chart, the opening hours: pixels only. No agent and no screen reader can read them.
• Wiring that points at nothing. A label that references an element that isn't on the page. The page renders fine. The name silently resolves to nothing.

The pattern behind the patterns is the one worth paying for: these defects repeat, because they live in templates. A clickable box that appears on forty pages isn't forty problems. It's one line in one component, and one fix clears it everywhere. Our reports group findings that way deliberately: fix the template once, not the pages one by one.

And because screen readers consume the same tree the machines do, every one of these fixes serves your human visitors and your machine visitors at the same time. That's the quiet economy of the whole approach. One fix, every audience.

Look at Your Own Tree

You can inspect this yourself, today, on any page you own. Right-click the page and choose Inspect. In the Elements panel, click the >> icon, choose Accessibility, and toggle "Show Accessibility Tree". What appears is what tree consumers receive. If a control or a heading you care about is missing from that view, it's missing for them.

Chrome's DevTools will even help you reason about what you find: the AI Assistance panel accepts "Review accessibility" against any element you select.

Try it on your highest-value page. Find your buy button in the tree. Find your price. If you can't, the machine that visits once can't either, and it already left.