402InfoSec
Synthetic sampleWebsite Rebuild Delivery Pack
A hypothetical small-business website rebuild showing how scope decisions, launch controls, and owner handoff could be documented.
This is not client work.
Assume a small property-services business needs a clearer website and estimate path. The current-state issues and proposed scope below are scenario assumptions, not observations from an engagement. A real project would verify the site's behavior, account ownership, redirect support, and form-delivery options before agreeing to this plan.
Project snapshot
Success criteria
- A visitor can identify the service area, core services, and next action without hunting through the site.
- The estimate form works on desktop and mobile and sends only the information needed for first contact.
- Every retained URL has a deliberate destination and changed URLs have direct redirects.
- The owner controls the domain, repository, hosting account, analytics, and content.
- The final site passes agreed accessibility, performance, metadata, link, and responsive checks.
Findings that shape the rebuild
| Observation | Business effect | Project decision |
|---|---|---|
| The homepage leads with a company history before explaining the services. | New visitors need extra effort to decide whether the company fits the job. | Lead with service area, buyer problem, and estimate path. Move history to About. |
| Four service pages repeat the same paragraphs with different titles. | Customers and search engines receive weak differentiation. | Consolidate into three service pages with distinct scope, examples, and calls to action. |
| The contact form asks for twelve fields and sometimes fails silently. | High friction and lost inquiries. | Use six first-contact fields, clear validation, a confirmation state, and a controlled delivery test. |
| The domain, hosting, and plugin licenses are spread across personal vendor accounts. | The owner cannot confidently change providers or recover access. | Document ownership, transfer accounts where appropriate, and leave a recovery checklist. |
| Existing local-service URLs have earned links and should not disappear. | A careless launch could create 404s and lose referral or search value. | Retain useful URLs or map each changed URL directly to the closest replacement. |
Proposed site structure
Home
Service area, strongest problems solved, service paths, project proof, and estimate call to action.
Commercial Grounds
Scope, property types, recurring work, seasonal planning, and estimate path.
Snow and Ice
Response model, service boundaries, priority sites, and readiness expectations.
Cleanup and Projects
One-time work, examples, fit boundaries, and quote information.
About
Operator story, service area, working principles, and direct ownership.
Work
Approved project images with useful captions instead of an unstructured gallery.
Contact
Short estimate form, public service area, safe first-contact guidance, and confirmation.
Page-by-page content decisions
| Page | Primary question | Required proof or input | Primary action |
|---|---|---|---|
| Home | Do you handle the kind of property and work I need? | Service area, three core services, approved work photos, operator context. | Request an estimate |
| Commercial Grounds | What recurring work is included? | Service list, property types, seasonality, exclusions, approved equipment images. | Discuss recurring service |
| Snow and Ice | Can you support our site during winter weather? | Coverage area, readiness process, communication model, contract boundaries. | Ask about winter coverage |
| Contact | What information do you need to tell whether this is a fit? | Name, reply method, property location, service need, timing, short notes. | Send request |
Technical acceptance checklist
Search continuity
- Unique title and description on each indexable page
- Canonical URLs and generated sitemap
- Direct redirect map with no chains
- Useful local-service content remains visible in HTML
Quality and accessibility
- Keyboard navigation and visible focus
- One clear H1 per page
- Responsive checks across agreed viewports
- No serious automated accessibility findings
Inquiry path
- Required fields and error states tested
- Spam control configured
- Successful delivery confirmed once in production
- No passwords or sensitive files requested
Owner control
- Domain and DNS remain in owner account
- Repository and deployment access documented
- Analytics ownership documented
- Rollback and update instructions delivered
Redirect map excerpt
| Old URL | Final destination | Reason |
|---|---|---|
| /lawn-care-services/ | /commercial-grounds/ | Closest retained service intent |
| /snow-removal/ | /snow-ice/ | Renamed canonical page |
| /gallery/ | /work/ | Project evidence reorganized with captions |
| /contact-us/ | /contact/ | Canonical contact path |
What the owner receives
- Deployed website and source repository under owner-controlled accounts.
- Final sitemap, redirect record, and page inventory.
- Content and image source record, including items that still need owner approval.
- Plain-English update, deployment, rollback, and recovery instructions.
- Launch validation results and a list of any accepted limitations.
- A short post-launch review window defined in the project agreement.