SEO steps for new website — Complete launch checklist

seo steps for new website — follow this step-by-step workflow to make a brand-new site search-friendly from pre-launch to early link-building readiness. Readable, technical, and checklist-driven so teams can act fast.

TL;DR checklist — Quick SEO steps to complete before launch

Fast checklist for immediate SEO fixes and launch tasks. Each item is actionable; use this as your pre-launch sprint list (tick boxes as you go). For term definitions used here, see Complete Guide to Search Engine Optimization.

Choose an SEO-friendly domain and enable domain privacy in WHOIS; confirm MX records for mail.
Pick hosting & enable HTTPS (install SSL); configure CDN and caching rules.
Install and configure your CMS with SEO plugin/module, set permalinks, and user roles.
Create robots.txt and an XML sitemap; block staging and private pages.
Set canonical tags and a consistent URL structure; decide www vs non-www and force one.
Configure Google Search Console, Bing Webmaster Tools, and submit sitemap.
Install GA4, tag important events, and set up a basic dashboard.
Optimize core on-page templates (title tag, meta description, H1/H2s) and add structured data for Organization and WebSite.
Run PageSpeed Insights and fix top 3 performance issues (images, render-blocking JS/CSS, caching).
Prepare linkable assets (resource pages, pillar content) and a small outreach plan for launch week.

For a short feature primer on how search results work, see Search Engine Results Guide and the SEO 101 Guide. Small teams can follow the SEO Features List Checklist as a printable pre-launch test.

Define goals, audience, and keyword focus for a new site

Before configuring servers and pages, define what success looks like. Target keywords, buyer intent, and a content scope (topical map) control architecture, URLs, and initial promotional focus. Use measurable KPIs and map keywords to content buckets so launch efforts are focused and trackable.

Define primary business goals (lead gen, sales, signups) and tie to KPIs (MQLs, conversion rate, organic sessions).
Research audience intent: informational vs transactional vs navigational terms; group by funnel stage.
Create a topical map and choose 3–5 priority keyword themes to target at launch.
Plan content buckets (pillar pages, resource pages, product pages, blog) and map 10–20 launch pages to themes.

How to set realistic SEO goals (KPIs to define)

Choose 3–5 KPIs: organic sessions, impressions (Search Console), conversions (GA4), indexed pages, and average position for priority keywords. Use baseline estimates and update targets after 30/60/90 days. For planning templates, see SEO Based Content Plan Guide and SEO goals and objectives guide. (Last updated: 2026-06-03.)

Choose primary focus keyword and content buckets

Pick one focus keyphrase per landing page; avoid duplication across pages.
Use the intent classification from your keyword research: top-of-funnel = guides; bottom-of-funnel = product pages.
Refer to Keyword Optimization Techniques Guide and Guide to 5 Types of Keywords for mapping.

Domain name, brand, legal and DNS setup

Domain selection and DNS setup affect early trust, deliverability, and technical SEO. Domain age has minor influence compared to quality content and links, but domain signals (WHOIS, history, privacy) matter during early trust-building. Review the Google Domain Authority Guide for background on trust signals.

Domain selection checklist (SEO-friendly considerations)

Prefer short, brandable names; avoid hyphens and exact-match spammy terms.
Decide on subdomain vs subfolder based on product separation (subfolders usually consolidate authority).
Enable WHOIS privacy if you don’t want public contact info; keep legal registration records up to date.
Check domain history (archive.org, WHOIS lookups) to avoid legacy penalties or spam associations — see Domain Name SEO Guide.

DNS and email setup basics (A, CNAME, MX)

Set DNS records before going live. Typical minimal records:

A  @  192.0.2.123
CNAME  www  yourdomain.com.
MX  @  10 mail.your-mail-provider.com.
TXT  @  "v=spf1 include:mailprovider.com ~all"

Allow TTL propagation (often minutes to hours). Set an SPF/TXT and DKIM records for deliverability to avoid emails landing in spam.

Hosting, performance and CDN choices for a new site

Choose hosting based on expected traffic, technical skill, and budget. TTFB (time to first byte) and geographic footprint matter for Core Web Vitals and crawl responsiveness. Managed hosting can simplify security and caching; VPS gives control for custom performance tuning.

Hosting Type	Pros	Cons
Shared	Low cost; easy setup	Variable performance; noisy neighbors
VPS	More control; scalable	Requires sysadmin knowledge
Managed (WordPress)	Optimized stack, support	Higher cost; plugin limits
Cloud (AWS/GCP)	Global footprint; autoscaling	Complex setup without expertise

