Free Growth Assessment
Free Checklist

SEO for a New Website: What to Set Up Before Launch

SEO for a new website means getting the site found, crawled and measured from day one. This checklist gives you thirty pass-or-fail checks to run while you plan, before launch, on launch day and in the first month.

Last updated: November 20, 2026
Plan
Pages, addresses, names and access.
Before Launch
Crawl, index, pages, speed and AI.
Launch Day
Lift blocks, verify, submit, test.
After Launch
Review at day seven and day thirty.
What It Is

What SEO for a New Website Means and Why It Starts Before Launch

SEO for a new website is the set of checks that decide whether Google, ChatGPT and your buyers can find the site on its first day. They’re easier to run while the site is still a build than after it’s live and quiet. Simple idea.

Google lists three minimum technical requirements. Googlebot can’t be blocked, the page has to return an HTTP 200 status, and it needs indexable content. Meeting them makes a page eligible, not indexed. Missing one keeps it out.

This sheet is for a brand-new site with no old addresses to protect. It sits under our website management services, which cover who looks after the site once it’s live. If the site replaces an old one, start with our guide to website migration SEO instead. A startup chasing authority should read our SEO for startups page too.

Brass key and a closed leather folder on a walnut console outside a glass office entrance lit at dusk
Where It Breaks

Why a Good-Looking New Site Still Launches Invisible

The launch looks fine. Pages load, the logo is right and the form works. Looks done. And Google has been told, by a setting left over from the build, to look away.

That’s the usual shape of it. A password or a noindex tag goes on during the build, which is correct, and nobody puts removing it on the launch list. A canonical still points at the build address and the error page says 200. None of it shows on screen.

Each one is a quick fix once somebody looks, but nobody is assigned to look, because the designer, the developer and the marketer each assume another has it, and by the time Search Console shows a problem the launch has already been announced.

Launch SEO that nobody owns doesn’t fail loudly. It just never starts.

How a New Site Goes Missing
Each one hides behind a site that looks finished.
A noindex tag or a robots rule left over from the build
A canonical link that still points at the build address
An error page that tells Google it is a real page
Service copy locked inside images or a script
Analytics that was never tested with a real form
Nobody named to read Search Console in week one
The Checklist

The SEO Checklist for a New Website

Copy the sheet into Google Docs or your project tool and run it in order. Each line carries a tag, Plan, Before launch, Launch day or After launch, so you can see what has to be done by when. The whole thing sits on this page, with no form, no email and no download. Print it if you like.

