What Happens After Your Website Launches: The First 90 Days

The first 90 days after a website launch run in four stages, and each one has a different job:

  • Verify (days 0 to 7): forms, redirects, tracking and indexability work on the live domain.
  • Get indexed (days 7 to 30): Google crawls and indexes the new pages.
  • Let it settle (days 30 to 60): rankings fluctuate and then steady.
  • Judge and plan (days 60 to 90): settled data is compared against the same period on the old site.

The fair point to judge a new site is day 72 to day 90, against the same weeks on the old site; day 72 is my calculation from Google's 12-day attribution window, explained below. Judging a new site in week two is the most common timing mistake I see, and it is too early: Google says it can take "a week or so" just to start crawling and indexing a new site, and Google Analytics can change key event attribution for up to 12 days after each event is recorded.

My post-launch routine below gives the day on which each number becomes trustworthy enough to act on. It picks up where the website project checklist and a pre-launch Webflow QA checklist end.

What happens in the first 90 days after a website launch?

The first 90 days after a website launch split into verify (days 0 to 7), get indexed (days 7 to 30), let it settle (days 30 to 60) and judge and plan (days 60 to 90), and each stage has a different definition of "normal". The table below is the whole timeline in one place. The delays quoted in it are Google's published figures; the stage boundaries and the day 72 row are my reading of them.

Delays quoted from Google: Search Console ownership verification, Page indexing report, Ask Google to recrawl your URLs, Site moves with URL changes. The day 72 figure is my calculation, explained below.
Stage and windowWhat Google and your analytics are doingWhat you should checkNormalWorry if
1. Verify (days 0 to 7)Search Console starts collecting data for the property, which takes "a few days" to accrueForms deliver, redirects resolve, tracking fires, the site is indexable, the sitemap is submittedLittle or no Search Console data yetA form or redirect fails, or the live site still carries a noindex tag
2. Get indexed (days 7 to 30)Google takes "a week or so" to start crawling a new site; a recrawl takes "a few days to a few weeks"Page indexing report and URL Inspection on your top pagesIndexed page count climbing week on weekKey pages listed as Not indexed with an error reason
3. Let it settle (days 30 to 60)On a relaunch with URL changes, a small to medium site takes "a few weeks" for most pages to move, with ranking fluctuationOld URLs in Search Console redirecting, 404s, first full month of analyticsRankings moving up and down, then steadyingImportant old URLs returning 404 instead of redirecting
4. Judge and plan (days 60 to 90)Key event attribution for days 31 to 60 is settled by day 72 (derived, see below)Settled weeks against the same weeks on the old site, then a ranked fix listA clear trend against the old site's baselineNo baseline exists to compare against

The same delays, read as a calendar, give the day each kind of number can be trusted:

Sources: GA4 data freshness, Search Console verification, Page indexing report, Site moves with URL changes. Day 42 and day 72 are my arithmetic, not Google figures.
WhenWhat becomes trustworthySource
24 to 48 hours after any dayGA4 data for that day is processedGoogle: "data processing can take 24-48 hours"
A few days after adding the propertySearch Console data starts to accrueGoogle Search Console Help
Up to a week or so after launchGoogle has usually started crawling and indexing the new siteGoogle Page indexing report help
Up to about two weeks after a fixA Validate Fix request in Search Console completesGoogle Page indexing report help
Day 42Key event attribution for days 1 to 30 has settledDerived: 30 + Google's 12-day attribution window
Day 72Key event attribution for days 31 to 60 has settledDerived: 60 + Google's 12-day attribution window
Day 365 at the earliestOld-URL redirects can be considered for removalGoogle: keep redirects "generally at least 1 year"

What should you check in the first week after a website launch?