Hosting checklist for SEO

Ensure HTTP/2 or HTTP/3 support and TLS 1.2+/modern ciphers.
Fast TTFB (target <200–500ms for primary markets) and regional presence near users.
Backups, easy SSL renewal, and staging environment.
Support for edge caching / CDN integration.

When to add a CDN and caching rules

Add a CDN when serving national or global audiences, or when assets (images, JS/CSS) are substantial. CDN caches static assets at edge locations to reduce latency. Typical caching rules:

Static assets: long max-age (e.g., 30 days) with fingerprinted filenames.
HTML pages: shorter cache times and use cache-control: no-cache or stale-while-revalidate for dynamic content.
Set cache invalidation strategy for releases to avoid stale content.

CMS selection and initial configuration

Choose a CMS that fits content volume and technical resources. WordPress is common for publishers and SMBs; headless CMSs are good for complex front-ends. Configure CMS settings to avoid indexing staging sites, duplicate content, and broken URL patterns. See Content Management System SEO Guide for step-by-step CMS-specific configuration and plugin recommendations.

Quick CMS comparison notes:

WordPress: plugin ecosystem (SEO, cache, schema) — fast to deploy with recommended hosting.
Headless (Contentful, Strapi): great for dev flexibility but needs more engineering for SEO-critical features.
SaaS builders (Wix, Squarespace): simple but check SEO features (canonical control, sitemaps).

Recommended CMS settings (permalinks, user roles)

Permalinks: /category/slug or /slug — avoid query strings for primary pages.
Set robots meta default to index,follow for production and noindex for drafts/staging.
Limit publishing rights; use roles to prevent accidental public posts.

Essential plugins/modules to install (security, SEO, cache)

Security plugin (WAF, login protection), backup plugin, caching plugin, image optimization plugin.
SEO plugin for metadata, XML sitemaps, canonical control, and schema output.
Analytics/consent plugin for GA4 and cookie compliance.

See Step by Step SEO for WordPress Guide and SEO in Web Development Guide for developer-level implementation.

Avoiding common CMS misconfigurations

Do not leave staging accessible to search engines (robots or basic auth).
Don’t run multiple sitemap generators; use one canonical sitemap.
Avoid auto-indexing archives or low-value tags/categories.

Core technical SEO setup (HTTPS, robots.txt, sitemap, redirects)

Core technical items ensure search engines can crawl, index, and trust your site. Define canonicalization, robots rules, and redirects before launch. For in-depth coding examples, consult SEO HTML Code Guide and the SEO HTTPS Guide. Also verify general compliance in Search Engine Friendly Website Guide.

Install SSL and force HTTPS across the site.
Publish a clean robots.txt and single XML sitemap; link sitemap from robots.txt.
Standardize on one canonical host (www vs non-www) and implement 301 redirects from the alternate host.
Create a launch redirect plan to map old pages (if any) to new equivalents using 301s.

How to install and force HTTPS

Obtain a certificate (Let’s Encrypt or paid CA). Configure server to redirect HTTP to HTTPS using 301. Example Nginx snippet:

server {
  listen 80;
  server_name example.com www.example.com;
  return 301 https://$host$request_uri;
}

Example Apache .htaccess redirect:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

robots.txt essentials and sitemap submission

robots.txt should allow crawl of essential assets and point to your sitemap:

User-agent: *
Disallow: /wp-admin/
Disallow: /staging/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://example.com/sitemap.xml

XML sitemap example entry:

<url>
  <loc>https://example.com/product/widget</loc>
  <lastmod>2026-06-01</lastmod>
  <priority>0.8</priority>
</url>

After you have the sitemap, submit it to Search Console and Bing Webmaster Tools (see Indexing section). According to Google Search Central documentation, sitemaps help discovery but don’t guarantee indexing — submission speeds discovery in most cases. For details see Google Search Central: Sitemaps.

Redirect strategy for launch (301 plan)

Use permanent 301 redirects for canonical moves. Keep a spreadsheet mapping old URLs → new URLs and test for redirect chains or loops. Example Apache redirect:

Redirect 301 /old-page/ /new-page/

Common rules: consolidate domain versions (force one host), avoid chains (A→B→C), monitor for 4xx/5xx after launch.

Site structure, URLs, navigation and internal linking

Think of site structure like a library: categories are shelves and pages are books. Flat structures (few clicks from home) help crawl and UX. Use breadcrumbs and consistent URL patterns. If internationalizing, follow the guidance in Modern International SEO Methods Guide.

