AI-ready website, for AI search and agents
A website machines can read.
Buyers increasingly arrive through AI assistants, and AI tools increasingly read websites on their behalf. A site built for human readers alone gives them little to work with. We rebuild or restructure yours so machines can read it and act on it, while it stays fast and clear for people.
Assistant visit
Continuous
Visit
A buyer's AI assistant lands on your site.
Read
llms.txtStructured data tells it exactly what you sell.
Extract
Offer, pricing, and proof, machine-readable.
Cite
Your company shows up in the answer.
The buyer
Arrives already convinced.
What happens on your site after handover.
What the build delivers
- Audit: how AI assistants and agents read your site today, and where they fail
- Rebuild or restructure on a fast, modern stack with clean redirects
- Structured data, machine-readable content, and llms.txt on every key page
- Performance pass: fast loads, clean mobile, accessibility basics
- A complete redirect map, reviewed before go-live, so every URL that earns traffic keeps its destination
- Handover: your team edits content without a developer
The living example
mapular.ai is built exactly this way: structured data on every page, machine-readable content, llms.txt, fast static rendering. AI tools parse this site correctly because it was built for them as much as for you. Your site can work the same way.
Same terms as everything we ship: fixed price, you own everything (code, content, accounts, documentation), and your team is trained to run it after handover.
What we migrate from
Most builds start on one of these. Every URL gets a redirect map, reviewed before go-live, so nothing that earns traffic today loses its destination.
Typical starting points
- WordPress
- Webflow
- Wix
- Squarespace
- Jimdo
- TYPO3
- Contao
- Drupal
- Custom / legacy CMS
Rebuilt on fast, AI-readable foundations such as Next.js or Astro. If your current platform can be made machine-readable in place, we restructure instead of migrating: the audit decides.
True of every build we do
- Fixed price
- Quoted once after the diagnosis, invoiced once. No day rates and no running meter.
- Criteria in writing
- We agree what the system has to do, and how it will be measured, before anything is built.
- It ships when it passes
- Tested on your data against those criteria. Until it passes, we keep working at no extra cost.
- You own everything
- Code, prompts, data, accounts, documentation. Yours from day one, so there is nothing to be locked into.
- Your team runs it
- Training and a handover built for people who did not write it. If you never speak to us again, it keeps working.
How you buy it
The same three steps for every job we take on. You can stop after either of the first two.
Step 1
Diagnosis
EUR 4,900, two weeks
What this work costs you today, what a system would take off your team, and a fixed quote with the acceptance criteria written down. Credited in full against a build that starts within 90 days. If it finds no job worth building, you get the fee back.
Step 2
Build
from EUR 14,900, fixed after the diagnosis
Built into the tools you already run, so there is no new platform to adopt. Tested against the criteria we wrote down, on your data. It ships when it passes, with training and full ownership.
Step 3
Run
optional
The answer to who owns it after we leave: monitoring, exception handling, and changes as the business changes. You own the system either way and your team is trained to run it, so this is a choice rather than a dependency.
See it in your situation
Questions buyers ask
Will we lose our search rankings?
That is the risk we design against. Every URL on the current site is inventoried and mapped to its new home before anything goes live, redirects are tested against the map, and the pages that earn your traffic today keep their content and their intent. Rankings usually move because a migration drops pages or changes URLs silently; that is what the map prevents.
Do we have to move off WordPress?
Not necessarily. The audit decides. If your current platform can be made machine-readable in place, we restructure it instead of migrating, which is cheaper and less disruptive. We only recommend a rebuild when the platform itself is what makes the site unreadable.
What does AI-ready actually mean?
Concretely: structured data that states your offers, prices and facts in machine-readable form, an llms.txt that gives AI tools a clean summary of what you do, semantic HTML instead of visual soup, fast server-rendered pages, and content that answers the questions buyers actually ask. Then we test it: we put your pages in front of AI tools and check whether they can state your offer and price correctly.
Can our team still edit content afterwards?
Yes, that is part of the handover. Your team edits content without a developer, and you own the code, the content, the accounts and the documentation. Nothing about the setup requires us afterwards.
How long does it take?
The audit is quick. The build itself depends on how many pages earn traffic and how much content needs restructuring rather than moving; your fixed quote states the timeline for your site before anything starts.
If the bigger problem is what happens after the visit, that is lead research and follow-up. Not sure which comes first? The two-week diagnosis exists to answer exactly that.
Is your site readable to the tools your buyers use?
25 minutes. We look at your site the way an AI agent does and tell you honestly what a build would fix, and what it would cost.