Confirm the site structure
Write down the intended public routes and check that navigation, footer links, breadcrumbs and calls to action all lead somewhere useful. Verify that a page is not linked before it exists. If the website has multiple languages, confirm each language switch preserves the correct destination or returns visitors to a safe landing page.
Test responsive behavior
Review a narrow mobile viewport, a tablet width and a desktop layout. Look for horizontal overflow, unreadable text, buttons hidden under sticky headers, broken image ratios and forms that cannot be completed with a keyboard. Check image dimensions and alternative text, and avoid loading oversized assets where smaller files will work.
Review indexing and metadata
Decide which pages should appear in search results. Drafts, thin placeholders and incomplete translations should normally remain noindex. For public pages, check the title, description, canonical URL, language attributes and internal links. A sitemap should include only the canonical URLs you intend search engines to discover.
Validate the build and release
Run the project build, automated checks and a broken-link review. Check environment variables and secret handling; browser code must never contain private API keys. Confirm production routing and redirects, then deploy only an approved commit. After deployment, inspect the live pages and logs rather than assuming a successful build means the website works.
Verify real user journeys
Open the homepage, navigate to a project, read an article and complete a contact flow. A form is not verified until its backend processes a submission and the intended recipient confirms delivery. Record issues with the affected URL and reproduction steps before marking the launch complete.
References and further reading
Related: Explore QBMFX projects · Contact