Top Website Builder Themes and AI Prompts

Create a fashion ecommerce website for [CLOTHING BRAND] selling [PRODUCT CATEGORY] to [TARGET CUSTOMER].

Goal: make the brand feel desirable, make products easy to browse, and push visitors toward add-to-cart without losing the editorial fashion feel.

Prompting approach: use this as the initial full-site brief, then refine section-by-section. Keep the business type, target audience, primary sales goal, visual style, and ecommerce requirements explicit so Wix or Lovable does not generate a generic store.

Pages: Home, Shop, Collection, Category, Product Detail, Lookbook/Journal, About, Contact, Wishlist, Search, Shipping & Returns, Privacy.

Homepage sections: seasonal hero with Shop New Arrivals CTA, collection tiles, bestseller/product grid, lookbook editorial strip, size/shipping/returns trust block, testimonial/social proof row, newsletter signup, final collection CTA.

Product detail requirements: large image gallery, size selector, color variants, price/sale state, shipping note, returns note, product description, related products, wishlist button, sticky mobile add-to-cart.

Real content to use first: [3 COLLECTION NAMES], [6 PRODUCT NAMES], [PRICE RANGE], [SHIPPING POLICY], [RETURN POLICY], [BRAND TONE], and [PHOTO STYLE].

Content model: Products, Collections, Categories, LookbookPosts, Testimonials, PromoBanners, EmailSignup.

Conversion rules: use one primary shop CTA above the fold, keep product cards tappable on mobile, add trust copy before checkout, and include empty/search/no-results states.

Design direction: modern editorial fashion, strong photography, crisp product cards, clean navigation, no clutter, fully responsive.

SEO: include collection keywords, product schema-ready fields, product/category meta titles, alt text guidance, and internal links from journal/lookbook to products.

Create a high-converting AI SaaS startup website for [PRODUCT] targeting [AUDIENCE].

Goal: turn cold visitors into free-trial signups, demo requests, or waitlist joins while making the product feel credible for B2B buyers.

Pages: Home, Pricing, Use Cases, Blog/Resources, About, Contact, Privacy, Terms.

Homepage sections: light hero with one primary CTA, product screenshot/dashboard cards, pain-to-outcome section, 3-5 feature blocks, workflow steps, integrations/trust strip, use-case cards, testimonial section, pricing preview, FAQ, final CTA.

Content model: Features, UseCases, Testimonials, PricingPlans, FAQItems, BlogPosts, CTAPlacements.

Conversion rules: keep the first CTA above the fold, repeat CTA after feature proof and pricing, add a secondary "Book demo" action, and label every outbound/action button with a clear placement name.

Design direction: clean light SaaS look, soft shadows, strong typography, dashboard/product visuals, no generic dark neon AI look, no crowded sections, fully responsive desktop/tablet/mobile.

SEO: create meta title, meta description, H1/H2 structure, FAQ-ready copy, internal links to resources, and schema-ready FAQ fields.

Build the first version with realistic sample copy, then ask me for logo, product screenshots, pricing, testimonials, and integration list.

Create a blog and magazine website for [NICHE] targeting [AUDIENCE].

Goal: turn organic/search traffic into repeat readers, newsletter subscribers, and downstream clicks to comparison or product pages.

Pages: Home, Category, Article, Author, Newsletter, Podcast optional, About, Contact, Privacy.

Homepage sections: featured story hero, pinned posts, latest posts, category rails, editor picks, popular guides, newsletter block, sponsor/ad slot, resource/internal-link section.

Article template: title, deck, author/date/read-time, table of contents, inline images, callout blocks, related posts, newsletter CTA, affiliate/context CTA after useful content, source/citation area.

Content model: Posts, Categories, Tags, Authors, Sponsors, NewsletterBlocks, RelatedLinks, CTAPlacements.

Conversion rules: newsletter CTA near the hero and after articles, internal links from info content to money pages, avoid outbound CTAs before the reader gets value.

Design direction: premium editorial, highly readable, fast scanning, strong image cards, clean mobile article cards, no crowded magazine clutter.

SEO: schema-ready article fields, breadcrumbs, category descriptions, author metadata, canonical URLs, related posts, and internal links to comparison/review pages.

Build an affiliate review and comparison hub for [NICHE].

