A new site from an AI builder - what next?

An AI builder gives you a good-looking site in an hour. That is a genuine breakthrough - a few years ago the same result meant weeks of work and several thousand zloty. The catch is that a website is not just what you see. And the things you do not see are exactly where the trouble appears after launch.

This is not a piece against builders. Wix, Framer, Durable, Lovable or v0 can produce something that looks professional in minutes. This is a piece about what happens the day after launch - when the site is live, but nobody has handled the layer the builder never mentions, because there is no way to click it.

A builder gives you a site, not a foundation

AI is great at generating the visible layer: layout, copy, sections, colours. It does not deal with what sits underneath - hosting, the domain, email, indexing, security and ownership. The client gets a car with a beautiful body and does not know whether there is an engine under the hood or just a dummy.

As long as the site merely „exists", everything is fine. The trouble starts when it has to do something: win clients from search, take submissions from a form, send confirmations by email, load fast on a phone and not break the law. That is when it turns out how much of this the builder actually handled.

What you do not see - and what decides everything

1. Hosting and platform lock-in

A builder site usually runs only on its own platform. You are not buying a website - you are renting a spot in someone else's system, billed monthly. Stop paying and the site disappears. Want to move it elsewhere and there is often no way, because there is no „site file" to take with you. Convenient at the start, expensive the moment you want out.

2. The domain and DNS

Ideally the domain is registered in your name, not on an agency's account or inside the builder's checkout. It is your single most important asset online. On top of that sit the DNS records that connect the domain to the site and to email. A builder usually attaches the site through a one-step „add this record" wizard - and nobody checks what happens to the rest along the way.

3. Company email

The most common slip-up. A builder makes a website, not email. An address like contact@yourcompany.com is a separate service, based on MX, SPF, DKIM and DMARC records on the same domain. If nobody sets them up, you either have no company email at all, or your messages land in recipients' spam - because the domain has no valid sending authorization.

4. SEO is not „type in keywords"

A builder generates titles and headings and calls it SEO. Real search visibility is a technical layer: loading speed, a correct URL structure, a sitemap, structured data, index control and redirects. It happens that a site ships with a noindex setting left over from staging, and Google simply does not show it. Pretty does not mean visible.

5. Performance and Core Web Vitals

Builders pile on scripts, tracking and heavy images that nobody optimizes. The result: the site loads slowly, especially on a phone, and Google treats speed as a ranking factor. A visitor waiting three seconds for a page to open usually does not wait - they go back to the results and click a competitor.

6. GDPR, cookies and forms

A contact form collects personal data. That comes with obligations: information about the data controller, consent, a privacy policy, a cookie banner with a real choice, and often a data processing agreement with the provider. A builder drops in a form with one click and mentions none of these. The responsibility stays with the company.

7. Analytics and measurement

Without analytics wired in correctly you do not know whether the site works at all: where people come from, what they click, how many enquiries it brings. Builders offer their own simplified stats, but they rarely give a real picture and even more rarely carry the history over when you change platforms. A site with no measurement is guessing instead of deciding.

8. Security and updates

„The site is on a platform, so it is safe" is a half-truth. An SSL certificate is usually there, but the rest depends on the provider: updates, protecting forms from spam and bots, limits, account access. One compromised panel password without two-factor login can be enough to lose control over the company's image online.

9. Backups and export

Where is the copy of your site? If the answer is „on the builder's platform", you do not have a copy - you have hope. An account failure, a dispute with the provider or a shut-down service, and you are left with nothing. A real backup is one you keep yourself and can restore independently of any single provider.

10. Who owns it

The most important question, usually asked last. If the site, the domain and the account sit with the contractor or inside the builder under their details, you do not have a website - you have access to one on someone else's terms. Ownership is the full set: the domain in your name, access to the hosting account, and - where possible - the site files in your hands.

When an AI builder really is enough

To be clear - not every company needs a custom site.

An AI builder is a good choice when:

• it is a simple brochure or event page that just needs to exist;
• speed and a minimal budget matter more than a position in Google;
• you do not collect sensitive data and do not build sales on it;
• you treat it as a temporary stage, deliberately, with a plan for later.

It is worth considering something more when:

• the site is meant to genuinely win clients from search;
• it needs to integrate with your systems, payments or a CRM;
• speed, availability and full control matter to you;
• and - the key point - you want the site to belong to you, not to the platform.

A modern, fast website does not have to cost a fortune today. But it does need someone to handle the layer the builder never shows.

A post-launch checklist

Run through it before you call the site finished:

1. Is the domain registered to my company and do I have access to it?
2. Does email on the domain work and not land in spam (MX, SPF, DKIM, DMARC)?
3. Is the site visible in Google, with no noindex left on?
4. Do I have analytics wired in and know where visitors come from?
5. Does the site have a privacy policy, a cookie banner and GDPR-compliant forms?
6. Does the site load fast on a phone?
7. Is there a backup independent of the platform?
8. Do I have access to every account (domain, hosting, builder) under my own details?
9. Can the site be exported or moved if the need arises?
10. Is the admin panel protected with two-factor login?

If the answer to several of these is „I don't know", it is not a company website yet - it is a nice draft that needs a foundation.

The bottom line

AI builders solved a problem that used to be real: having a good-looking site once took a lot of time and money. It is a great tool. But they traded a visible cost for a hidden one - pushed back in time and tucked into a layer you cannot see in the editor.

A website is not a picture. It is a domain, email, hosting, indexing, security, legal compliance and ownership. A builder gives you the first floor in an hour. The foundation has to be added separately - deliberately, before the site starts carrying the image and the sales of the company.

That is why the question after launch is not „does it look nice?" but: does this site actually belong to me, and can it do what I expect of it?

Got a site from a builder and not sure whether the foundation underneath is set up sensibly - domain, email, SEO, backups and access? A short audit usually takes a few hours and ends with a concrete list of things to fix. Get in touch.