Almost two decades ago, I wrote about the power of 301 redirects. That piece covers the mechanics: server syntax, CMS-specific how-tos, and other minutiae. This one is about everything else that can go wrong when you merge, move, or rebuild a site. Updated for 2026. Here’s the fresh haps on why layout, intralinking, and 301 redirects matter during a redesign and what other SEO pitfalls to avoid when rejiggering your website.
Don’t Hastily Delete Text Content
Confer with your SEO collaborators before deciding what to delete. Digital-messaging stakeholders of varying backgrounds define value differently; one’s trash is another’s treasure. Inevitably, some content ends up on the cutting-room floor or is moved to a different directory.
Discarding, or even hastily reorganizing, pages that Google and LLMs ‘like’ is wasteful. If only there were a way of letting Google know that we’ve permanently changed our content schema. Enter the 301 redirect. I won’t go into technical detail here—suffice it to say 301s are powerful and easy to implement. (Already a 301 expert? Skip to the next section at your own peril.)
When You Remove Or Rename, Redirect.
Let’s call these “SEO’s Three R’s of Redesign”? Sure.
Depending on your situation, you’ll want to 301-redirect URLs accordingly.
Find Every URL, Not Just the Linked Ones
Crawlers like Screaming Frog only find what your site links to. But pages fall out of navigation all the time, and a URL can keep serving a 200 and keep ranking long after nothing points to it. Your CMS might not even list it in the sitemap. This bit me in August 2026.
So, build your URL list from multiple sources and deduplicate. GSC’s indexed URLs show what Google thinks you have. Server logs show what Googlebot actually requests. Backlink target URLs surface pages with external equity and no internal support, the most expensive kind to lose. Analytics landing pages show what still earns.
Whatever’s missing from that list becomes a 404 on launch day, and nobody notices until traffic does.
301 redirects when a page doesn’t make the cut
When merging two companies’ sites into one, and there’s messaging and/or product overlap, you’ll invariably want to leave some content out of the new website. If oldsite1URL/redwidgets didn’t make it to the new site (maybe because oldsite2URL.com’s red widget page is superior), 301 redirect that old URL to an appropriate asset on the new site. Something like newsiteURL/redwidgets.
Quick side note about merging content: If oldsite2 had a better red widget page, don’t assume all of oldsite2’s pages are better through the SEO lens. Ask your SEO guru if there are obvious outliers on either site.
If, during the merger, the company decides to no longer deal in red widgets, redirect that old page to the most appropriate page on the new site. If nothing on the new site is a reasonable substitute, resist the urge to dump it on the homepage. Google tends to treat a redirect to an unrelated destination as a soft 404 anyway, so you get the downside of a dead end without the clean signal. Serve a 410 instead. An accidental 404 is a mistake. A deliberate 410 is a decision.
A 301 on its own isn’t magic during a merger
If site A has a ranking page about [something] and you decide not to migrate that content to the new site, electing to only 301-redirect it to a tenuously related URL on the new site, those rankings will wither. The content is no small part of why that hypothetical page was ranking. Preserve content you care about; a 301 can only do so much.
301 redirects when you change domains and nothing else
If you’re only changing domain names but keeping all of your content and directory structure, set up a blanket redirect on the web server to send everything from the oldsiteURL/[whatever] to the applicable newsiteURL/[whatever] address. You may be tempted to set up a domain-level redirect at the registrar, but that redirect doesn’t handle SSL well. Stick to the web server for 301 redirects.
301 redirecting images?
While images aren’t often recognized as substantial SEO assets, if you’re aware of high-ranking images, be sure to give them some 301-love too. Many sites can safely ignore image assets when migrating to a new site or domain. However, if the images’ filenames and alt tags weren’t already optimized, add that toward the bottom of the SEO honey-do list.
Other SEO redesign concerns? There’s more!
Tell Google You’ve Moved!
Changing domains? File a Change of Address in Search Console once your 301s are live. If you’re still on URL-prefix properties rather than a domain property, file it for each variant. Then submit your old sitemap on the old property alongside the new one. Search Console will warn you that those URLs redirect. That’s the point: you’re handing Googlebot a list of pages to go find your 301s on.
Intralinking:
If a page used to be featured prominently in the site’s top navigation or footer but is orphaned or otherwise deprecated on the new site, Google will take note of its demotion. Falling from hundreds (or thousands) of internal inlinks to zero is a strong negative ranking signal. Screaming Frog’s Inlinks column gives you the number for both sites; sort by biggest drop and you have your worry list.
Ensure neither your dev nor CMS adds inexplicable nofollow attributes to links. (I’ve seen it happen.)
Compare the current site and the development version visually too. Run both through Screaming Frog and compare the crawl tree graphs, which map click depth and are where a demotion shows up. Or if you want something a little more maddening but maybe a little more helpful, try the “Force-Directed” diagrams. If the visualizations don’t appear somewhat similar at first blush, consider digging deeper.
Changing links and structure is often beneficial, but doing it poorly can be problematic.
Titles and meta descriptions:
I’ve written about title and meta description best practices. Check it out.
Assuming you’ve put effort into yours, maintain them during your website transition. Just do it. Maybe because they’re not visible on pages, people sometimes don’t migrate titles and descriptions to new sites.
¯\_(ツ)_/¯
Layout changes affect SEO & UX:
- Does the new layout use a tall hero image to push the text content far below the fold?
- Did you lose good funneling-CTA links (calls to action) in the redesign process?
- Did the words-per-line increase to the point where readability suffers?
- Did you accidentally remove attention-grabbing images? Captions? Engaging sidebars?
- Did you get overly creative when naming menu items? (I defer to designer-Dan from the year 2000 on how to obfuscate navigation with the best of intentions.)
- Are you taking this opportunity to improve (or eliminate) the hamburger menu?
- Does the new site’s convoluted background affect legibility of text?
- Did you test new ideas to see if they resonate with your typical viewer?
- Did you forget that we’ve been living in an increasingly “mobile first” web world for the better part of a decade now?
- Etc.
If layout changes inadvertently hurt user experience (UX), your SEO can suffer too.
Order of operations matters. Especially in complex situations
When a project involves more than one change (a merge and a domain change, say), resist the urge to stage them weeks apart. Sequencing means some URLs move twice and you inherit redirect chains you’ll maintain forever, so one well-tested cutover usually beats two tidy-looking ones.
Remember to password-protect the development site
If you don’t, your dev site is now prematurely and unfortunately competing against your soon-to-be old site. People who do remember to hide staging often use noindex or cross-domain canonicals instead of auth, and then ship with the tag or canonical still in place. Use HTTP auth or IP restriction, never noindex, never a canonical pointing at the old domain.
What else?
- Is your new site slower or otherwise less responsive?
- Have you gone through the unholy slog of trying to merge two Google business profiles?
- Does the old site have enhancements like SEO blurbs you should preserve?
- Did the “let’s trash our underperforming old content!” stakeholders prioritize their targets well? Compare a full URL list to those in the Google index to find candidates to nix. If you want to nix more, look for stragglers in GSC data.
- Is your new CMS less capable than the old one? e.g. Did it muss up your canonicals?
- Did some other marketing cog get too much leeway at the expense of your hard-earned SEO capital? Sometimes that’s okay! SEO doesn’t have to drive every decision.
Involving your SEO maven in the conversation will help your organization plot the path forward. SEO best practices don’t always define the direction, but they can help us read the map.
Dan Dreifort consults on SEO and UX. He makes noise in a couple of bands and pets all the cats. He’s self-publishing a few short stories in the not-too-distant future. Promise. He also promises to update that aging 301 redirect piece real soon. (Done. It’s updated!)
Dan Dreifort 