New Website SEO Checklist
Thirty lines. Tick each box, then write the result.
Part 1 Plan, Pages, Names and Access
1. A page list with one search phrase for each pagePlan
List every page the site needs on day one, such as the home page, each service, about and contact. Give each one the main phrase a buyer would type, and make sure no two pages chase the same one. Our guide to keyword research for MSPs shows how to find them, and our keyword research template is the sheet to keep them in. Pass is one page and one phrase on each row.
Result and notes
2. Every address is planned in plain wordsPlan
Google recommends readable words and hyphens in a URL. Pick the final address of each page now, since changing it later means redirects. Our post on website architecture for SEO covers how to group service pages. Pass is a list of addresses a buyer could read aloud.
Result and notes
3. One address for the site is chosen, on HTTPSPlan
Decide whether the site lives at the address with www or without, and run it on HTTPS from the first day. Every other version will need a permanent redirect to the chosen one, and Google calls a redirect a strong signal that the target should be canonical. Pass is one chosen address and a note of the redirects to set.
Result and notes
4. The build site is private, and every block is written downPlan
Build on an address nobody can open without a password. Google says robots.txt isn’t a way to keep a page out of Google, and points to a password or a noindex tag instead. Write down each block you set, so you can lift every one at launch. Pass is a build site behind a login and a list of blocks to remove.
Result and notes
5. You own the keysPlan
Register the domain, hosting, analytics and Search Console under accounts your company controls, not a freelancer’s or a former vendor’s. A Domain property in Search Console is verified with a DNS record at your domain provider, so you need that login anyway. Pass is a named owner and a second admin for each login. Our SEO onboarding checklist covers the same list from the partner’s side.
Result and notes
Part 2 Crawling and Indexing, Can Google Reach Each Page
6. Every wanted page returns a 200 and has text on itBefore launch
Google lists three minimum technical requirements for appearing in Search. Googlebot isn’t blocked, the page returns an HTTP 200 status and it has indexable content. Crawl the build and list each address with its status. Pass is every wanted page showing 200 with real words on it.
Result and notes
7. A made-up address returns a real 404Before launch
Type an address that doesn’t exist. The page should say it’s missing and the server should send a 404 status. Google says an empty page or an error message sent with a success code shows up as a soft 404 in Search Console. Pass is a 404 status and a page that offers a way back to the home page and the services.
Result and notes
8. Every other version of the address redirects in one hopBefore launch
Try the http version, the www version and the address with and without a closing slash. Each should land on the chosen address in one step. Google says a permanent redirect, a 301 or 308, tells it the target should become canonical. Pass is one hop each, with no chains.
Result and notes
9. Each page names its own address as canonicalBefore launch
A page can be reached with tracking tags or a different slash. A rel=canonical link tells Google your preferred version, and Google calls it a strong signal. Check that each canonical points at its own live address, never at the build site and never at the home page. Pass is a self-pointing canonical on every page, and internal links that use that same address.
Result and notes
10. The XML sitemap lists the pages you want found, and only thoseBefore launch
List absolute, canonical addresses and nothing else. Google ignores the priority and change-frequency tags, and says submitting a sitemap is a hint, not an order. Keep one file under 50 MB or 50,000 addresses, and add a Sitemap line to robots.txt. Pass is a sitemap that matches the page list from line 1.
Result and notes
11. Every page is reachable by real linksBefore launch
Google says it only reliably crawls a link that is an a element with an href. Buttons and script-driven menus can hide pages from it. Walk the site from the home page and count the clicks to each page. Pass is every wanted page linked from another page with a plain link and words a buyer would understand.
Result and notes
12. The words are in the page, not only in a script or an imageBefore launch
View the page source, then switch scripts off in the browser. The copy, headings and links should still be there. Google also notes that server-side or pre-rendering is still a good idea, since not all bots run JavaScript. Pass is the same copy and links with scripts off. Line 29 repeats the check on the live site.
Result and notes
Part 3 Pages, Does Each Page Say What It Is
13. Every page has its own titleBefore launch
Google says every page should have a title element, descriptive and concise. Skip titles such as Home, and put the service and the buyer’s word near the front. Pass is a unique title on each page that says what is on it.
Result and notes
14. Key pages have a description written for a personBefore launch
Google builds snippets from the page content and uses the meta description when it describes the page better. So write one for each key page, in plain words, and don’t expect it to show every time. Pass is a short, unique description for each service page, the home page and the contact page.
Result and notes
15. Every page has one job, real words and a name behind itBefore launch
Delete placeholder text and coming-soon pages. Google asks whether it’s clear who created the content, and its spam policy treats many pages made to rank with no value for people as scaled content abuse. Pass is a page list where each page has a purpose, finished copy and the company or a person standing behind it.
Result and notes
16. Headings tell a reader what the page coversBefore launch
Write one H1 that says what the page is, and subheadings that match how a buyer would scan it. Google says heading order does not matter for Search, so this line is for people and screen readers. Pass is a page you can skim through its headings alone.
Result and notes
17. Images have a job, a plain filename and alt textBefore launch
Google says the filename and the alt text are the key signals about an image, with the alt text as the main attribute. Name each file in plain words and describe it for a person who can’t see it. Keep the page’s message out of images. Pass is a described image everywhere one appears.
Result and notes
18. Markup matches what a visitor can seeBefore launch
If you add structured data, Google says it shouldn’t mark up content readers can’t see. Add only what the page shows, such as the company name and logo, then run the page through the Rich Results Test. Google also says AI features need no special schema. Our schema markup services page covers the setup. Pass is markup that describes only things on the page.
Result and notes
Part 4 Mobile and Speed, Does It Work in a Buyer’s Hand
19. The phone version holds the same contentBefore launch
Google indexes the mobile version of your pages and says the content should match desktop. A different layout is fine, such as accordions, if nothing is dropped. Open each key page on a phone and compare it with the desktop copy. Pass is the same copy, links and images on both.
Result and notes
20. A lab speed test is run and recorded before launchBefore launch
The Core Web Vitals targets are an LCP of 2.5 seconds, an INP of 200 milliseconds and a CLS of 0.1, measured at the 75th percentile of real page loads. A brand-new site may not have enough real visits yet, so run PageSpeed Insights on each key page now and again after launch. Pass is a recorded mobile result and a list of what to fix. Our website speed optimization page covers the fixes.
Result and notes
21. Forms, phone links and booking work from a phoneBefore launch
Submit every form on a phone over mobile data, tap each phone number and open each booking link. Check the message lands with a person and not in a spam folder. Pass is a test entry for each form, received in the right inbox the same day. Our lead generation website design page shows how C4 plans a site around the booked call.
Result and notes
Part 5 AI Search, Can the Answer Tools Read and Quote You
22. A decision is written for each AI crawlerBefore launch
OpenAI, Anthropic and Perplexity each document separate bots, such as OAI-SearchBot and GPTBot, ClaudeBot, Claude-User and Claude-SearchBot and PerplexityBot, and each treats search and training differently. Decide bot by bot, write it into robots.txt, and check that your firewall isn’t blocking the ones you allow. Our AI crawler post sorts them by job. Pass is a written rule for each bot and a firewall check.
Result and notes
23. What a buyer asks is answered in plain textBefore launch
Google says important content should be available in textual form. Put who you serve, what you manage, where and how to start in words on the page, not only in an image, a PDF or a video. Pass is a service page where each of those facts can be read in the page source.
Result and notes
24. Each key page opens with a direct answerBefore launch
This one is our own habit, not a Google rule. Open each key page with one or two sentences, under 40 words, that answer the question the page is about, so a reader or an answer tool can lift them. Google says AI features need no special optimizing, so this is about clarity. Pass is a lead on every service page that makes sense with nothing around it.
Result and notes
25. A day-zero log of AI answers is savedLaunch day
Ask ChatGPT, Perplexity, Claude and Gemini the questions a buyer would ask about your service and your city, with the same wording every time. A new company won’t be named yet, and that’s the point. Pass is a dated log of who is named, which becomes your baseline. See our guides to prompt research and measuring AI search visibility for the method, and our AI search prompt library for thirty questions to start the log from.
Result and notes
Part 6 Launch Day and the First Month, Switch It On and Watch
26. Every build block is lifted on the live addressLaunch day
Open the live robots.txt, the page source and the response headers. Look for a leftover rule that disallows the whole site, a noindex tag or header, and a password. Google warns that if robots.txt blocks a page, the crawler never sees a noindex rule. Pass is a live site with none of the blocks from line 4.
Result and notes
27. Search Console is verified and the sitemap is submittedLaunch day
Add a Domain property with the DNS record Google gives you, then submit the sitemap in the Sitemaps report. Submitting is only a hint, so it helps and doesn’t command. Pass is a verified property, a submitted sitemap and two named people with access.
Result and notes
28. Analytics is on and one key event is testedLaunch day
Install Google Analytics 4 and mark the actions that matter, such as a form sent or a booking made, as key events. Then do each one yourself and watch it appear. Pass is a tested event for each action and a note on how your own visits are kept out of the reports.
Result and notes
29. The home page and key pages are inspected and sent to GoogleLaunch day
In the URL Inspection tool, run the live test on the home page and each key page, check the tested page, then request indexing. Google says a quota applies, crawling can take a few days to a few weeks and a request doesn’t promise inclusion. Pass is a tested result for each page and the requests logged.
Result and notes
30. The first-month review is booked and loggedAfter launch
Put two dates in the calendar, day seven and day thirty. Read the Page indexing report and the Performance report, list each page that isn’t indexed with Google’s reason, fix what you can and rerun the AI log from line 25. Google says it can take a few weeks to notice a new site, so judge the fixes and not the rankings. Pass is a dated row for each review.
Result and notes
Hand moving a blank card on a board of blank cards joined by crimson string, beside a steel ruler
Free Tools