Designing an SEO-friendly URL structure

Keep URLs short, readable, and keyword-relevant (avoid long query strings for primary pages).
Use hyphens for spaces and lowercase only: example URL structure: /category/subcategory/product-name/

Example URL structure:

/resources/seo-basics/
 /products/widget/
 /blog/how-to-start-seo/

Internal linking plan and anchor text guidance

Link from pillar pages to cluster pages; use descriptive anchor text (not exact-match spammy anchors).
Include breadcrumbs on content pages to surface category structure.
Avoid deep nesting that requires many clicks; aim for most pages within 3 clicks from home.

For site maps and technical structure examples, refer to Site Structure Optimization Guide and URL SEO Optimization Guide. For keyword placement in URLs see Keywords in URLs Guide.

On-page content requirements: pages, metadata, headings and templates

Templates drive consistent SEO signals. Each template (category, product, article) must include optimized title tags, meta descriptions, canonical tags, H1/H2 hierarchy, and schema where applicable. Map keywords to templates and avoid keyword cannibalization.

Page templates for category, product, article pages

Category: keyword-rich H1, short intro (100–200 words), internal links to top articles, pagination rel=next/prev as needed.
Product: unique descriptions, structured data for product, price, availability, reviews.
Article: byline, publish/update dates, estimated read time, table of contents for long posts.

Metadata checklist and title tag formula

Title tag example:

<title>Primary Keyword – Brand Name</title>

Meta description formula: benefit + keyword + CTA (under 155 characters). Example meta tag:

<meta name="description" content="How to set up X — quick steps, checklist, and sample code. Start today." />

Always include a self-referential canonical in templates to prevent duplicate content:

<link rel="canonical" href="https://example.com/this-page/" />

For metadata best practices and formulas, see SEO description guide and SEO Headings Best Practice Guide.

Content length and quality guidance for new pages

Quality beats arbitrary word counts. For informational pages, aim for substantial coverage of intent (often 800–2,000+ words depending on topic depth). Use templates to ensure semantic depth, internal linking, and clear CTAs. Publishers with community content should follow SEO plan for community content guide.

Media, images, and structured data

Optimize media for speed and accessibility. Add structured data to key templates to help search engines understand page roles (Organization, WebSite, Breadcrumb). Below is a minimal JSON-LD snippet to include in the site header for Organization + WebSite:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Brand",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png"
}

Image optimization checklist

Compress images with modern formats (WebP/AVIF where supported) and use responsive srcset.
Add descriptive alt text that describes the image function or content.
Lazy-load below-the-fold images but ensure LCP image is not lazy-loaded.

Basic schema to add at launch (Organization, WebSite, Breadcrumb)

Add Organization and WebSite schema, and output Breadcrumb structured data on category/article pages. Example breadcrumb JSON-LD:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type":"ListItem","position":1,"name":"Home","item":"https://example.com/"},
    {"@type":"ListItem","position":2,"name":"Blog","item":"https://example.com/blog/"},
    {"@type":"ListItem","position":3,"name":"This Article","item":"https://example.com/blog/this-article/"}
  ]
}

Performance, Core Web Vitals and mobile readiness

Core Web Vitals are three metrics that measure user experience: LCP (Largest Contentful Paint — perceived load speed), INP (Interaction to Next Paint — replaces FID for interactivity), and CLS (Cumulative Layout Shift — visual stability). Measure with PageSpeed Insights or Lighthouse. For recommended audits and fixes, see web.dev: Core Web Vitals and use PageSpeed Insights (PageSpeed Insights).

Quick fixes to improve Core Web Vitals before launch

Optimize largest images (compress, use responsive images and WebP/AVIF).
Defer or async non-critical JS; reduce render-blocking resources.
Implement server-side caching and CDN edge caching for static assets.

Example PageSpeed Insights walkthrough (tool walkthrough placeholder): run PageSpeed Insights on a key landing page, note LCP and CLS. Typical top-three fixes: (1) compress/serve images in WebP, (2) remove unused JS/CSS, (3) preconnect to critical third-party origins. After applying those, re-run and track score improvements. (Placeholder for screenshots showing before/after; include in editorial assets.)

Mobile-first considerations and viewport settings

Ensure responsive design, touch target sizes, and viewport meta tag:

<meta name="viewport" content="width=device-width, initial-scale=1">

Test mobile flows using Lighthouse and real devices. For mobile UX best practices, see Mobile SEO Marketing Guide and the SEO Web Design Guide.

Indexing, Search Console, analytics and tracking setup

