Redesigning a law firm or nonprofit website without losing search traffic

You keep search traffic through a website redesign by treating it as a site move. Before launch, list every URL that earns traffic or links. Map each one to the page on the new site that does the same job, and send it there with a single server-side 301 or 308 redirect. Carry over the content, titles, internal links and structured data that made the old pages rank. Then watch Search Console closely for the first weeks. Google says rankings may fluctuate during a move and that, for a medium-sized site, it can take a few weeks or more before the new URLs replace the old ones in results.

When a redesign loses traffic, look at the mechanics before the design. Google’s own troubleshooting list for site moves leads with two mechanical failures: noindex or robots.txt blocks left over from development, and redirects that point at wrong, non-existent URLs. Both are preventable, and both are decided before launch day.

When a redesign counts as a site move

If any URL changes, Google’s guidance on site moves with URL changes applies, even on the same domain. A new CMS that turns /attorneys/jane-smith.html into /people/jane-smith is a site move. So is merging three practice-area pages into one.

The same guide asks you to change one thing at a time. Its example is a site that wants a new domain, a new CMS and a new layout, and its advice is to do them one after the other. A redesign is already the layout change. If a rebrand also brings a new domain, launch the domain move separately.

Search Console’s Change of Address tool only applies when you move between domains or subdomains. Google says you don’t need it for moving paths within the same domain.

Inventory everything before it changes

The redirect map can only be as complete as the list of old URLs. Google names where to find them:

• XML sitemaps. Google notes your most important URLs have likely been submitted this way.
• Server logs or analytics, for the URLs that get the most traffic. Pick a period that covers seasonal swings.
• The Links report in Search Console. Its Top linked pages view shows which of your pages have the most backlinks from other sites.
• Your CMS, which can usually export every URL that hosts content.
• Embedded files. Google lists images, videos, JavaScript and CSS, and separately downloads such as PDF documents, which “might already be getting traffic from Google Search or links.”

Add a full crawl of the live site, and export the Performance report by page and by query. Its default view covers the past three months, so widen the date range. Keep the query export. After launch it is how you check whether the pages that used to answer a query still do.

Treat the Links report as a floor. Google says it “isn’t a comprehensive list of every link on your site.”

Map every old URL to the page that does its job

Map by content, not by slug. /services/estate-planning and /practice/trusts-and-estates share nothing in the URL and everything for the reader. The right destination is the new page that answers the same question. Matching slugs by string similarity produces confident, wrong redirects.

Then follow Google’s rules:

• Use server-side permanent redirects, 301 or 308. Google’s redirects documentation says permanent redirects show the new target in search results, while temporary ones keep showing the source. A 302 left in by accident tells Google the old URL is still the real one.
• One hop. Googlebot can follow up to 10 hops, but Google advises redirecting to the final destination directly and, where that isn’t possible, “ideally no more than 3 and fewer than 5.” If the old site already has redirects, point them straight at the new URL instead of adding a link to the chain.
• No homepage dumps. Redirecting many old URLs to one irrelevant page, such as the homepage, “might be treated as a soft 404 error.” When several old pages were genuinely consolidated into one, redirecting them all to it is fine.
• Honest errors for retired pages. Content with no equivalent on the new site should return a 404 or 410.
• Keep redirects for at least a year. Google says this gives it time to transfer signals, including links on other sites. From the user’s side, it suggests considering keeping them indefinitely.

Set redirects at the server or CDN, not in JavaScript. Google lists JavaScript redirects last because “rendering may fail,” and then Google might never see the redirect.

Keep what the old pages were ranking with

A redirect to a thinner page is a redirect to a weaker page. If the new practice-area page drops half the questions the old one answered, the address moved and the reason it ranked did not.

Carry these over, page by page:

• Content. Rewrite for voice if you want, but keep the topics, facts and questions the page ranked for. The query export tells you what those were.
• Titles. Google asks for a descriptive and concise title on every page. Its own example of what to avoid is “Profile” for a specific person’s profile, which many bio templates ship with.
• Internal links. Point links on the new site at the new URLs directly, since Google notes redirects are slow for users. Every page you care about should have a link from at least one other page, and Google can generally only crawl a link that is an <a> element with an href.
• Canonicals and hreflang. Each new URL should carry a self-referencing canonical. Multilingual annotations need the new URLs.
• Structured data. If the old templates output JSON-LD, the new ones should too. Google’s guidelines say not to mark up content that isn’t visible on the page, and that correct markup still doesn’t guarantee a rich result.

New templates also change how fast pages load. We cover that in what site speed costs and how Core Web Vitals measure it.

Keep staging out of Google, then let the real site in

