cd /news/developer-tools/the-production-checklist-ai-skips-18… · home topics developer-tools article
[ARTICLE · art-64887] src=dev.to ↗ pub= topic=developer-tools verified=true sentiment=· neutral

The Production Checklist AI Skips: 18 Things Between a Demo and a Live Site

Senter Engineering identified 18 production gaps that AI-generated websites consistently miss, including server-side rendering, Open Graph tags, Core Web Vitals optimization, and automated deployment pipelines. The company compiled a checklist covering invisible but critical elements that affect search engine crawlers, link previews, and caching behavior, noting that these items are often skipped because they are not visible in demo screenshots.

read2 min views1 publishedJul 18, 2026

Every AI-generated site we have inherited was missing the same eighteen things. None of them are visible in a screenshot. All of them are visible to Google.

July 10, 2026

An AI-generated site looks done. It has a hero, sections, a color palette, and copy that reads well in a screenshot. Then we open the page source, and the production work is missing. Not some of it. The same eighteen things, every time. None of them change what a human sees in a browser. All of them change what a crawler, a link preview, or a cache does with the page. Here is the list we run before we call anything live.

This is where the gap is widest, because a client-rendered single-page app hands crawlers an empty div and expects them to run JavaScript to fill it. Many will not. We fix that with static work.

A link is content too. When someone pastes the URL into Slack or iMessage, the site is representing itself, and the defaults are usually blank.

Fast is a feature Google measures. Core Web Vitals are a ranking input, and they punish the exact patterns AI scaffolds produce by default.

These are one-line headers that never appear in the design, so they never get added.

The last item is the one that keeps the other seventeen from rotting. We want a deploy pipeline that fails loudly, environment config kept out of the bundle, and a build that regenerates the sitemap on every deploy so it cannot drift away from the routes that actually exist. This is the foundation we lay under every MVP we build, and it is why we wrote our post on encoding these standards as reusable skills instead of remembering them by hand.

None of these eighteen items is hard on its own. Any one of them is an afternoon at most. They get skipped for a single reason: they are invisible in the artifact you are reviewing. You approve a demo by looking at it, and looking at it cannot tell you the canonical tag is missing, the share image is broken, or the whole page is an empty div to a crawler. The demo was never the product. This checklist is the difference.

This is the kind of work we do for our own products and for the teams we take on. MVP development, or get in touch.

── more in #developer-tools 4 stories · sorted by recency
── more on @senter engineering 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/the-production-check…] indexed:0 read:2min 2026-07-18 ·