Landing-page information structure

Inputs to prepare

• —One sentence on what the product does and who it is for
• —An ideal-customer sketch: what they want, what confuses them, what makes them hesitate
• —One primary and one secondary action, for example Get Started and View Demo
• —Proof you can actually use: real numbers, customer quotes with name and role, logos, awards or guarantees. If you have none yet, mark them as placeholders
• —A feature list, ideally each tied to the objection it answers, plus pricing and FAQ if relevant
• —Visual direction and delivery: palette, fonts, a single HTML file or a named stack, and your own image and video URLs

Method steps

1. 01Pick one reader and one action. Following @JayPROb01, open the prompt with what the customer wants, what makes them hesitate and what the page should get them to do.
2. 02Look at a few sites in the same niche for section order, CTA wording and trust elements. Take the structure, not the copy.
3. 03Lay out the skeleton: hero with the value proposition, primary button and one trust signal; then proof; then how it works and features, each tied to an objection; pricing and FAQ if needed; close with one CTA that repeats the key number.
4. 04Put each section's headline, numbers, quote authors and button labels in the prompt itself, the way @aigoldrushh and @viktoroddy do, rather than just asking for a testimonials section.
5. 05State the visual no-gos and the delivery format, such as no stock gradients or default fonts, one HTML file, responsive layout, no follow-up questions.
6. 06After generation, check section by section that nothing is missing and long lists were not cut, then rewrite generic copy by hand. To explore, generate a few variants per section and stitch the best ones.

Variables to swap

• —Product, target customer, and the primary and secondary actions
• —Proof format: logo wall, big numbers, named testimonials, awards or a guarantee bar
• —Number and order of sections, such as adding a comparison table, founder letter or case studies, or dropping pricing
• —The objection each feature answers
• —Visual direction: dark or light, one accent color, font pairing
• —Delivery: single HTML file, Next.js with shadcn, or React with Vite and Tailwind

Common failures and limits

• —Long lists get dropped. Retest data: in the 2026-08-23 run of grok-4-3, the 10-product grid was missing entirely and all three automatic reviewers marked it degraded. With many sections and items, check every block after generation.
• —Fake proof. @thisdudelikesAI's prompt allows simulated social proof, and @aigoldrushh labels the footer as a demo store. Swap placeholder numbers and quotes for real ones before launch, or label them clearly.
• —Template look. From the prompts' own avoid lists: @elvissun bans purple-blue gradients, default fonts and the predictable hero-CTA-features-testimonials template, and @JayPROb01 asks for no buzzwords and no filler. Keep the logic, but make the look and copy your own.
• —Copy stays too safe. @elvissun reports that 4 of the 6 hours 14 minutes went into copy, because AI drafts were directionally right but generic. That step still needs a person.
• —Missing asset URLs. In our stored copies of prompts such as google-stitch-claude the video URLs are empty, so a straight copy will lack the background videos. Supply your own media.