# When the interface disappears Topic: [Machine-readable website](https://btlabs.dev/en/ai-website) > Assistants answer questions without anyone seeing the source. What that means for businesses, what is proven — and why websites stay precisely because of it. There is a kind of software you use every day and never see. The anti-lock braking system in a car, for instance. It has no interface, no menu, no settings dialogue. It works, and you notice it only because something did not happen. Part of what still exists today as a website with menus and forms is moving in the same direction. Not immediately and not everywhere — but far enough that it is worth asking what it means for a business. ## What "the disappearing interface" means The technical term is [Zero UI](https://btlabs.dev/en/glossary/zero-ui), sometimes generative interface. Two different developments sit behind it, and they are often lumped together. **The first: the interface is created at the moment of the request.** Instead of a fixed form with twelve fields, a system builds exactly the three fields needed for this case. That exists in early form already — language models can generate controls nobody designed in advance. **The second: there is no interface at all.** Someone asks an assistant whether your business is open on Saturday. The assistant answers. Your website was involved, but nobody saw it. The second development is the practically significant one, because it is already happening. ## What it does to your business If nobody sees your page any more, everything built to be looked at loses weight: the image at the top, the arrangement, the colour choices, the text that appears as you scroll. And everything built to be queried gains weight: are the opening hours stored so they can be read out? Does it say anywhere which location they apply to? Is there an unambiguous statement of what you do — and what you don't? That is not a design question but one of data management. And it is why we have been writing for a while that a website has two audiences: people and machines, with different demands on the same content. Important: the interface does not disappear everywhere. Someone choosing a craftsman usually still wants to see what they have built. The shift affects looking things up first — opening hours, availability, prices, responsibilities — and the decision itself only much later. ## A typical example A hospitality business in the Vinschgau valley had its opening hours clearly on the site — as a nicely set graphic in the header, part of the layout. Perfectly readable for guests. We asked three assistants whether it was open on Wednesdays. Two said the information was not available. One gave hours taken from a three-year-old directory entry that were no longer correct. The business had done nothing wrong. The information was there, current and well presented — just in a form a machine cannot open. Storing the same information additionally as [structured data](https://btlabs.dev/en/glossary/structured-data) was an afternoon's work. The graphic stayed where it was. That is the whole point: it is rarely about doing something differently. It is almost always about providing the same thing **additionally** in a second form. ## Why this is not new The shift looks more dramatic than it is if you take it for a break. It is more like the next step in a sequence. There was a time when a website was a brochure put online. Then the search engine arrived, and suddenly the same content had to be readable by a program that classifies it. Whoever thought only about design back then disappeared from the results. Then the phone became the primary device, and the same content had to work in the palm of a hand. Same content again, new form again. Now a third audience joins, one that neither scrolls nor clicks but queries. Anyone who knows the sequence sees it: it is not the website that dies. What died, every time, was the assumption that there is exactly one way to use it. ## What we know for certain — and what we don't This is a topic where much is asserted, so let's separate. **It is proven** that assistant systems answer questions without a click on the source. Several studies of zero-click searches show this — with different figures, but pointing the same way. **Plausible but unproven** is how fast this continues and which sectors are affected when. Anyone giving you a year is estimating. **False** is the claim that websites become superfluous. The opposite follows from the thing itself: if a machine answers, it needs a source. Whoever has no well-kept source of their own does not appear in the answer — or appears wrongly. ## What follows from this, practically Nothing dramatic. Preparing for a world with less interface looks exactly like a properly maintained website today: - The hard facts are there machine-readably, not only as running text or an image. - They do not contradict each other across website, map service and directories. - Every language version contains the same facts. - It states explicitly what you do — and where your service ends. That is the same list as for [AI optimization](https://btlabs.dev/en/posts/ai-optimization-website-south-tyrol), and that is no coincidence: both are answers to the same shift. Whoever ensures today that their details are queryable is prepared for an interface that may no longer exist. The rest is observation. We keep an eye on this because we measure it — not because we know how fast it goes. --- Source: https://btlabs.dev/en/posts/when-the-interface-disappears Last-Modified: 2026-10-18T07:00:00.971Z Languages: [de](https://btlabs.dev/llms/de/posts/wenn-die-oberflaeche-verschwindet) · [it](https://btlabs.dev/llms/it/posts/quando-l-interfaccia-scompare) See also: [llms.txt](https://btlabs.dev/llms.txt) · [ai.txt (Policy)](https://btlabs.dev/ai.txt) · [identity.json](https://btlabs.dev/identity.json)