withMission.techStart a conversation

Website Redesign SEO for Nonprofits: Keep the Traffic You Already Have

A surprising share of the search traffic a nonprofit website earns lands on pages nobody on staff would pick as important, like a program explainer from years ago or an eligibility page people still find through Google every week. A redesign is when those pages disappear, usually without anyone deciding they should.

This is the SEO half of our guide to planning a nonprofit website redesign, which covers cost and choosing who builds the site. This one is about keeping your traffic through the change, and who keeps that work going once the builders move on to their next client.

01A website redesign is a website migration

A redesign gets discussed as a visual project, with mockups and a homepage for the board to approve. Underneath, nearly everything search engines know about your organization is being moved. Even on the same domain, that is a website migration, and website migration SEO applies to it.

Google ranks URLs, not organizations. When the URL that ranked for your food pantry's hours starts returning a 404, Google cannot know the information moved unless a 301 redirect says so. Without one, the ranking and every link pointing at the old address hit a dead end, and the new page starts from nothing. Leave SEO for after launch and the list of old URLs you would need for the repair may have gone with the old hosting account.

02What gets lost in a website redesign

Six things go missing. Usually only the first is on anyone's list.

  1. 01

    URLs

    The new navigation moves /programs/youth-mentoring to /what-we-do/mentoring. A new CMS drops the date folders from blog addresses, or the site moves from www to the bare domain. Each is a URL change even when the content is identical, and needs a redirect.
  2. 02

    Titles and descriptions

    Someone wrote the volunteer page's title by hand to match what people search for. The new template builds titles from the page name, so "Volunteer at our Saturday food sort" becomes "Get Involved | Organization Name."
  3. 03

    Inbound links

    A county resource directory links to your intake page, a university course page to a research summary. You cannot get those sites to change anything, so only a redirect keeps those links alive.
  4. 04

    Form destinations

    Every form had a destination: an inbox, the CRM, an email list, a webhook. The rebuilds get configured in a week from a list of fields, and the newsletter signup that used to reach the email platform now notifies an address nobody reads.
  5. 05

    Analytics continuity

    Tracking gets reinstalled, sometimes into a new property, sometimes without the GA4 key events that counted gifts. The first signal is then a development director noticing months later that online gifts are down.
  6. 06

    Pages nobody knew were earning

    An old how-to, a glossary entry, a page about who qualifies for a program, a PDF. They are not in the navigation, and in a content audit they look like clutter. In analytics they are often top-ten landing pages.

03Build the URL inventory from three sources

Every item in a website redesign SEO checklist depends on one document, a list of every URL the current site has with enough data beside each to decide what happens to it. No single source lists them all, so build it from three.

  1. 01
    Crawl the site with Screaming Frog or the audit in whatever SEO tool you already use. It records each URL's title, description, H1, and status code, and misses orphaned pages and PDFs linked only from emails.
  2. 02
    Take the XML sitemap, usually /sitemap.xml or /wp-sitemap.xml on WordPress, which lists pages the navigation has forgotten.
  3. 03
    Export twelve months of landing pages from analytics and from the Pages report in Search Console. Twelve months catches the year-end giving page, and Search Console will turn up leftovers from a redesign two cycles ago that still collect impressions.

Merge them into one sheet and give each row its search traffic, its linking domains, its current title, description, and H1, and a decision.

Keep, redirect, or retire

  1. 01

    Keep

    The URL stays exactly as it is. It is the best outcome for any page that earns traffic, and a URL does not have to match the new navigation to work.
  2. 02

    Redirect

    The content moves or is folded into another page, and the old URL gets a 301 to whatever replaces it best.
  3. 03

    Retire

    The URL returns a 404 or 410, which is fine for an event from 2017. Nothing goes in this column until someone has checked its traffic and links. A retired page with twelve linking domains is a redirect you forgot to make.

Attach the finished inventory to the website redesign RFP, and every bidder prices the same migration.

04The 301 redirect map

A 301 redirect map is a list that pairs every URL on the old site with its destination on the new one, one row per old URL. The developer implements it as permanent redirects at launch, and you check the live site against it afterwards.

Redirect mapping is clerical, and it decides more of the outcome than anything else in website redesign SEO.

  • Map one to one. Each old URL points at the single most relevant new page, and consolidated pages point at the page that absorbed them.
  • Never send the leftovers to the home page. Google warns against pointing many old URLs at one irrelevant destination in its site-move guidance, and says they may be treated as soft 404s, so the ranking goes anyway. The visitor who clicked a link about pantry hours lands on a hero image instead. A plain 404 page with a search box serves them better.
  • If the 2018 redesign sent /services/pantry to /programs/pantry and this one moves it to /get-help/food, the 2018 address now redirects twice. Point every old redirect straight at the final page, which means finding the previous redesign's list.
  • Use 301s. A 302 tells search engines the move is temporary, so check which one the plugin or host issues while it is still one setting.
  • The donation platform and the event pages break maps most often, because their links to your site live in another system's settings, where a crawl will not find them.
  • Keep the redirects. Google's guidance says at least a year, which is too short for any URL that was ever printed on paper.

