Here is how to spot a vibe coded website in under five minutes: look for the identical centered-hero layout everyone gets by default, emoji doing the job of icons, placeholder text nobody replaced, a contact form that submits into the void, and a view-source full of chatty AI comments. Any two of those together and you are almost certainly looking at AI output that no human reviewed. We should know. We vibe code websites for a living, and the entire difference between our builds and the ones on our rescue bench is the review pass, not the generator.
Why would you even want to spot one? Three reasons come through our inbox. You hired an agency and want to know what you actually paid for. You are sizing up a competitor’s suspiciously fast redesign. Or your own weekend build is acting weird and you want to know how deep the problems go. Whatever brought you here, the nine signs below are the checklist we run in September 2026, followed by the code-level checks and what any of it costs to fix.
1. The hero you have seen a hundred times
Centered headline, one-line subhead, two buttons side by side, three feature cards below the fold, soft gradient background. That layout is the statistical average of the training data, and every default generation regresses to it. Human-built sites make odd choices somewhere. Unreviewed AI builds make the safe choice everywhere, which is its own kind of loud. We wrote a whole essay on why vibe coded websites look the same, and the sameness itself is the tell.
2. Emoji where icons should be
A rocket in the features grid, a lightbulb next to “our vision,” a handshake above the contact form. Models reach for emoji because they render everywhere without an icon library. Real projects almost always pick an icon set, any icon set. Emoji-as-infrastructure is the fastest visual tell on this list, and once you notice it you will see it in every AI-built SaaS page on the internet.
3. Placeholder text that survived launch
Search the page for “Lorem ipsum,” “Your Company,” “John Doe,” “123 Main Street,” and a phone number with 555 in the middle. Then check the footer year and the copyright name. AI generations ship with scaffolding text baked in, and owners who do not read their own site never swap it out. One restaurant site we rescued still promised “cuisine description here” in the third menu section, four months after launch.
4. The form that goes nowhere
This is the expensive one. The AI writes a valid-looking form, invents a backend endpoint that was never built, and the thing fails silently forever. Fill the form with a test message and see what happens. No confirmation, no error, no email, just a quiet page refresh? That is the signature defect of unreviewed vibe coding, and it is the first thing we test on every rescue diagnostic because it is the defect that costs owners actual customers.
5. View source: one giant file with narration
Right-click, View Page Source. A vibe coded static site is usually one enormous HTML file with the CSS inlined and comments that narrate the build: “Hero section starts here,” “You can replace this with your logo,” “TODO: connect form later.” Models write comments for the human they are talking to, not for the next developer. Working sites written by people have boring comments or none. Sites written by chat have a tour guide living in the markup.
6. Missing basics: favicon, titles, descriptions
Look at the browser tab. Default globe icon instead of a favicon? Every page titled the same thing, or worse, titled “Document”? No meta descriptions anywhere? Basics like these are invisible in a chat preview window, so they never get generated unless someone asked. It is also why these sites struggle on Google long before content quality even enters the conversation.
7. Specifics that are a little too smooth
Round-number stats with no source (“10,000+ happy customers”), testimonials from stock-photo faces with two first names, an address that adds a suite number to a real street, five founding team members who do not exist on LinkedIn. Models pad thin content with confident filler. Verify one claim and the whole facade usually comes down. This is the sign that should worry you most if you paid an agency, because it means nobody on their side read the site either.
8. Console errors and the odd-width collapse
Open DevTools, check the console: 404s for images that were never uploaded, a JavaScript error from a library that is referenced but not loaded. Then drag the browser window slowly from wide to narrow. AI layouts are usually fine at phone width and desktop width because those are the defaults it optimizes for, and they fall apart at tablet widths nobody prompted about. Overlapping nav, text running out of cards, a hero image cropping someone’s head off at 900 pixels.
9. The uniformity tell
Every card has the same corner radius. Every shadow is the same shadow. Every section has identical padding, every heading the same size jump. Human designers break their own systems on purpose at least once per page. Default AI output applies one design token set with perfect, eerie consistency. On its own this proves nothing, plenty of design systems are strict, but combined with two or three other signs it seals the diagnosis.
How to tell if a website is AI generated at the code level
The visual signs get you to “probably.” The code gets you to “definitely.” Run the URL through Wappalyzer and you will often see no CMS, no analytics, no framework, just bare HTML on a static host, which is the classic chat-export profile. Paste the page into the W3C validator: AI output validates suspiciously clean or fails in weird repeated patterns, rarely in between. Check the source for class names like “container mx-auto px-4” (default Tailwind everywhere) or fully inlined styles with hex colors repeated fifty times. And look at the image filenames: “hero-image-1.jpg” and “team-photo-placeholder.png” mean nobody ever renamed the scaffolding.
Is there a one-click detector for vibe coded websites?
Not a trustworthy one, as of September 2026. AI text detectors are notoriously unreliable even on plain prose, and nobody has shipped a serious “was this site vibe coded” scanner because the honest answer is often “partially.” What does exist: the technology-profile check through Wappalyzer described above, Lighthouse for the quality signature, and your own eyes on the nine signs. The manual checklist takes five minutes and beats every automated shortcut we have tested, mostly because the question you actually care about is not “did an AI write this” but “did a human ever read it.” No scanner measures that. The signs do.
What if the vibe coded website is yours?
First, no shame. The generation was the smart part; the missing piece is a review pass, and that is fixable in an afternoon. Triage by severity before spending anything.
| What you found | Severity | The honest fix |
|---|---|---|
| Emoji icons, same-y layout, uniformity | Cosmetic | DIY with a better prompt, free |
| Placeholder text, missing favicon and titles | Embarrassing | An hour of find-and-replace, free |
| Dead form, console errors, broken widths | Costing you customers | Rescue diagnostic $450, credited toward fixes from $950 |
| Invented facts and fake testimonials, live | Legal exposure | Take them down today, then rebuild the page |
The first two rows are genuinely DIY territory: rerun the site through a longer, more specific prompt and read the output this time. Our vibe coding mistakes post covers the patterns to avoid on the second pass. Rows three and four are where a professional pays for itself, and our calm triage guide walks through what to check before you spend a dollar.
Spotting vibe coded websites: quick answers
Is a vibe coded website automatically bad?
No. We build vibe coded websites for paying clients and they score 90+ on Lighthouse and rank on Google. The quality split is not AI versus human, it is reviewed versus unreviewed. Every sign on this list is really a symptom of “nobody looked at the output,” which is a process failure a human can fix in hours.
Can Google tell if a website is AI generated?
Google says it rewards helpful content regardless of how it was produced, and our testing backs that up: reviewed AI-built sites index and rank fine. What tanks rankings is the stuff on this list, thin invented content, missing titles, broken pages. We covered the ranking question properly in do AI generated websites rank on Google.
How do I check if the agency I paid vibe coded my website?
Ask two questions. One: can I have the Git repository? Two: can you walk me through why you chose this stack? An honest shop answers both in minutes, and plenty of honest shops use AI heavily, ours included. Silence, excuses, or a zip file with one 4,000-line HTML document tells you they generated and shipped without review. That is what you are checking for, not AI use itself.
Are sites from AI website builders the same as vibe coded sites?
Different animal, same family. Builder sites live inside a subscription platform: the AI assembles their templates, hosting is bundled, and export ranges from partial to nonexistent. A vibe coded site is code you generated in a chat and own outright, with nobody between you and the file. The failure modes differ too. Builders fail toward sameness and lock-in, chat builds fail toward the unreviewed defects on this list. The nine signs above catch the second kind; the first kind you can usually spot from the subdomain.
What does it cost to fix a vibe coded website?
Cosmetic issues cost nothing but a weekend and a better prompt. Functional problems, dead forms, broken layouts, missing SEO basics, start at $450 for our diagnostic, which is credited toward repair work that starts at $950. A full rebuild on a clean foundation is $2,800 flat for a static site. Every number is public on our pricing page, so you can compare quotes without a discovery call.