Where to Check Each Part

You don’t need a paid suite for this. A site crawler, a phone, a browser, PageSpeed Insights, the Rich Results Test, Search Console and the AI tools themselves cover every line. Nothing exotic. The table shows where to look.

Want the work done for you? Our SEO, AEO and GEO for tech companies page shows how C4 approaches search for firms like yours, and our technical SEO services page covers the crawl and index side.

Part of the checklist Free tool What to look at Source
Plan, lines 1 to 5 A shared sheet, plus your domain and hosting logins The page list, phrases, addresses, the chosen domain, the private build and who owns each login URL structure, robots.txt intro and site verification
Crawling and indexing, lines 6 to 12 A site crawler, view-source and a scripts-off browser Status codes, redirects, canonicals, the sitemap, links and whether the words are in the page technical requirements, canonicals and crawlable links
Pages, lines 13 to 18 View-source and the Rich Results Test Titles, descriptions, finished copy, headings, images and markup title links, image SEO and structured data rules
Mobile and speed, lines 19 to 21 A phone and PageSpeed Insights The same content on mobile, the three Core Web Vitals and every form mobile-first indexing and Web Vitals
AI search, lines 22 to 25 Your robots.txt, your firewall settings and the AI tools A rule for each bot, plain-text facts, a direct lead and a day-zero log OpenAI, Anthropic, Perplexity and Google AI features
Launch day and first month, lines 26 to 30 Search Console, Google Analytics 4 and the live robots.txt Leftover blocks, the sitemap, key events, indexing requests and the day-seven and day-thirty reviews noindex, URL Inspection, key events and page indexing

