Choose a clear job for every page
A portfolio should help a visitor understand your work and decide whether to contact you. A small business site should explain what you offer, who you serve, and how to take the next step. Start with those questions rather than a long list of visual effects.
Outline the pages and their real content. A photographer might need a homepage, project gallery, about page, and contact page. Prepare your own images, project descriptions, and contact details so the site has something specific to say.
Describe the content and visual direction together
The builder works best with a brief that names the audience and the action you want visitors to take. Include mobile behavior and accessibility expectations. Use placeholder copy only where you plan to replace it.
Build a portfolio website for an architectural photographer. Include a homepage with a selected-project gallery, individual project details, an about section, and a contact form. Use generous spacing, dark gray type, and large images. Make the gallery responsive and give every form field a visible label. Use clearly marked image placeholders and do not invent clients, awards, or testimonials.Open the app builder
Review the mobile experience early
Try the site at a narrow width before polishing every desktop detail. Navigation should be usable, body copy should be readable without zooming, and buttons should be easy to tap. Check that images keep their intended crop and that headings do not push important actions off-screen.
Use real content while you test. A name, headline, or address that is longer than the placeholder can expose layout problems. Keyboard navigation and visible focus indicators matter for visitors who do not use a mouse.
Connect forms and business services deliberately
A contact form needs somewhere to send its submissions. A storefront needs a payment integration, order handling, and appropriate account access. Ask the builder to distinguish between a visual frontend and a working service integration.
Configure the required backend and provider settings outside the browser source. Test success, validation, and failure messages. Never treat a simulated confirmation in a preview as proof that an email was delivered or a payment was processed.
How do I prepare an AI-built website for search?
Publish a supported site through BrainHalf, or export its source if you prefer your own host. Ask for descriptive page titles, useful copy, canonical URLs, crawlable HTML, a sitemap and real 404 responses. Check those on the published site; publishing a generated app does not guarantee that its search setup is complete.
Compress photographs, include appropriate image descriptions, and reserve their dimensions to reduce layout shifts. After publishing, test the live URL, check forms, and use Google Search Console to inspect indexing. Search visibility depends on the published site’s content and reputation as well as its technical setup.
Reference documentation