Direct answerA fast website build depends on complete, approved inputs. Gather the business facts, service details, customer questions, proof, images, legal wording, account access and one decision-maker before the delivery clock begins.
Business facts
These details should agree across the website, form, metadata and structured data.
- Public business name and legal name where needed
- Verified email, phone and response expectation
- Truthful public location or service area
- Approved operating hours
- Founder or team details with permission
- Actual in-person model and Google Business Profile eligibility
Offer and services
Write one approved source list instead of sending conflicting notes.
- Primary services and profitable priorities
- Who each service is for
- Important exclusions or minimums
- How estimates, bookings or calls begin
- Verified prices or price ranges when public
- Truthful emergency, warranty, financing and availability wording
Proof and trust
Proof must be real, current and permitted.
- Project photos with location and consent notes
- Before-and-after pairs with matching context
- Reviews and testimonials with publication permission
- Licences, insurance, certifications and memberships
- Guarantees or warranties with approved terms
- Real partner or supplier logos with permission
Images and brand files
Keep original, full-resolution files. Screenshots copied from social media often lose quality and may not preserve consent or ownership records.
- Vector or high-resolution logo
- Colour and font references
- Horizontal and vertical project images
- Owner/team photos only when approved
- Image creator, licence and consent record
- Remove visible private data, addresses and licence plates
Five-page content map
A common structure is a starting point, not a rule.
| Page | Gather before build |
|---|---|
| Home | Core service, audience, coverage, proof, primary action |
| Services | Grouped offers, fit, exclusions, process |
| Work / Proof | Approved examples, captions, consent |
| About / Process | Real story, people, steps, responsibilities |
| Contact / Quote | Required fields, routing, privacy wording, fallback |
Accounts and approvals
Do not send passwords in a general intake document. Use the provider’s secure access or delegation flow.
- Domain and DNS owner confirmed
- Hosting decision and billing owner
- Email and form recipient approved
- Analytics and Search Console access
- Privacy, terms and accessibility review owner
- One person authorized to give final approval
Printable launch-ready check
Use Print → Save as PDF. This resource is intentionally available without an email gate.
- Every public fact verified
- No placeholder contact details
- Content and photos approved
- Scope and add-ons agreed
- Deposit complete
- Decision-maker confirmed
- Domain and required accounts accessible
- Form delivery tested
- Legal pages reviewed
- Final mobile and keyboard check scheduled