This is a workflow note on prompt structure for AI site-generation tools, using Hostinger's builder as the test case.
The core technical constraint
Mode selection is immutable post-initialization. Once a project starts in Manual or Agentic mode, there's no migration path — switching requires instantiating an entirely new project.
Decision tree for mode selection:
- Requires auth/user accounts/multi-step logic? → Agentic mode
- Static/content-driven site (portfolio, blog, brochure)? → Manual mode
Get this wrong and you're rebuilding from scratch, not migrating state.
Prompt specificity as the primary output-quality variable
I ran a controlled comparison — same tool, two prompt structures, same target site type:
Prompt A (low-spec): "A website for my bakery."
Prompt B (high-spec): business type + audience + exact page list
- one concrete narrative detail + explicit style parameters (colors, not adjectives)
Output quality difference between A and B was not marginal. SmashingApps ran this comparison directly and found the gap consistent across multiple generation attempts — vague input reliably produces template-adjacent output regardless of underlying model quality.
Practical prompt template that reduces post-generation cleanup
[Business type] + [target audience/location] + [exact required pages]
- [one real business detail] + [explicit style direction: colors, mood, NOT vague adjectives]
Post-generation review workflow
Before editing anything:
Review every generated page, not just the homepage
Distinguish "not yet customized" (expected — placeholder text/images) from "actually wrong" (missing/incorrect pages — re-prompt before manual edits)
SEO configuration — not automatic by default
Sitemap generation and basic site-structure are automated. Meta titles/descriptions per page are not — these require manual configuration through the SEO panel or explicit prompting in Agentic mode.
Reference
Full technical walkthrough, including the exact prompt template and mode-decision logic, is in this AI website builder prompt engineering writeup.
Takeaway for 2026 workflows
Treat prompt construction as a discrete engineering step, not an afterthought. Output variance correlates directly with input specificity, not model capability.
Top comments (0)