A website launch checklist for service businesses.
Before you approve a new website, follow a customer from the first page to the inquiry that reaches you. These six checks help you review the business details, the experience and the care needed after launch. Use them with your designer and keep the results.
Considering Immersyn? Our launch standard explains our review process and the record to keep with your project.
Free tool · No signup
Make it your checklist.
Use the guide below to review each area, then keep the open questions for your designer. This records your own checks; it does not inspect a website or approve it for launch.
0 of 6 areas reviewed0 marked as needing attention
01
Make sure the business details are true.
A customer should understand the work you do, where you do it and how to reach you.
Read each service page as a new customer. Confirm what is included, who the service is for and any information needed before you can quote or book.
Check the business name, service area, phone, email and opening hours against your own records. If a price appears, confirm its scope and any conditions.
Approve photos and claims before publishing. Use imagery you have permission to use; label concepts clearly and publish reviews, qualifications and results only when they are genuine.
What to confirmYou can stand behind every published detail, and a customer can tell whether you serve their needs.
02
Follow the inquiry all the way to you.
A working button is the beginning of a customer journey. Check the delivery and the reply.
On your phone, follow the main action from the homepage and a service page. A call should use the right number; a booking link should open the intended service; an inquiry should carry the relevant context.
Agree on a clearly labeled test inquiry with your designer. Confirm it reaches the intended inbox or portal with the customer details intact, rather than relying on the confirmation screen alone.
Try an empty form and an invalid email. Errors should identify the field to fix, preserve useful input and let the visitor try again. Check the success message and decide who will respond.
What to confirmThe inquiry reaches the right place, and you know who will handle it. Fix a wrong number or failed delivery before launch.
03
Use it on a real phone and with a keyboard.
The person who needs your service may be outside, in a hurry or using a different way to navigate.
Open the site on a narrow phone screen. Read the heading, open the menu and reach the contact action without sideways scrolling, tiny text or overlapping controls.
Move through navigation and the form with the Tab key. Check visible focus, field labels and error messages; make sure an open menu can be closed and you can return to the page.
Review photo crops, text contrast and loading on a slower connection. Check reduced-motion settings so animation does not hide information or make a required action harder to use.
What to confirmThe main customer journey works on the devices and access methods you reviewed. Record any remaining accessibility or performance work.
04
Give search engines a clear, approved site.
Search discovery starts with useful public pages and working access to them.
Open the final HTTPS domain and follow links between the homepage, services and contact route. Give each public page a descriptive title and a preferred canonical URL.
Keep private proposals, demos and unapproved client previews out of search. Check indexing settings for the real public site before handing over its sitemap.
In the verified Search Console property, inspect the exact public page and run a live test. Check crawl access, the page fetch and indexing permission. Submit the canonical sitemap and read its processing status.
What to confirmThe approved site can be fetched and its search settings match your intent. Track actual indexing separately after launch.
05
Know what you measure and what you collect.
Useful reporting starts with a small set of clearly defined outcomes.
Agree on the main outcome: a qualified inquiry, a booking or a call. Keep visits, button clicks, form submissions and confirmed inquiries distinct in reports.
Check which cookies, analytics and third-party tools the site actually uses. Make the privacy information match that behavior, and verify that optional tools follow the visitor’s choices.
Test the contact journey after declining optional analytics. Record what your measurement can miss, including declined tracking, phone conversations and inquiries received elsewhere.
What to confirmYou can explain each reported number and where it comes from. Customer contact still works with optional tracking declined.
06
Write down who looks after it next.
A launch needs a clear owner for the work that follows.
Confirm who controls the domain, hosting and accounts, how renewals are handled and where to request an update. Keep account recovery and support details accessible to the right people.
Review the written scope, ownership and cancellation terms. Clarify which content and licenses transfer, what ongoing care includes and how larger changes are agreed.
Agree on a way to recover from a failure and a date to review the site. Recheck contact delivery after changes, update outdated services and keep a record of approved edits.
What to confirmYou know who handles an outage, a content change or a renewal, and the agreement describes the handoff.
After launch
Check Google separately.
Each result answers a different question. Keep the public URL, live crawl test and index report together when reviewing search discovery.
01 / Published
Your page opens.
The agreed page is available on the final public domain. Your customers can visit it directly and follow its links.
02 / Access checked
Google can fetch it.
A successful live test checks current access and eligibility. An accepted indexing request asks Google to crawl the page.
03 / Indexed
The index report confirms it.
Check the Google Index report for the exact URL and Google-selected canonical. Indexing allows a page to be considered for search results; rankings are a separate outcome.
Why does it still say “URL is not on Google”?
A new page may have no recorded crawl yet. A successful live test or accepted request does not mean indexing has completed. Read the Page indexing reason: a blocked fetch needs attention, while an unknown URL with a passing live test still needs Google to crawl and assess it. Google decides whether and when a page is indexed.
Request indexing after a useful new page or meaningful change, then recheck the report. Repeated requests for the same unchanged page do not increase its crawl priority. In the Sitemaps report, confirm processing succeeds as well as submission. Google explains URL Inspection and sitemap processing in its own guidance.
Your first month
Keep a short review list.
Check whether inquiries arrive with the information you need, which services visitors ask about and where the website leaves a question unanswered. Improve that specific step before adding more pages.
Review real outcomes.
Compare search impressions and clicks over similar periods. A few impressions cannot establish a useful ranking trend. Review confirmed customer inquiries alongside the search data, with the limits of your measurement in mind.