Prevent SEO problems during a website deployment by checking what search engines can crawl, which URLs they should index, and where old URLs lead—before, during, and after release. Treat a URL or domain change as a site move that needs a migration plan; for ordinary releases that keep URLs intact, still verify crawlability, indexability, and canonical URLs.
Before the release: record the current state and plan changes
Capture a baseline of important URLs
Before code freeze, crawl or export the live site’s important URLs. Record their response codes, titles, canonical declarations, and indexability directives. This gives you a comparison point for detecting unintended changes after deployment. Google recommends validating redirects and indexing after a move; a baseline makes those checks practical. See Google’s site-move guidance.
As an Amazon Associate I earn from qualifying purchases.
Map old URLs to relevant destinations
If URLs will change, create an old-to-new URL map and review it before cutover. Redirect each moved page to its closest relevant replacement, not automatically to the homepage. For content that is removed or merged without a suitable replacement, decide whether it should return an appropriate not-found or gone response instead of redirecting users and crawlers to unrelated content. Google warns against irrelevant redirects in its redirect guidance.
Recommended Free Tools
- Include high-value pages and URLs found in the baseline crawl.
- Record the intended final destination for every redirect.
- Flag URLs with no replacement so their response can be decided deliberately.
Set production indexing rules
Decide what the production robots.txt should allow. If staging blocks crawling, prepare and review the production file in advance. Also identify staging-only noindex directives in page markup and X-Robots-Tag response headers, and assign someone to remove or change them at release. Google specifically warns that leftover robots.txt blocks and noindex rules can interfere with a site move. Check the production configuration against its migration guidance and the Search Console page indexing report help.
#1 Best Overall
These controls serve different purposes: robots.txt governs crawling, while a noindex directive tells a crawler not to index a page. A robots.txt block can also prevent a crawler from seeing a page-level directive. Verify the deployed settings from the public production site rather than assuming staging and production behave alike.
Prepare Search Console access and the sitemap
Verify both old and new site variants in Search Console before a domain or protocol change. Check the relevant host and protocol variants, and preserve verification files or tokens through deployment. Prepare an updated sitemap containing the intended canonical production URLs—not staging URLs or stale old addresses. Google’s site-move documentation covers migration preparation; its page indexing report help explains monitoring.
For hosting moves, plan DNS and capacity
If the host changes but the URLs do not, review DNS time-to-live (TTL) with your operations team. Google suggests that, when faster DNS cache refresh is desired, a conservative TTL such as a few hours can be set at least a week before the move. This is guidance, not a guarantee that every resolver will refresh immediately. See Google’s hosting-move guidance.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #2
Coordinate server capacity as well. Google says crawling may increase after a migration while it processes redirects from old URLs and crawls the new site. Make sure the team responsible for hosting knows when to watch performance; the site-move documentation discusses the transition.
At release: verify redirects, canonicals, and crawl controls
Deploy direct redirects to final destinations
Where possible, implement redirects server-side and point each old URL directly to its final, relevant destination. Avoid loops and unnecessary redirect chains. Googlebot can follow up to 10 hops, but Google advises linking directly to the final destination to reduce the chance of problems. See Google’s redirect guidance.
Test representative URLs across templates
Inspect old URLs, including high-value pages and examples from each major template. Confirm the response code, final destination, HTTPS behavior, and absence of loops. A crawler can check redirect behavior across many URLs; Google mentions Screaming Frog as one possible tool in its site-move guidance. For a small set of critical URLs, direct requests or browser checks can supplement a crawl.
Check destination canonicals and indexability
Inspect the destination page’s HTML or rendered output. Confirm that its rel="canonical" points to the intended new canonical URL when that is the desired URL, and that temporary noindex directives have not survived. A redirect alone does not confirm that the destination declares the intended canonical; Google addresses both checks in its redirect documentation.
From the public production environment, check robots.txt, page-level robots meta tags, and X-Robots-Tag headers. Confirm that each reflects the intended production policy, not the staging configuration.
Update links, sitemap, and domain settings
Make important internal links and sitemap entries point to the new URLs. Submit the updated sitemap through Search Console when appropriate. A sitemap can help Google discover URLs, but submission does not guarantee indexing; consult the page indexing report help.
If the domain changed, use Search Console’s Change of Address process where applicable, and ensure the old homepage and canonical pages redirect to their intended new destinations. See Google’s Change of Address tool instructions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.After release: crawl production and monitor Search Console
Run a production crawl
Once the deployment is public, crawl production and review response codes, redirect destinations, canonical URLs, and accidental crawl blocks or noindex directives. Compare the results with the baseline and URL map. Google recommends crawling to check redirects and identifies Screaming Frog as one possible crawler in its site-move documentation.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Investigate indexing and not-found signals
Watch Search Console for unusual increases in not-found errors, indexing problems, or crawl errors. Use URL Inspection to investigate individual pages that appear to be missing. A page may be excluded for an intentional reason, such as a deliberate noindex or a removed URL, so check the reported status against the release plan. Google’s page indexing report help describes the report and its statuses.
Best Value
Keep the sitemap and migration signals current
During a URL move, warnings about old sitemap URLs that redirect can be expected. Keep the live sitemap updated with the new URLs and monitor indexing over time, as described in Google’s site-move guidance.
Keep redirects in place and allow time for recrawling
Do not remove old redirects as soon as the new site launches. Google says moving most pages in a medium-sized site’s index can take a few weeks, while larger sites may take longer. The timing varies, and crawl rate depends on site size and available crawl capacity. Keep redirects active and monitor the transition rather than treating incomplete indexing immediately after launch as proof that the migration failed. See Google’s migration guidance.
Choose validation that fits the release
Manual checks and automated crawls answer different operational needs. Search Console adds indexing and crawl signals, but it does not replace direct checks of configured redirects. Google supports crawl-based redirect checks and Search Console monitoring in its site-move guidance.
| Approach | Coverage | Repeatability | What it shows | Best release use |
|---|---|---|---|---|
| Manual spot checks | A few selected URLs | Usually a one-time inspection unless documented and rerun | Direct response, final URL, rendered page, and visible directives for each checked URL | Cutover checks for critical pages and quick diagnosis of a specific failure |
| Automated crawl | Broad coverage of crawlable site URLs | Can be rerun as a release check | Patterns in status codes, redirects, canonicals, and indexability across crawled pages | Pre- and post-release comparison and repeatable sign-off |
| Search Console | Google’s reported crawl and indexing signals, not a direct audit of every configured redirect | Ongoing monitoring | Indexing and crawl issues, sitemap processing, and individual URL inspection | Postlaunch monitoring and investigation of pages that appear missing |
For release sign-off, name who runs each check, when it runs, and where results are recorded. A crawler helps find broad patterns; targeted requests help verify critical destinations; Search Console shows how Google reports discovery and indexing.
What this checklist can—and cannot—guarantee
These checks reduce avoidable configuration errors, but they cannot guarantee rankings, prevent every traffic decline, or make Google index a page on demand. Google’s own migration guidance says that recrawling and indexing take time and vary by site. As Google puts it, “Search Console is your friend, especially during a site move.”
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
