cargomastersgroup.roWebsites and automations for busy US teams

Insights · cargomastersgroup.ro

Website launch checklist: pre-launch QA for business sites

By the cargomastersgroup.ro editorial team · · 4 min read

In short: Before a business website goes live, check five areas: content accuracy, function (forms, links, buttons), mobile layout and speed, technical setup (HTTPS, redirects, indexing, sitemap) and domain and email. Test on real phones, submit every form, remove any setting that blocks search engines, and confirm someone receives each enquiry. Then watch the first two weeks closely.

Pre-launch QA (quality assurance) is a structured check of a website before it goes public, meant to catch the errors that visitors, clients or search engines would otherwise find first. It is not a design review. The question is simple: does every page say the right thing, and does every button, form and link do what it should?

Use the checklist below with two people if you can: one who knows the business and one who has never seen the site. The second person will notice what the first has stopped seeing.

1. Content and accuracy

  • Company name, address, email and phone number are identical on every page and match other listings.
  • Each service is described as you actually deliver it, with no placeholder text or sample content left over.
  • Prices, hours and service areas are current, or deliberately left out.
  • Team names and titles are correct and every person shown has agreed to appear.
  • Every claim can be supported: no unverifiable statistics, awards or reviews.
  • Spelling and grammar have been checked by someone other than the writer.
  • The privacy notice and any terms page exist and are linked from the footer and from forms.

2. Forms, links and contact paths

  • Submit every form with real data and confirm the message arrives in the right inbox, not just the developer's.
  • Check that form confirmation messages are clear and that the sender receives an acknowledgment if one is promised.
  • Tap the telephone button and email links on a phone to confirm they open the right app with the right details.
  • Click every menu item, button and footer link; fix or remove anything that leads to an error page.
  • Confirm a helpful 404 page exists with a route back to the home page and contact details.
  • If an AI assistant is on the site, ask it ten real customer questions and one it should not answer, and check the handoff to a person.

3. Mobile, speed and accessibility

Most first visits to a business site happen on a phone, so test on at least one iPhone and one Android device, not only in a desktop browser's mobile preview.

  • Text is readable without zooming and buttons are large enough to tap.
  • Nothing overflows sideways; no horizontal scrolling.
  • Images are compressed and sized for the screen; pages load quickly on a mobile connection.
  • Every meaningful image has alt text, and headings follow a logical order.
  • Text has enough contrast against its background, and the site can be navigated with a keyboard.

4. Technical and search setup

ItemWhat to checkWhy it matters
HTTPSEvery page loads over https with no browser warningsVisitors and browsers treat insecure pages as untrustworthy
Indexing settingAny 'noindex' tag or robots.txt block used during development is removedA leftover block keeps the whole site out of search results
RedirectsOld page addresses redirect to their closest new equivalentKeeps existing links and bookmarks working
Titles and descriptionsEach page has a unique title and meta descriptionThese form the snippet people see in search results
Structured dataschema.org markup for your organization and FAQs validates without errorsHelps search and AI systems read your business details
XML sitemapLists live pages only, submitted to Google Search Console and Bing Webmaster ToolsHelps new pages get discovered
Canonical tagsEach page points to its own preferred addressAvoids duplicate versions competing

5. Domain and email

  • The domain is registered in the company's name with auto-renewal on and a working billing contact.
  • Both the www and non-www versions lead to the same address.
  • Business email sends and receives, and SPF, DKIM and DMARC records are in place.
  • Mail sent from the website's forms is not landing in spam.
  • Login details for the domain, hosting and editor are stored where more than one person can reach them.

Launch day and the first two weeks

  1. Take a full backup of the final version before switching anything.
  2. Make the DNS change at a quiet time and keep the old site available until the new one is confirmed working.
  3. Repeat the form and phone-button tests on the live domain, not on the staging address.
  4. Check Search Console and Bing Webmaster Tools for crawl errors after a few days.
  5. Watch incoming enquiries: if they drop sharply, test the forms again before assuming anything else.
  6. Collect the small fixes people report and apply them together at the end of week two.

Trade-offs worth accepting

A launch does not need every page to be perfect. Accurate core pages, working contact paths and a clean technical setup matter far more than a finished blog or a final photo. It is usually better to go live with fewer, correct pages and add more later than to delay while enquiries go to an outdated site. What you should not compromise on is anything that breaks trust: wrong contact details, broken forms, security warnings or claims you cannot back up.

Every business website we configure goes through these checks before launch, and the technical items overlap with our SEO and GEO setup.

Questions and answers

Who should test the site before launch?

Ideally two people: someone who knows the business well enough to spot wrong facts, and someone new to the site who will notice confusing navigation, unclear buttons or missing information.

What is the most common launch mistake?

A setting left over from development that tells search engines not to index the site, followed closely by contact forms sending enquiries to an address nobody checks. Both are quick to test and easy to miss.

Should we wait until every page is finished?

Usually not. Launch with accurate core pages and working contact paths, then add articles and extra pages over time. Do not launch with wrong contact details, broken forms or unsupported claims.

Talk to us about your project

Email support@cargomastersgroup.ro or send a request. We reply by email within one business day.