Your deploy ships at 2:47 PM. The build passes. DNS propagates across nameservers. Your domain resolves. Your browser loads the homepage—fonts render, images appear, scripts execute. You exhale.

Then the second question hits: what happens to your SEO in the next 48 hours?

This window decides whether Google discovers your pages in days or drifts for weeks. Whether your old URLs redirect cleanly or scatter 404s across the index. Whether Search Console connects before your first crawl budget arrives—or after you've already lost it.

Below is the exact 48-hour checklist I run after every production deploy. It covers Search Console verification, IndexNow pings, redirect audits, canonical checks, and the seven technical tasks that separate fast indexing from slow obscurity. If you're past hour 47, start with task one anyway—late beats never.

I've launched dozens of sites over the years — from small marketing pages to large headless CMS builds on Next.js and Astro — and the first 48 hours after launch are where most teams either set themselves up for strong organic growth or silently torpedo their SEO for months. The difference isn't some secret sauce. It's a checklist. A boring, methodical, critically important checklist.

This is that checklist. Not the fluffy "make sure your content is good" advice you'll find elsewhere. This is the specific, technical stuff you need to do in the first two days, in roughly the order you should do it.

Table of Contents

Website SEO Launch Day Checklist: What to Do in the First 48 Hours

Hour 0-1: Pre-Flight Verification

Before you even think about search engines, you need to make sure the basics aren't broken. I've seen launches where the staging noindex tag was still in the <head>. That's a fun one to discover three weeks later.

Check for Leftover Staging Directives

This is the number one mistake. Open your browser, view source on your homepage, and search for:

<meta name="robots" content="noindex">

If that's still there, stop everything and fix it. Check your HTTP headers too — some frameworks (especially Next.js) can set X-Robots-Tag headers at the server level:

curl -I https://yourdomain.com | grep -i robots

You should see nothing. If you see X-Robots-Tag: noindex, your entire site is invisible to search engines and nothing else on this checklist matters.

Verify SSL and Canonical URLs

Hit these four URLs manually:

  • http://yourdomain.com
  • http://www.yourdomain.com
  • https://yourdomain.com
  • https://www.yourdomain.com

All four should 301 redirect to a single canonical version. Most sites use https://yourdomain.com (non-www, HTTPS). If any of these serve a 200 response instead of redirecting, you have duplicate content from minute one.

Verify Page Titles and Meta Descriptions

Spot-check your top 10 pages. Make sure each has a unique <title> tag and <meta name="description">. I use Screaming Frog for this, but you can also just curl a few pages:

curl -s https://yourdomain.com | grep -o '<title>[^<]*</title>'

If you're running a headless CMS setup — Sanity, Contentful, Storyblok — make sure your headless CMS development layer is actually populating these fields from the CMS content, not hardcoding placeholder text.

Hour 1-2: robots.txt and Sitemap Configuration

robots.txt

Your robots.txt file lives at https://yourdomain.com/robots.txt. It needs to exist, and it needs to be correct.

For most new sites, here's what it should look like:

User-agent: *
Allow: /

Sitemap: https://yourdomain.com/sitemap.xml

That's it. Don't overcomplicate it on launch day. You can add specific disallow rules later for admin pages, search results pages, or other non-indexable content. The critical thing right now is:

  1. You're not accidentally blocking everything (Disallow: / is the nuclear option)
  2. You're pointing to your sitemap
  3. The file is accessible (returns a 200, not a 404)

If you're using Next.js, the App Router has built-in support for generating robots.txt:

// app/robots.ts
import { MetadataRoute } from 'next'

export default function robots(): MetadataRoute.Robots {
  return {
    rules: {
      userAgent: '*',
      allow: '/',
    },
    sitemap: 'https://yourdomain.com/sitemap.xml',
  }
}

For Astro builds, you'll typically use the @astrojs/sitemap integration and create a static robots.txt in your public/ directory.

XML Sitemap

Your sitemap tells search engines exactly which pages exist and when they were last modified. It should be at https://yourdomain.com/sitemap.xml.

A good launch-day sitemap:

  • Includes only pages you actually want indexed (no 404s, no redirects, no noindex pages)
  • Uses the correct canonical URLs (HTTPS, correct www/non-www)
  • Has accurate <lastmod> dates
  • Stays under 50,000 URLs per sitemap file (use a sitemap index if needed)

Test it right now:

curl -s https://yourdomain.com/sitemap.xml | head -50

Make sure it's valid XML, not an HTML page. I've seen React apps that intercept /sitemap.xml and serve the app shell instead. That's useless to Googlebot.

Hour 2-4: Google Search Console Setup

