SEO Checklist for a New Website

An SEO checklist for a new website is mostly a build checklist: the decisions that determine whether a site can rank are made before the first page is designed, and the expensive mistakes (blocked crawlers, duplicate URLs, a redesign that drops old URLs, pages with no clear topic) are all avoidable. This guide splits the work into four phases: before the build, during the build, launch day and the weeks after launch. Each item is short enough to tick off. The same list applies to a five-page site for a new firm and to a thousand-page rebuild for a large organization; the difference is how many people it takes to work through it.

Before the build

These decisions shape everything that follows. Make them with whoever owns the site, the content and the development.

Goals, audience and keywords

• Write down what the site is for: leads, sales, appointments, applications, information. Every later decision refers back to this.
• List the questions your audience types into a search engine and group them by topic. Each group becomes a page or a section; a page with no question behind it has no reason to exist.
• Check what currently ranks for those searches and note the format (service page, guide, comparison, local listing). Match the format before trying to beat the content.
• Pick one primary search phrase per page and two or three related ones. Two pages aimed at the same phrase will compete with each other.

Site structure and URLs

• Draw the sitemap: home, sections, pages, and the links between them. Every important page should be reachable within three clicks of the home page.
• Decide the URL pattern now: lowercase, hyphens between words, no dates or IDs, a trailing-slash convention, one URL per page. Changing this after launch means redirects.
• If the site replaces an old one, export every old URL (from the sitemap, analytics and Search Console) and map each to its new equivalent. This redirect map is the single most important SEO document in a rebuild; the website redesign checklist covers it in detail.
• Choose the domain form (www or not, https only) and plan one canonical version.

Platform and hosting

• Choose a platform that lets you control titles, meta descriptions, headings, URLs, redirects, canonical tags, robots directives and structured data on every page. WordPress with an SEO plugin does; some site builders do not.
• Choose hosting with a content delivery network, server-side caching and HTTPS by default. Speed starts here, not in a plugin.
• Plan analytics and Search Console access from the start, with an owner named.

During the build

This is the technical SEO checklist and the on-page SEO checklist combined, applied while pages are being built rather than audited afterward.

Crawling and indexing

• Keep the staging site out of the index: password protection or a noindex header, and remember to remove it at launch.
• Generate an XML sitemap automatically that lists only canonical, indexable pages.
• Write robots.txt to allow crawling of pages, CSS and JavaScript, and to block only admin paths and internal search results.
• Set a self-referencing canonical tag on every page; make sure pagination, filters and tracking parameters do not create indexable duplicates.
• Return proper status codes: 200 for pages, 301 for moved URLs, 404 or 410 for removed ones, with a useful 404 page.

On-page basics for every page

• One H1 that states the topic, then H2 and H3 headings that outline the content in order.
• A unique title tag of roughly 50 to 60 characters with the primary phrase near the front, and a meta description of roughly 140 to 160 characters that says what the page offers.
• The primary phrase in the first paragraph, naturally, and related phrases in subheadings where they fit.
• Descriptive link text between pages (“website development services”, not “click here”), and links from every new page to related pages and back.
• Images with descriptive file names and alt text, sized for the layout, compressed, and served in a modern format.
• Content that answers the question on the page fully. Thin pages built to hold a keyword are a liability.

Structured data

• Organization (or LocalBusiness for a physical location) on the home page with name, logo, address, phone and social profiles.
• BreadcrumbList on inner pages; Article or BlogPosting on posts; FAQPage where a page carries real questions and answers; Product where it applies.
• Validate with a structured-data testing tool before launch and keep it in sync with the visible content.

Speed and mobile

• Build mobile-first; test on a real phone, not only a resized browser window.
• Set explicit width and height on images and embeds so the layout does not shift as they load.
• Load the largest visible image early and defer scripts that are not needed for the first screen.
• Measure against the Core Web Vitals thresholds on a staging URL before launch; the Core Web Vitals guide explains the three metrics and how to fix them.

Local signals (if you serve a place)

• Show the business name, address and phone number exactly the same way on the site, in LocalBusiness schema and in your Google Business Profile.
• Create a page per location only when you have real, distinct content for it: what you do there, how clients reach you, local context. Do not create a page per city with swapped names and nothing else, and do not list an address you do not have.
• Embed a map and give directions on the contact page.

Launch day

A website launch SEO checklist is short, and every item on it has sunk a launch when skipped.

