How to Redesign Your Association Website Without Losing Your Google Rankings

The most expensive website mistake an association can make isn't a bad design. It's launching a new site that breaks every link to the old one.

It happens routinely. Traffic halves overnight. Members email to say a bookmark is dead. A link in last month's newsletter goes to a 404. Six months later someone works out that the redirects were never done.

It's entirely preventable, and the prevention has to happen before launch. Here's the checklist.

---

Why it happens

Your old site has URLs like /about/committees.html. The new one has /committees. Every old address that isn't explicitly pointed at its new home returns "page not found."

That breaks:

• Google's index — the rankings you've accumulated over years are attached to specific URLs
• Members' bookmarks
• Links in old email newsletters — which members do go back to
• Links from other websites — your city, your state association, local media, brokerages
• Links inside your own documents — PDFs that reference other pages

Redirects are the fix: a rule that says "anyone asking for the old address gets sent to the new one." Done properly, nobody notices anything changed.

---

The checklist

Before you build — inventory everything

Crawl the old site and save the results. Every URL, every document, every image. Do this while the old site is still up; once it's gone, reconstructing the list is painful and incomplete.

Get your top pages from analytics. Export the last 12 months of pageviews by URL. These are the pages that must not break.

Get your top pages from Google Search Console. Which URLs currently receive search traffic, and for which queries. This is different from your analytics list and equally important.

Note every inbound link you know about — your state association, city, local media, partner organisations. These are worth telling directly about the change.

While you build — map old to new

Build a spreadsheet with two columns: old URL, new URL. Every single old URL gets a row.

Rules that help:

• One-to-one wherever possible. Old committees page → new committees page.
• If content is being merged, point the old URL at the merged page, not the homepage.
• If content is being deleted, point it at the closest relevant page or the nearest section. Don't send everything to the homepage — it's a poor experience and search engines treat it as a soft error.
• Don't forget documents. PDFs get indexed, linked and bookmarked like pages.
• Watch for chains. Old → interim → new is slower and loses value. Point directly at the final destination.

This is tedious and it is the single highest-value hour of the whole project.

At launch — verify

Test the redirects before you cut over, not after. Take your top 100 URLs and check each one lands where it should.

Submit the new sitemap in Google Search Console.

Keep the old site's analytics running so you can compare.

After launch — watch for a month

• Crawl the new site for broken internal links, missing images, and forms pointing at old addresses. Internal links are the most commonly missed item — pages linking to pages that moved.
• Check Search Console's coverage report weekly for the first month. It will tell you which URLs are erroring.
• Expect a small dip. A 10–20% fluctuation for two to four weeks while search engines re-crawl is normal. A 60% drop that doesn't recover means something is broken — usually redirects, occasionally a noindex tag left on from staging.

That last one is worth its own warning: staging sites are usually set to block search engines, and that setting has to be removed at launch. It is the most common single cause of a catastrophic post-launch traffic loss, and it's a one-line fix that nobody thinks to check.

---

Questions to ask your vendor

Whoever builds your site — us or anyone else — these answers tell you whether they've done this before:

1. Will you crawl and archive our current site before we launch?
2. Will you give us the old-URL-to-new-URL mapping to review? (You should review it. You know which pages matter.)
3. How will you verify the redirects work before cutover?
4. Will you check for broken links after launch, and fix them?
5. Who removes the search-engine blocking when we go live?

A vendor who hasn't thought about this will give vague answers. It's a fast way to sort experienced from optimistic.

---

What we do

For each launch we crawl and archive the existing site in full — every page, document and link — and build the redirect map from that inventory rather than from memory. Before cutover the mapping is reviewed against the pages that actually receive traffic. After launch we re-crawl the new site and status-check every internal link, external link and asset, then fix what's broken.

It's not the part of a website project anyone gets excited about. It's the part that determines whether your members notice the launch for the right reasons.

---

Related

• SEO basics for real estate associations
• How to choose a website vendor for your association