SEO Checklist for a New Website: Before and After Launch

An SEO checklist for new website launches should cover three stages: planning the structure before you build, the technical setup before launch, and the checks you run in the first weeks after going live. The most important items are making sure search engines can index the live site, redirecting every old URL if you are replacing a site, submitting a clean XML sitemap, giving every page a unique title and one main keyword, and setting up Google Search Console from day one.

New sites lose search visibility for avoidable reasons: a “discourage search engines” setting left switched on, missing redirects from the old domain, or a sitemap that errors out. This checklist is ordered so you catch those problems before customers or search engines do.

Before you build: plan pages and keywords

SEO starts with the site map, not with the finished site. Before design work begins:

• List every page the site needs: home, services or products, about, contact, and key supporting content.
• Assign one main keyword to each page. We use one main keyword per page on our own sites so pages don’t compete with each other for the same search.
• Match each page to search intent. Service and product pages target buying searches; guides target questions.
• Plan the URL structure: short, readable, lowercase, words separated by hyphens. Avoid dates and IDs in URLs for pages that will be updated.
• Plan internal links: every page should be reachable within a few clicks of the homepage, and supporting content should link to the service or product page it supports.

If you want a fuller planning framework for the first year after launch, our SEO strategy template builds on this step.

Before launch: on-page basics for every page

Check each page in the staging site against this list:

• A unique title tag that includes the page’s main keyword and reads naturally.
• A meta description that explains what the page offers and gives a reason to click.
• One H1 per page that describes the page clearly, with H2s and H3s that structure the content.
• Body content that answers what the searcher wants, not just a headline and a contact form.
• Descriptive image file names and alt text for meaningful images.
• Internal links with descriptive anchor text, not “click here”.
• No placeholder text, lorem ipsum, test pages or duplicate demo content left over from a theme.

Before launch: technical setup

These are the items that decide whether search engines can crawl and understand the site.

Indexing controls

• Keep the staging site out of search results while it is being built, using password protection or a noindex setting.
• Write down exactly what you used to block staging, so you know what to remove at launch.
• Review robots.txt. Make sure it doesn’t block important sections, CSS or JavaScript files that pages need to render.
• Use robots.txt to keep crawlers out of low-value URL patterns, such as internal search results or filter parameters, where appropriate.

That last point comes from our own experience. On growthscribe.com, Search Console’s “Page with redirect” report filled up mostly with URLs created by ?filter- parameters. Blocking that pattern in robots.txt cleaned up the report and kept crawling focused on real pages. Check for similar parameter patterns on your own site, especially on shops and directories.

Canonicals and duplicates

• Each page should have a self-referencing canonical tag unless it is a deliberate duplicate.
• Choose one version of the site, with or without www, and make sure the others redirect to it.
• Make sure HTTP redirects to HTTPS and the SSL certificate is valid.

XML sitemap

• Generate an XML sitemap that lists only indexable pages you want found.
• Open the sitemap in a browser and check every sitemap file loads without errors.
• On larger sites, use a sitemap index split into smaller sitemap files.

We learned the value of that check directly: one of our post sitemaps started returning a server error because the server ran out of memory building a single large sitemap page. Splitting it into smaller pages fixed it. A sitemap that fails to load quietly tells search engines nothing about your pages.

Structured data

• Add Organization structured data with your business name, logo, website and social profiles.
• If a founder or author is central to the brand, add Person structured data and connect it to the Organization.
• Use consistent @id values so the same organization and person are recognized across pages and across your sites. We link Organization and Person schema this way across the sites we run.
• Add page-level types where they fit, such as Product, Article or FAQ, and validate them with Google’s Rich Results Test.

Speed and mobile

• Test key templates (home, service, product, blog post) for speed and Core Web Vitals on mobile.
• Compress and correctly size images, and lazy-load images below the fold.
• Use page caching and a CDN where your hosting supports it.
• Check every template on a real phone: readable text, tappable buttons, no content shifting as the page loads.

Speed is easier to build in than to retrofit. Our Durga Steel website speed case study shows what building for Core Web Vitals from the start looks like.

If you are replacing an old website: redirects

Skip this section only if the domain is brand new. Otherwise, it is the most important part of the checklist.

1. Export a full list of URLs from the old site, using a crawler such as Screaming Frog, the old sitemap and your analytics.
2. Export the old site’s top pages and linked pages from Google Search Console.
3. Map each old URL to the most relevant new URL in a spreadsheet. Don’t send everything to the homepage.
4. Set up permanent (301) redirects for every mapped URL.
5. After launch, crawl the old URL list and confirm each one redirects once, to the right page, with no chains or loops.

Launch day: the SEO checklist for new website go-live

• Remove the staging block: noindex settings, password protection, or the “discourage search engines” option in WordPress settings.
• Confirm the live robots.txt is the version you intended.
• Verify the site in Google Search Console, ideally as a domain property, and submit your XML sitemap.
• Set up analytics and confirm key conversions, such as form submissions, are recorded.
• Crawl the live site to find broken links, missing titles, redirect chains and pages accidentally set to noindex.
• Test every form and checkout end to end.
• Update your business profiles and social bios with the new URLs.

The first weeks after launch

• Check Search Console’s indexing reports regularly. Look for pages excluded unexpectedly, server errors and redirect issues, and investigate patterns rather than single URLs.
• Use the URL Inspection tool on your most important pages to confirm Google can fetch and render them.
• Watch the old site’s top pages to make sure their redirects are being followed.
• Monitor rankings and clicks for your main keywords, but don’t panic over early fluctuations, which are normal after a launch or migration.
• Fix crawl errors and broken links as you find them.
• Start publishing the supporting content you planned, linking each piece to the page it supports.

Common new website SEO mistakes

• Leaving the “discourage search engines” or noindex setting on after launch.
• Launching without redirects from the old site.
• Every page using the same title, often just the business name.
• Several pages targeting the same keyword.
• A sitemap full of redirected, noindexed or error URLs.
• Thin service pages with a headline and a form but nothing that answers the searcher’s question.

Getting a second pair of eyes before launch

This SEO checklist for new website launches covers what most businesses need, but launches are where small oversights cost the most. If you would like someone to review the staging site, map redirects or set up Search Console and structured data with you, you can get help from our SEO services team, or email support@growthscribe.com with your launch date and staging URL.

FAQ

When should I start SEO on a new website?

Start before the site is built. Decide which pages you need and which keyword each page targets while planning the site structure, then handle the technical setup before launch. Fixing structure after launch is much harder than getting it right first.

How long does it take for a new website to appear in Google?

It varies. Submitting your sitemap in Google Search Console and linking to the site from your existing profiles helps search engines discover it, but there is no fixed timeline for indexing or ranking. Watch the indexing reports in Search Console rather than guessing.

Do I need redirects if my new website replaces an old one?

Yes. Every important old URL should redirect permanently to the most relevant new page. Without redirects, you lose the value those old pages built up and visitors following old links hit errors.

Should I block my new website from search engines while it is being built?

Yes, keep the staging or development version out of search results, for example with password protection or a noindex setting. The critical step is removing that block when you launch, which is one of the most commonly missed items.