In the first week after a website launch, check the things that silently lose money or visibility from day one: form delivery, redirects, tracking, indexability and account access. Every agency checklist on the first page of Google says "fix bugs and confirm tracking"; this is the specific list I run, in this order, because the early items cost the most if they are wrong.

  1. Submit every form on the live domain and confirm the email or CRM entry arrives at an inbox the company controls, not the developer's.
  2. Open your ten most valuable old URLs (from the old site's analytics or Search Console) and confirm each one redirects with a 301 to the closest new page.
  3. Confirm the live site is indexable. A staging noindex setting that survives launch is the most expensive one-line mistake I know of; the Webflow noindex guide shows where each setting lives.
  4. Verify the domain in Google Search Console under a company-owned Google account, then submit the sitemap in the Sitemaps report.
  5. Fire one test conversion and find it in Google Analytics 4 Realtime, so you know the key event works before real visitors arrive.
  6. Write down the baseline: last 90 days of clicks, sessions and leads from the old site, before anyone forgets what normal looked like.

Search Console collects data "as soon as anyone adds it", even before verification, but Google says "it takes a few days for data to start to accrue for the property" (Search Console Help). An empty Performance report on day two is expected, not a problem.

How long does Google take to index a new or relaunched website?

Google says it can take "a week or so" for Google to start crawling and indexing a new page or site, and that a requested recrawl "can take anywhere from a few days to a few weeks". Those two quotes come from the Page indexing report documentation and the recrawl guide respectively.

Two further details from the same Page indexing documentation change how the report should be read in month one:

  • 100% coverage is not the goal. Google says "you should not expect all URLs on your site to be indexed, only the canonical pages". Filtered views, tag archives and duplicates showing as Not indexed are often correct.
  • Fix validation is slow. After you fix an indexing issue and click Validate Fix, validation "typically takes up to about two weeks, but in some cases can take much longer".

In practice that means a fix made in week three may not show as passed until week five. Requesting indexing for your five or ten most important pages through the URL Inspection tool is worth doing once; requesting it daily is not, because Google states that a crawl request does not guarantee inclusion.

How long do rankings fluctuate after a relaunch with URL changes?

Rankings fluctuate for a few weeks after a relaunch with URL changes, because Google has to recrawl the site and transfer signals from old URLs to new ones; Google's own guidance is to "expect temporary fluctuation in site ranking during the move". Its site move documentation adds that "a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer".

The same page sets the rule I treat as non-negotiable: keep the redirects "for as long as possible, generally at least 1 year". Deleting a redirect list during a post-launch cleanup in month two undoes the signal transfer that was still in progress. Mapping old URLs to new ones before a redesign is a pre-launch job, covered in the redesign section of why a website gets traffic but no leads.

When I moved this site from Webflow to Astro, Vercel and Sanity in November 2026, every existing URL was kept and redirects are managed in Sanity. Keeping URLs identical is the single biggest thing you can do to make stage three boring, which is the goal.

A fluctuation that steadies is normal. My own rule of thumb, not a Google threshold, is to start investigating a decline that is still falling at day 42, the point where month one's data has settled. The usual causes are findable: a block of old URLs returning 404, a template that lost its title tags, or pages that were never redirected.

When can you trust your analytics numbers after launch?

Analytics numbers after a launch become trustworthy in layers: Google Analytics 4 data takes 24 to 48 hours to process, and key event attribution keeps changing for 12 days after each event is recorded. Google's GA4 data freshness page says "data processing can take 24-48 hours" and "attribution credit for key events can change for up to 12 days after the key event is recorded". Search Console marks its newest Performance data as "preliminary", meaning it "might change in the next few hours" (Performance report help).

The 12-day window applies to which channel or source gets credit for a conversion, not to the raw count of sessions or leads. From it, here is the worked calculation behind the day 42 and day 72 rows above. The arithmetic is mine; only the 12-day window is Google's.

  • Month one covers days 1 to 30. Its lead-source attribution settles on day 42 (derived: 30 + 12).
  • Month two covers days 31 to 60. Its lead-source attribution settles on day 72 (derived: 60 + 12).
  • Comparing month two with month one inside the first 90 days mostly measures the indexing ramp-up, not performance. The fair test from day 72 is settled weeks against the same weeks on the old site, which also cancels out most seasonality.

Google's own SEO Starter Guide points the same way for search changes: "some changes might take effect in a few hours, others could take several months", and "you likely want to wait a few weeks to assess whether your work had beneficial effects". Speed data runs on its own clock; the Webflow Core Web Vitals guide covers when field data appears for a new site.

Which post-launch mistakes cost the most?

The three most expensive post-launch mistakes are canonical tags or a sitemap still pointing at the staging domain, analytics that a consent banner or tag change silently breaks, and redirects removed in a month-two cleanup. I rank the six below by how much they cost and how long they usually go unnoticed, because the site looks fine to the people who built it.

  1. Canonicals or sitemap pointing at staging: Google is told the staging copy is the original, so live pages compete with it. First check: URL Inspection shows the Google-selected canonical for a live page.
  2. Analytics broken by a consent banner or tag change: conversions read as zero or double, and the day 90 decision rests on wrong data. First check: one test conversion with the banner accepted and one declined.
  3. Redirects removed in a month-two cleanup: signal transfer stops before Google finishes and old links land on 404s. First check: keep the redirect list for at least a year.
  4. External profiles still linking to old URLs: Google Business Profile, directory listings and ads depend on redirects forever. First check: update every profile you control in month one.
  5. Reading the indexing ramp-up as success: month two beats month one only because more pages are indexed. First check: compare against the old site's same weeks.
  6. Accounts owned by the developer: Search Console, analytics or the domain sit in someone else's account and access disappears when the project ends. First check: confirm a company email is an owner on every account.

Account ownership has its own full guide, who owns your website, because the domain registrant record matters more than any of the analytics accounts.

Who should do the post-launch work, you or your developer?

Post-launch work should be split by who holds the access and who can read the result: the developer owns technical fixes in stages one and two, and the company owns content, leads and the day 90 decision. A launch is not the end of a developer's job, but it should be the start of the company's.

  • Developer, days 0 to 30: redirects, indexability, form routing, tracking, and every error the Page indexing report surfaces.
  • Company, from day 1: answering leads, publishing content, and keeping the baseline. Day-to-day text and image edits do not need a developer; the Webflow editor tutorial covers what a content editor can change alone.
  • Both, days 60 to 90: a short review that turns the data into a ranked list of fixes and next pages.

If the developer stays on after launch, put that scope in writing; the Webflow retainer agreement guide lists the clauses that keep it clear. Companies hiring a developer directly can see how I structure that on the for companies page.

Want a second pair of eyes on your first 90 days?

If your site launched recently and you are not sure whether what you see is normal for its stage, book a 15-minute call. Bring your launch date and Search Console access, and you will leave knowing which stage the site is in, whether its indexing and redirects look healthy, and the one fix to make first.

FAQ

How long after launch should you wait before judging a new website's results?

A new website's results are fair to judge from about day 72 to day 90 after launch, against the same weeks on the old site. Google says indexing a new site can take a week or so to start, and GA4 says key event attribution can change for up to 12 days, so lead-source attribution for days 31 to 60 settles around day 72 (derived: 60 plus 12).

Why is my new website not showing up on Google yet?

A new website often does not show up on Google in its first week or so because Google says it can take a week or so to start crawling and indexing a new site. Check that the live site has no noindex tag, submit the sitemap in Search Console and request indexing for the key pages once.

How long do rankings fluctuate after a relaunch with URL changes?

Rankings after a relaunch with URL changes typically fluctuate for a few weeks. Google's site move guidance says to expect temporary ranking fluctuation and that a small to medium site can take a few weeks for most pages to move, with larger sites taking longer. A decline still falling at day 42 is worth investigating, by my own rule of thumb.

How long should old URL redirects stay in place after a relaunch?

Old URL redirects should stay in place for as long as possible after a relaunch, and Google's guidance is generally at least one year. Removing redirects early stops Google transferring the old pages' signals and sends visitors from old links to 404 pages.

Why do GA4 numbers for last week keep changing?

GA4 numbers for recent days keep changing because Google Analytics data processing can take 24 to 48 hours and attribution credit for key events can change for up to 12 days after the event is recorded. Compare periods that ended at least 12 days ago.

What should a website owner have in hand 90 days after launch?

A website owner should have four things 90 days after launch: a pre-launch baseline, two settled months of post-launch data, a Page indexing report with no unexplained errors on key pages, and a ranked list of fixes and next pages agreed with the developer.

Agency with more Webflow work than developers?

I build white-label Webflow sites for agencies with an AI-accelerated, senior-reviewed workflow. Book a 15-minute fit call for a straight answer on scope, timeline and cost.

Book a 15-min fit callSee how I work