SEO Checklist for a New Website: Build the Search Foundation Before You Launch

Start with site structure, not with a list of SEO tricks

The original version of this tutorial focused on individual items such as a sitemap, title tag, privacy page and common footer. Those ideas are still useful, but a modern launch should connect them into one system.

Decide what the site is about, who it serves, which major sections are needed and how users will move from broad topics to specific pages. A clear structure also makes pillar pages and topic clusters easier to build later.

Define the important sections before hundreds of URLs are created

• Group related topics: create meaningful categories or hubs rather than a flat collection of unrelated pages.
• Keep navigation understandable: important pages should be reachable through normal links, not only through search or JavaScript interactions.
• Choose stable URL patterns: avoid changing folder names and URL structures unnecessarily after launch.
• Prevent duplicate routes: decide how HTTP/HTTPS, www/non-www, trailing slashes and URL parameters will be handled.
• Plan for growth: shared header, footer and navigation components make a large site easier to maintain.

Google says it primarily discovers pages through links from pages it already knows. A sitemap can help discovery, but internal linking and a usable site structure remain fundamental.

Make the preferred version of the site technically consistent

For the performance part of the launch, see our fast-loading webpage and Core Web Vitals guide.

Know the difference between robots.txt, noindex, canonical and sitemap

These mechanisms solve different problems. A frequent launch mistake is to use one of them for a job it was not designed to do.

• robots.txt: primarily controls crawler access. It is not the right mechanism for reliably keeping a web page out of Google.
• noindex: tells supported search engines not to include a crawlable page in search results.
• canonical: indicates the preferred URL when duplicate or substantially similar URLs exist.
• XML sitemap: lists canonical URLs you want search engines to discover and consider for crawling.

See the detailed robots.txt guide and our index, noindex, canonical and sitemap decision guide.

Submit a clean sitemap and inspect important URLs

Include canonical, indexable URLs in the XML sitemap. Avoid filling it with redirects, duplicate URLs, error pages or pages that intentionally use noindex.

Google currently recommends submitting sitemaps through Search Console or referencing them in robots.txt. The old unauthenticated sitemap “ping” endpoint has been deprecated and should not be used.

After launch, use Google Search Console to confirm ownership, submit the sitemap, inspect important pages and monitor indexing and performance.

Launch useful pages, not placeholders created only to fill the menu

Avoid publishing thin “under construction” pages just because a future section appears in the navigation. Publish the URL when it has a useful purpose and enough content to satisfy the intended visitor.

• Give each important page a clear purpose and primary search intent.
• Write a unique, descriptive title and visible H1.
• Use headings to make long pages scannable.
• Write useful examples, instructions, comparisons or evidence instead of repeating keywords.
• Use descriptive images and alt text where visuals genuinely help.
• Keep facts, screenshots, product names and interface instructions current.

For keyword and intent discovery, use our long-tail keyword research guide and Google Trends guide.

Write titles for users, not around an old “keyword space” formula

The old version of this page advised small sites to avoid using their brand in the title because it “wasted space.” That is too rigid. Google recommends titles that are unique, clear, concise and accurately describe the page. A business or site name can be useful when it helps identify the result.

Meta descriptions should summarize the page for searchers. Google may generate snippets from the page content, so the actual text on the page also matters.

Build discovery paths before the site becomes difficult to manage

Internal links should help a reader move naturally from one concept to another. Use descriptive anchor text and link the first natural occurrence of an important related concept when the destination adds value.

For a larger tutorial or knowledge site, use the section sitemap or URL inventory to identify relevant supporting pages. Cross-section links are useful when the relationship is real—for example, a programming tutorial using SQL can link to a detailed SQL concept page.

Do not link every repeated occurrence of the same term. The purpose is to create a useful learning path, not to maximize the raw number of links.

Make it clear who operates the site and how user data is handled

• Provide an appropriate contact method.
• Publish a privacy policy when you collect, process or track user data.
• Use terms, disclosures or disclaimers where the site genuinely needs them.
• Identify authors or publishers when that information helps users evaluate the content.
• Keep the copyright/footer area in a shared template so maintenance does not require editing every page.

Install measurement before you need historical data

Configure Google Analytics 4 or your chosen analytics platform before or at launch, then connect Search Console so you can evaluate discovery, clicks, landing pages and engagement over time.

Do not judge a new site only by rankings during its first days. Watch indexing, impressions, query relevance, user engagement and whether important pages are being discovered through internal links and the sitemap.

Final checks before announcing the website

1. Preferred HTTPS host resolves correctly.
2. Temporary staging noindex or access restrictions are removed where appropriate.
3. robots.txt is publicly accessible and does not accidentally block important content.
4. Canonical tags point to the preferred URLs.
5. The XML sitemap contains the correct canonical indexable URLs.
6. Search Console ownership is verified and the sitemap is submitted.
7. Navigation and internal links work on desktop and mobile.
8. Important pages have unique titles, useful H1s and enough substantive content.
9. 404 pages, redirects and forms have been tested.
10. Analytics, key events and consent behavior are tested.
11. Core Web Vitals and obvious performance problems are reviewed.
12. The site has appropriate contact, privacy and trust information.

Once the site is live, run the Plus2Net webpage audit framework on the most important landing pages and fix the highest-impact issues first.

Good new-site SEO is mostly good website planning

A strong launch gives users and search engines clear pages, clear relationships between pages, consistent technical signals and a way to measure what happens next. That foundation is easier to scale than trying to repair a confusing structure after hundreds of URLs are already live.