Key takeaways
- Audit content, rankings and backlinks before design starts, and map every old URL to its new home, so the rebuild doesn’t erase search visibility.
- Plan a shallow, topic-based site structure and treat the SEO migration as its own project with redirects, staging tests and 60 days of monitoring.
- Make performance a design requirement: Google’s “good” Core Web Vitals thresholds are an LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
- Build accessibility in from the start; WebAIM’s 2026 scan found detectable WCAG failures on 95.9% of the top one million home pages.
- Verify analytics, conversion events and Search Console on staging before launch so the first weeks of data are trustworthy.
A website rebuild is a chance to fix structure, improve search performance and make the site work better for your audience, beyond changing how it looks. Skip the right steps and you can lose traffic, rankings and leads that took years to earn. This guide covers what to do before, during and after a rebuild in 2026 so the new site performs better than the old one.
Why should you run a content and SEO audit before the redesign starts?
Run a content and SEO audit first because it shows which pages bring in traffic, rank for high-intent searches or earn links, and which add nothing, so you design around facts rather than assumptions. Skipping it risks rebuilding around the wrong content or deleting pages that carry your rankings.
When businesses come to Emulent after a rebuild went wrong, the cause is usually the same: nobody audited existing content before launch, and problems were migrated into a new design.
Four things to check in a pre-rebuild audit:
| Audit area | What to review |
|---|---|
| Traffic and rankings | Use Google Search Console and Google Analytics to find pages that drive organic traffic and the queries they rank for. Those pages come first in the rebuild. |
| Content quality | Flag thin, duplicate and outdated pages, then decide whether to keep, update, combine or remove each one. |
| Backlinks | Use tools such as Ahrefs or Semrush to find URLs that have earned links, and plan redirects so that authority carries over. |
| A URL map | Record every current URL and its planned destination. It becomes the basis of the redirect plan and keeps the team aligned. |
How do you build a site architecture that works for users and search engines?
Build a site architecture that groups related content into topic clusters, keeps important pages within a few clicks of the homepage and uses clean URLs and deliberate internal links. Structure decides how search engines crawl the site and how visitors find what they need.
Start by defining your main topics and the content that supports each. A flatter structure, with core pages close to the homepage, usually performs better than a deep one that buries important content.
Teams often spend weeks on design and hours on structure. The balance should be much closer to even, because a strong architecture keeps paying off and a weak one creates problems that are expensive to undo.
Four steps for planning structure:
- Group content into topic clusters. Pair each main topic page with supporting pages and link them together to show depth.
- Set URL rules early. Choose short, descriptive URLs before building and avoid long or auto-generated strings.
- Plan internal links. Decide which pages deserve the most links based on business and search value, and map them before development.
- Draw a visual sitemap. It exposes orphan pages, duplicate categories and gaps while changes are still cheap.
What does a solid SEO migration plan involve?
A solid SEO migration plan involves one-to-one 301 redirects, testing on a staging site, an updated XML sitemap and weekly monitoring for at least 60 days after launch. Migrations are among the riskiest parts of a rebuild because search engines need time to recrawl and re-index changed URLs, and mistakes can wipe out years of rankings.
Treat migration as its own project with a timeline and checkpoints that start before launch and continue for weeks afterward.
Four parts of a migration plan:
- 301 redirect mapping. Point every changed URL directly to its new page. Avoid redirect chains, which slow crawling and dilute link value.
- Staging tests. Check redirects, title tags, canonical tags and structured data on a staging site, where fixes cost far less than after launch.
- XML sitemap updates. Submit a new sitemap in Search Console at launch and again after the first round of indexing.
- Post-launch monitoring. Track crawl errors, indexing and rankings weekly for at least 60 days, and fix problems quickly.
How do Core Web Vitals and page speed fit into a new website?
Core Web Vitals and page speed should be design requirements from the start, because Google uses them as ranking signals and slow pages lose visitors and conversions. A beautiful site that loads slowly hurts both search performance and sales.
Core Web Vitals measure three things. Google’s recommended thresholds for a good experience are a Largest Contentful Paint (loading) of 2.5 seconds or less, an Interaction to Next Paint (responsiveness) of 200 milliseconds or less and a Cumulative Layout Shift (visual stability) of 0.1 or less. Test them before launch with PageSpeed Insights and Lighthouse.
We’ve seen well-designed sites score poorly because performance never came up in design reviews. Put the designer and developer in the same conversation early and make speed a shared goal.
Four choices that affect load speed:
- Image formats and compression. Use modern formats such as WebP or AVIF and compress before upload. Oversized images are among the most common and easiest problems to fix.
- Font loading. Use font-display: swap and limit font files per page so text appears while fonts load.
- Third-party scripts. Review analytics, chat and ad scripts and remove any that don’t justify their load time.
- Hosting and CDN. Server response time depends on hosting. For WordPress sites, we recommend managed hosting such as Kinsta, paired with a content delivery network.
Why should accessibility be part of the plan from the beginning?
Accessibility should be planned from the start because it’s far cheaper to build in than to retrofit, it reduces legal risk and it improves usability for every visitor. The Web Content Accessibility Guidelines (WCAG) set the standard, and websites that fall short face a regular flow of ADA-related demand letters and lawsuits in the United States.
Most sites still fall short. WebAIM’s 2026 analysis of the top one million home pages found detectable WCAG failures on 95.9% of them, with low-contrast text the most common problem.
Four accessibility checks to include in quality assurance:
- Color contrast. Confirm text and background combinations meet WCAG contrast ratios. WebAIM’s Contrast Checker makes this quick during design reviews.
- Keyboard navigation. Every interactive element must work with a keyboard alone, one of the most overlooked issues in new builds.
- Alt text. Give meaningful images descriptive alt text and decorative images empty alt attributes so screen readers skip them.
- Form labels and errors. Every field needs a visible label and clear error messages. Placeholder text isn’t enough because it disappears when typing starts.
How should you set up tracking and analytics before the site goes live?
Set up tracking before launch by testing every conversion event on staging, rebuilding goals around the new site’s paths, cleaning up your tag manager and verifying Search Console. Launching without verified analytics leaves you blind during the weeks that matter most.
Run new tracking alongside the old setup well before launch so you have a baseline. The worst time to discover broken conversion tracking is three weeks after launch, when someone asks why leads dropped.
Four tracking checks before launch day:
- Conversion events. Test every form submission, phone click and checkout step in Google Analytics 4 on the staging site.
- Goals and funnels. Rebuild GA4 goals around the new conversion paths instead of carrying over outdated ones.
- Tag manager cleanup. Remove unused tags and test the rest on the new build.
- Search Console. Confirm verification, ideally at the domain level, and submit the new sitemap on launch day.
Update your cookie consent and privacy policy at the same time, since new tags and tools often change what data the site collects.
How can Emulent help with your next website rebuild?
Emulent helps businesses plan and run rebuilds that audit before building, structure content with purpose, protect SEO during migration and launch with performance, accessibility and tracking in place. A rebuild done this way becomes an advantage instead of a setback.
A counterpoint: not every site needs a full rebuild. If the structure and platform are sound, targeted fixes to speed, content and conversion paths may deliver more for less money and less risk.
Our website design team handles both full rebuilds and focused improvements. Contact Emulent to plan a rebuild that keeps the rankings and leads you’ve earned.