During the first seven days, test every enquiry route, check analytics and Search Console, submit the sitemap, inspect priority pages, follow redirects, test mobile usability and confirm backup access. Record a launch baseline; the first week is too soon to judge organic search or lead performance.

Launch day proves that the domain opens. It does not prove that the website can receive leads, collect useful data or reach search engines.

Use the first week to check the pages, contact routes and measurement from a visitor’s point of view.

Updated 4 November 2026: clarified account access, Google’s indexing timelines and Business Profile eligibility.

Day 1: Test the customer routes

Start with the actions that can create revenue.

Test:

  • every contact form;
  • telephone links;
  • WhatsApp links;
  • email links;
  • booking links;
  • checkout or payment steps;
  • downloadable documents.

Use a phone and a computer. Submit forms through mobile data and Wi-Fi. Confirm the inbox, spam folder and any CRM record.

Read the received notification. Check the reply address and every field.

Ask one person who did not work on the project to complete the main task without guidance. Watch where that person hesitates.

Record the result in a launch log. “Tested” should include the date, device, route and outcome.

For a service business, ask a colleague to send a test enquiry through one main service page or WhatsApp link. Confirm who receives it and whether the reply gathers enough detail to scope the work.

Day 2: Confirm analytics

First confirm that someone at the business can access its Google Analytics property and that the site tag is installed. If tracking or the needed events are missing, ask the site implementer to configure them. Then open Realtime while you browse the site from another device. Realtime and DebugView can confirm collection during setup; many other reports take 24–48 hours to process.

Check:

Action Expected event
Page opens page_view
Form starts form_start
Form submits successfully generate_lead
Phone link opens One consistently named contact event
WhatsApp link opens One consistently named contact event
Document downloads file_download

Do not send names, email addresses, telephone numbers or form text to Google Analytics. Google also warns against PII in page URLs and campaign parameters, since Analytics can collect those values.

Google lists generate_lead for a form submission or information request. Set it as a key event only after you confirm it fires once on a successful submission. A button click should not count as a lead when the form later fails.

Save a screenshot of the Realtime test and note the Analytics property owner.

Day 3: Verify Search Console and the sitemap

Confirm that the business has access to its Search Console property. If it does not, ask the current property owner to add an authorised user or have the site implementer help set up and verify a property.

Choose the Search Console property that matches your access and the site area you need to track:

Property Scope When it fits
Domain All protocols and subdomains Use it when you can add the required DNS record and want one view across the domain.
URL-prefix The exact protocol, hostname and path prefix Use it when you need a narrower scope or cannot edit DNS. Verify the exact address prefix you want to track.

Find the sitemap, often at /sitemap.xml. Google Search Central explains how to build and submit one. Open it in a browser and check that it:

  • loads without an error;
  • uses the live domain;
  • lists canonical URLs;
  • excludes staging pages and redirects;
  • includes the pages you want indexed.

Submit the sitemap through Search Console.

Google describes sitemap submission as a hint, not a guarantee that it will fetch or crawl every URL. A sitemap can help a new site with few external links get discovered.

If you can edit robots.txt, add the sitemap location there as another discovery route. Otherwise ask the developer or platform provider to make the change.

Day 4: Inspect priority pages

Use URL Inspection for the homepage and the main service pages. Check the indexed version, then run a live test when you need to diagnose a current crawl or rendering problem.

Run the live test and check:

  • page fetch;
  • indexing allowed;
  • canonical URL;
  • mobile rendering;
  • structured data where relevant.

Request indexing after fixing a genuine issue or launching an important page. Google says crawling can take days or weeks, and a request does not guarantee inclusion. Repeated requests do not speed up crawling.

An indexed page can still fail to appear for a particular search. Indexing means Google has a version of the page in its index; it does not guarantee a ranking.

Check the public page source too. A noindex tag left from staging can hide the whole site.

Day 5: Find broken paths

Crawl or click through the site.

Check:

  • navigation;
  • footer links;
  • internal article links;
  • old URLs;
  • image paths;
  • canonical tags;
  • redirects;
  • social preview images;
  • favicon;
  • policy pages.

If the new site replaced an old one, map each valuable old URL to the closest new page. Sending all old pages to the homepage wastes context and can frustrate visitors.

Open the website with both www and the root domain. Confirm one version redirects to the chosen canonical version over HTTPS.

Review the server or platform logs for 404 errors. Some may come from old bookmarks, search results or external links that the project team did not know existed.

Day 6: Test mobile performance and accessibility

Use a mid-range phone, not only the designer’s computer.

Check:

  • text size;
  • tap targets;
  • menu access;
  • sticky elements;
  • form keyboard types;
  • image loading;
  • layout movement;
  • contrast;
  • focus states;
  • reduced-motion behaviour.

Run PageSpeed Insights for a Lighthouse lab test and Chrome User Experience Report field data where available. Field data represents a rolling 28-day period and may be absent when Google has too little real-user data for the page or origin. Use the lab report to investigate a particular page, and treat both reports as diagnostic evidence.

Fix large images, blocked content and scripts that delay the first useful screen. Keep motion that helps orientation. Remove motion that blocks reading or form use.

Navigate with a keyboard. Label form fields. Add useful alt text to informative images. Decorative images should not repeat surrounding text.

Day 7: Secure the handover

Confirm that the business controls or can access:

  • domain registration;
  • DNS;
  • hosting;
  • source repository or CMS;
  • Search Console;
  • Analytics;
  • business email;
  • form service;
  • backups;
  • third-party licences.

Run a backup and document how to restore it.

Record the current versions of plugins, frameworks and important integrations. Store secrets in the hosting environment, not in a shared document or repository.

Set a review schedule for forms, updates, backups and content.

Create a launch baseline

The first week has too little data for a serious performance verdict.

Record a baseline instead:

Measure First-week record
Indexed priority pages Count
Organic impressions Count
Form tests passed Count
Real enquiries Count
Mobile performance Key findings
404 errors Top paths
Analytics events Pass or fail
Business Profile website link Correct or incorrect

Compare the baseline after 30 and 90 days.

A site can receive no organic leads in week one and still have a sound setup. Search systems need time to crawl, understand and test pages. The business may also need promotion, listings, links and useful content.

How to promote a website after launch

Tell existing customers and contacts the new website address. Update business listings you control and check that an eligible Google Business Profile points to the new site. An eligible service-area business can travel to customers; it does not need a storefront. Online-only businesses are not eligible. Before paying to promote a page, test its contact route and confirm that analytics records the action you want to measure.

If these checks uncover problems with the website’s enquiry route or measurement, review IDJoy’s website design scope.