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.
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.

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.
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.

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.
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.
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.
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.
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.
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 to Run This Checklist in Four Steps
Own. Test. Launch. Review.
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.
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.
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.
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
- 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
- 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

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.
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.