A new website can look perfect and still be invisible to Google because one setting was left on from the staging server. This technical SEO checklist covers what to verify in the days before launch and the day after, so search engines can find, read and index the site properly. You do not need to do every check yourself, but you should know what each one is and ask your developer to confirm it in writing.
Technical SEO checklist: before launch, on staging
1. Confirm the staging site is blocked, and know how it is blocked
Staging sites should not appear in Google. Password protection is the safest method. If your developer has used a “noindex” setting or a robots.txt block instead, write down exactly where, because the same setting must be removed at launch. Google notes that robots.txt is not a mechanism for keeping a page out of Google. To keep pages out of the index, use noindex or a password.
2. Every page has a unique title and meta description
The title appears as the clickable headline in search results. Google’s SEO starter guide describes a good title as unique to the page, clear, concise and accurate. Google uses the meta description mainly as a source for the snippet below the title, which affects whether people click. Check for duplicates and for any page still showing a template title like “Home | My WordPress Site”.
3. One H1 per page that says what the page is about
The main heading should match the page’s purpose. A service page for “Commercial cleaning in Abu Dhabi” should say that, not “Welcome”.
4. Clean, readable URLs
Use short, descriptive, lowercase URLs with hyphens: /services/commercial-cleaning/ rather than /page?id=4471. Decide on trailing slashes and stick to one pattern.
5. Canonical tags are correct
A canonical tag tells Google which version of a page is the main one when similar versions exist, such as URLs with tracking parameters. Google treats it as a hint rather than a rule, and may pick a different page. Check that each page’s canonical points to itself on the live domain, not to the staging address.
6. Internal links work
Run a crawl with a tool such as Screaming Frog (free for small sites) and fix broken links, links pointing at staging, and pages that nothing links to.
7. Images are compressed and described
Resize large images, use modern formats such as WebP, and give meaningful images alt text that describes what they show. This helps both search and visitors using screen readers.
8. Mobile layout and speed are checked
Test key pages on real phones. Run PageSpeed Insights on the home page and main service pages, and fix any obvious problems with Core Web Vitals before launch rather than after.
9. Structured data where it fits
Add schema markup that matches the page content: Organization or LocalBusiness on the home or contact page, FAQPage where there are real FAQs, Article on blog posts. Validate it with Google’s Rich Results Test.
10. If you are replacing an old site, the redirect map is ready
List every old URL that has traffic or links and map it to the closest new page. Google’s site move guidance recommends server-side permanent redirects and keeping them for as long as possible, generally at least a year.
Launch day
- Remove the staging block. Check that no page carries a noindex tag by mistake and that robots.txt does not say “Disallow: /”.
- Force HTTPS. Every http:// address should redirect to https://, and the www and non-www versions should redirect to one chosen version.
- Switch on the redirects from the old site and test a sample of old URLs.
- Check that the XML sitemap is live, lists only pages you want indexed, and uses the live domain.
- Submit forms on the live site and confirm the enquiries arrive.
- Confirm analytics and any conversion tracking are firing on the live domain.
The first week after launch
- Verify the site in Google Search Console if it is not already, and submit the sitemap.
- Use the URL Inspection tool on the home page and two or three key pages to check Google can fetch and render them.
- Watch the Pages report for unexpected “Excluded” or “Not found (404)” entries.
- If the domain changed, use the Change of Address tool in Search Console for the old domain.
- Update your Google Business Profile, social profiles and any directory listings with new URLs.
- Re-run a crawl to catch anything broken by the move to the live server.
The mistakes that cause the most damage
- Launching with “Discourage search engines from indexing this site” still ticked in WordPress settings.
- Canonical tags still pointing at the staging domain.
- No redirects from the old site, so years of links and rankings lead to 404 pages.
- Sitemaps listing redirected, broken or noindexed URLs.
- Blocking CSS or JavaScript in robots.txt, which stops Google rendering the page properly.
Any one of these can undo months of work, and each one takes minutes to check.
A note on what technical SEO does not do
Technical SEO makes sure Google can access and understand your site. It does not make the content worth ranking. Once the checklist is clean, your effort is better spent on clear service pages, useful articles and a steady stream of reviews and links.
Every website Emberoot builds goes through a pre-launch check like this one before handover, and for sites that need ongoing search work we cover it under digital marketing.
Launching soon and want a second check? Book a call before the switch.
Frequently asked questions
What is the difference between technical SEO and on-page SEO?
Technical SEO covers how search engines access and process your site: crawling, indexing, redirects, sitemaps, speed, HTTPS and structured data. On-page SEO covers the content of each page: the words, headings, titles, images and internal links. A site needs both. Technical problems can stop good content being found, and clean technical set-up cannot rescue weak content.
How soon will Google index my new website?
There is no fixed time. A small new site with a submitted sitemap is often crawled within days, while full indexing can take a few weeks. You can request indexing of key pages through the URL Inspection tool in Search Console. Links from other sites, such as your business directories and social profiles, help Google find it sooner.
Do I need an XML sitemap for a small website?
Google says sitemaps are not required, and a small, well-linked site can be found without one. Most CMS platforms generate one automatically, though, and submitting it in Search Console costs nothing. It helps Google discover new pages faster and gives you indexing reports grouped by sitemap, which makes problems easier to spot.