When a client asks us to rebuild an aging site in Breakdance, the design conversation is rarely the hard part. The hard part is everything the client can’t see: the years of search visibility built into the old site’s URLs and content, the way that site might already be showing up when someone asks ChatGPT or Perplexity a question related to the client’s business, and the small structural details in the existing markup that quietly hold a layout together. A rebuild that ignores any of that isn’t really a redesign win. It’s a new coat of paint on a site that just lost the things that made it work.
This is how we approach a legacy migration to Breakdance when the goal is a site that looks and performs better, without giving up the search rankings, AI visibility, or structural integrity the old site had already earned.
What “Not Breaking the Site” Actually Covers
A safe migration protects four things at once, not just one. Search rankings are the obvious one, but they’re not the only thing at risk during a rebuild.
Answer engine visibility matters just as much now. If a site is already being referenced when someone asks an AI tool a question related to the client’s industry or services, that visibility comes from specific things, clear structured content, consistent entity information, well-formed schema, and a careless rebuild can quietly remove all of it even while search rankings hold steady.
The underlying HTML structure matters too. Heading hierarchy, semantic landmarks, alt text on images, these aren’t just SEO details, they’re also what search engines and AI crawlers use to actually understand a page’s structure. Breakdance gives a lot of visual freedom, and that freedom can lead to a heading used because it looks right rather than because it reflects the actual content hierarchy, which quietly degrades how both search engines and AI tools parse the page.
And the UI and UX of the site matter on their own terms. A migration that technically preserves rankings but ships a confusing mobile navigation or breaks a form a client relied on for leads has still failed, even if the SEO checklist came out clean.
Protecting all four at once is what separates a genuinely careful migration from one that just happens to look fine on the surface.
Start With an Honest Audit
Before any work happens in Breakdance, we pull a complete inventory of the existing site. Every indexed URL, not just the ones in the main navigation, since older blog posts, campaign landing pages, and archive pages often carry more traffic and more AI-citation value than anyone expects.
We check which pages are actually earning organic traffic and which ones show up when we test relevant queries against ChatGPT, Perplexity, and Gemini directly, since that’s the only reliable way to know whether a site currently has any AI visibility worth protecting. We pull the existing meta titles and descriptions, since these usually took real iteration to get right. We look at the heading structure on pages that are performing well, and we note which images have meaningful alt text already in place, since that’s easy to lose during a rebuild if nobody’s tracking it.
This step is tedious and it’s tempting to rush past it when a client is excited to see the new design. Skipping it is exactly how a migration ends up losing things it didn’t need to lose.
Map Every URL Before Building Anything
The single most common cause of ranking loss in a migration isn’t the new design, it’s URLs that change without a plan. We build a full spreadsheet mapping every existing URL to its destination on the new Breakdance site, and we keep URLs identical wherever there’s no strong reason to change them.
Where a URL does need to change, a permanent redirect goes live before launch, pointing directly to the closest new equivalent, not routed through a chain of old redirects that dilutes the signal search engines and AI crawlers use to understand the change.
Preserve Content and Heading Structure, Then Improve It Later
We migrate existing content largely as-is during the rebuild itself rather than rewriting everything at once. A page that’s ranking well, or already getting cited by an AI tool for a relevant question, is doing so because of a specific combination of structure and phrasing that’s already been evaluated favorably. Changing the builder, the template, and the copy all in the same project removes every stable reference point, which makes it far harder to diagnose anything that shifts afterward.
Heading hierarchy gets carried over deliberately too. If a page’s H1 and H2 structure is already indexed and understood, we replicate that structure in Breakdance rather than restructuring it for purely visual reasons. Breakdance offers a lot of design flexibility, but flexibility isn’t a reason to flatten a heading structure that’s already doing its job.
Carry Over Schema and Structured Data on Purpose
Meta titles, meta descriptions, canonical tags, and any structured data, review schema, FAQ schema, article schema, need to move over intact, and we check this specifically rather than assuming it happened automatically. This is often where older sites hide a gap, since structured data was frequently handled by a plugin or hardcoded into a theme that’s being replaced entirely during the migration.
Before launch, we compare the structured data output on the old site against the new Breakdance build using a rich results testing tool. This step matters directly for AI visibility too, since well-formed FAQ and article schema is one of the clearer signals answer engines use when deciding what to cite.
Protect the Markup, Not Just the Content
This is the part that’s easy to overlook. Breakdance’s visual builder makes it simple to create a layout that looks right without necessarily generating clean, semantic HTML underneath it. We check that headings are used for actual hierarchy rather than visual sizing, that images carry meaningful alt text rather than empty or generic placeholders, and that interactive elements, forms, menus, accordions, remain accessible and keyboard-navigable, not just visually consistent with the old site.
We also test the rebuilt UI against the same devices and browsers the old site was actually used on. A layout that looks clean on a designer’s monitor can behave very differently on the mid-range Android devices a lot of real visitors are using, and a migration that quietly breaks mobile navigation is a UX regression a client will notice fast, regardless of what’s happening with rankings.
Test on Staging, Then Watch Closely After Launch
We build the full migration on staging first, run the entire redirect map against it, and review a real mix of pages, not just the homepage and the obvious top performers, but older, less glamorous content that’s still pulling in traffic or AI citations. After launch, we monitor search console closely for several weeks, and we re-run the same AI queries we tested during the audit to confirm the site is still showing up where it did before. Some fluctuation right after a migration is normal. A steady decline that doesn’t recover, or a site that’s quietly stopped getting cited by AI tools it used to show up in, usually points to something specific worth tracking down, most often a redirect gap, a piece of missing schema, or content that changed more than intended.
Frequently Asked Questions
Does migrating a site to Breakdance hurt SEO? Not inherently. Ranking loss during a migration almost always comes from missed redirects, changed URLs, or lost content and heading structure, not from the act of switching builders itself. A carefully planned migration can preserve rankings and often improve them through better performance.
Can a redesign affect whether AI tools like ChatGPT or Perplexity cite a site? Yes. AI visibility depends on clear structured content, consistent entity information, and well-formed schema, all of which can be lost during a rebuild if they aren’t specifically checked and carried over.
How long does it take for rankings to recover after a migration? Most well-executed migrations show minimal disruption, with search engines re-crawling and re-indexing within a few weeks. A migration that follows a proper redirect and content preservation plan generally avoids any real recovery period at all.
The Goal Is an Uneventful Migration
From a search engine’s perspective, and increasingly from an AI answer engine’s perspective too, a well-run migration to Breakdance should feel almost uneventful. The design changes, the performance improves, the editing experience gets better for whoever manages the site day to day, but the URLs, the content depth, the markup, and the signals search engines and AI tools already trust stay intact. That’s the standard we hold every legacy migration to, and it’s the difference between a client getting a better-looking site and a client getting a better-looking site that quietly stopped performing the way the old one did.
If your team is planning a legacy migration and wants a second set of hands that already treats SEO and AI visibility as part of the build, not an afterthought, that’s exactly the kind of project we take on.