05Carry the metadata and headings across

A page can keep its URL and still lose its ranking if the new template rewrites what the page says about itself. On every page that earns traffic, carry the title, meta description, and H1 across from the inventory, or improve them with the old version in front of you.

Headings count too. If the eligibility page had an H2 for each program and the new design folds them into an accordion with no heading elements, the structure search engines were reading is gone. Crawl staging and compare it with the live crawl column by column. Every changed title on a page that earns traffic should be a change somebody chose.

06Staging and index control

Staging gets indexed. A search engine follows a link pasted into a public document, and an unfinished copy of your site competes with the real one. Put staging behind a password. A robots.txt disallow does not stop indexing when the URL is linked from elsewhere, and a noindex tag works only if someone remembers to take it off.

The more common failure runs the other way, when the setting that kept staging out of search goes live with the site. On WordPress it is a checkbox labeled "Discourage search engines from indexing this site." Nobody notices, and the site slides out of search over the following weeks. A password left on a live site gets noticed in five minutes.

Keep the old site live and crawlable until the moment of launch, then keep a crawl export and a database backup for several months. The map will have mistakes, and the old site is where you look up what a URL used to be.

07Website relaunch SEO: verify launch week in bulk

Launch week turns the map into redirects, and you check every one of them on the live site. Sampling ten URLs is how the one that mattered gets missed.

Request each old URL from the inventory and record where it lands and how many hops it took. A crawler in list mode does this in minutes. Each row should be one 301 to a live page that matches the map, and anything else gets fixed that day.

  1. 01
    Crawl the new site for internal links still pointing at old URLs.
  2. 02
    Check robots.txt and a few templates for a stray noindex, then submit the new XML sitemap in Search Console.
  3. 03
    Run URL Inspection on the highest-traffic pages.
  4. 04
    Watch the Page indexing report daily for two weeks. Missed redirects show up there first, as 404s.
  5. 05
    Submit every form and a real gift on the live site, and read the receipt.
  6. 06
    Confirm analytics records key events in the same property as before.

If the domain changed too, file the move with the Change of Address tool in Search Console once the redirects are live.

08The ninety-day watch: a normal dip or a redirect problem

Traffic moves after every redesign. A normal dip is spread across the site, with clicks softening for a few weeks while Google recrawls and swaps new URLs in for old ones, then drifting back toward baseline.

A redirect problem has names. Specific pages lose their traffic and stay down, and Search Console shows their old URLs returning 404s. A website redesign traffic drop concentrated in a handful of pages is usually a mapping mistake, and fixable while you still have the inventory.

A sitewide drop within days usually means a noindex went live. If conversions fall while traffic holds, a form or the tracking broke, and that belongs with whoever owns the forms.

Compare against the baseline at thirty, sixty, and ninety days, year over year for the same weeks. A site that launches in October and runs into year-end giving will look like a triumph against September whatever happened to the redirects.

09Who owns this after launch day

Everything above has to be somebody's job. On most redesigns it is nobody's in particular, because each hire stops when the thing they were hired to make is finished.

  1. 01

    A marketing firm

    Hired for

    The brand, the messaging, the design, the copy, and the launch.

    Where it stops

    At launch day. A good firm writes and designs better than most technical studios, and some map redirects well.

  2. 02

    A web studio

    Hired for

    The build, the templates, the integrations in scope, and the handover.

    Where it stops

    At the handover, sometimes followed by a maintenance retainer. The studio fixes what breaks when asked. Whether next spring's receipts still link to the right page is not what it was asked.

  3. 03

    Someone past launch day

    Hired for

    The organization's technology over time.

    Where it stops

    It does not.

The redirect map needs a row when a program page is renamed next spring. Analytics stays continuous only if nobody starts a fresh property. Form destinations break when the associate whose inbox got the volunteer notifications leaves. The domain registrar and DNS are often in the name of whoever set them up a decade ago, and the logins to the CMS, the hosting, the donation platform, and the analytics are wherever the project left them. Then comes the year after, when people who were not in the project edit the site.

A marketing firm is the right hire for what a marketing firm does. If your site does not say clearly what you do, hire one. The organization also needs someone whose job continues after launch, named before the RFP goes out. That can be a staff member with this checklist and an hour a month. It can also be a technology partner or a fractional CTO. The builders hand over to that person, and the handover covers what our knowledge transfer guide describes: accounts in the organization's name, the redirect map, the form destinations, and the reasons behind the decisions.

We sell the retained version of that seat. Weigh this section accordingly.

