The AI website:
built for the AI era.
When people search for a recommendation today, they often ask an AI directly. An AI website is built so that ChatGPT, Perplexity & Co. can find your business, cite it correctly and provide the right contact — in addition to Google, not instead of Google. That's the whole point: your site becomes a digital knowledge and service interface — readable for people, dockable for AI agents. We build these websites from Bolzano in South Tyrol — for businesses whose customers ask in German, Italian and English.
Three things a normal
website can't do.
Machine-readable profile
Your services, facts, and contact channels are available as structured data (llms.txt, brand.json, JSON-LD) — AI systems don't have to guess, they read. Learn about AI discoverability (GEO) →
Direct channel for AI agents
Via the MCP interface, AI assistants receive your approved facts and your direct contact — instead of outdated snippets from third-party sources. What agents really need →
Speed & clean signals
Under 200 ms median response time in the load test (August 2026, cached page), clean structure, no cookie banner — good groundwork for search engines and AI crawlers. Migrate from your old system →
What does ChatGPT know about your business today?
Before you build anything: we check for free what AI models currently output about you — and where your blind spots are. We'll discuss the results in a straight-talk conversation.
- Free AI-Ready Check
- Honest assessment, no pitch
- Even a "your page is fine" is an answer
Free · no commitment · results in the conversation
Request the AI-Ready Check →Further reading.

What an AI agent finds on your website: a five-step self-check
Before an AI agent reads your pages, it checks a handful of agreed addresses. You can check five of them yourself with a browser in a few minutes — with what each one means and how common it is.

Headless: why the way your website is built matters
A website today is not just looked at — it is queried. What a headless architecture changes, where it helps, and why we deliberately do not build purely headless.