This is your single most important SEO tool on launch day. Don't skip it. Don't delay it.

Adding Your Property

  1. Go to Google Search Console
  2. Add your property using the Domain option (not URL prefix) — this covers all subdomains and protocol variants
  3. Verify via DNS TXT record (your hosting provider or Cloudflare makes this easy)

Domain-level verification takes a few minutes to propagate. While you're waiting:

Submit Your Sitemap

Once verified, go to Sitemaps in the left sidebar and submit your sitemap URL. Google will fetch it and report any errors.

I typically see the initial sitemap processing complete within 1-4 hours. Google will tell you how many URLs were discovered and how many are valid.

Request Indexing for Key Pages

Use the URL Inspection tool at the top of Search Console. Paste in your most important URLs — homepage, key landing pages, top blog posts — and click Request Indexing.

Google limits you to roughly 10-12 index requests per day per property. Prioritize:

  1. Homepage
  2. Core service/product pages
  3. About page
  4. Top content pages

Don't waste requests on pagination pages, tag pages, or anything you'd consider secondary.

Check Coverage Report

Within 24 hours (often sooner), the Pages report will start populating. Watch for:

  • Not indexed: Crawled - currently not indexed — Google found the page but chose not to index it
  • Not indexed: Discovered - currently not indexed — Google knows the page exists but hasn't crawled it yet
  • Excluded by robots.txt — your robots.txt is blocking something you didn't intend

Website SEO Launch Day Checklist: What to Do in the First 48 Hours - architecture

Hour 2-4: Bing Webmaster Tools and IndexNow

