Back to blog

SEO for a New Website: Setup Checklist Before and After Launch

SEO Course

SEO for a New Website: Setup Checklist Before and After Launch

By Forsa | SEO Audit and Technical SEO Specialist

SEO setup for a new website: domain, platform, HTTPS, Search Console, GA4, sitemap, robots.txt and site structure, with a launch and first-30-days checklist.

Updated 31 October 2026 · Part of the SEO guide series

Short answer: SEO for a new website starts before launch: choose a platform that lets you control titles, URLs and indexing; serve the site on HTTPS; plan a simple structure; then, at launch, verify the site in Google Search Console, submit an XML sitemap, check that nothing blocks indexing and set up analytics. After that, publish useful pages and earn links. Expect results over weeks to months, not days.

Before launch

1. Choose a domain for people, not keywords

Pick a name that is easy to remember, spell and say. Google notes that keywords in the domain name alone have hardly any ranking effect beyond appearing in breadcrumbs, so a brandable domain is fine.

2. Choose a platform you can control

Make sure your CMS or site builder lets you edit titles, meta descriptions, headings, URLs, image alt text, redirects, canonical tags and noindex, and generates an XML sitemap. JavaScript-heavy builds should render main content in the HTML (server-side rendering or prerendering).

3. Use reliable hosting and HTTPS

Fast, stable hosting reduces server errors and slow pages. Serve every page over HTTPS with a valid certificate and redirect HTTP to HTTPS. Secure serving is one of the page experience questions Google asks site owners to consider.

4. Plan a simple structure

  • Group pages into clear sections (for example /services/, /blog/, /about/).
  • Keep important pages within a few clicks of the homepage.
  • Use short, readable URLs: /services/roof-repair/, not /page?id=123.
  • Plan one page per main topic or service to avoid overlapping pages later.

5. Prepare core pages

Homepage, main service or product pages, About (who you are), Contact (with consistent business details), and policies. Write unique titles and descriptions for each.

6. Keep the staging site out of Google

Password-protect the staging site. Do not rely on robots.txt for this; Google says robots.txt is not a way to keep pages out of search. Before launch, remove any noindex you used on staging from the live site.

Launch day

7. Verify the site in Google Search Console

Property type Covers Verification
Domain property (example.com) All subdomains and protocols (http, https, www, m) DNS record only
URL-prefix property (https://www.example.com/) Only URLs starting with that exact prefix Several methods (HTML file, meta tag, Analytics, Tag Manager, DNS)

A Domain property gives the most complete data; add a URL-prefix property too if you need a quick verification method or section-level data.

8. Submit an XML sitemap

List the canonical, indexable URLs you want in Google and submit the sitemap in Search Console. See what is a sitemap for format and best practices.

9. Check that nothing blocks indexing

  • robots.txt does not disallow important sections.
  • No noindex on pages you want indexed.
  • Canonical tags point to the live HTTPS URLs.
  • Use URL Inspection on the homepage and a key page, then request indexing.

10. Set up analytics

Install Google Analytics 4 (or your analytics tool) and define the key events: form submissions, calls, purchases, sign-ups. Link GA4 with Search Console to see organic queries next to on-site behavior. Respect consent rules where they apply.

11. Add Bing Webmaster Tools

Bing runs its own index, so verify your site in Bing Webmaster Tools too (it offers an option to import sites from Search Console) and submit the same sitemap.

Verify Your Launch With Free Checks

Right after launch, test the live site instead of assuming the settings carried over from staging:

  • Run the homepage and 1 or 2 key pages through a free SEO audit to catch missing titles, missing meta descriptions, slow loading, mobile problems and broken basics.
  • Use an AI crawler access check to confirm that robots.txt does not accidentally block search and AI crawlers you want to reach your content.
  • Open /robots.txt and /sitemap.xml in a browser and confirm they load and list your live HTTPS URLs.

Example: A Local Service Site Launch Checklist

WhenTaskDone when
2 weeks beforePlan 6 core pages and URLsEach service has 1 page and 1 target topic
1 week beforeWrite unique titles and descriptionsNo 2 pages share a title
Launch dayRemove staging noindex, verify HTTPS and redirectsOnly 1 version of the site resolves
Launch dayVerify Search Console, submit sitemap, install GA4Sitemap shows as processed
Week 1Request indexing for key pages, create Business ProfilePages appear in URL Inspection as indexed
Weeks 2 to 4Publish first helpful articles, ask for local linksNew pages linked from existing ones

The first 30 days

  1. Watch Search Console's Page indexing report for errors and excluded pages.
  2. Fix broken links, redirect old URLs (if replacing a site) with permanent 301 redirects.
  3. Publish your first helpful content that answers real customer questions.
  4. Link new pages from existing ones so Google can find them.
  5. Set up your Google Business Profile if you serve customers locally.
  6. Start earning mentions and links: partners, suppliers, local directories, industry associations.

For the technical details behind these steps, see technical SEO foundations.

Common launch mistakes

  • Leaving noindex on from staging.
  • Blocking the whole site in robots.txt.
  • Launching without redirects from an old site's URLs.
  • Multiple versions (http/https, www/non-www) without redirects to one.
  • Thin placeholder pages ("Coming soon") indexed.
  • No analytics or conversion tracking at launch.

How long does SEO take for a new site?

Google says some changes take effect within hours and others can take several months, and suggests waiting a few weeks before judging whether a change helped. A new site with no links or history usually takes longer to gain visibility for competitive terms; less competitive, specific queries tend to come first.

FAQs

How do I do SEO for a new website?

Set up the foundations (HTTPS, a controllable platform, clear structure), verify the site in Search Console, submit a sitemap, make sure nothing blocks indexing, install analytics, then publish useful content and earn links over time.

How do I get my new website on Google?

Verify it in Google Search Console, submit an XML sitemap, use URL Inspection to request indexing for key pages, and link to it from other sites and profiles so Google can discover it.

Should I use a Domain or URL-prefix property in Search Console?

A Domain property covers all subdomains and protocols and gives the most complete data, but needs DNS verification. A URL-prefix property covers one exact prefix and can be verified in more ways. Many sites use both.

Do I Need to Request Indexing for Every Page?

No. A sitemap and good internal links are usually enough for Google to find your pages. Use the request indexing option in URL Inspection for your most important new or updated pages, and be patient, because it does not guarantee immediate indexing.

Can I Launch Before the Content Is Finished?

Yes, but do not index placeholder pages. Publish only pages that are useful and complete, keep unfinished sections off the sitemap and add the rest as it is ready. Thin or empty pages can hold back how Google sees the whole site.

Does my domain name need keywords for SEO?

No. Google says keywords in a domain name alone have hardly any ranking effect beyond breadcrumbs. Choose a memorable, brandable name.