Register properties, verify ownership, and submit sitemaps right after launch. Use GA4 for analytics and map conversion events to business KPIs. For indexing checklists, consult SEO Indexing Guide and the How to Analyze SEO Performance for reporting.

Registering and verifying site in Search Console

Create a property in Google Search Console (choose domain property for full coverage or URL-prefix if needed).
Verify ownership using DNS TXT (recommended) or HTML file upload; keep verification in place after launch.
Submit sitemap(s) in Search Console > Sitemaps and monitor coverage reports.

Placeholder: include screenshots showing DNS TXT verification, sitemap submission, and successful URL inspection (add for editorial publishing assets).

Configuring GA4 and key events to track

Install GA4 via gtag or GTM and verify events in Realtime and DebugView.
Track conversions: form submissions, sign-ups, purchases, and key CTA clicks.

<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXX');
</script>

Use event names consistent with reporting (e.g., purchase, lead_form_submit). For setting KPIs and interpreting data see How to Analyze SEO Performance and Typical SEO Report Guide.

Launch checklist: final tests and go-live steps

Use this pre-launch checklist to move from staging to production. Do the items in order and record test results.

Switch DNS to production (confirm TTLs) and test domain resolution.
Force HTTPS and verify no mixed content warnings.
Ensure robots.txt allows crawling and staging is blocked.
Submit sitemap to Search Console and request indexing for priority pages.
Run full crawl with a crawler (Screaming Frog or similar) and fix any 4xx/5xx or redirect chains.
Verify GA4 and Search Console data flows.
Smoke-test main user journeys on mobile and desktop.

Staging to live migration checklist

Remove noindex meta and staging flags.
Implement DNS and CDN configuration changes during low-traffic windows.
Deploy redirects and monitor logs for crawl errors.

Post-launch verification (indexing, sitemap, performance)

Use Search Console URL Inspection to request indexing for 10–20 priority pages.
Check coverage report and fix errors; watch performance and Core Web Vitals metrics.
Monitor organic impressions and sessions over the first 30 days — expect gradual increases depending on content and links; see benchmarks in industry reports (e.g., Ahrefs or Moz).

Post-launch SEO steps and early link-building readiness

After launch, focus on content promotion, linkable assets, and scaled outreach. Build readiness by creating high-value pages that naturally attract links and by preparing outreach materials. Use our detailed SEO Links Guide and Training for Link Building Best Practices to expand the outreach tactics described here. For editorial outreach templates, see Editorial Links Guide.

Create linkable pages and assets (resource pages, tools, case studies)

Identify linkable asset types: original research, tools/calculators, comprehensive resource pages, case studies.
Publish at least one resource-level asset at launch and promote it to relevant communities and newsletters.
Prepare outreach lists and pitch templates; track outreach and responses in a CRM or spreadsheet.

For cost estimates and planning, consult Organic Link Building Guide and compare in-house vs agency options in Benefits of Link Building Services.

Outreach and small-scale link-building to start

Begin with low-risk tactics: resource page outreach, unlinked brand mentions, and broken link building.
Use conservative anchor text and diversify sources; avoid paid placements without clear disclosure and quality controls.
Track placements, referral traffic, and changes in organic visibility over 30/60/90 days.

Use our recommended reading Types of Link Building and Resource Page Link Building for practical methods. If you publish video content, integrate promotion with Search Engine Optimization for YouTube.

Use our detailed Editorial Links Guide and consider low-cost traction tactics in Build Link Popularity. For a full campaign blueprint, see Complete Linkbuilding Plan Guide.

Common launch problems and troubleshooting

Here are frequent issues, how to diagnose them, and quick fixes.

Not indexed — Diagnosis: Search Console coverage shows noindex or crawl errors. Fix: remove noindex, submit sitemap, request indexing.
Canonical issues / duplicate content — Diagnosis: multiple versions resolve; fix: add self-referential canonical, consolidate URLs, fix rel=prev/next where applicable.
Redirect loops — Diagnosis: server logs or crawler show 5xx errors or chains; fix: correct server rules and avoid host canonical conflicts.
Sitemap errors — Diagnosis: sitemap 4xx/5xx or invalid XML; fix: validate XML and resubmit.

How to diagnose indexing issues

Use Search Console URL Inspection to see crawl, index, and canonical status.
Run a site:example.com query for quick visibility check (not exhaustive).
Use a crawler to identify blocked paths, noindex tags, or canonical mismatches.

Refer to Fix SEO: Practical Troubleshooting Guide for full workflows.

