A new church website is exciting for about three days. Then Sunday afternoon arrives and someone forwards a two-year-old sermon link from Facebook to their brother-in-law, and the page is gone. Then the giving link on a printed connect card sends people to a 404. Then Google quietly starts serving competitors for a search that used to bring your church to the top of the page.
Nine times out of ten, the redesign was beautiful and the launch was on time. The one thing that never made it onto the launch checklist was a redirect map. It is the least glamorous part of a website relaunch and, next to hosting itself, the part that most quietly decides whether the new site keeps the trust and traffic the old one built.
What a Redirect Map Actually Is
A redirect map is a plain spreadsheet with two columns. The old URL on the left. The new URL on the right. That is it.
For every meaningful page on your old site, the map tells the server where to send someone who taps the old link. When it is in place, an old bookmark, an old Facebook share, an old Google result, and an old printed QR code all quietly land on the right page of the new site. When it is missing, they all land on a 404, and the visitor almost never tries again.
The server carries out the mapping through what is called a 301 redirect, which is a signal to browsers and search engines that the page moved permanently. Google reads that signal and transfers most of the search authority the old page earned to the new one. A 302, which most tools default to, tells Google the move is temporary — and Google keeps waiting for the old page to come back, which it never will.
What to Actually Catch
Before you touch the new site, spend an hour making the list. Three sources cover almost everything.
Your top pages in Google Search Console. Export the last twelve months of pages by clicks. The top forty or fifty URLs are usually eighty percent of the traffic worth protecting. Sermon archives, "plan your visit," giving, staff pages, and specific event landing pages tend to dominate.
Your top pages in Google Analytics. Same idea, different angle. GA will surface pages that get traffic from Facebook and email but not from search, which Search Console misses. Sermon detail pages and event pages especially.
Your sitemap.xml. If your old CMS generated one, it is the closest thing to a complete list of what exists. Download it, and you have the universe of URLs you might need to map.
Cross-reference the three lists and you will have a couple hundred URLs at most for a typical church site. Not all of them need one-to-one redirects. Most old blog and news posts can point to a category page or the homepage. But every sermon URL, every ministry page, every giving link, and every event page that has been shared publicly deserves its own row.
The Mechanics Most Churches Miss
A few practical notes from redesigns we have handled.
Sermon archives are the highest-stakes migration. A sermon shared four years ago on someone's timeline is still winning souls quietly today. Losing those URLs is not just SEO damage — it is severing a piece of the church's public witness. If your old sermon URLs looked like /sermons/2023/07/16/hope-in-the-storm and the new ones look like /messages/hope-in-the-storm, every one of them needs a redirect row.
Giving pages get printed on paper. Bulletins, connect cards, tote bags, the back of business cards. If the old giving URL is /give and the new one is /donate, redirect /give even if you also promote the new URL going forward. Paper does not update.
Watch for trailing slashes and capitalization. /Sermons/ and /sermons are two different URLs to a web server, and Google indexes them separately. Pick one style on the new site and redirect the other to it.
Do the redirects at the hosting or CDN level, not through a WordPress plugin. Plugin-based redirects run inside the CMS, so they are slower and, more importantly, break the moment someone deactivates the plugin during maintenance. Netlify, Vercel, Cloudflare, and most modern hosts all support a simple redirects file that the edge network handles before the CMS ever wakes up.
The Two-Week Grace Period
The week you launch, keep the old site live on a subdomain like old.yourchurch.org. Nobody should link to it publicly, but you will use it constantly. When something breaks, you can compare old versus new side by side. And if a broken redirect surfaces, you can pull the original URL, verify the content, and add the row to your map without guessing.
For the two weeks after launch, monitor 404s daily. Google Search Console will report them, and your hosting dashboard usually will too. Every 404 that gets traffic is a missing row in your redirect map. Add it. By day fourteen, the file goes quiet, and you can move on with confidence.
A Small Act of Stewardship
Every URL your church has ever earned is a small deposit of trust — a person who read something and cared enough to share it, print it, or bookmark it. A redirect map is how you honor those deposits when you rebuild. It is unglamorous, it does not show up in any launch announcement, and the people whose bookmarks still work will never know you did it.
That is what makes it hospitality.
If your church is planning a website relaunch this fall and no one has yet asked about a redirect map, we would be glad to help you build one before the new site goes live.