Yes, Bing matters. It powers roughly 9% of US search traffic as of early 2026, plus DuckDuckGo, Yahoo, and increasingly, AI-powered search results in Copilot and ChatGPT (through Bing's index).

Bing Webmaster Tools Setup

  1. Go to Bing Webmaster Tools
  2. You can import your Google Search Console setup directly — Bing offers this option and it saves time
  3. Submit your sitemap here too

Bing's indexing is often faster than Google's for new sites, partly because of IndexNow.

IndexNow Protocol

IndexNow is a push-based protocol that instantly notifies search engines when your content changes. Bing, Yandex, and several other engines support it. Google does not (yet — they've been "evaluating" it since 2022).

Here's how to set it up:

  1. Generate an API key (any string, like a UUID)
  2. Create a key file at https://yourdomain.com/{your-key}.txt containing just the key
  3. Ping the IndexNow API:
curl "https://api.indexnow.org/indexnow?url=https://yourdomain.com/&key=your-api-key"

For bulk submissions:

curl -X POST "https://api.indexnow.org/indexnow" \
  -H "Content-Type: application/json" \
  -d '{
    "host": "yourdomain.com",
    "key": "your-api-key",
    "urlList": [
      "https://yourdomain.com/",
      "https://yourdomain.com/about",
      "https://yourdomain.com/services"
    ]
  }'

Many hosting platforms and CMS tools support IndexNow natively now. Cloudflare has an IndexNow integration. WordPress has plugins. If you're running a Next.js site, you can add IndexNow pings to your build/deploy pipeline or CMS webhook handlers.

Hour 4-8: Redirects — The Silent Killer

If this is a brand new domain with no history, you can mostly skip this section. But if you're relaunching an existing site — new design, new CMS, new URL structure — redirects are where launches go wrong.

Map Every Old URL to Its New Equivalent

Before launch, you should have a redirect map. After launch, you need to verify it works.

Take your old sitemap (you did save it, right?) and test every URL:

# Quick bash one-liner to check redirects
while read url; do
  status=$(curl -o /dev/null -s -w "%{http_code}" -L "$url")
  echo "$status $url"
done < old-urls.txt

You're looking for:

  • 301 redirects to the correct new page (not 302s — use 301 for permanent moves)
  • No redirect chains (old URL → intermediate URL → final URL). Each redirect should go directly to the destination
  • No redirect loops (URL A → URL B → URL A)

Common Redirect Gotchas

Issue What happens How to spot it
Missing trailing slash redirect /about and /about/ are different URLs Check both variants
Case sensitivity /About vs /about Test with wrong casing
Query parameter handling Old URLs with ?id=123 Check old parameterized URLs
Fragment handling Anchors #section get stripped Review old linked anchors
Mixed content redirects HTTP → HTTPS plus path change Ensure single 301, not chain

In Next.js, you handle redirects in next.config.js:

module.exports = {
  async redirects() {
    return [
      {
        source: '/old-blog/:slug',
        destination: '/articles/:slug',
        permanent: true,
      },
    ]
  },
}

For large-scale redirects (hundreds or thousands), consider handling them at the edge — Vercel Edge Config, Cloudflare Workers, or your CDN's redirect rules. Putting 2,000 redirects in your application config can slow down builds.

Hour 4-8: Analytics and Tracking Verification

Google Analytics 4 (GA4)

Make sure your GA4 property is firing correctly on every page. The easiest check:

  1. Open your site in Chrome
  2. Open DevTools → Network tab
  3. Filter by collect or google-analytics
  4. Navigate between pages — you should see network requests for each pageview

For single-page apps (which most Next.js and Astro sites are, at least partially), verify that client-side navigations trigger pageviews. This is a super common miss — the initial page load fires analytics, but subsequent navigations don't.

If you're using Next.js App Router with the @next/third-parties package:

import { GoogleAnalytics } from '@next/third-parties/google'

export default function RootLayout({ children }) {
  return (
    <html>
      <body>{children}</body>
      <GoogleAnalytics gaId="G-XXXXXXXXXX" />
    </html>
  )
}

Google Tag Manager

If you use GTM, verify the container is loading and your tags are firing. Use the GTM Preview mode (Tag Assistant) to debug.

Set Up Core Web Vitals Monitoring

This matters for SEO ranking. Your launch-day metrics will become your baseline. Set up real-user monitoring:

  • Google Search Console → Core Web Vitals report (takes a few days to populate)
  • web-vitals JavaScript library for real-time data
  • Vercel Analytics if you're on Vercel (built into the platform, $10/month for Pro)

As of 2026, Google's ranking uses these CWV thresholds:

Metric Good Needs Improvement Poor
LCP (Largest Contentful Paint) ≤ 2.5s 2.5s - 4.0s > 4.0s
INP (Interaction to Next Paint) ≤ 200ms 200ms - 500ms > 500ms
CLS (Cumulative Layout Shift) ≤ 0.1 0.1 - 0.25 > 0.25

Note: INP replaced FID (First Input Delay) in March 2024 as the responsiveness metric. If any guide still mentions FID, it's outdated.

Hour 8-24: What Actually Gets Indexed First

This is the question everyone asks, and the answer might surprise you.

Google's Crawl Priority

From my experience across dozens of launches, here's the typical indexing order:

  1. Homepage — almost always first, usually within 4-24 hours after sitemap submission and index request
  2. Pages linked from the homepage — your main navigation pages get crawled next
  3. Pages with external backlinks — if your new site already has links from other sites pointing to it, those destination pages get priority
  4. Sitemap-only pages — pages that are only discoverable via the sitemap (not linked from navigation) get crawled last

What Slows Down Indexing

  • Thin content — pages with very little unique text get deprioritized
  • Duplicate content — if Google detects pages that are too similar, it'll index one and skip the rest
  • Orphan pages — pages with no internal links pointing to them (even if they're in the sitemap) are treated as low-priority
  • New domains with no authority — brand new domains take longer. This is just reality. Google is cautious with unknown domains.

Realistic Indexing Timeline for a New Domain (2026)

Timeframe What to expect
0-4 hours Sitemap fetched, homepage crawled
4-24 hours Homepage indexed, top-level pages crawled
1-3 days Main navigation pages indexed
1-2 weeks Most sitemap URLs crawled
2-4 weeks Full index coverage for quality pages
1-3 months Search rankings start stabilizing

For established domains doing a relaunch, indexing is much faster — usually 24-72 hours for the majority of pages, assuming your redirects are working correctly and you haven't radically changed your URL structure.

Hour 24-48: Monitoring and Fixing Issues

Check Google Search Console Coverage

By now, you should see data flowing in. Look at the Pages report and address any issues:

  • Soft 404s — pages that return 200 but Google thinks are error pages (usually because they have almost no content)
  • Server errors (5xx) — your site is returning errors to Googlebot even if it looks fine in your browser (this can happen with aggressive rate limiting or bot detection)
  • Redirect errors — broken redirect chains or loops

Monitor Your 404s

Check your server logs or analytics for 404 errors. Real users and search engines are hitting URLs that don't exist. For a relaunch, each 404 is a missed redirect that's costing you link equity.

Fetch and Render Key Pages

Use the URL Inspection tool's Live Test feature to see exactly how Google renders your pages. This is critical for JavaScript-heavy sites. If you're using client-side rendering for important content, Google might not see it.

This is one reason we often recommend server-side rendering or static generation for content-heavy sites. Our Next.js development and Astro development work almost always uses SSR or SSG for exactly this reason.

The Complete 48-Hour Checklist Table

Time Task Priority Tool
Hour 0 Remove staging noindex tags Critical View source, curl
Hour 0 Verify SSL and canonical redirects Critical Browser, curl
Hour 0 Spot-check page titles and meta descriptions High Screaming Frog, curl
Hour 1 Verify robots.txt is accessible and correct Critical Browser
Hour 1 Verify XML sitemap is valid and complete Critical Browser, XML validator
Hour 2 Set up Google Search Console Critical GSC
Hour 2 Submit sitemap to Google Critical GSC
Hour 2 Request indexing for top 10 pages High GSC URL Inspection
Hour 3 Set up Bing Webmaster Tools High Bing
Hour 3 Implement IndexNow Medium API, hosting config
Hour 4 Verify all redirects (relaunch only) Critical curl, Screaming Frog
Hour 4 Verify GA4 is tracking all pages High GA4 Real-time, DevTools
Hour 4 Set up Core Web Vitals monitoring Medium GSC, web-vitals
Hour 8 Check initial crawl stats in GSC High GSC
Hour 24 Review GSC coverage report High GSC
Hour 24 Check for 404 errors in logs/analytics High Server logs, GA4
Hour 48 Fetch and render test key pages Medium GSC URL Inspection
Hour 48 Verify indexed page count matches expectations High site:yourdomain.com

FAQ

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

For a brand new domain, expect the homepage to be indexed within 24 hours if you submit your sitemap through Google Search Console and request indexing. Full site indexing typically takes 2-4 weeks. Established domains being relaunched usually see full re-indexing within 3-7 days. These timelines assume you've done everything in this checklist — without Search Console submission, a new domain might wait weeks before Google even discovers it.

Should I submit my site to Google or wait for it to be discovered naturally?

Always submit proactively. The idea that you should "let Google find you" is outdated advice from a decade ago. Submit your sitemap through Google Search Console and use the URL Inspection tool to request indexing for your most important pages. There's zero downside and it accelerates discovery by days or weeks.

Does IndexNow work with Google?

No, not as of mid-2026. Google has been evaluating IndexNow since late 2021 but hasn't officially adopted it. IndexNow currently works with Bing, Yandex, Naver, and a few others. It's still worth implementing because Bing's index powers DuckDuckGo, Yahoo Search, and is used by AI assistants like Microsoft Copilot and (partially) ChatGPT.

What's the difference between a 301 and 302 redirect for SEO?

A 301 is a permanent redirect that passes most link equity (ranking power) to the destination URL. A 302 is temporary and tells search engines the original URL might come back, so they're less likely to transfer ranking signals. For site relaunches and URL changes you don't plan to reverse, always use 301. I see teams accidentally use 302s all the time because that's the default in some frameworks.

Why are my pages showing as 'Discovered - currently not indexed' in Google Search Console?

This means Google knows your pages exist (from your sitemap or internal links) but hasn't crawled them yet. For new sites, this is normal in the first few days — Google queues URLs and crawls them based on priority. If pages stay in this state for more than 2-3 weeks, it usually means Google doesn't consider them high enough priority. Improving internal linking and adding unique, valuable content to those pages helps.

Do I need both Google Search Console and Bing Webmaster Tools?

Yes. They serve different search engines and give you different data. Google Search Console covers roughly 90% of search traffic in most markets, but Bing Webmaster Tools covers the rest plus provides access to IndexNow integration, which can speed up indexing on Bing-powered engines. Setup takes about 5 minutes for Bing since you can import your GSC configuration directly.

How do I check if my JavaScript content is being indexed by Google?

Use the URL Inspection tool in Google Search Console and click 'Test Live URL'. Then view the rendered HTML — this shows you exactly what Googlebot sees after executing your JavaScript. If critical content is missing from the rendered output, you need to switch to server-side rendering for that content. This is especially common with React SPAs that fetch content client-side. Frameworks like Next.js and Astro handle this well out of the box with SSR and SSG.

Should I block AI crawlers in my robots.txt on launch day?

This is a judgment call that depends on your business. Bots like GPTBot (OpenAI), ClaudeBot (Anthropic), and Google-Extended (Gemini training) can be blocked via robots.txt if you don't want your content used for AI training. However, blocking GPTBot may affect how your content appears in ChatGPT's search results. My recommendation: launch with everything allowed, monitor your server load from AI crawlers, and add blocks selectively if needed. Don't let this decision delay your launch — you can always update robots.txt later.

If you're planning a site launch and want help getting the technical SEO foundation right from day one, get in touch or check out our pricing. Getting this stuff wrong is expensive to fix later. Getting it right from the start is much cheaper.