Quick fixes for crawl errors and duplicate content

Fix robots.txt disallows, remove accidental noindex tags, and ensure canonical tags point to preferred URLs.
Remove query-parameter indexation via parameter handling in Search Console or canonicalization.
Monitor server logs to ensure Googlebot is not being rate-limited.

Tools, templates, 30/60/90 SEO plan and next steps

Use a small, practical toolset to speed implementation and reporting. For platform comparisons and training, see Fast SEO Guide and Linkbuilding Platform Comparison Guide.

Suggested toolset (free + paid)

Free: Google Search Console, PageSpeed Insights, Lighthouse, GA4
Paid/advanced: Ahrefs or Moz for backlink research, Screaming Frog for crawling, Cloudflare for CDN and WAF
Project tools: Trello/Asana for tasking and a shared Google Sheet for redirects and sitemaps

Examples of authoritative resources: Google Search Central, web.dev / PageSpeed Insights, and tool docs like Ahrefs Blog for industry research and benchmarks.

Simple 30/60/90 implementation plan

30 days: Verify indexing, fix high-priority technical issues, publish 5–10 core pages, submit sitemap, launch outreach for 1–2 linkable assets.
60 days: Expand content by 20–30%, continue outreach, monitor rankings, fix duplicate content issues, and iterate on Core Web Vitals.
90 days: Scale content production, launch a broader link-building campaign, and measure conversions vs KPIs; adjust strategy using data.

What we can’t guarantee: no guaranteed rankings; indexing and ranking depend on competition, content quality, and backlink profile. According to a 2024 industry report, indexing speed and ranking improvements vary by site and niche.

Experience case example: Pre-launch checklist applied to a small ecommerce launch (anonymized): implemented HTTPS, canonicalization, XML sitemap, and published 12 product & category pages; submitted sitemap on launch day. Outcome: core pages indexed within ~3 days and the site recorded ~120 organic sessions in the first 30 days (approximate and conditional on content and promotion).

Tool walkthrough (PageSpeed Insights example): Run PageSpeed Insights on a landing page, note LCP 4.2s, CLS 0.15, INP high. Applied three fixes: compress LCP image (WebP), defer 3 non-critical scripts, enable CDN caching for static assets. Re-run showed LCP reduce to ~1.8s and CLS to 0.02. Include screenshots in editorial assets to show before/after.

Last updated: 2026-06-03

Frequently Asked Questions

What are the first SEO steps for a new website before launch?

Choose an SEO-friendly domain, enable HTTPS, set up hosting/CDN, configure your CMS with proper permalinks and SEO plugins, create robots.txt and an XML sitemap, register the site in Search Console, and install GA4 — then test redirects and run a pre-launch crawl.

How long does it take for a new website to be indexed by Google?

Indexing time varies; according to Google Search Central, new pages can appear within 1–14 days in typical cases — faster if you submit sitemaps and request indexing, but times depend on site authority, content quality, and crawl frequency.

Should I use www or non-www for my domain — which is better for SEO?

Neither is inherently better for SEO; pick one (www.example.com or example.com), enforce it with 301 redirects, and set the preferred domain in Search Console to avoid duplicate-host confusion and ensure consistent canonical signals.

How do I add my new site to Google Search Console and submit a sitemap?

Create a property (domain or URL-prefix), verify ownership via DNS TXT or HTML file, then go to Sitemaps > add your sitemap URL (e.g., /sitemap.xml) and submit; use URL Inspection to test individual pages after submission.

How much does it cost and how long before I see results from initial SEO work on a new site?

Costs range from DIY (minimal tool fees) to agencies ($1k+/month); results typically start showing in 30–90 days for indexing and early traffic, but meaningful ranking improvements depend on niche competitiveness and link-building effort.

My pages are not indexed after launch — what troubleshooting steps should I take?

Check Search Console coverage and URL Inspection for noindex or crawl errors, ensure robots.txt isn’t blocking crawlers, verify canonical tags, submit the sitemap, and inspect server logs for Googlebot access issues or rate-limiting.

How can I make sure my site is secure and trustworthy for search engines?

Install a valid SSL certificate and force HTTPS, keep software updated, configure security plugins or a WAF, set proper DNS and WHOIS records, implement structured Organization schema, and ensure privacy and contact pages are present.

What on-page elements should I prioritise for every page at launch?

Prioritise an optimized title tag, concise meta description, single H1, logical H2s, self-referential canonical, descriptive alt text for images, and required schema (WebSite/Organization or Product) for relevant pages.