Before a small-business website launches, check that its key information is accurate, visitors can use the main contact route, critical pages work on phones and desktops, and the business knows who maintains the site and how to regain access. Search setup and analytics are useful follow-up tasks, not universal launch requirements.
A launch checklist should help you decide what must work before the site goes public and what can be completed afterward. A long list of technical recommendations does not make every item a launch blocker.
Updated 7 November 2026: this checklist separates launch blockers from follow-up tasks and reflects current Google search and Gmail sender guidance.
What should work before you launch?
Hold launch if key information is inaccurate, the main customer journey is broken, or nobody has been named to maintain the site. Before it goes live, agree how the business can recover or transfer access if the provider is unavailable; confirm account access and support details at handover. Check these items first; the next sections explain how to test them:
- Priority pages explain the real service, audience, offer, contact details and any prices shown. Remove placeholder text and confirm you have permission to use the copy and images.
- The main contact route works and has a named person responsible for replies. Use the contact section below for the test.
- Essential pages work on common devices, the live domain loads over HTTPS, and no issue blocks a visitor’s main task. See the technical and accessibility checks below.
- A named maintainer is responsible for the site, and the business has an agreed recovery or transfer route. Confirm account access at handover.
- If the site accepts bookings or payments, complete a test booking or order using the provider’s test mode. Confirm the customer receipt, business notification and next steps for changes or cancellations.
If a lower-risk item is unfinished, name the person responsible and set a date to review it. Do not describe a site as fully handed over until the business knows how to access and maintain the accounts it needs.
How should you check content and clarity?
Read the important pages as a new customer would. A visitor should be able to understand what the business does, who it serves and how to take the next step.
- The first screen uses plain language to describe the service and audience.
- The main offer is specific, and page headings describe the content that follows.
- Service pages explain what is included and where the scope ends.
- About and contact details identify the business and match its public information.
- Images are relevant, licensed or properly attributed; alt text describes meaningful images and decorative images have empty alt text.
- Proofread the published pages, not only the draft document.
How do you test the contact path?
A form can look finished while still failing to deliver a message. Test the full path before launch, and repeat the test after a major form or email change.
- Submit a controlled test from a phone and desktop browser.
- Required fields, labels and error messages make it clear how to finish or correct the form.
- A confirmation appears after submission, and the message reaches the intended inbox.
- If the form collects personal information, ask only for what is needed, explain its purpose beside the form and limit who can view submissions.
- Phone and email links open the expected app on a phone.
The web.dev forms guide covers accessible forms, input validation and testing across devices. Use a test message that does not include unnecessary personal information. The Information Regulator’s privacy principles recommend collecting only data needed for a defined purpose and using access controls.
Which technical checks matter before launch?
Check the pages and features that support the main customer task. A technical score alone does not show whether the site works for its intended visitors.
- On a phone, priority pages do not require horizontal scrolling or hide essential content and controls.
- Images are appropriately sized and compressed for their use.
- Layout remains stable enough to read and use while content loads.
- Buttons and links respond and lead to the expected destination.
- HTTPS works on the live domain, including redirects from any alternate domain the business still uses.
What search setup should you plan?
Google can discover pages through links and other signals. Descriptive titles help explain each page, a sitemap can list pages for discovery, and Search Console helps owners investigate search status.
- Each important page has a clear, descriptive title. A unique meta description can help summarize the page, but Google may create a search snippet from page content instead.
- URLs are readable, internal links work, and headings make the page structure easy to follow.
- Check that priority pages are not accidentally hidden from search by a page setting such as
noindexor a rule in the site’srobots.txtfile. - If the site has a sitemap, check that it is reachable and lists the correct live page URLs, not duplicate or test versions.
- Verify the business’s Search Console property if the owner wants search reporting. After launch, inspect important URLs and review their indexing status.
Google’s SEO Starter Guide explains these practices. Its recrawl guidance says that crawling can take days or weeks and a request does not guarantee indexing.
How should you prepare business email?
A domain-based email address can make the sender identity consistent with the business website. The address alone does not improve delivery or prevent spam. Ask the email provider which authentication settings the business needs and follow its setup instructions.
- Confirm who manages the business email account and can recover it.
- Ask the email provider or administrator to check the domain’s authentication. SPF lists authorized mail services, DKIM signs outgoing messages, and DMARC tells receiving servers how to handle messages that fail checks. The settings depend on the provider and sending volume.
- Send a test message to an external mailbox and check that replies reach the monitored inbox.
Gmail’s sender guidelines set different requirements by sender volume. Authentication helps protect a domain and can reduce delivery problems, but it does not guarantee that every message reaches the inbox.
Which accessibility checks belong on your list?
These checks catch common barriers; they are not a full WCAG conformance audit. For a formal accessibility commitment, use the applicable standard and a broader evaluation.
- Give meaningful images useful alternative text; use empty alt text for decorative images.
- Check text and controls for readable contrast.
- Navigate the main pages and form with a keyboard.
- Make sure each form field has a visible label that screen readers can identify, with errors that explain how to fix the problem.
- Respect reduced-motion settings for non-essential animation.
- Set the correct page language in the document.
The W3C WAI introduction to accessibility explains how accessible design supports people with disabilities and people using small screens, bright sunlight or limited bandwidth.
What should you measure after launch?
Measurement helps you investigate how visitors use the site, but analytics is not the only way to find problems. Decide what is useful for the business and who will review it.
- If the business uses analytics, verify that the setup records the intended pages and actions.
- Track a meaningful enquiry action, such as a completed form, where the site and analytics setup support it.
- Review form delivery, spam and broken paths after launch as well as traffic totals.
Google Analytics describes an event as a way to measure a specific interaction, such as a link click or purchase. For the first review, start with whether the site’s main actions work and whether useful enquiries arrive.
What should the handover include?
A provider may manage accounts during a project. Before handover, the business should know which accounts it controls, what the provider continues to manage and how access can be recovered.
- List where the domain is registered, the hosting provider, website platform, email service and measurement accounts.
- Confirm the business has owner-level access or a written recovery and transfer process.
- Record renewal dates, recurring costs, support responsibilities and who should be contacted if something stops working.
- If losing site content or settings would disrupt the business, confirm whether backups exist and how to restore them.
- Share credentials through a secure password manager or the provider’s approved transfer method; do not put passwords in an ordinary handover document.
- Agree who maintains the site, updates content and responds to problems after launch.
When should you do each check?
Use the project stages rather than a fixed countdown; deadlines depend on the scope and the people involved.
- During planning: confirm the offer, content, domain and account responsibilities.
- Before launch: test the main pages and contact path, check the live domain, name the site maintainer and agree a recovery or transfer route.
- At handover: confirm account access, credentials, renewals, support and remaining work.
- After launch: review the follow-up tasks assigned above and note any issue that needs a new owner or deadline.
Keep a short list of any remaining task with its owner, due date and impact. This lets the business make a clear launch decision without treating every optional setup item as a blocker.
Confirm what your website package includes
IDJoy’s working method describes the project stages and approval points. The package page lists the inclusions for each offer. Confirm the selected quote’s domain, hosting, email, analytics, support and renewal terms before treating them as included.
A launch checklist works best when each high-priority task has an owner. If you want help reviewing your project scope, describe the project and we can discuss the checks that apply.