The crawl, index, markup, speed and crawler rows come from the Google, OpenAI, Anthropic and Perplexity pages linked in the last column. The pass conditions, the page and launch-day lines and the timing tags are our own suggestions.

The Timing

What Runs When, From the Plan to Day Thirty

Thirty lines sounds like a lot until you sort them by when they run. A few are decisions, many are tests on the finished build, a handful switch the site on, and one is a review. Sorting by timing keeps the routine short enough to finish, and finishing is the only way a checklist survives the launch rush. Keep it small.

Plan

Decide Early, 5 Lines

The page list, addresses, the chosen domain, a private build and the logins. Cheap to settle now, and costly to change once the site is built.

Before Launch

Test the Build, 19 Lines

Status codes, redirects, canonicals, sitemap, links, page basics, mobile, speed and the AI crawler rules. Run them on the finished build, and again after any big change.

Launch Day

Switch It On, 5 Lines

Lift every block, verify Search Console, submit the sitemap, test analytics, inspect the key pages and save the day-zero AI log.

After Launch

Review Twice, 1 Line

One line, run at day seven and again at day thirty. Read the indexing report, fix what Google reports and rerun the AI log.

Google says it can take a few weeks to notice a new site, and that a crawl request does not promise inclusion. So the after-launch work is a review, not a verdict. For the routine on a live site, see our technical SEO checklist for MSP websites and the website maintenance checklist.

How It Works

How to Run This Checklist in Four Steps

Own. Test. Launch. Review.

1
Step 1

Copy the Sheet and Name an Owner

