Share
The new website looks better. The services are easier to find and the design finally reflects the business you are today. Then someone notices that a page customers used to find through Google has disappeared.
A website relaunch changes more than what visitors see. It can change the content search engines find and the paths people follow to reach it. If those changes are handled late in the project, a polished launch can leave important gaps.
Website relaunch SEO brings search considerations into planning, development and postlaunch review. The goal is to preserve useful content and access to it while making the site better for customers. No process guarantees unchanged rankings, but a deliberate plan helps reduce avoidable problems.
Start Website Relaunch SEO Before Design Decisions Are Final
Bring marketing, development and the person responsible for SEO into the project early. Agree on which decisions need a search review before approval. Page removal and changes to navigation deserve attention alongside new layouts.
Clarify the scope. A visual update that keeps existing URLs creates different work from a domain change or a rebuild that reorganizes every service page. Google recommends separating major changes when practical, so discuss whether the project can be staged.
Give someone responsibility for approving the SEO work and someone responsibility for fixing technical issues after launch. Put time for that work on the schedule. Launch day should have an available team that knows how to respond if a key page or function fails.
Run a Prelaunch SEO Audit and Save Your Baseline
Before the current site is replaced, document what it contains and how it performs. Keep a record of important pages and their content, including titles and headings. Save a crawl of the old site if your team has the tools to produce one.
Use Google Search Console to review search clicks and impressions by page and query. Look at the services people find through nonbranded searches as well as searches for your company name. Separate those groups so a stable volume of brand searches does not hide changes elsewhere.
In your analytics system, record organic visits and meaningful actions such as completed inquiries. Check how those actions are defined before comparing them later. A new tracking setup that counts different events can make the results look different even if visitor behavior has not changed.
Choose a comparison period that reflects your business. Note seasonal patterns and major campaigns. Share the baseline with the launch team so everyone knows which pages and customer journeys need particular attention.
Protect Valuable Content During a Website Redesign
Review pages for the questions they answer and their business relevance before deciding what to remove. A short page may explain a specialized service that would be difficult to find inside a broad overview.
For a hypothetical professional services firm, several industry pages might appear repetitive at first. On closer review, each could address a different buying requirement. Consolidating them may be sensible, but the new content still needs to explain those requirements clearly.
Improve weak or outdated material where appropriate. Google’s people-first content guidance emphasizes usefulness and whether readers can accomplish their goals. Preserve accurate explanations and relevant evidence while making the material easier to understand. Carrying over every paragraph is not necessary; carrying forward the information customers need is the more useful test.
Plan URL Changes and Test Your 301 Redirects
Keep useful existing URLs when there is no reason to change them. For pages that move, create a record matching each old address to its most relevant replacement. Have a person familiar with the services review those matches.
Permanent server-side redirects, commonly 301 or 308 redirects, direct visitors and search engines to the new address. They provide a strong signal that the destination should replace the old URL. Temporary redirects communicate a different intent, so the implementation should match the actual change.
Test the route from the old address to the final page. Look for loops or unnecessary intermediate redirects. Update internal links to use the final address directly rather than relying on redirects for normal navigation.
When a page is permanently removed without a relevant replacement, an appropriate 404 or 410 response tells crawlers the content is unavailable. A visually attractive error page still needs the correct response code. Do not treat every removed page as an opportunity to send visitors to an unrelated destination.
Check Technical SEO Before the Relaunch Goes Live
Review representative service pages and articles, then check any templates with different behavior. A working homepage cannot establish that the whole site is ready.
Confirm Crawling and Indexing Settings
Development settings can accidentally carry over to the live website. Check that public pages intended for search do not contain a noindex instruction. This instruction can appear in page metadata or an HTTP response header.
Review robots.txt separately. It manages crawler access and is not a reliable way to keep a web page out of search results. Blocking a crawler can also prevent it from seeing page-level instructions. Keep intentional restrictions where needed and remove development-only blocks from public content.
Review Canonical Tags and the XML Sitemap
A canonical tag indicates a preferred version when pages have duplicate or very similar content. Check that it points to the intended live page rather than a development address or an unrelated page. It is a signal to Google, not a guarantee of which URL Google will select.
Generate an XML sitemap with the final URLs you want indexed and submit it in Search Console. Sitemap submission helps discovery but does not guarantee indexing. Review the sitemap for development addresses and pages that redirect or should remain out of search.
Test Mobile Performance and the Inquiry Process
Check important pages on mobile devices, including navigation and forms. Review Core Web Vitals for loading performance, responsiveness and visual stability. These measures contribute to page experience; a good score does not guarantee strong rankings.
Complete a test inquiry and confirm it reaches the right team. Test the associated tracking, too. A search visitor who reaches the new website still needs a reliable way to contact you.
Use an SEO Migration Checklist on Launch Day
Recheck the live website after deployment. Configuration and infrastructure can differ from the development environment, so prelaunch approval should be followed by live verification.
- Open priority pages and follow a sample of old URLs through to their replacements.
- Verify public-page indexing settings and canonical destinations.
- Confirm the live sitemap and Search Console access.
- Test forms and confirm analytics records the intended actions.
Record the launch time and any fixes made afterward. This gives the team a useful reference when reviewing changes in performance.
Monitor Search Visibility After the Website Relaunch
Check priority URLs in Search Console’s URL Inspection tool when you need to understand their indexing status. The live test can help diagnose current access problems, but a successful test does not guarantee the page will be indexed.
Review search performance by affected page groups rather than only the sitewide total. Compare equivalent periods and consider reporting delays. Look for changes in impressions as well as clicks, then investigate the pages and queries involved.
If organic visits appear to fall, first check whether tracking still works. Next examine access, indexing and the content changes made to affected pages. Fix observable faults before rewriting the entire site in response to a short-term movement.
A useful relaunch plan leaves room for investigation and improvement after publication. Preserve your baseline and change log, keep the responsible team involved and use what the evidence shows to decide the next adjustment.
Plan a Website Relaunch With Search in Mind
Preparing to replace your website? d2 Digital Designs can help connect website strategy, content and technical execution so search considerations are part of the project from the start. Email info@d2.design to discuss your relaunch and the work that needs to happen before it goes live.
Frequently Asked Questions
Can a website relaunch affect SEO if the domain stays the same?
Yes. Changes to URLs or content can affect search visibility on the same domain. New templates can also introduce access or indexing issues. Review the actual changes rather than using the domain name alone to judge risk.
How long does SEO take to settle after a website migration?
Google says processing URL changes can take weeks or longer, depending on the site and crawling conditions. There is no fixed recovery date. Monitor the affected URLs and investigate errors rather than treating every decline as temporary.
Do you need to use Google’s Change of Address tool for a redesign?
A redesign on the same domain does not by itself require it. Google’s tool applies to eligible domain or subdomain moves, not ordinary path changes or an HTTP-to-HTTPS move.
Should you change URLs to add more keywords during a relaunch?
Do not change established URLs solely to fit a keyword phrase. Consider clarity and the practical need for a new structure. If a change is justified, plan the replacement and test the redirect.
Does submitting a new sitemap guarantee your pages will appear in Google?
No. A sitemap helps Google discover URLs, but discovery and indexing are different steps. Pages still need to be accessible and meet applicable indexing requirements, and inclusion is not guaranteed.