Skip to main content
Services
Hire developers
Company
CoachOSPortfolio
Contact us+91 95124-74119info@globerixai.com

Website QA Checklist: What to Test Before You Launch

A practical website QA checklist covering functionality, devices, speed, accessibility, SEO, security and a launch-day smoke test.

3 min read. Updated November 16, 2026. By the GloberixAI editorial team.

What should you test before launching a website?

Before launch, test that every form, link and key journey works; check the site on real browsers and devices; measure speed and Core Web Vitals; test accessibility with a keyboard and a checker; review SEO basics such as titles, canonicals, redirects and sitemap; check security and privacy settings; and run a smoke test on the live site right after launch.

The checklist at a glance

The checklist at a glance
AreaWhat to checkUseful tools
FunctionalityForms, links, navigation, search, checkout, error pagesManual test scripts, browser DevTools
Browsers and devicesChrome, Safari, Firefox, Edge, iOS, Android, several screen sizesReal devices or a device cloud
PerformanceCore Web Vitals, image sizes, cachingPageSpeed Insights, Lighthouse
AccessibilityKeyboard use, contrast, headings, labels, alt textAccessibility checkers, screen reader spot checks
SEOTitles, descriptions, canonicals, robots, sitemap, redirects, structured dataSearch Console, rich results test, a site crawler
Security and privacyHTTPS, form spam protection, secrets, updates, cookie noticeSecurity headers check, dependency audit

Functionality

  • Submit every form and confirm that the message actually arrives in the right inbox.
  • Click every main link and button, including in the header, footer and emails.
  • Test the main user journeys from start to finish: contact, sign-up, purchase, booking.
  • Check error states, empty states and what happens with wrong input.
  • Check the 404 page and any redirects from old addresses.

Browsers, devices and layout

  • Test the latest versions of the main browsers and at least one real iPhone and Android phone.
  • Check small, medium and large screens and landscape orientation.
  • Look for overlapping text, clipped buttons and horizontal scrolling.
  • Test with slow connections, because many visitors are not on fast Wi-Fi.

Performance and accessibility

  • Run PageSpeed Insights on the main templates, as explained in our Core Web Vitals guide.
  • Make sure images are the right size and in modern formats.
  • Use the whole site with only a keyboard and check that focus is always visible.
  • Check color contrast, heading order, form labels and meaningful alt text.

SEO and analytics

  • Every page has a unique title, a clear description and one main heading.
  • Canonical tags are correct, and the staging site is not indexable while the live site is.
  • robots.txt and the XML sitemap are correct, and the sitemap is submitted in Search Console.
  • Old URLs redirect to the right new pages. See our website redesign checklist.
  • Structured data validates, and tracking and consent work as intended.

Security, privacy and backups

  • The site uses HTTPS everywhere, and secrets are not in the code repository.
  • Forms have spam protection and are rate limited.
  • Dependencies and platform software are up to date.
  • Privacy policy and cookie notice are in place and accurate.
  • Backups and uptime monitoring are set up.

Launch-day smoke test

Our web development team tests every project against a checklist like this before it goes live.

  1. Open the live home page and the main journeys on desktop and a phone.
  2. Submit the contact form and confirm delivery.
  3. Check that HTTPS, the www redirect and the sitemap work.
  4. Watch error logs and uptime for the first hours.

Key takeaway: Write your checklist down and keep it. A repeatable checklist is what turns testing from a hope into a habit.

Frequently asked questions

Who should test the website?

Both the people who built it and someone who did not. Fresh eyes find problems that builders no longer notice.

How long does website QA take?

It depends on the size and complexity of the site. A small brochure site can be tested in a day or two, while an application with accounts and payments needs much longer.

Is automated testing necessary?

It helps most for sites that change often or have complex journeys, because it catches regressions. Manual testing remains important for usability and visual checks.

Should I test on the staging site or the live site?

Do the full test on staging, then a short smoke test on the live site right after launch.

Want help with this?

Tell us what you are building and we will reply within 24 hours on business days.