Overhauling your website is a big undertaking. It is also one of the fastest ways to accidentally turn years of SEO progress into a very expensive guessing game.
A successful site migration does more than move pages from one place to another. It protects rankings, traffic, conversions, crawlability, indexation, content authority, and increasingly, your brand’s visibility across AI-powered search experiences. That means your migration plan needs to plan for both traditional SEO and GEO.
That does not mean you need to chase a brand-new set of mysterious AI ranking tricks. Please do not let anyone sell you an “AI migration schema package.” The fundamentals still matter.
Google has said its best SEO practices remain relevant for AI features like AI Overviews and AI Mode, and that there are no additional technical requirements to appear in those experiences beyond being eligible for Google Search with a snippet. That is the key point: GEO does not replace SEO. It extends the stakes.
During a migration, every important page needs to remain discoverable, crawlable, understandable, and trustworthy. Search engines and AI-assisted discovery systems are less likely to cite, summarize, rank, or recommend content they cannot access, render, or interpret.
No two site migrations are identical, but one constant in these transitions is the need for a clear SEO/GEO checklist. Following these steps helps protect hard-earned visibility before, during, and after the transition.
What Counts as a Site Migration?
A site migration is any major change to a website that can affect how search engines crawl, index, understand, or rank the site.
That can include:
- Moving to a new domain
- Changing URL structures
- Moving from HTTP to HTTPS
- Switching CMS or e-commerce platforms
- Redesigning the site
- Consolidating multiple sites or subdomains
- Changing hosting or server setup
- Updating navigation or site architecture
- Removing, merging, or rewriting large amounts of content
- Launching international, multilingual, or regional versions of a site
Some migrations are relatively simple. Others are more like changing the engine, tires, paint color, and license plate while the car is still moving. Either way, SEO and GEO need to be part of the plan from the start, not added at the end.
Why SEO and GEO Are Both at Risk During a Migration
A poorly handled migration usually does not cause a “Google penalty” in the manual action sense. That framing is a little dramatic.
What usually happens is more practical: search engines lose signals.
Old URLs disappear without redirects. Internal links point to dead pages. Canonical tags reference the wrong version. XML sitemaps are outdated. Staging noindex tags make it to production. Structured data gets dropped. Analytics tracking breaks. Pages that used to perform well are merged, rewritten, or buried three clicks deeper than before.
The result can look like a penalty: traffic drops, rankings fluctuate, leads slow down, and everyone suddenly becomes very interested in the redirect spreadsheet they ignored two weeks ago.
Google notes that visibility can fluctuate during a site move while its systems discover and process moved URLs. Some movement is normal. But preventable technical mistakes can turn a temporary dip into a longer recovery.
For GEO, the risk is similar. AI-powered search experiences still need accessible, clear, well-structured content to reference. If your strongest content becomes harder to crawl, loses context, or disappears behind broken redirects, your AI visibility can take a hit too.
How to Migrate a Website Without Losing SEO and GEO Visibility
1. Plan the Website Migration Carefully
Before anyone starts moving pages, define the scope of the migration.
- What is changing?
- What is staying the same?
- What are the business goals?
- What are the SEO risks?
- What are the GEO risks?
A redesign has a different risk profile than a domain migration. A CMS migration has different technical considerations than a content consolidation. A full rebrand with new URLs, templates, copy, and navigation structure is not a single project. It is several wearing one trench coat.
Start by documenting:
- The migration type
- The launch date and timeline
- Key stakeholders
- SEO requirements
- GEO and AI visibility considerations
- Analytics and reporting requirements
- Development constraints
- Approval steps
- Rollback plan
Migrate in phases when possible
While it may be tempting to update all content, URL structures, design, metadata, internal links, schema, and templates simultaneously, we do not recommend introducing too many changes at once unless there is no practical alternative.
Multiple large changes at once make troubleshooting harder. If organic traffic drops after launch, was it the redirect logic? The new templates? The content rewrite? The internal links? The robots.txt file? The canonical tags? Perhaps it was the new JavaScript framework quietly hiding half your content?
When possible, prioritize the migration in stages. If you are unsure which tasks are most important, bring IT, development, analytics, SEO, paid media, and content stakeholders into the planning process early.
2. Create a Complete URL and Content Inventory
A site crawl can give you a strong starting point, but it should not be your only source of truth. Crawlers can miss orphaned pages, blocked pages, erroring pages, legacy landing pages, and valuable URLs that still earn traffic or backlinks.
Google recommends building URL lists from sources like sitemaps, analytics, server logs, Search Console links, CMS exports, and embedded assets such as images, videos, JavaScript, and CSS.
Use multiple sources to build a complete inventory, including:
- Current XML sitemaps
- Google Search Console landing pages
- GA4 landing pages
- Site crawl exports
- CMS URL exports
- Server log data, if available
- Backlink data
- Paid search landing pages
- Social campaign landing pages
- Email campaign URLs
- PDFs and downloadable assets
- Image and video URLs
- Orphaned pages
- Pages returning errors
This inventory becomes the foundation for your redirect map, content decisions, QA process, and post-launch monitoring.
Do not ignore images, videos, PDFs, and other media. These assets can rank, earn links, drive referral traffic, and support topical relevance. If they are moving, they need a plan too.
3. Prioritize Pages for SEO and GEO Migration
Not every URL has the same value. Prioritizing pages helps the migration team focus on the areas most important for rankings, traffic, conversions, and authority.
Start with pages that have:
- High organic traffic
- High conversion rates
- Revenue or lead value
- Ranking keywords
- Authoritative backlinks
- Strong internal link equity
- Paid media dependencies
- Important local or product visibility
- Existing featured snippet, AI Overview, or answer-style visibility
- Clear topical authority for your brand
These pages should receive extra QA before and after launch. Their redirects should be tested manually. Their internal links should point directly to the new destination. Their metadata, schema, copy, headings, and media should be reviewed carefully.
For GEO, look for pages that clearly answer high-intent questions, define key entities, explain products or services, compare options, or support decision-making. These are the pages most likely to matter in AI-assisted discovery. This is true even if AI visibility reporting is still limited across platforms.
4. Decide What to Migrate, Improve, Consolidate, or Retire
A migration is a good time to clean house. It is not a good time to blindly drag every page from the old site into the new one because “we might need it someday.” That is how websites become digital attics.
For each URL, decide whether to:
- Migrate it as-is
- Improve it before launch
- Consolidate it with a stronger related page
- Redirect it to a relevant destination
- Return a 404 or 410 if it has no replacement and no meaningful value
This is where SEO and content strategy need to work together.
Thin, outdated, duplicative, or low-value content can weaken the overall site experience. But deleting content without checking traffic, rankings, backlinks, conversions, and internal links can create avoidable losses.
Do not make content decisions based only on pageviews. Some low-traffic pages support sales conversations, long-tail visibility, internal linking, local relevance, or AI-friendly topical depth. Others are just sitting there collecting dust and confusing everyone.
The job is to know the difference.
5. Map Redirects Carefully
Redirect mapping is one of the most important parts of an SEO/GEO site migration.
Using your URL inventory, create a document that maps each old URL to the most relevant new URL. Begin with high-priority pages and work your way down.
For permanent URL changes, Google recommends permanent server-side redirects whenever possible and notes that 301 and 308 status codes indicate a page has moved to a new location.
A few redirect rules worth treating as non-negotiable:
- Redirect each old URL to the closest relevant new URL.
- Do not redirect large groups of unrelated URLs to the homepage.
- Avoid redirect chains.
- Avoid redirect loops.
- Do not rely on JavaScript redirects unless there is no better option.
- Test redirects before launch.
- Test them again immediately after launch.
- Keep redirects in place for at least one year, and longer when possible.
Google specifically advises avoiding irrelevant redirects to the homepage and keeping redirects for at least one year so signals can transfer to the new URLs.
Redirect examples
Weak redirect:
/enterprise-seo-services/ → /
Better redirect:
/enterprise-seo-services/ → /services/search-engine-optimization/enterprise-seo/
Weak redirect:
/blog/how-to-choose-running-shoes/ → /blog/
Better redirect:
/blog/how-to-choose-running-shoes/ → /blog/best-running-shoes-guide/
Redirects are not just technical housekeeping. They are how we tell search engines, AI systems, and users where the value moved.
6. Update Internal Links Instead of Relying on Redirects
Redirects are necessary, but they should not become your internal linking strategy.
Once the new URL structure is confirmed, update internal links to point directly to final URLs. This improves crawl efficiency, reduces server load, avoids redirect latency, and creates a cleaner user experience.
Review and update:
- Main navigation
- Footer links
- Breadcrumbs
- Related posts
- Blog body links
- Product or service page links
- CTA buttons
- Image links
- XML sitemap links
- HTML sitemap links
- Canonical URLs
- Hreflang references, if applicable
This is also the right time to strengthen internal linking to priority pages. If a page matters for SEO or GEO, it should not be an orphan. Search engines and AI systems both benefit from clear site architecture and contextual relationships between pages.
Google’s AI features documentation specifically calls out making content easy to find through internal links as a continued best practice for AI features in Search.
7. Preserve On-Page SEO and Structured Data
A migration can quietly strip out the details that helped pages perform in the first place.
Before launch, confirm that priority pages retain or improve:
- Title tags
- Meta descriptions
- H1s and heading structure
- Body copy
- Image alt text
- Internal links
- Canonical tags
- Open Graph and social metadata
- Structured data
- Author or reviewer information, when relevant
- Product, service, local, or organization details
- FAQ or Q&A content that genuinely helps users
Structured data is not a magic GEO button. As much as we’d love to say it could, it does not guarantee rankings, rich results, AI citations, or anything else.
But it does help search engines understand page content. Google explains that structured data provides explicit clues about a page’s meaning and helps classify its content. That makes it worth preserving during a migration.
The key is accuracy. Structured data should match what users can actually see on the page. Do not add a schema for content that is not visible. That is not optimization. That is asking for trouble in JSON-LD.
8. Build GEO and AEO Into the Migration Plan
GEO, or generative engine optimization, focuses on how your content appears in AI-generated answers and AI-assisted search experiences. AEO, or answer engine optimization, focuses on making content clear and useful for direct answers.
During a migration, these should not be treated as separate from SEO. The same technical failures that hurt traditional rankings can also hurt AI visibility.
If AI systems cannot crawl the page, understand the entity, find the answer, verify the source, or access the updated version, the page is less likely to be useful in generated answers.
Here’s what that actually means for your migration.
Confirm important crawlers are not blocked
Review robots.txt, meta robots tags, CDN settings, firewall rules, and bot management tools.
You are looking for accidental blocks that could prevent important search or AI crawlers from accessing the new site. This includes Googlebot, Bingbot, and, depending on your brand’s AI search goals, OpenAI’s OAI-SearchBot.
OpenAI says OAI-SearchBot is used to surface websites in ChatGPT search features, and that sites that opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though they may still appear as navigational links. OpenAI also notes that OAI-SearchBot and GPTBot settings are independent, so a site can allow OAI-SearchBot for search visibility while disallowing GPTBot for model training use.
That does not mean every brand should allow every AI crawler. It means crawler decisions should be intentional, not inherited from a staging rule someone forgot existed.
Keep important answers in crawlable text
Do not hide critical content inside images, inaccessible scripts, or interactive elements that crawlers may struggle to process.
For SEO and GEO, the important information should be available as clear, crawlable HTML text. That includes product descriptions, service explanations, pricing context, location details, FAQs, author credentials, and claims that need supporting evidence.
Google’s AI feature guidance includes making important content available in textual form as one of the best practices that remains worthwhile for AI search features.
Make pages easier to understand and cite
AI systems do not “read” your pages like a person leisurely browsing with coffee. They parse, retrieve, summarize, and compare information.
Help them out.
Use:
- Clear H2s and H3s
- Concise definitions
- Direct answers to common questions
- Descriptive tables where useful
- Step-by-step explanations
- Specific examples
- Consistent entity names
- Updated dates where freshness matters
- Evidence for factual claims
Microsoft’s Bing Webmaster Tools AI Performance announcement says clear headings, tables, FAQ sections, examples, data, and cited sources can help improve clarity and make content easier for AI systems to reference accurately.
Again, this is not about writing for robots. It is about writing in a way that is useful, specific, and easy to verify. Conveniently, humans like that too.
Preserve entity and brand signals
If your migration changes your domain, company name, product names, service pages, author pages, location pages, or structured data, make sure those changes are consistent across the site.
Update:
- Organization schema
- LocalBusiness schema, if applicable
- Author pages and bios
- About page
- Contact page
- Location pages
- Product and service pages
- Social profiles
- Business listings
- Google Business Profile
- Bing Places
- Knowledge panel-adjacent sources, where applicable
For local businesses, this matters even more. Bing’s AI Performance announcement specifically highlights accurate business information for local AI visibility and recommends using Bing Places for Business to keep address, hours, and contact details up to date.
9. Test the New Site in a Sandbox
Testing is where the migration starts to feel real. It is also where many of the most painful launch-day issues can be caught early.
Use a staging or sandbox environment so your team can review the new site before it goes live. Because testing is for your team’s eyes only, keep the staging site blocked from indexation through password protection, private hosting, robots.txt blocks, or noindex tags.
But—and this is a very important but—make a launch plan for removing those temporary blocks.
Google lists forgotten noindex or robots.txt blocks as a common site migration mistake that can prevent the new site from being indexed completely.
In staging, review:
- Site architecture
- Navigation
- Internal linking
- Redirect map logic
- Canonical tags
- Robots.txt rules
- Noindex/nofollow directives
- XML sitemap
- Structured data
- Page templates
- Metadata
- Heading structure
- Forms
- Search functionality
- Checkout or lead flow
- Tracking pixels and analytics events
- Mobile experience
- Page speed
- Core Web Vitals
- Accessibility basics
- Content accuracy
- Broken images, videos, PDFs, and downloads
Get people from SEO, development, analytics, paid media, content, UX, sales, and leadership to review the site. Each group sees different risks. That is annoying in meetings but useful before launch.
10. Define Benchmarks and Set Up Tracking
Even an experienced SEO team will struggle to identify migration success without clean benchmark data from the legacy site.
Before launch, export and save:
- Organic sessions
- Organic conversions
- Revenue or lead volume by landing page
- Top organic landing pages
- Top ranking keywords
- Google Search Console clicks and impressions
- Index coverage data
- Crawl error data
- Backlink data
- Top linked pages
- Page speed and Core Web Vitals data
- Local visibility data, if relevant
- AI citation or AI visibility data, where available
Make annotations in GA4, Looker Studio, rank tracking tools, and reporting dashboards to mark critical migration dates. If the migration happens in phases, annotate each phase separately.
For GEO, benchmarking is still evolving. Google Search Console does not currently break out AI Overview or AI Mode performance as a separate report, while Bing has started reporting AI citations. But you can still track priority query visibility, branded search demand, landing page performance, and any third-party AI visibility data you trust enough to use directionally.
Bing Webmaster Tools introduced an AI Performance report that shows when site URLs are cited in AI-generated answers across Microsoft Copilot, AI-generated summaries in Bing, and select partner integrations. If Bing and Copilot visibility matters for your brand, this is worth adding to the post-launch reporting process.
11. Launch the New Site During a Low-Risk Window
Launch day is exciting. It is also not the day to discover your developer is out of the office, your analytics lead is on a plane, and the only person with DNS access is at a wedding.
Schedule the launch thoughtfully. Choose a lower-traffic window when key stakeholders are available, and the team can monitor the site in real time.
Before pushing the new site live, confirm:
- A full backup of the legacy site exists.
- The rollback plan is documented.
- DNS and hosting changes are ready.
- Redirects are prepared.
- Analytics and tracking are installed.
- Search Console and Bing Webmaster Tools access is confirmed.
- The new XML sitemap is ready.
- Robots.txt production rules are ready.
- Staging blocks will remain on staging only.
- Paid media and social campaign URLs are updated.
- Local listings are ready to update if the domain has changed.
- The team knows who owns each launch-day check.
If you are changing domains, use Google’s Change of Address tool where appropriate. Google says the tool is used for domain changes, but not needed when moving from HTTP to HTTPS.
12. Complete a Launch-Day SEO/GEO QA Check
Once the site is live, run the QA checklist immediately. This is not the time for “we’ll circle back next week.” Next week is when traffic drops become harder to diagnose.
Check:
- Important redirects are live and pointing to the right final URLs.
- There are no unexpected redirect chains or loops.
- High-priority old URLs resolve to the correct new pages.
- Crawling blocks are removed from production.
- Staging and development sites remain blocked.
- Canonical tags point to live, indexable URLs.
- XML sitemap includes the correct new URLs.
- The sitemap is submitted to Google Search Console and Bing Webmaster Tools.
- Robots.txt is correct.
- Noindex tags are removed from pages that should be indexed.
- Tracking and analytics tools are firing.
- Forms, carts, lead flows, and search functions work.
- Paid search, paid social, email, and affiliate links point to the correct URLs.
- Google Business Profile and Bing Places are updated if the domain has changed.
- Structured data validates on key templates.
- Priority pages are crawlable and render important content.
- OAI-SearchBot and other relevant crawlers are not accidentally blocked if AI search visibility is part of the strategy.
Google explains that sitemaps help search engines crawl a site more efficiently by providing information about important pages, videos, files, relationships, last modified dates, and alternate language versions. Do not skip the sitemap update. It is basic, but basic is often where migrations go sideways.
13. Monitor and Adjust After Launch
A lot of clients think the work is complete when the new site is live, but that is when the most important monitoring begins.
For the first few days, monitor closely. For the next several weeks, monitor consistently. For larger migrations, continue migration-specific reporting for at least 30 to 90 days.
Watch for:
- Organic traffic changes
- Ranking fluctuations
- Conversion changes
- Indexation changes
- Crawl errors
- 404 spikes
- Redirect issues
- Canonical issues
- Sitemap errors
- Page speed changes
- Core Web Vitals shifts
- Broken internal links
- Broken backlinks
- Missing metadata
- Duplicate content
- Structured data errors
- AI citation changes, where measurable
Google recommends monitoring both the old and new sites in Search Console and analytics after a move, with old-site traffic ideally declining as new-site traffic rises.
Some ranking and traffic fluctuation is normal. Avoid making complex changes too quickly unless there is a clear technical issue. Search engines need time to crawl, process, and reassign signals.
That said, do not ignore obvious problems. Broken redirects, accidental noindex tags, blocked crawlers, incorrect canonicals, and missing tracking should be fixed right away.
14. Keep Reporting Human-Friendly
Migration reporting should not just be a pile of charts with a shrug attached.
Organize reporting around what stakeholders actually need to know:
- What changed?
- What is stable?
- What dropped?
- What improved?
- What needs action?
- What is still being processed by search engines?
- What are we monitoring next?
For SEO, focus on visibility, traffic, rankings, conversions, indexation, crawl health, and page-level performance.
For GEO, focus on the signals you can actually measure: crawlability, indexability, content clarity, structured data preservation, branded and non-branded query visibility, and AI citation reporting where platforms provide it.
Do not overstate GEO performance if the data is directional or incomplete. The industry is still building reliable measurement standards. We can be strategic without pretending the dashboard knows more than it does.
Final Takeaway: A Migration Is a Visibility Handoff
A successful site migration is not just a launch. It is a handoff of trust, authority, relevance, and accessibility from the old site to the new one.
The design matters. The CMS matters. The user experience matters. But none of that does much good if search engines cannot understand what moved, where it moved, and why the new version deserves to keep earning visibility.
The same is true for GEO. AI-powered search experiences still depend on crawlable, trustworthy, well-structured content. If you are already doing SEO well, you have a strong foundation. If you are sloppy with redirects, internal links, structured data, crawler access, or content clarity, AI is not going to politely clean up the mess for you.
The fundamentals still matter. They just show up in more places now.
We know more than most that a site migration is a group effort with a lot of moving parts. Get the right tools, team, and strategy in place before launch, and your new site has a much better chance of keeping the visibility your old site worked hard to earn.
If your brand is planning a migration, Eight Oh Two can help protect your SEO performance, strengthen your GEO readiness, and find the growth opportunities hiding inside the move. Give us a shout via our contact form, or connect with us on LinkedIn to discuss detailed data insights while finding big-picture opportunities for growth.
