Skip to main content

Website Acceptance Checklist

Use this before releasing a main-site change or paid landing page. Record evidence, not just a checked box.

Decision path and proof​

  • Each priority page has a clear job, audience, and next step.
  • Services, markets, project fit, cost or scope drivers, process, and why-us claims agree with the business.
  • Local projects, client words, and other proof have sources and permission.
  • Relevant household decision-makers can understand the project, tradeoffs, and likely disruption.
  • Calls to action match the reader's readiness instead of forcing every visitor into the same form.

Experience and access​

  • Navigation, links, and controls are obvious and work by keyboard.
  • Text is legible, headings are ordered, images have useful alternatives, and focus is visible.
  • Critical paths work on current phone and desktop sizes without horizontal overflow.
  • Images are useful, properly sized, and do not hide important text.
  • Pages load reliably enough for the intended audience and connection conditions.

Technical continuity​

  • HTTPS, canonical URLs, indexing directives, sitemap, and crawl access are intentional.
  • Required redirects preserve old high-value routes without chains or loops.
  • Broken links, missing pages, duplicate content, and accidental thin pages are resolved.
  • Search and local-profile destinations use the approved public identity.
  • The remodeler controls the domain, platform access, analytics, and source assets.

Leads, privacy, and measurement​

  • Calls, forms, confirmation states, notifications, CRM receipt, and spam handling pass end to end.
  • The page collects only needed information and has appropriate privacy and consent treatment.
  • Tracking records the agreed event without exposing personal data unnecessarily.
  • Measurement can distinguish a response from a qualified outcome.
  • A named person owns failures after launch.

Verdict​

Record PASS, CONDITIONAL, or BLOCKED, plus the tested URL, traffic context, device screenshots, tester, issue severity, recommendation, evidence, conditions, owner, and verification date. A live page is not accepted until its primary lead path and critical redirects are verified.

  • A rollback owner, known-good state, trigger, and verification path exist.
  • Launch-day and stabilization monitoring have named owners.
  • The maintenance owner accepted access, documentation, open risks, and the phase-two backlog.

A successful staging response, visible tracking tag, login, or single form test proves only that check. It does not prove the complete production route, data, lead, or recovery system.

Related guidance: website growth and rebuild, website launch and stabilization, and paid readiness and learning.