Paste the sheet into a shared doc. Put one name against each part, the developer for parts two and four, the marketer for parts one, three and five, and the owner for the logins and launch day. Names, not teams.

2
Step 2

Run Parts One to Five on the Build

Work through the plan and build lines before the launch date is set in stone. Write each result in the box, even when the answer is fine. Fine is a result. Log it anyway.

3
Step 3

Run Part Six on Launch Day

Lift the blocks first, then verify, submit, test and inspect, in that order. Save the AI answer log before anything has had time to change.

4
Step 4

Review at Day Seven and Day Thirty

Read the indexing report, fix what it flags and rerun the log. Then book the routine for the live site. Short routine. Same every time.

Keep It In-House or Bring in a Specialist

Good to Keep In-House
  • You control the build and the domain
  • The page list is short
  • One person can own the sheet through launch
  • You want a dated baseline before hiring anyone
  • Nobody is racing a fixed date
Bring in a Specialist When
  • The developer and the marketer rarely talk
  • The site leans on a script-heavy framework
  • Several domains or subdomains are involved
  • The launch date is fixed and nobody owns the list
  • Nobody has time to tend any of it
Consultant and company owner walking through an unfinished office at dusk, one carrying rolled blank drawings
Ways to Work

Run It Yourself, or Let C4 Own the Launch

The checklist works fine on its own. If you’d rather have a partner carry it, our website management services page explains how C4 looks after a site once it’s live, and our lead generation website design page covers building the site backward from the booked call.

The sheet is one piece of a bigger system. Use our SEO forecasting guide to set honest expectations before launch, the AEO checklist to test a single page for AI answers, and the monthly SEO checklist to keep the live site healthy.

If you’d rather have help turning the page list into a plan, our keyword research services page explains how C4 does it, and our guide to bottom-of-funnel SEO shows which phrases sit closest to a sale. Wondering whether any of this still matters now that AI answers exist? Our look at whether SEO is dead covers what AI search changed and what it didn’t.

Already Have a Site on Another Address?

This sheet assumes there are no old addresses to protect. If the new site replaces a live one, old addresses need a map and 301 redirects, and that is a different job. Start with our guide to website migration SEO.

Common Questions

Questions MSP Owners Ask About SEO for a New Website

What is SEO for a new website?

SEO for a new website is the setup work that lets Google and AI tools find, read and measure the site from its first day. It covers the page plan, crawl and index settings, page basics, speed, AI crawler rules and tracking.

How long does it take a new website to show up on Google?

Google says it can take a few weeks to notice a new site, and crawling a requested address can take a few days to a few weeks. A ranking is a separate question and Google promises none. Run the day-seven and day-thirty reviews, and judge the fixes.

Do we need to submit a sitemap for a brand-new site?

Submit one. Google treats a sitemap as a hint, not an order, so it helps discovery but doesn’t replace links from the site itself. Make sure every wanted page is also linked from another page.

Should we block the site from Google while we build it?

Keep it private, but use a password and not robots.txt. Google says robots.txt isn’t a way to keep a page out of Google and points to a password or a noindex tag. Then lift every block on launch day.

Do AI search tools need anything different from Google?

Not much, according to Google. It says AI Overviews and AI Mode need no extra requirements, no AI text files and no special schema, only a page that’s indexed and eligible for a snippet. The other tools document their own crawlers, so our AI crawler guide sorts them by job.

What if the new site replaces an old one?

Then it’s a migration, not a launch. Old addresses need a map and permanent redirects so the search value they earned carries over, and our website migration SEO guide covers the order of work.

Is the checklist free to use?

It’s free and it sits on this page, with nothing to download and no email to hand over. Copy it into the tool your team already uses, or book a session if you’d like C4 to run it with you.

Want Someone to Own the Launch Checklist With You?

Run the list on your build first. Then book a session, and we’ll go through what failed in the order it should be fixed, so you leave with a short fix list and not another report.