A launch-ready business website clearly says who it serves, what it sells, why it is credible and what to do next. Its contact and buying paths work end to end; material terms are easy to find; pages are usable by keyboard and on small screens; titles, URLs and crawl settings are correct; accounts are secured; analytics records meaningful actions; and somebody owns monitoring, updates and backups after launch.
Reviewed for material changes on August 13, 2026
Positioning and content
A new visitor should be able to identify the offer, intended customer and next step from the first screen and nearby context. Replace broad claims with concrete outcomes, constraints and evidence. Give each page one main job and a title that describes it plainly.
Use real language from customer conversations and support questions. Build pages around decisions people need to make, not internal departments. Google recommends logical site organisation and descriptive URLs because they help both people and search systems understand how content relates.
- The homepage states audience, offer and primary action.
- Product or service pages explain deliverables, process and fit.
- Pricing is shown or the route to a meaningful quote is clear.
- Proof is specific, attributable and placed near the claim it supports.
- About and contact information establish who operates the business.
- Navigation labels use customer language and every important page is linked.
- Copy, dates, team details and availability are current.
- Spelling, punctuation and brand names have had a human proofread.
Trust, terms and transactions
Show material prices, limitations, delivery expectations and conditions where the decision happens. In US guidance, the FTC says online truth-in-advertising standards apply and disclosures needed to avoid deception should be clear and conspicuous. Check the consumer, ecommerce, privacy and sector rules that apply in every market you serve.
Test the complete transaction with production-like accounts. A working button is not enough if the order lacks confirmation, the lead has no owner or a refund cannot be traced.
- Forms explain why each piece of personal data is requested.
- Required legal and privacy information is current and reachable.
- Testimonials, reviews and endorsements are genuine and properly disclosed.
- Checkout or enquiry confirmation sets the next expectation.
- Support, cancellation, returns and refund routes are easy to find.
- Business address, email and phone details are correct where displayed.
- Emails reach the right inbox and have a monitored reply path.
- Failed payment and form states tell the customer what to do next.
Responsive use and accessibility
Test with a narrow phone, keyboard, browser zoom and real production content. W3C recommends using the latest WCAG version, currently WCAG 2.2. Automated checks can find some failures, but they do not tell you whether the journey makes sense.
Watch people complete the main task without coaching. Confusion that occurs before a click will not appear in a broken-link report.
- Heading order and page landmarks describe the content structure.
- Links and buttons have clear names and the correct semantics.
- Keyboard focus is visible and follows a sensible order.
- Text and controls have adequate contrast.
- Images have useful alt text when they convey information.
- Forms have labels, clear errors and preserved valid input.
- The page works at 200 percent zoom without hiding essential content.
- Motion can be avoided or reduced where appropriate.
Search, performance and resilience
Give every important page a descriptive title, useful summary and stable URL. Check canonicals, redirects, sitemap, robots controls, social previews and structured data against the final production address. Do not leave a staging noindex rule on the public site.
Measure load, interaction and layout stability and remove needless scripts, oversized media and duplicate fonts. Secure owner accounts with multifactor authentication, keep dependencies current and prove that the restore or rollback process works.
- Production returns the intended status code for pages and redirects.
- No internal links, images, downloads or scripts return errors.
- Titles and descriptions are unique where the pages are distinct.
- The XML sitemap contains canonical public URLs.
- Core Web Vitals have been checked in lab and monitored in the field.
- Domain, DNS, email and builder accounts have named business owners.
- MFA, password management, updates and recovery details are in place.
- A backup or previous deployment can actually be restored.
Measurement and ownership after launch
Track the actions that reflect the site's job: qualified form completions, bookings, purchases, calls or account starts. Check that events fire once, carry no unnecessary personal data and appear in the reporting view the team will use.
Assign owners and review dates for content, integrations, privacy text, analytics, security updates and renewals. A website is not maintained by having a footer year that changes automatically.
- Primary conversion events have been observed end to end.
- Consent choices behave as intended in the relevant markets.
- Error monitoring and uptime alerts reach a person who can act.
- Form and order volumes are reconciled with destination systems.
- A launch-day and first-week review are in the calendar.
- Content owners and review dates are recorded.
- Subscription and domain renewals use a controlled payment method.
- The team knows how to publish, roll back and ask for help.
Sources and checks
Product limits and prices came from the companies themselves:
- Google Search Central: SEO Starter Guide
- W3C Web Accessibility Initiative: WCAG overview
- Google web.dev: Web Vitals
- Federal Trade Commission: online advertising and marketing
- CISA: Secure Our World
Plans move. We date every check so you know when to verify again.