A launch-day experiment by WebDevStudios
It looks done.
Same site. Very different Tuesday.
Two identical websites. One vibe-coded in four minutes. One built on WordPress. Let’s launch them both and see what happens when the internet shows up.
vs
Let’s be fair
AI is genuinely great at the top 20%.
This isn’t an anti-AI site. Vibe coding is a real superpower for the part of a website you can see and click. Here’s where it shines.
Visual design & layout
A polished hero, a grid, a palette, and type that works, in minutes instead of days.
Clickable prototypes
Show the idea instead of describing it. Get alignment before the first real meeting.
Campaign experiments
Spin up five landing page variants for a two-week test and keep the winner.
Components & boilerplate
The repetitive scaffolding no developer wants to type out by hand again.
Internal tools
The dashboard only your team will ever see, behind a login, with a short shelf life.
First drafts
Copy, content structure, and alt text: a starting point that beats a blank page.
20%
All of that is real, and all of it shows up in the screenshot. The trouble is what’s left when the demo ends and the site has to survive real visitors, real editors, and real lawyers.
Below the waterline
The other 80%.
Fourteen things a production website has to do that never show up in a screenshot. The deeper you go, the more expensive they are to miss. WordPress has spent two decades building all of them. A fresh prompt starts at zero.
80%
Getting found
If nobody can find it, the design doesn’t matter.
SEO foundations
Sitemaps, meta titles, canonicals, and structured data, with fallbacks for the pages nobody wrote copy for.
Social share previews
Open Graph images, titles, and excerpts generated from every page automatically.
Redirects & 404s
Old URLs, typos, and migrations all land somewhere useful instead of nowhere.
Running the site
A site launches once. It gets edited every single day.
Editorial workflow
Drafts, previews, scheduled publishing, and revisions for people who don’t write code.
Roles & permissions
Admins, Editors, Authors, and custom roles, so people get exactly the access they need.
Media pipeline
Every upload resized, compressed, converted to modern formats, and served responsively.
Forms & lead capture
Validation on both sides, spam filtering, entry logs, and notifications to the right inbox.
Managing risk
This is where the expensive surprises live.
Security patching
A dedicated security team, coordinated disclosure, and automatic security releases.
Accessibility
Core is built to WCAG accessibility standards, and the ecosystem has the tools to keep you there.
Privacy & consent
GDPR and CCPA consent, with tracking scripts blocked until a visitor opts in.
Backups & rollback
Revisions on every page, plus mature tooling for backups and staging sites.
Staying alive
The real question: who’s maintaining this in three years?
Maintainability
A documented, conventional codebase that thousands of agencies and developers already know.
Integrations
Tens of thousands of plugins for CRMs, marketing automation, SSO, analytics, and more.
Scale & uptime
Caching, CDNs, and managed hosting tuned for traffic spikes.
Fourteen layers. Zero of them in the demo.
Each one ships with WordPress core or a mature, maintained plugin. In a vibe-coded app, each one is another prompt, another dependency, and another thing nobody owns.
Launch day
Same day. Very different outcomes.
Eight things that happen to every real website, most of them before lunch on day one. Both sites, side by side.
Keep scrolling. The clock’s running.
Googlebot shows up.
The first crawler arrives looking for a map of your site.
Sitemap? Never heard of it.
No sitemap and no pings. Google finds your homepage eventually. Maybe.
GET /sitemap.xml
← 404 Not Found Map served. Search engines pinged.
WordPress generates the sitemap and refreshes it every time you publish.
GET /sitemap_index.xml
← 200 OK · every page listed Your CEO shares it on LinkedIn.
Big moment. Four thousand followers are about to see a preview card.
A gray box.
No og:image and no og:title. Three likes, all from family.
A card you’d actually click.
Featured image, title, and excerpt, pulled in automatically.
Someone types /prodcuts.
Fat thumbs. It happens hundreds of times a day.
A white screen of nothing.
No route, no 404 page, no redirect. Just a quiet bounce.
GET /prodcuts
← blank page · bounce Redirected, helpfully.
A redirect rule sends them to the right place, and any other wrong turn gets a helpful 404.
GET /prodcuts
← 301 → / A spam bot finds your contact form.
It has a lot to say about cryptocurrency.
Your inbox is a crypto newsletter now.
No server-side validation and no spam filter. Two real leads are buried in there somewhere.
POST /api/contact × 4,112
→ inbox: 4,114 new Bots blocked. Real leads logged.
Validation on both sides, spam filtering, and every real entry stored and emailed.
spam: blocked by honeypot entries: 2 saved · team notified
Marketing uploads a 14MB hero photo.
Straight off the camera. It looks incredible.
Phones everywhere start buffering.
Served as-is: one size, one format, all 14 megabytes.
hero.png 14.2 MB LCP 9.4s
Resized before anyone noticed.
Multiple sizes, WebP, and srcset, so every device gets the right one.
hero.webp 182 KB · 6 sizes LCP 1.1s
A visitor arrives from Berlin.
GDPR would like a word.
Trackers fired before hello.
Analytics and ad pixels load before consent. That’s a compliance problem.
gtag.js loaded · consent: none pixel.js loaded · consent: none
Scripts waited politely.
A consent plugin blocks every tag until the visitor opts in.
gtag.js → awaiting consent pixel.js → awaiting consent
Someone spots a typo on the homepage.
“Freshly roasted” is spelled “freshy roasted.”
“Can you ask the dev to re-prompt it?”
The copy lives in a component file. Nobody in marketing knows what that is.
ticket #212 “pls fix typo” status: in dev queue
Fixed in eight seconds.
An Editor logs in, fixes it, and hits Save. They can’t break the design.
editor@lumen → Save live in 8s
A security advisory drops. It’s Friday.
A dependency you didn’t know you had is vulnerable.
Who owns this? The AI?
Nobody’s watching the dependencies, and it’s 4:58 on a Friday.
$ npm audit
3 high · 1 critical Patched before the weekend.
Security releases apply automatically, backed by a dedicated security team.
security release applied 5:03 PM · no action needed
One site is still the same site. The other has a backlog.
The receipt
The vibe app was free.
Here’s the bill.
Every gap is a prompt, a dependency, a late night, or a ticket in somebody’s queue. And that’s just day one.
The confession booth
It looked done until…
Got a vibe-coding horror story? Fill in the blanks. No judgment. We’ve all shipped a gray share card.
Receipts of our own
Don’t take our word for it.
Check this site.
It Looks Done runs on WordPress, built by WebDevStudios. Every claim on this page should be true of this page, so here’s how to verify each one yourself.
-
SitemapsWe have a sitemap nobody wrote.
WordPress generates it and updates it every time an editor publishes.
Open the sitemap ↗ (opens in a new tab) -
404s & redirectsTypos land somewhere useful.
Misspell a URL on purpose. You’ll get redirected or get a helpful 404, never a white screen.
Try /prodcuts ↗ (opens in a new tab) -
Open GraphOur share card made itself.
This is the preview LinkedIn, Slack, and iMessage will show. No designer involved.
-
Meta & canonicalsEvery page has the boring tags.
Titles, descriptions, and canonical URLs, with fallbacks for pages nobody wrote copy for.
<title>It Looks Done: Same site. Very different Tuesday.</title> <meta name="description" content="AI is great at the visible 20% of a website. Watch launch day happen to a vibe-coded app and a WordPress site, and see the other 80%."> <link rel="canonical" href=""> <meta property="og:image" content="https://itlooksdone.com/wp-content/uploads/2026/10/og-image-1.webp">
-
PrivacyAnalytics waited for permission.
No tracking scripts load until you opt in. Reopen the settings and see.
-
FormsThe confession booth is real.
Submit it empty. It validates in your browser and again on the server, filters spam, and logs every entry.
Go to the form ↑
How we built this
We took our own advice.
WebDevStudios built this site the way we’d build yours: AI for the 20% where speed wins, engineering for the 80% that has to survive launch day.
AI did the 20%
- Visual direction Layout and design passes, starting from an HTML prototype.
- Copy drafts First passes and variants, edited by humans.
- Scaffolding Block boilerplate and test setup.
Engineers did the 80%
- A real block theme 14 custom blocks your editors can actually use.
- Launch-day plumbing SEO, redirects, consent, and forms, configured and checked.
- Tests on every change Automated accessibility checks and a test for every claim above.
Where’s your line?
Vibe it. Or build it to last.
AI is a tool, not a platform. The question isn’t whether to use it. It’s knowing where it saves you time and where it starts costing your company real money.
Great fit for AI
Vibe it.
- Prototypes & pitch demos Show stakeholders the idea before you fund it.
- Short-lived campaign pages Two-week tests where speed beats longevity.
- Internal tools Behind a login, one team, low risk.
- Design exploration Try ten directions before you commit to one.
- Writing code faster on a real platform AI-assisted development inside WordPress gets you both.
Needs the other 80%
Build it to last.
- Your primary website The front door for your brand, your SEO, and your pipeline.
- Anything that captures leads or revenue If the site breaks, the business notices.
- Sites with more than one editor Marketing, comms, and HR all need to publish safely.
- Regulated industries Healthcare, finance, higher ed, government, and nonprofits.
- Anything meant to live past next year Someone has to maintain it after the prompt window closes.
The 10-second gut check.
Flip on whatever’s true about the site you’re planning.
Low risk, short life, small team. This is exactly what AI is great at.
Use AI for the 20%.
Build the 80% to last.
The best teams don’t choose between AI and a real platform. They use AI to move faster on top of a foundation that already handles launch day.
Doing it yourself?
Start on the platform that runs 40%+ of the web.
Free, open source, and two decades deep on everything below the waterline. Bring your AI tools with you.
- Free and open source, forever
- Tens of thousands of maintained plugins
- Two decades of security releases
Want it built right?
WebDevStudios pairs AI speed with WordPress built to last.
A family and veteran-owned WordPress agency. We use AI where it makes us faster and engineering where it keeps you safe, so you get the 20% quickly and the 80% done right.
2008 Founded by Brad & April Williams
18 years Building on WordPress
- One of the longest-running WordPress agencies worldwide
- Led by a recognized WordPress author and community leader
- An extension of your team, not just another vendor