Goal: convert high-intent visitors researching [NICHE] products into qualified affiliate clicks while keeping the site useful, transparent, and SEO-friendly.

Public pages: homepage ranking, category pages, product review pages, comparison pages, alternatives pages, articles/buyer guides, methodology, about, contact, privacy, affiliate disclosure.

Homepage sections: top picks hero, ranked cards, quick comparison table, best-for filters, buyer guide explainer, latest reviews, methodology summary, FAQ, final CTA.

Review page template: score summary, who it is best for, pros/cons, pricing, feature table, screenshots/media, alternatives, FAQ, internal links, and repeated Visit Site CTAs.

Data model: Products, Categories, Rankings, Reviews, Comparisons, Articles, CTAPlacements, ClickEvents, DisclosureBlocks.

Conversion rules: separate Read Review from Visit Site buttons, route outbound CTAs through /go/:token, pass placement IDs, repeat CTAs after proof sections, and keep disclosure visible but not intrusive.

Design direction: 5listed-style editorial UI, score badges, clean cards, sticky comparison anchors, mobile-friendly tables, accessible contrast.

SEO: ItemList, Review, Breadcrumb, FAQ-ready fields, comparison keyword headings, internal links from articles to reviews and ranking pages.

Build with sample products first and make it easy to swap real affiliate links later.

Create a restaurant or cafe website for [RESTAURANT NAME] in [CITY/NEIGHBORHOOD].

Goal: make mobile visitors hungry, help them check menu/location/hours fast, and push them toward reservation, online order, call, or directions.

Pages: Home, Menu, Reservations, Order Online, Gallery, About, Blog/Updates, Contact, Privacy.

Homepage sections: large food/venue hero, Reserve Table and Order Online CTAs, featured dishes, menu preview, chef/story block, reviews, gallery, opening hours, location/map, events/news, FAQ.

Menu requirements: categories, item names, prices, descriptions, dietary tags, specials, and empty state for seasonal menu updates.

Conversion rules: sticky mobile action bar with Reserve, Order, Call, Directions; repeat reserve/order near menu and location; show reviews before final CTA.

Design direction: image-rich, premium, warm, easy to scan, fast mobile load, clear contrast over food photography.

SEO: cuisine, neighborhood, opening hours, menu keywords, local business schema-ready fields, image alt text, and contact/location metadata.

Create a photography or designer portfolio website for [PERSON/BRAND] targeting [CLIENT TYPE].

Goal: make the work feel premium, prove credibility, and guide visitors toward an inquiry without turning the portfolio into a generic resume page.

Pages: Home, Work/Projects, Project Detail, Services, About, Journal optional, Contact, Privacy.

Homepage sections: full-bleed visual hero, selected projects, service positioning, featured case study, client logos/testimonials, process, about teaser, inquiry CTA.

Project detail requirements: project title, role/services, client context, challenge, solution, image gallery, outcomes, testimonial, next project link.

Conversion rules: keep Work and Contact visible in nav, repeat inquiry CTA after selected work and case studies, use a short form with budget/timeline fields.

Design direction: image-first, spacious, editorial, minimal UI chrome, fast gallery loading, strong mobile image crops.

SEO: service/location keywords where relevant, case study headings, descriptive alt text, project slugs, and internal links between work and services.

Build a client CRM and internal operations dashboard for [TEAM/WORKFLOW].

Goal: help admins/operators manage [RECORD TYPE], track status, collaborate on next steps, and see performance without spreadsheet chaos.

Users and roles: Admin, Manager, Operator, Viewer. Define permissions for create, edit, archive, assign, comment, export, and settings.

Data model: Users, Clients, Records, Statuses, Tasks, Comments, Files, ActivityEvents, Reports, Settings.

Views: dashboard overview, records table, record detail drawer/page, create/edit form, kanban/status board, task list, reports, settings.

Core states: empty, loading, error, no-results, draft, archived, pending approval, overdue, completed.

Conversion/usefulness rules: prioritize quick filters, saved views, inline status updates, visible owner/next action, and activity history.

Design direction: quiet operational UI, compact readable tables, stable controls, clear hierarchy, desktop-first with tablet/mobile fallback.

Build MVP with sample records, then ask me for fields, roles, workflows, integrations, and reporting metrics.