1. Remove the staging noindex and password protection, then confirm the live site’s source shows no noindex tag and robots.txt no longer blocks everything.
2. Confirm HTTPS works on every page and that http, www and non-www variants all redirect to the one canonical version.
3. Load the redirect map and test a sample of old URLs, including the top fifty by traffic and every URL with backlinks.
4. Submit the XML sitemap in Search Console and request indexing of the home page and the most important pages.
5. Verify analytics is recording on the live domain and that goal or conversion events fire.
6. Crawl the live site with a crawler tool and fix anything returning 404, 500, redirect chains, missing titles or duplicate titles.
7. Run the home page and two inner pages through a page-speed tool on mobile and note the baseline.
8. Check the site search, contact forms and any booking or checkout flow by hand.

After launch

New website SEO does not end at launch; the first weeks tell you what the build got wrong.

Week one

• Watch Search Console’s page indexing report for pages excluded as “crawled, not indexed”, “duplicate” or “blocked”, and fix the cause.
• Look for 404s in Search Console and server logs; old URLs you missed in the redirect map will show up here.
• Confirm the sitemap shows as processed with the expected page count.

Month one

• Compare impressions and clicks by page against the old site, if there was one. A drop on specific pages usually means a missed redirect or a page whose content shrank.
• Check the Core Web Vitals report in Search Console once it has enough data, and fix any pages flagged as poor.
• Review title tags against the queries each page actually gets, and adjust where the searcher’s wording differs from yours.
• Add internal links from older pages to new ones, and from the new pages to each other where the content relates.

Ongoing

• Publish content that answers the next question in each topic group, and link it into the section it belongs to.
• Keep the platform, plugins and dependencies updated; security problems and slow pages both cost rankings.
• Re-crawl the site quarterly for broken links, redirect chains and orphan pages.
• Keep a change log. When rankings move, the first question is what changed on the site that week.

A realistic expectation: a new site on a new domain takes months to earn rankings, while a rebuilt site with a correct redirect map should hold most of its existing positions through the switch. The website development timeline shows where these SEO phases sit in the overall build.

Where PS3G fits

PS3G builds websites with this checklist built in: structure, URLs, redirects, on-page elements, schema, speed and local signals are part of the build, not a separate audit afterward. Our website development service covers design, build, content migration and the launch-day checks above, and our SEO services continue the after-launch work for sites we build or maintain: indexing and Search Console monitoring, Core Web Vitals, on-page improvements and content that fills the gaps in each topic. We do SEO only for websites we build or maintain, because the fixes usually need a developer, and we do not offer paid advertising, social media or email marketing. The checklist works the same for a founder’s first site and for a department’s rebuild inside a large organization.

Related reading

• Website Redesign Checklist: 40 Steps That Protect Your Rankings
• Website Development Timeline: Phases, Durations and a Template
• Core Web Vitals Explained: LCP, INP and CLS and How to Fix Them
• SEO services for sites we build and maintain

Frequently asked questions

When should SEO work start on a new website?

Before design. Keyword grouping decides which pages exist, URL rules decide how they are addressed, and the redirect map for a rebuild has to be ready before the old site is switched off. An SEO review after the site is built can fix titles and descriptions, but it cannot cheaply fix structure, URLs or a platform that hides the controls you need.

What is the most common SEO mistake at launch?

Leaving the staging site’s noindex tag or robots.txt block in place, which tells search engines to ignore the new site. Close behind are missing redirects from old URLs, which throw away the rankings and backlinks the old site had, and launching with http and https or www and non-www versions both live, which splits the site into duplicates.

How long does it take for a new website to rank?

A brand-new domain usually takes months to earn meaningful rankings, because search engines need time to crawl, index and gather signals about it. A rebuilt site that keeps its domain and redirects old URLs correctly should hold most of its positions through the change and improve as the new content and speed take effect. Nobody can promise a timeline.

Do I need structured data on a new website?

Yes, at least the basics: Organization or LocalBusiness on the home page, BreadcrumbList on inner pages, and Article or BlogPosting on posts. FAQPage and Product apply where the content fits. Structured data helps search engines understand what each page is and can earn richer results, but it must describe content that is visible on the page.

Does this SEO checklist for a new website cover local pages for every city I serve?

Only where you have something real to say about each place: how you serve it, what clients there typically need, how meetings work. Pages that repeat the same text with the city name swapped, or that list an address you do not have, tend to be ignored or treated as spam. One honest service-area page often outperforms a dozen thin city pages.