Examples, not a bundle
Choose the repair that matters most.
That might be mobile layout, tap-to-call paths, broken content, metadata, accessibility, or deployment checks. The written scope names the exact repair; the list is not a promise to include every item.
How it moves
- Review the current page
- Approve the inputs for the local repair
- Review the completed local version
- Accept the exact written scope and acceptance checks
- Pay the private checkout before publication or DNS changes
- Approve the separate public release
The sequence stays intentionally small: current-page review, approved inputs, local repair, owner review, exact written scope, private payment, and a separate launch decision.
Outside this offer
- unlimited design
- an automatic retainer
- a guaranteed ranking or revenue result
- invented business copy or claims
- a paid-ad campaign
- Anything outside the written scope is a separate agreement.
Payment boundary: the private checkout is sent only after the scope and acceptance checks are agreed. Payment is due before publication or DNS changes, and the public release still requires separate approval.