A website launch is not finished when the new pages look correct in a browser. Search engines still need to rediscover the site, process redirects, understand canonicals and update their view of the URL estate.
The first fourteen days are therefore a monitoring period, not a waiting period.
Before launch: establish a baseline
Record the URLs that matter commercially before anything changes. Include priority service pages, product categories, high-performing articles and pages responsible for enquiries or sales.
Also capture the old-to-new redirect map where URLs are changing. This gives you something concrete to compare against after launch.
Day 0: verify the crawl path
Immediately after launch, check:
Google Search Essentials separates technical eligibility from whether Google chooses to crawl, index and serve a URL. Discovery work can remove barriers and improve signalling, but it should never be presented as a guarantee of indexation or rankings.
robots.txtis appropriate for production;- important pages do not carry accidental
noindexdirectives; - canonical tags point to the intended live URLs;
- the XML sitemap loads and contains the right hostnames;
- priority pages return successful responses;
- redirects reach the intended final URLs without unnecessary chains.
A staging directive left behind for even a few days can create avoidable disruption.
Days 1–3: watch discovery
Confirm that the sitemap remains reachable and that new or changed URLs are being discovered. Use Search Console diagnostics for high-priority Google URLs and supported notification mechanisms for participating engines.
Do not panic because every URL has not been processed immediately. Focus on patterns. If an entire directory is missing or blocked, that is much more significant than one low-priority page taking longer than expected.
Days 4–7: inspect exceptions
By the end of the first week, review:
- crawl errors;
- redirected URLs still present in the sitemap;
- unexpected canonical selections;
- pages classed as discovered but not crawled;
- broken internal links;
- orphaned priority pages.
The aim is to remove contradictions. If the sitemap, canonical tags, redirects and internal links all tell different stories, search engines have more work to do.
Days 8–14: compare against the baseline
Now compare the new estate with the original priority list. Which important URLs are indexed? Which have moved? Which have lost internal links? Which old URLs still appear when they should redirect?
Traffic can fluctuate after a migration, but technical visibility should become clearer rather than more confusing.
Automating the monitoring
For sites that change often, manually repeating these checks is inefficient. IndexFlow monitors sitemap discovery and helps surface broken or changed URLs so launch monitoring becomes an exception-based process.
That does not replace Search Console or a proper migration audit. It reduces the chance that a sitemap or discovery problem sits unnoticed for weeks.
If you need to verify an individual page first, use the guide on how to check whether a page is indexed.
The launch rule
Treat the first fourteen days as part of the launch project. The development work may be complete, but the search-discovery work is still in motion.
A clean launch process gives search engines consistent signals: one preferred URL, one working destination, one accurate sitemap entry and clear internal links. Monitor that consistency until the new site has settled.
Apply the idea without creating more noise
Start with the page's actual job and the reader's next decision. Check the evidence already available, identify the gaps preventing that decision, and improve those before adding another page or campaign. A useful change should make the journey clearer, not simply make the estate larger.
Measure the result against a baseline. For informational content that may mean qualified impressions, clicks and progression to a relevant commercial page; for commercial content it should extend to enquiries, sales or another meaningful conversion. This keeps optimisation tied to business value rather than publishing volume.
Implementation and measurement
Treat the recommendation as a decision process rather than a publishing task. Define the page or campaign's intended audience, the problem it should solve and the next useful action before changing anything. Compare the current experience with that job, then prioritise the smallest changes that remove genuine friction or ambiguity.
Use evidence at the point it matters. Primary guidance can establish factual constraints; first-party data, examples and experience can explain what those constraints mean in practice. Internal links should expand a concept or move a qualified reader to the next relevant step, not exist simply to increase link counts. The anchor should make the destination understandable before the click.
After implementation, record a baseline and review the metric that matches the job. Discovery work should improve qualified visibility; educational content should create useful progression into deeper or commercial pages; conversion work should be judged on enquiries, sales or another meaningful outcome. Avoid claiming causation from a single short observation window.
This also creates a maintenance loop. When products, evidence, search behaviour or official guidance changes, refresh the affected passage and its linked destinations rather than producing another overlapping URL. That keeps the estate coherent and reduces the risk of thin, stale or competing pages.