This checklist is for a marketing website. If the project has customer accounts, private records, subscriptions or custom payments, see the app launch review scope instead. Those features change the review scope.
1. Confirm the accounts and editable project
Know which account owns the builder project, source repository, domain registrar and host. Check that you can edit and deploy the actual project, rather than only view a preview or an image. Write down the build and deployment process and the paid services it depends on.
Invite a developer through the provider's access controls when needed. Do not put account passwords or API secrets in a contact form or shared document. Separate project access from billing access.
2. Review the facts and images
Read the service list, service areas, hours, contact details and price claims. Remove generated testimonials, certifications, team photographs or project outcomes you cannot support. Confirm permission to use every photo, logo and other asset.
A generated page can sound confident while naming a service you do not offer. The final reviewer should be someone who knows the business and can approve the exact revision.
3. Follow the customer journey on a phone
Start on the home page and do the task a customer should do: find a service, understand the next step, call, text or request a quote. Check narrow screens, navigation, readable text, image loading and keyboard focus. Look for content cut off at an edge and buttons that become hard to reach.
Opening a developer's desktop preview is not a substitute for that journey. Test the actual production URL after deployment as well.
4. Send a clearly labeled test inquiry
Agree on test data with the business owner. Submit a request once, verify that the destination received it, check the notification and confirmation, and confirm what happens if a required field is missing. If requests are saved in an admin panel, find the same test record there.
A “Thank you” screen alone does not establish delivery. A browser request that fails should not look successful. Exclude test records from lead reports, and make sure a reload does not create another request.
5. Connect the domain without breaking email
Review current DNS records before editing them. Connecting a website should preserve the records your email provider needs. Verify HTTPS, the preferred hostname, redirects and any old URLs that customers still use. Keep a rollback note with the previous settings.
Publishing on a builder's default URL may already be straightforward. v0's deployment documentation, for example, distinguishes its deployment workflow from the development preview. Follow the current documentation for your own host; the builder's publish button does not independently verify your business workflow.
6. Check search settings and measurement
Check page titles, descriptions, canonical URLs and whether production pages accidentally retain a noindex directive from a preview. Include useful pages in the sitemap and connect the owner's Search Console account. Indexing and rankings remain Google's decisions; a successful deployment does not guarantee either.
Use a small measurement plan. Count a saved inquiry separately from a button tap. Apply the site's consent requirements, and keep test visits and submissions out of acquisition results. More tracking tags do not fix an unclear offer or an undelivered form.
7. Keep a launch evidence sheet
Write down the pages and workflows tested, the corrections made, any remaining issues, the production URL, account owners and rollback steps. Include who will update the site and which work is covered by support.
A useful record says “this test inquiry arrived at the agreed inbox” rather than “the entire site is flawless.” Basic checks have limits, and a narrow launch review is not a comprehensive security or accessibility certification.
When to get help
Our Review & Publish offer is $990 for an eligible existing marketing site: up to five public pages, one standard form, one domain and up to two named minor corrections. Hosting, domains and paid tools are separate. We confirm eligibility and scope before work; larger repairs or a new design need a different quote.
Send your site for a launch quote. A preview link and a few lines about what remains are enough to start. Keep private credentials out of the brief.