Make launch
a checked decision.

Review the published result.

Work through the site as a visitor, not only as its builder. Start at the homepage, explore a relevant page, and follow the intended action. Then repeat the journey using a keyboard and a narrow viewport. Record specific problems with the page, condition, and steps needed to reproduce them.

A checklist is an aid to review, not a guarantee that every possible issue has been found. Match the depth of testing to the consequences of the project, and involve an appropriate specialist when private data or important business actions are involved.

Eight checks before handover.

1. Check the content.Compare visible copy with approved facts. Confirm names, contact details, dates, and image permissions. Remove unsupported claims and explain missing information before it becomes a public promise.
2. Follow the real journey.Open every main-navigation item, footer destination, article link, and call to action. Verify the email destination as well as the visible address. Open an interior page directly at its own URL.
3. Review changing screen space.Inspect narrow, medium, and wide layouts, including the widths between presets. Try portrait and landscape conditions. Check long titles, wrapping links, sticky headers, and the fully open mobile menu.
4. Use different ways to navigate.Move through the page with a keyboard. Look for visible focus, a useful skip link, sensible heading structure, and controls that do not rely on hover. Inspect zoom and reduced-motion behavior.
5. Confirm the assets.Check that images, stylesheets, scripts, favicons, and downloads load from the published site. Preserve image proportions and make sure informative images have appropriate descriptions.
6. Review the page descriptions.Check unique titles, meta descriptions, canonical addresses, and social previews. Ensure structured data describes visible facts and does not add invented ratings, business details, or credentials.
7. Validate discovery files.Compare the sitemap with the actual indexable pages. Read the RSS feed in a compatible reader or validator and inspect article dates and links. Keep private or unfinished work out of public publishing.
8. Hand over ownership.Record who controls the domain, hosting, files, and connected services. Keep a recoverable copy and document the publishing process. Ask the maintainer to make a routine update before the handover is complete.

Go deeper where the project needs it.

Use the responsive website guide for layout and interaction checks, the SEO launch plan for discoverable content, and the automation guide when external services are connected. For application work, start with permissions before publishing.

Keep open issues separate from completed checks. A visible list of unresolved questions helps the release owner make an informed decision instead of assuming that a finished design means a finished system.