10What is different about a nonprofit site

Most SEO website redesign advice is written for online stores. A nonprofit site has obligations theirs do not, and most of them sit outside the site's own pages.

Start with the donation platform. The return URL, the thank-you page, the tribute forms, the receipt's links, and the page recurring donors use to update a card all live in its settings. Change them on launch day. And do not launch in November or December.

Funders and partners link to program pages from a foundation's grantee list, a community foundation directory, a 211 listing, a county resource guide. The people who run those sites will not answer your email, so keep those program pages at their current URLs.

Volunteer and event registration links sit in calendar invitations, on ticketing platforms and partner sites, and in last year's confirmation emails. Write down where each form's submissions go before it is rebuilt. If the honest answer is several systems that disagree, our guide to choosing a nonprofit CRM starts there.

Grant report PDFs on WordPress sit at paths like /wp-content/uploads/2023/05/, which change entirely when the CMS does. A program officer reviewing your renewal clicks the link in last year's report and gets a 404. The annual report and the QR code on event signage are the same problem on paper, and you cannot recall a printed appeal, so those URLs stay or redirect for good. Short addresses like /give and /annualreport are worth keeping forever.

11The website redesign SEO checklist

Fifteen items for anyone trying to redesign a website without losing SEO. Lift them into your project plan or your RFP.

Before anyone designs anything

  1. 01
    Take a baseline: twelve months of landing pages from analytics and Search Console, and conversion counts for every form and donation flow.
  2. 02
    Build the URL inventory from a crawl, the XML sitemap, and those landing pages, with traffic, linking domains, title, description, and H1 on every row.
  3. 03
    Mark every URL keep, redirect, or retire, and retire nothing without checking its traffic and links.
  4. 04
    List every form with its destination, and every platform that links back to the site.
  5. 05
    Make the inventory and a complete 301 redirect map RFP requirements, and name who owns the map after launch.

During the build

  1. 01
    Build the redirect map alongside the new navigation, one row per old URL, nothing sent to the home page.
  2. 02
    Collapse old redirect chains to one hop, and confirm the redirects are 301s.
  3. 03
    Carry titles, descriptions, and headings across on every page that earns traffic.
  4. 04
    Keep staging behind a password and the old site live until launch.
  5. 05
    Crawl staging and compare it with the live crawl.
  6. 06
    Prepare new return URLs, thank-you pages, and receipt links in the donation and event platforms.

Launch week and the ninety days after

  1. 01
    Verify every old URL on the live site in bulk.
  2. 02
    Check for noindex, submit the new sitemap, and inspect the top pages in Search Console.
  3. 03
    Test every form and a real gift end to end, read the receipt, and confirm key events are recording in the same analytics property.
  4. 04
    Compare with the baseline at thirty, sixty, and ninety days, and keep the redirects and the inventory for good.

12Website redesign and SEO: questions we get asked

Will a website redesign hurt SEO?
It can, and when it does the cause is mechanical: URLs changed without redirects, pages cut without checking their traffic, titles regenerated by new templates, or a staging block left on at launch. A redesign built from a URL inventory and a one-to-one 301 redirect map usually sees a short dip while search engines recrawl, then returns to baseline.
How long does a traffic drop last after a redesign?
A few weeks for a well-mapped redesign, which is what Google's site-move guidance describes for a medium-sized site. If specific pages are still down after six to eight weeks, look them up in the redirect map. A missing or misdirected redirect is the likely cause, and the longer it sits the less of the old ranking comes back.
What is a 301 redirect map?
A 301 redirect map is a spreadsheet with one row for every URL on the old site and a column for where it goes on the new one. At launch the developer loads it as permanent 301 redirects, and after launch you test the live site against it. A good one sends nothing to the home page and has no chains.
Do we need an SEO agency for a redesign?
Usually not, for a nonprofit site of ordinary size. The inventory, the redirect map, the metadata carryover, and the launch check can be done by a careful staff member or by the studio building the site, if it is in scope. A specialist earns the fee on a site with thousands of pages or a domain change.
Should our marketing agency handle the redirects?
They can, if the contract says so and names who verifies them. The harder part comes after the engagement ends and a program page is renamed. Whoever maintains the redirects then needs the map and the logins, and should be on your staff or on a retainer that runs past launch day.
Can we redesign without losing SEO?
Yes. Keep every URL you can, redirect the rest one to one, carry the metadata over, keep staging behind a password, and check everything on the live site in launch week. Organizations that lose traffic in a redesign mostly skipped the inventory.

Know what your site is carrying before you redesign it

A Mission Surface Review builds the inventory before anyone is hired, along with where every form's submissions land. It becomes the evidence in your RFP. If you would rather do it yourselves, this guide is the method, and we would rather you did it than skipped it.

Ask about a Mission Surface ReviewHow to write a nonprofit website RFP