When the interface disappears
Part of what is called a website with menus and forms today becomes pure query. What Zero UI means for a business — and how much of it is actually proven.
Frequently asked questions about the AI website.
Product & technology
What is btlabs Core, exactly?
btlabs Core is the platform we build websites on: fast, trilingual, free of cookie banners — and with your data in your hands.
The difference from a website builder lies underneath. Your content does not exist as finished pages but as structured data. From that the website for people is generated, and the same source answers the questions of search engines and AI assistants. One place to maintain, many channels.
btlabs Core is developed by Berger+Team, a freelancer collective in South Tyrol.
What's the difference between a classic CMS and a headless platform?
A classic CMS (WordPress and the like) is a construction kit: a prefab house, extended with plugins — and more fragile with every update. btlabs Core is a custom-built foundation: your content lives cleanly separated in the core system and is delivered through interfaces to any channel — website, AI assistant, app. In parallel, consistent, fast.
Why not just WordPress?
Yes — it's extremely flexible. The difference only shows up in day-to-day operation: to make your website readable for AI assistants and cleanly structured for search engines, you need several plugins and custom builds — each of which has to be found, set up, and maintained long-term. With btlabs Core, that's built in from the start, not retrofitted:
- Structured data (company, opening hours, prices, FAQ, etc.) are built into the foundation, not retrofitted via a plugin.
- Multilingualism doesn't run via a translation plugin, but is part of the structure — each language with its own texts, own URLs, own SEO.
- Analytics without cookie banner, because it comes cookieless by default, rather than being retrofitted via a consent tool. Separately, we track web visits and AI visits.
- An MCP interface, with which you can chat directly with your website — check, revise, or create content, in conversation with an AI, without clicking through an admin menu.
With WordPress, you'd have to find each of these building blocks individually, coordinate them, and keep them updated. With us, they belong together from the start.
Do I have to constantly update plugins like on WordPress?
No. One of the biggest security risks on the web is the plugin chaos of classic CMSs. With us there's no sprawling third-party plugin zoo you have to update yourself — everything is version-pinned and maintained by us. Security patches run automatically at server level — you don't have to lift a finger.
Multilingual — is that shaky?
No. German, Italian and English are anchored at the core — translated URLs, clean language signals, one editing interface. No after-the-fact translation workarounds. More: Multilingual website in detail.
What does my business gain if AI assistants can talk directly to my website?
Your details are ready exactly where people increasingly ask. Instead of an AI scraping your page and guessing, it reads exactly the content you've provided through an open interface — MCP (Model Context Protocol): services, opening hours, contact details. The aim: fewer incorrect statements about your business and correctly sourced citations — whether an AI uses this route is up to its provider. You stay in control — you decide which content is accessible, and every access is logged.
Is MCP access secure?
Yes. Every access is governed by permissions and every step is logged. With an access key you set per area and action what an assistant may do; a sign-in by consent gets full access, and deleting via chat is final.
How do I get MCP access for my website, and what's included?
We set up MCP access for you whenever you want it — it's part of expanding your website, not a mandatory component. This lets you, or an AI assistant of your choice, work directly with your own website: maintaining content, querying your own data, automating recurring tasks. We agree together on what can be accessed — opening hours, services or contact details, for example — and you always keep an overview of who accesses what and when.
The effort is manageable: one-off setup, then the access runs alongside your website. It's most worthwhile once you update content regularly or have recurring questions about your own data — then an AI can take over the routine work, on request.
Are my new pages reported to Google automatically?
No, not directly. With instant reporting switched on (a setting), every published address goes straight to Bing and the other participating search engines; Google does not take part in this procedure. Google finds your new page through the always-current sitemap on its next crawl — usually quickly, but not on demand.
What happens if the website goes down?
There are backups in separate locations, a copy outside the data centre, and outside monitoring that reports an outage. For getting back online we have set ourselves target values and we rehearse the procedure. This is not a contractually guaranteed availability, and we deliberately do not promise a percentage — we could not back it up.
Can I add a fourth language later?
Yes, but it is not a click. German, Italian and English are anchored in the core; a further language is a guided change that needs lead time — addresses, search engine signals and the admin interface all have to come along. It plans well; it does not happen spontaneously.
What is already built in technically for Google?
In btlabs Core, the technical groundwork for search engines is part of the foundation: XML sitemaps per content type, meaningful URLs with an automatic 301 redirect when you change an address, canonical tags, robots control per page and structured data following Schema.org. Every page is delivered fully rendered from the server, so even crawlers that don't execute JavaScript see the complete content. To be honest about it: instant notification via IndexNow reaches Bing and others, but not Google — and nobody can guarantee a ranking or stars in the search results.
How can I tell whether an AI mentions me?
For that, btlabs Core has the citation monitor. You set up to ten test questions — phrased the way your customers would ask, without naming you — and the system puts them to up to ten AI models. The result is sorted into four levels: not mentioned, mentioned, recommended or first choice, along with the websites mentioned instead. Two things belong to the picture: the monitor is switched off by default, and every run costs something through your own AI access. And the answers are samples, not a guarantee of what a customer will see tomorrow.
Do you also take care of link building and PR?
The platform itself doesn't build links or write press releases — that's handwork, not software. btlabs Core provides the groundwork: clean, unambiguous data about your business that others can easily link to and cite, and in the cockpit the backlinks Bing knows for your most important pages. Link building and PR themselves are something we offer as a service from Berger+Team, if you want it.
Do I need a Google Business Profile if my website already has everything?
Yes. The map in Google Search and Google Maps show details from the Business Profile, not from your website. The website gives search engines and AI systems unambiguous details about your business. What matters is that both say the same thing: you manage the profile at Google, and your website's name, address, phone and opening hours in one place in btlabs Core.
Why do name, address and phone number need to match everywhere?
Search engines and AI assistants piece together the details about your business from many sources: your website, your Business Profile, directories, review sites. If these sources contradict each other, search engines and assistants can't tell which is right — and at worst give out the wrong phone number or old opening hours. On your website, you maintain these details in one place in btlabs Core; the other sources you align by hand — again whenever something changes.
Do I have to submit my sitemap to Google myself?
It isn't required: your robots.txt names the sitemap, and Google finds it there on its own. It's still worth entering it once in Google Search Console — it's part of the setup, which takes about a quarter of an hour, and only there can you see whether Google was able to read it. After that there's nothing more to do: the sitemap updates itself as soon as you publish something.
No sales talk.
Eye to eye.
Write us what you have in mind — you'll get an honest assessment, no pitch.
- Response typically within 24 hours
- Free AI-Ready Check on request
- Non-binding & without obligation
Everything you need —
at a glance.
What btlabs Core can do, how to reach us directly, what it costs, and why you can trust us — the hard facts, compact and ready to expand.