Most website launches go wrong in small, boring ways: a contact form that emails nobody, a staging setting that hides the site from Google, a WhatsApp button that opens the wrong number. This website launch checklist gives you 40 checks to run before you go live, grouped by area and with an owner for each, then a launch-day sequence and a first-week routine. It works whether an agency, a freelancer or your own team built the site.
In short:
- Launch problems are rarely dramatic. They are a wrong digit in a phone number, a form with no recipient, or a noindex tag left over from staging.
- Run every check on the preview or staging site first, then repeat the critical ones on the live domain within the first hour.
- Give each check an owner: the business checks facts and contact routes; the developer checks indexing, redirects, backups and email records.
- Launch early in the working week, keep a rollback plan, and plan a short first-week routine instead of assuming the job ends at go-live.
In this guide
How to use this website launch checklist
A launch is where separate jobs meet: content, hosting, the domain, email, tracking and search. Each is usually handled by a different person, and the gaps between them are where things break, so the checklist is grouped by owner.
The preview or staging site is the copy you review on a temporary address; the live site is what customers reach on your domain. Most checks pass on staging first, but some, such as SSL, redirects and email records, only mean something on the live domain, so they return in the launch-day sequence.
| Area | Checks | Usually owned by | When |
|---|---|---|---|
| Content and pages | 1–6 | Business owner, with the writer | One to two weeks before launch |
| Forms and contact routes | 7–12 | Business owner tests; developer fixes | A week before, and again on launch day |
| Links, mobile and speed | 13–20 | Developer, with spot checks by the owner | A week before |
| SEO and indexing | 21–29 | Developer or SEO specialist | Days before, and on launch day |
| Analytics, legal pages and email | 30–35 | Developer, with the owner approving legal text | Days before |
| Backups, security and sharing | 36–40 | Developer or host | The day before and on launch day |
Copy the 40 items into a shared sheet with columns for status, owner, date and notes. A check is done only when someone has tried it on a real device and written down what they saw. "It should be fine" is not a status.
Content and pages: checks 1–6
Content mistakes are the ones customers notice first and developers are least likely to catch, because only you know whether the opening hours or the price list are right.
- Business facts are correct everywhere. Check the business name, commercial registration number if shown, phone, WhatsApp, email, address and working hours in the header, footer and contact page, and compare them with your Google Business Profile. One wrong digit costs calls silently, because nobody tells you they could not get through.
- No placeholder or demo content is left. Search the site for "lorem ipsum", "sample" and "test". On WordPress, delete the default "Hello world" post, the sample page, demo products, theme demo photos and the default tagline.
- Every page has one purpose and a next step. Read each page as a stranger and ask what the visitor should do when they reach the bottom. A service page without a call or enquiry button is a dead end. Our guide to website copy that persuades covers how to write that next step.
- Both languages are proofread by a fluent reader. If the site is in Arabic and English, each version needs its own proofread. Check that Arabic pages show Arabic menus, buttons, form labels and error messages, and that prices and phone numbers match across both versions. Our bilingual website design guide explains the layout side.
- Images are licensed, compressed and described. Confirm you own or have licensed every photo, resize large camera files before upload, and give meaningful images alt text that describes what they show.
- Prices, offers and claims are current and approved. Remove expired promotions, state whether prices include VAT, and keep only claims you can support. Have the person with authority sign off the final text in writing, so nobody rewrites the home page on launch morning.
Forms, WhatsApp and every way to reach you: checks 7–12
A business website exists to produce enquiries. If any contact route fails, the site can look perfect and still lose customers. Test these as a customer would, from your own phone, on mobile data rather than the office Wi-Fi.
- Every form arrives where it should. Submit each form with realistic details and confirm the message reaches the right inbox, not the developer's address or a spam folder, and that the visitor sees a clear confirmation. Note who receives each form and who covers when they are away.
- Form validation helps rather than blocks. Try submitting an empty form, a wrong email format and an Arabic name. Enter Saudi mobile numbers in the formats people actually type, such as 05 followed by eight digits and +966 5 followed by eight digits. If the form rejects a valid number, you lose that lead without knowing it.
- Spam protection does not stop real people. A CAPTCHA or honeypot field should block bots, not customers. Submit the form from a phone on a second network; if the challenge fails for you, it fails for customers too.
- The WhatsApp button opens the right chat. Tap it on an iPhone and an Android phone, then click it on a computer, where it should open WhatsApp Web or the desktop app. Confirm the number, and that any pre-filled message reads naturally in the visitor's language.
- Tap-to-call links dial the correct number. Phone links should use the full international format (+966 and the number without the leading zero) so they work from any phone. Tap every phone number on the site, including the footer.
- The map and directions point to the right place. Open the map from a phone and check it lands on your building, not an old address, and test each branch. Your Google Maps listing matters as much as the embed; see our Google Business Profile guide for Saudi businesses.
Links, mobile and speed: checks 13–20
Links and navigation
- No broken internal links. Click through every menu, footer link and button, or run a link checker over the staging site. Pay attention to links that were written by hand in the content, which often still point at the staging address.
- Social icons and external links go to your real profiles. Many themes ship with icons linked to the theme author's accounts or to the platforms' home pages. Remove icons for accounts you do not use rather than leaving them empty.
- A useful 404 page exists. Type a nonsense address on your domain. The page that appears should say clearly that the page was not found and offer the menu, a search box or links to your main services, in the right language.
Mobile and browsers
- Test on real phones, not only a resized browser. Use at least one iPhone and one Android phone. Check that the menu works, text is readable without zooming, buttons are easy to tap, nothing scrolls sideways, and chat bubbles do not cover the form's send button. Our article on designing for mobile first explains why this matters most.
- Check the main browsers and both directions. Open key pages in Chrome, Safari, Edge and Firefox. On a bilingual site, check both text directions in each, especially arrows and form fields.
- Run basic accessibility checks. Move through a page with the Tab key and confirm you can see where you are and reach every link and form field. Check text contrast, form labels and alt text. Our website accessibility checklist goes further.
Speed
- Measure Core Web Vitals on your key pages. Run the home page, a service page and the contact page through PageSpeed Insights on mobile. Google's web.dev defines good results as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real visits. Before launch you only have lab data, so treat it as an early warning.
- Caching is on and dead weight is gone. Confirm caching and compression are active and images use modern formats. Delete plugins you tried during the build and no longer use, and question autoplay video headers. Our article on why website speed drives sales explains the business case.
SEO and indexing checks before you go live: 21–29
Search settings are where one forgotten checkbox does the most damage, because nothing looks broken: the site works, it just does not appear in Google. For the design decisions that affect rankings long before launch, see SEO-friendly web design.
- Remove the noindex setting from staging. Staging sites are normally hidden from search engines, and that setting is easy to carry over to the live site. In WordPress, open Settings, then Reading, and make sure "Discourage search engines from indexing this site" is unticked, then search the source of a few live pages for noindex and ask the developer to confirm no X-Robots-Tag header is sent. Google is plain: once Googlebot sees a noindex rule, the page is dropped from results.
- robots.txt does not block the site. Visit yourdomain/robots.txt. A line reading Disallow: / under User-agent: * blocks the whole site, a common staging leftover. Blocking is not the same as noindex: Google cannot see the noindex rule on a blocked page, so it may still appear if other sites link to it. Add a Sitemap line to the file.
- Every page has a unique title and meta description. Titles should say what the page offers, and where relevant the city, for example "Industrial cleaning services in Riyadh" rather than "Services". Check that no two pages share the same title, and that the home page title is more than the company name alone.
- Headings and language settings are correct. Each page should have one main heading, with sub-headings in a logical order. Arabic pages need the right language code and right-to-left direction in the page markup, and on a bilingual site each page should link to its other-language version through hreflang so Google can show the right one.
- There is one version of the site. Pick www or non-www and redirect the other to it. Confirm that http redirects to https, that trailing slashes are handled consistently, and that canonical tags point to the live domain, not to staging.
- Old URLs redirect to their new equivalents. If you are replacing a site, map every old URL with traffic or links to the closest new page with a permanent redirect. Google treats 301 and 308 as permanent, calls server-side redirects the most reliable kind, and advises permanent redirects only when the change is final. Our website redesign checklist covers redirect mapping in detail.
- The XML sitemap lists only real pages. Open the sitemap and make sure it contains your live pages with full https addresses on your domain, not staging links, test pages, empty tag archives or image attachment pages. Google asks for fully qualified, absolute URLs and allows up to 50,000 URLs or 50 MB uncompressed per sitemap.
- Search Console is verified and the sitemap submitted. Add the domain as a property in Google Search Console, ideally as a domain property so all versions are covered, and submit the sitemap. Google is clear that a sitemap is a hint rather than a guarantee of crawling, but the Sitemaps report shows when it was read and whether it had errors. Our guide to getting found on Google explains the next steps.
- Your listings point to the new site. Update the website link on your Google Business Profile, social bios, directory listings and printed QR codes. If the domain changed, these are often forgotten for months.
Most launch-day SEO disasters come down to one checkbox: a noindex setting carried over from staging.
Analytics, legal pages, email and backups: checks 30–40
These checks decide whether you can measure the launch, whether you are telling visitors the truth about their data, whether your replies reach customers' inboxes, and whether you can recover if something goes wrong.
Measurement
- Analytics is installed once and recording. Open the live site in a private window and confirm the visit appears in the real-time view. The tracking code should be on every page, and not installed twice through a plugin and the theme, which doubles your numbers.
- Enquiries are tracked as conversions. Set up events for form submissions, WhatsApp clicks and phone taps, then trigger each one yourself and confirm it registers. Without this, you will know how many people visited but not how many tried to contact you, which is the number that matters.
Legal pages and consent
- Privacy policy and terms are published and accurate. Link them from the footer of every page, in both languages if the site is bilingual. The privacy policy should describe what the site actually collects: form fields, analytics, cookies and third-party tools. Our overview of Saudi website legal requirements sets out what applies to most businesses.
- Consent and data handling match your policy. If you use cookies or tracking that need consent, the banner should work and its choices should be respected. Forms should collect only what you need. The PDPL website compliance checklist covers Saudi personal data rules in general terms; it is not legal advice, so ask a qualified adviser about your specific case.
Email deliverability
- Your domain's email is authenticated. Ask whoever manages your domain to confirm SPF, DKIM and DMARC records are in place for every service that sends email as you, including the website, your email provider and any newsletter tool. Google's sender guidelines require all senders to Gmail to set up SPF or DKIM, and senders of more than 5,000 messages a day to use all three. See our guide to business email on your own domain.
- The website's own emails reach the inbox. Form notifications should go through an authenticated mail service from an address on your domain, not the server's default mail function. Send tests to Gmail and Outlook and check the spam folders.
Backups, security and sharing
- A full backup exists and a restore has been tested. Take a complete backup of files and database the day before launch and store a copy away from the hosting server. A backup that has never been restored is a hope, not a plan; ask the developer to restore it once to a test location.
- Accounts and access are cleaned up. Remove test users and old developer accounts, give each user the lowest role they need, and turn on two-factor authentication for administrators. Domain, hosting and admin accounts belong in the company's name, with access known to more than one person.
- Software is updated, SSL is valid and renewals are on. Update WordPress, the theme and plugins before launch, not the week after. Check the padlock on several live pages and look for mixed-content warnings from images still loading over http. Confirm the SSL certificate renews automatically and note the domain and hosting renewal dates with auto-renew turned on.
- The favicon and site icon are set. Your logo mark should appear in the browser tab, bookmarks and on phone home screens. A default theme icon looks unfinished.
- Social previews look right. Paste your home page and a service page into a WhatsApp chat with yourself. The preview should show the correct title, a short description and a clear image, not a cropped logo. These previews come from Open Graph tags, which your SEO plugin or developer can set per page.
Once the site is live, these checks become routine rather than a one-off. Our website maintenance checklist sets out the weekly, monthly and yearly tasks.
Launch day: the go-live sequence
Pick the launch time deliberately. In Saudi Arabia the working week runs Sunday to Thursday, so a launch on Sunday, Monday or Tuesday morning leaves several working days for the team to fix anything that appears. Avoid the hours before the weekend, the start of Eid holidays or a big campaign. Then work through this sequence.
1. Freeze changes
Nobody edits content or installs plugins during the launch window. Last-minute edits are a common reason a checked site breaks on the day.
2. Back up both sites
Take a final backup of the old site, if there is one, and of the new site. This is your rollback.
3. Switch the domain
A day or two ahead, the developer lowers the DNS time-to-live on the records that will change. On the day, point the domain to the new hosting; some visitors may see the old site for a few hours while the change spreads.
4. Repeat the live-only checks
On the real domain, re-check indexing (checks 21 and 22), the single https version and redirects (25 and 26), SSL and mixed content (38), and a sample of old URLs.
5. Test every contact route again
Submit each form, tap WhatsApp and phone links, and confirm analytics and conversion events fire (checks 7, 10, 11, 30 and 31). Email settings often change when hosting changes, so re-test check 35.
6. Tell Google
Submit the sitemap in Search Console and use URL Inspection on the home page and one or two key pages to request indexing.
7. Announce it
Update your Google Business Profile, social bios and email signatures, then share the link. Your social preview (check 40) is what people will see first.
Have a rollback plan
Decide in advance who can call a rollback and what triggers it, such as forms not arriving or the site down for more than a set time. Then restore the old DNS settings or the previous backup and fix the problem calmly on staging.
What usually goes wrong
Staging settings on the live site
Noindex, robots.txt blocks and canonical tags still pointing at the staging address.
Email breaks after the move
Changing name servers without copying the MX records can stop company email, not only website mail.
Hard-coded staging links
Images and buttons that still load from the temporary address and break once it is removed.
No one watching the inbox
Enquiries arrive on launch day and sit unanswered because the form recipient was never agreed.
The first week after launch
A launch is a starting point. The first week is when real visitors find the problems no checklist can predict, so keep the routine short and specific.
| When | What to check | Who |
|---|---|---|
| Day 1 | Send a test enquiry through each form in the morning and afternoon; confirm the site loads on mobile data; look for errors in Search Console | Owner and developer |
| Days 2–3 | Review not-found errors and add redirects for any old URLs you missed; collect feedback from staff and early customers | Developer |
| Day 5 | Open analytics: are visits and conversion events recording, and where are visitors coming from | Owner |
| Day 7 | Send one batch of fixes, update your access and renewal records, and write down who now owns each task | Owner |
Expect indexing to take time. New pages can appear in Google within days or take several weeks, and nobody can guarantee rankings or a date. Search Console's Page indexing report will tell you which pages are in and why others are not.
This article stops at the end of week one. For month one and beyond, including measurement habits and renewal dates, read what to do after your website launches.
How Webnaa launches a website
Webnaa is based in Riyadh and provides web design for businesses across Saudi Arabia. Most of the checks above are built into how we deliver a site, so you are not left to run them alone:
- Before work starts you get the price, scope and delivery date in writing. The preview link is sent within 24 hours at most from receiving all the information and content we need from you.
- You review the design on a preview link before launch. If you do not like it during the design stage, a money-back guarantee applies, per the refund policy.
- We test on phone and computer, then launch on your domain with hosting and SSL included. The domain is a standard one, registered in your name.
- Search engine setup is part of the job: we connect the site to Google Search Console and submit the sitemap.
- The privacy policy and terms are ready at launch, along with a contact form, WhatsApp button, direct call number, map location and a printable QR code.
- On every website, we write the content for you from the business details you send through one form, and WordPress websites add an easy WordPress dashboard.
On a WordPress website, you edit the site yourself from the dashboard, and technical support after launch is included in the subscription, along with fixing technical faults, security and technical updates, and backups. The website design service starts from SAR 39 a month with no setup fee and no long contract; a 5-page WordPress website in Arabic and English is SAR 324 a month, paid in advance every 6 months or for a year at 10% off. A new page after launch is priced as in the calculator and added to your subscription. Work out your own price in the price calculator, and how we work walks through each stage. If you already have a site and only need someone to look after it, see our website maintenance service.
Choose what you need, see your exact price
The price updates with every choice. No surprises, no hidden fees.
The calculator is off. Press the power button to start
From Zoho, a global provider with data centres in Riyadh and Jeddah. More than 10 addresses are quoted separately.
Launch a website that has already been checked
Tell us about your business and see your design on a preview link before anything goes live.
FAQ
How long before launch should I start the website launch checklist?
For a small business site, start content checks one to two weeks ahead and technical checks about a week ahead, leaving two working days for fixes.
Why is my new website not showing on Google?
First check the basics: the noindex setting, robots.txt and whether the site is verified in Search Console with a sitemap submitted. If those are fine, it may simply not be crawled yet. Use URL Inspection to see Google's view of the page. Indexing can take days or weeks, and no one can guarantee a date or a ranking.
What is the best day to launch a website in Saudi Arabia?
Early in the working week, on a Sunday, Monday or Tuesday morning, so your team and your developer have several working days to respond. Avoid launching just before the weekend, a public holiday or a major campaign.
Do I need redirects if I keep the same domain?
Yes, if any page addresses change. Search engines and customers know your old URLs, so each one with traffic or links should permanently redirect to its closest new page. If every URL stays the same, you do not need them.
Who should sign off a website before it goes live?
One person with authority, usually the owner or manager, approves the text, prices and contact details in writing. The developer signs off the technical checks.
Summary
A good website launch checklist is less about technology than about making sure nothing falls between people. Check the content and every contact route yourself, have the developer handle indexing, redirects, email records and backups, and repeat the critical checks on the live domain within the first hour. Launch early in the working week, keep a rollback plan, and give the first week a simple routine.
Sources: Google Search Central: block indexing with noindex, Google Search Central: build and submit a sitemap, Google Search Central: redirects and Google Search, web.dev: Web Vitals, Google: email sender guidelines. Webnaa: pricing, how we work.