If ChatGPT cannot explain what you do, you do not exist to the people asking it.
Your buyers ask an answer engine before they ask you. It replies using what it can read on your website. Most websites were built to be ranked by a search engine, not read by a machine that answers on your behalf.
Three month build · three waves · you own everything at handover
Search handed your buyer ten links. An answer engine hands them three names.
Your buyer types the question into ChatGPT or Perplexity, or reads the AI answer above the Google results, and gets back a few names with a reason attached to each. No page two. The comparing already happened somewhere they never saw.
Here is the part that stings. The engine built that shortlist by reading websites. If yours is hero images, a brochure and a contact form, there was nothing to read, nothing to quote, and your name was not in the answer. A competitor's was, often for no better reason than being easier to read.
If AI engines can read, trust and quote your site, you win the buyers who ask AI first.
Every part of this engagement exists to serve that one sentence. Nothing is in the scope because it is fashionable.
Where you are now, and where you end up.
Three months, three waves, one direction. The rail below is on-site readiness: the layer we control, measured from day zero so you can see it move.
-
Today
Answered by someone else
An engine asked about your category builds a shortlist from what it can read. Your site gives it very little to work with.
-
Month 1 · Foundation
Live and readable
- Rebuilt site, live on your hosting
- Structured data, llms.txt, robots, sitemap
- Answer-first copy on every core page
- Baseline measured before anything changes
-
Month 2 · Depth
Your answers, published
- Answer articles on the questions buyers really ask
- FAQ blocks and internal linking
- You approve the questions, your expert signs off the answers
-
Month 3 · Handover
Pointed at the gaps
- Content aimed where competitors are still cited
- Deployed and configured on your hosting account
- Code, content, assets and a maintenance guide
-
From here
The quotable one
You own a site engineered to be read, trusted and quoted, plus a measured record of what moved. Ongoing work is a choice you make with that record in hand.
Designed to take almost none of your time.
Email only, by design
One monthly report, plus short approval requests. No standing meetings. Every decision is a reply yes or no with a date and a stated default, so silence never stalls delivery.
Two gates, both yours
You approve the questions before we write. Your expert signs off the drafts before we publish. We own the research and the craft; accuracy stays with you.
Yours at handover, in full
Deployed to your hosting account. Code, content, assets and a maintenance guide are yours at the end. Nothing stops working if you walk away.
The retainer is a decision, not a default
Off-site AEO and ongoing content are optional. Decided together at the month three review, with the final report in front of both of us. Never priced in advance.
Two layers, reported together, every month.
They move at different speeds. Reporting only the fast one would flatter us, so you get both.
The input score
What we control, and what moves first. Your on-site AEO score, measured at baseline and again every month end with the same tooling.
Outcome signals
What follows, and what lags. These start near zero and climb as the work compounds.
- Whether engines name or cite you on a frozen set of real buyer prompts
- Search Console impressions and indexed pages
- GA4 organic sessions and AI-referral traffic
The honest part. AI visibility is engineered for, not guaranteed. We control the inputs, not the models. Progress is measured monthly against a fixed prompt set, and a month that goes sideways is reported as such.
At the end of month three, this is yours.
- A rebuilt website, live on your hosting, in your account, structured so an answer engine can parse it without guessing.
- The AEO infrastructure underneath it: structured data, llms.txt, robots and sitemap, canonical URLs, answer-first copy and a performance pass.
- A body of answer content covering the questions your buyers actually ask, researched and written by us, signed off by your own expert.
- Measurement you can read without a translator: a day zero baseline, a monthly report on both layers, and a final before and after.
- Every file, plus a maintenance guide, with no platform lock-in and no dependency on us continuing.
Tell us about your site.
Send us your website and what you sell. We will tell you whether an answer engine can currently make sense of it, what the rebuild involves, and what it costs, in writing, before anything starts. If you do not need this yet, we will say so.
Systems and sites we have shipped, with what each one was built to do.
The questions clients actually ask.
These are taken from real conversations, in the order they usually come up.
Who owns the website and the files after the project?
You do. Code, content, assets, hosting details and a maintenance guide are all handed over at the end of the build. There is no platform lock-in and nothing stays behind a Centaurtech login.
Who updates the site after launch?
Your team, for content. The site is built as static, text-native HTML, which is a large part of why answer engines can read it cleanly. Where your quote includes a content section such as News or a marketplace, your team publishes into it directly and there is no cap on how much you publish there. Structural changes, new page types and a fresh AEO push come back to us.
Do we have to come back to Centaurtech for every change?
No. Routine content is yours to edit. We handle structural work or a new AEO push, and a retainer is available if you want that handled continuously. It is an option, not a condition of the build.
Who approves the content?
You do, at two gates in every content wave, both by email. First you approve the list of questions we plan to answer. Then your named subject-matter expert signs off the drafted answers before anything publishes.
Centaurtech owns the research, the drafting and the optimisation. Sign-off on factual accuracy always stays with you, because it is your expertise being quoted.
What is on-site AEO versus off-site AEO, and which does this cover?
On-site AEO is everything on your own domain: structure, structured data, llms.txt, answer-first copy and articles. That is this engagement.
Off-site AEO is earning mentions and citations on the third-party sources answer engines already trust, plus continuous monitoring. That sits in the optional retainer afterwards, not in the build.
Will we actually show up in ChatGPT, Perplexity or Google AI Overviews?
That is the goal and the whole build is engineered for it, but nobody can promise it. AI visibility is engineered for, not guaranteed. We control the inputs, not the models.
What we commit to is making your site the clearest, most quotable source in your category and measuring what happens every month against a fixed prompt set. Anyone guaranteeing you a spot in an AI answer is guaranteeing something they do not control.
How do you measure results?
Two layers, reported together every month. Layer one is the on-site input score: what we control, measured against a baseline taken on day zero. Layer two is outcome signals: whether answer engines name or cite you on a frozen set of real buyer prompts, Search Console impressions, and GA4 organic and AI-referral traffic.
The prompt set never changes during the build. Rewriting the prompts to make a chart look better would make the trend meaningless, so we freeze them at baseline and reuse them verbatim.
How does communication run during the build?
By email, and deliberately so. One monthly report in a fixed format, plus short approval requests. Every decision is asked as a reply yes or no with a date and a stated default if you go quiet, so an unanswered email never stalls delivery.
No standing meetings are included. An optional wrap-up call at the end is fine if you want one.
How long does it take?
Three months, delivered in three monthly waves. The rebuilt site goes live in the first wave, so you are not waiting until the end to have something real. The pace comes from genuine constraints, mainly approval gates and content production, not from stretching the work out.
What happens after month three?
You have a finished site you own and a final report. From there, off-site AEO and ongoing content are available as an optional monthly retainer.
The level is decided together at the month three review with the final report in hand, which is deliberately the only sensible time to decide it. It is never priced in advance and it is never a condition of the build.
What does it cost?
It is scoped and quoted per engagement, because the honest answer depends on how many pages your business needs and how deep the content has to go. Tell us about your site and we will send a written quote with the page list, the content volume and the payment terms all named before anything starts.
What do you need from us?
Brand assets such as your logo, photos and product data. Access to your hosting so we can deploy to your own account. A named subject-matter expert who can sign off content. Access to Search Console and GA4 if you have them, so measurement covers both layers. Beyond that, approvals by email.
What if we already have a website we like?
Liking it and being readable by a machine are different tests, and plenty of good-looking sites fail the second one.
If your existing site is already structured well, the rebuild is lighter and the effort shifts toward content and structured data. If it is image-heavy, built on a page builder that outputs little real text, or spread thin across many shallow pages, the rebuild is where most of the value is. We tell you which one you are before you commit.
What is not included?
Not included. Domain registration, hosting fees, paid stock imagery and any third-party licences or subscriptions are outside this scope. These are arranged directly by you, or billed at cost if you would like us to handle them on your behalf.