A staging site has to stay out of the index, and robots.txt alone doesn’t do that. Google says robots.txt “is not a mechanism for keeping a web page out of Google”. A blocked URL can still appear in results, just without a description. Password protection is the clean option for staging. A noindex rule also works, but only if robots.txt doesn’t block the page, because Google has to crawl it to see the rule.

The classic launch mistake is the reverse: the staging protection ships with the site. A Disallow: / in robots.txt or a sitewide noindex goes live, and the new site tells Google to stay away. Google lists this first among common site-move mistakes. Its advice is to prepare the production robots.txt in advance and, if you used noindex during development, keep a list of the URLs to remove it from at launch.

Give that line on the launch checklist a named owner.

Launch day and the first weeks

On launch day:

• Remove staging blocks. Check robots.txt, and check a sample of page templates for noindex.
• Test every redirect from the old-URL list, not a sample. Google suggests the URL Inspection tool for single URLs and scripts or command-line tools for large lists. Each old URL should return one 301 or 308 to a page that returns 200.
• Submit sitemaps. Submit the new sitemap in Search Console. Google also suggests submitting a sitemap of the old URLs, so you can watch it fall toward zero indexed pages as the new one rises. Warnings that the old URLs redirect are expected.
• Update the links you control: email signatures, ad destinations, social profiles, directory listings. Then contact the sites behind the most valuable external links from your inventory.

In the first weeks:

• Page indexing report. Watch for a rise in Not found (404), Soft 404 and other errors. Google says it frequently sees redirects pointing at wrong, non-existent URLs, and an unusually high number of Not found errors is how that shows up.
• Server logs. Look for Googlebot activity and unexpected error codes. Google says that after a migration it will crawl the new site more heavily than usual, so server capacity matters.
• Performance report. Compare pages and queries against the pre-launch export. New URLs should start appearing for the queries the old ones held.

How long recovery takes, according to Google

Google gives a general rule, not a promise. For medium-sized websites, it says “it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones,” and longer for larger sites. The speed depends mostly on the number of URLs and server speed. It also says visibility may fluctuate during the move, that this is normal, and that “a site’s rankings will settle down over time.”

Google does not publish a timeline for traffic to return, and it varies by site. What you can watch is direction: new URLs indexed and rising, old ones falling, and the same queries showing up against new pages. A dip with clean redirects is a move in progress. A dip with old URLs returning 404s is a broken launch, and it won’t fix itself.

Law firms: practice areas, attorney bios and intake

• Practice-area pages are the ones a redesign is most likely to restructure: merged, split or renamed. Map these by hand. A page that was split redirects to the new page closest to its main topic. Pages that were merged all redirect to the consolidated page, which Google explicitly allows.
• Attorney bios are often the pages other sites link to: event listings, publications, directories. Check the Links report for bio URLs specifically. For lawyers who have left, decide page by page. If nothing on the new site does that page’s job, a 404 or 410 is the honest answer. Sending every departed lawyer’s bio to the homepage is the pattern Google warns against. On the new template, title bios with the lawyer’s name and practice, not “Profile.”
• Intake forms are where a redesign’s damage shows up as lost matters rather than lost rankings. After launch, submit every form end to end: the submission, the routing to intake, the confirmation, and the conversion event in analytics.

More on how we approach firm sites: websites for law firms.

Nonprofits: donation pages and campaign URLs

• Donation pages live outside the website: printed appeals, email templates, receipts, partner sites. Redirect every old donate URL to the live form, then run a test gift through the new flow, including recurring-gift management links.
• Campaign URLs such as /gala or a past year’s appeal are often printed or behind QR codes and missing from the sitemap. Pull them from server logs. Send each one to the current campaign or a relevant archive page, not the homepage.
• Reports and PDFs. Annual reports, impact reports and research briefs often hold links from funders and press. Google names PDF documents among the files to move.
• Timing. Google suggests timing a move to coincide with lower traffic if your traffic is seasonal. If giving peaks at year end, don’t launch in December.

More on how we approach mission-driven sites: websites for nonprofits.

Migration planning is part of our SEO, GEO and AEO work: the inventory, the redirect map, the launch checks and the weeks after.

FAQ

Will a redesign hurt our Google rankings?

If URLs and content stay the same, there is no move for Google to process. If URLs change, Google says to expect temporary ranking fluctuation while it recrawls and reindexes the site, and that rankings settle over time when redirects are correct.

Should we keep our existing URLs?

If they are readable and stable, keeping them removes most of the risk. Google’s URL structure guidance favors readable words over long ID numbers. Changing clean URLs for taste alone adds work with no search benefit.

How long should 301 redirects stay in place?

Google says to keep them as long as possible, generally at least one year, and to consider keeping them indefinitely for users.

Do we need Search Console’s Change of Address tool?

Only if the domain or subdomain changes. Google says it isn’t needed for moving paths within the same domain, for HTTP to HTTPS, or for switching between www and non-www.