The short version: Using vibe coding, I had a website that looked finished within an hour. A technical review turned up 15 flaws: in search visibility, data protection, tracking and the contact form. Most of them were invisible in the browser. AI tools like Bolt build what you describe. What you don't describe is left to chance.
I wanted to share my new blog article about the ChatGPT business profile on LinkedIn. The preview, however, didn't show the article but my homepage: its title, its image, its description.
Yet at first glance, my freshly AI-built website looked flawless.
My experiment: rebuilding ibloom.at with Bolt
I have been building websites since 2003. I know how much work goes into a good one. Now tools like Bolt promise that describing a website is enough. AI takes care of the rest. This approach is called "vibe coding". The term was coined in early 2025 by AI researcher Andrej Karpathy, and it captures the essence: you no longer program, you describe. Websites are just one use case, and far from the most important one. Above all, vibe coding is used to build apps, internal tools, automations and prototypes.
I was curious and, frankly, sceptical too. So I ran the experiment on the one website where I answer to no one: my own.
A website in one hour
The result impressed me. My only instruction to Bolt was to modernise the site, with no guidance on design or structure. After one hour, there was a website that looked finished: a modern look, responsive design for phone and tablet, blog, portfolio, contact form. Even the second language was added at the push of a button. Concept, design and implementation in WordPress would have taken me weeks.
My first thought was: now anyone can do this.
15 flaws my AI-built website was hiding
Then I reviewed the site. The way I have reviewed every client website for over 20 years: not just with my eyes, but also with the tools that show what happens beneath the surface. And with the knowledge of where to look. Here is what I found:
Social media and Google
- LinkedIn showed my homepage for every article. Anyone who wanted to share a blog post was in fact sharing the homepage.
- To search engines, the site was empty. The server delivered the same empty base page for every URL. The text was only assembled in the browser via JavaScript. Visitors don't notice. But many search engines and AI tools don't run JavaScript and see nothing but an empty page. Bolt reported the issue as fixed. The source code, however, showed that the page was still empty.
- Titles and descriptions for Google were missing. In the source code, every subpage carried the homepage's title.
- Every page silently redirected. Google received conflicting signals about which URL was the right one.
- The error page wasn't one. Anyone who entered a wrong URL ended up on the blog without notice. Google never learned that the address didn't exist.
- The headings in the articles were structured incorrectly. Visually unnoticeable, but Google and screen readers were missing a structural level.
Two languages
- The language switcher led nowhere. Anyone switching an article to English got "Article not found".
- Google didn't recognise the translations. The references between the German and English versions were missing.
Data protection
- The cookie banner had no effect. Visitors could decline tracking and were counted anyway.
- Every visit sent the visitor's IP address to Google. Fonts were loaded directly from Google before anyone had consented. In German-speaking countries, this is a well-known trigger for legal warning letters.
Tracking and enquiries
- Google Analytics stayed empty, even though the setup seemed correct. Behind it were five independent errors.
- The contact form looked finished. In reality, it sent nothing: I had to set up the sending in the background myself.
- The form exposed internal error messages. When something went wrong, any visitor could read technical details not meant for the public.
Images
- The images weren't actually on the new site. Bolt had merely linked them from the old one. They would all have disappeared when the domain moved.
- 150 images had no fixed size. Content visibly shifted while the page was loading.
And the AI itself? It repeatedly reported "done and verified", even when that wasn't true.
Fifteen problems, most of them invisible in the browser.
Why AI-built websites are often not finished
I am not an AI sceptic. I keep working with Bolt. Many of these flaws aren't Bolt's fault but stem from the way such tools build websites. And from the way we describe our requirements. My instruction to Bolt, after all, was simply: modernise.
But AI builds what you describe. What you don't describe, because you don't know about it, is left to chance. And that is exactly where the flaws lie that later cost you visitors, enquiries or, in the worst case, a legal warning.
Psychology has a name for this: the Dunning-Kruger effect. People with little knowledge of a field find it hard to judge what they are missing, and therefore tend to rate their result as good. That is what makes "now anyone can do this" so deceptive: the website looks finished, so it seems finished.
A website that looks finished is far from finished.
Frequently asked questions about vibe coding and AI-built websites
What is vibe coding?
With vibe coding, you describe to an AI in everyday language what an app, a tool or a website should do and what it should look like. The AI writes the code itself. Well-known tools include Bolt, Lovable, v0 and Replit.
Can you create a website with AI that is actually finished?
A website that looks finished: yes, often within a few hours. A website that is found on Google, complies with data protection law and reliably delivers enquiries: not without a review. In my test, I found 15 flaws, most of them invisible.
Is an AI-built website GDPR-compliant?
Not automatically. On my site, the cookie banner counted visitors even after they had declined, and fonts were loaded from Google without consent. Neither is visible on the site itself. You have to check for it specifically.
How do I check whether my AI-built website has flaws?
Three quick tests to start with:
- Open a subpage and press Ctrl+U (Cmd+Option+U on a Mac). Do you see your text and a page title of its own? Or almost nothing?
- Test an article in the LinkedIn Post Inspector. Does the article appear, or your homepage?
- Submit your contact form and check whether the message actually arrives.
If one of these tests fails, there is usually more to find.
What comes next
Over the coming weeks, I will work through these points one by one: how to recognise the problem, why it is so easily overlooked and how I solved it. Clear and accessible, no technical background needed.
Next episode: what Google, LinkedIn and ChatGPT see of your website, and why that is often something completely different from what you see.
Have you built your website with Bolt, Lovable, v0, Replit or a similar tool and want to know whether it delivers what it promises? Get in touch.



