CivAll
Blog

How to Migrate a Government Website Without Losing Accessibility or SEO

Dino JukloDino Juklo
•
Illustration of an outdated, faded government website on the left flowing through teal arrows into a modern, colorful website on the right, with a building photo and three content cards.

To migrate a government website without losing accessibility or SEO, inventory and audit your content first, map every old URL to a new one with 301 redirects, carry accessible structure into the new templates, and test in staging before launch. Then monitor search performance and broken links for at least 90 days.

A government website can have a large library of pages and many contributors across departments. A migration is the best chance you’ll get to fix accessibility problems, and also the easiest moment to break the URLs that residents, bookmarks, and search engines depend on. This website migration checklist walks through five steps, so your team can move with confidence and your service pages stay easy to find. CivAll empowers your team to catch and fix all accessibility issues during the migration process.

Why Do Website Migrations Put Accessibility and Search Rankings at Risk?

Because a migration changes the things both depend on. Old URLs vanish without redirects, page titles and headings reset, and alt text and table headers get dropped during content import. New templates can introduce fresh barriers, and settings meant for staging sometimes carry into production, such as a block that keeps search engines out.

The stakes are real for a government site. Service pages for permits, payments, and records often hold years of accumulated search authority, plus inbound links from other government and community sites. Lose the URL and you lose that history, and residents land on an error page when they needed a form. The good news is that nearly all of these failures are preventable with planning.

Step 1: Inventory Your Content and Set a Baseline

Start by knowing what you have. Crawl the current site and export every URL with its page title and traffic. Flag your high-value pages, such as permits, payments, forms, and emergency information. These get the most careful handling.

Next, record your baseline. Pull current search traffic and rankings from your analytics and search console, so you can compare after launch instead of guessing. Run a baseline accessibility scan too, so your team knows what you’re fixing versus what you might accidentally break. Our guide to auditing a government website for accessibility covers a full audit, including the manual testing a scan can’t replace.

A baseline turns the post-launch conversation from “traffic seems down” into a clear before-and-after.

Step 2: Decide What Moves, What Merges, and What Retires

Sort every page into one of four groups: keep, rewrite, merge, or retire. Cutting redundant and outdated department pages improves usability and gives search engines a clearer picture of your site. It also leaves less content to keep accessible.

Retired pages that have inbound links still need a redirect. And before you retire anything, check your state’s records retention requirements, since public records rules are set at the state level and can affect what you’re allowed to remove.

Before you decommission the old site, capture a complete, dated copy of it. Web content can be a public record, and once the old platform is gone, so is your ability to show what residents saw on a given date. Confirm with your records manager how long that copy needs to be kept.

If your government plans to rely on the Title II archived web content exception, keep in mind that archived material should be clearly set apart and left unaltered. Confirm how the exception applies to your situation with counsel.

Step 3: How Do You Map URLs and Plan Redirects?

Build a URL map that pairs every old URL with its best new equivalent, then redirect each one with a 301. Start with a spreadsheet and send each page to the most relevant new page, never everything to the home page.

Include PDFs and documents in the map, since they often hold backlinks and search traffic. Keep URL structures where they make sense, and carry over page titles, meta descriptions, and canonical tags. Update your XML sitemap and your internal links so they point to the new URLs directly.

Google’s site move guidance recommends pointing each old URL straight to its final destination and keeping redirects live for at least a year. Share it with whoever will set up your redirects, so the plan follows Google’s recommendations from the start.

If your domain is changing, such as a move to a .gov domain, verify both domains in Search Console and use its Change of Address tool.

Step 4: How Do You Carry Accessibility Into the New Site?

Start from accessible templates: a logical heading hierarchy, landmarks, skip links, visible focus, and sufficient contrast. Then confirm that the content import keeps alt text, table headers, descriptive link text, and captions. Check forms, calendars, and embedded third-party tools, since those often break first.

Fix documents during the migration instead of copying old problems forward. CivAll Documents automates PDF accessibility, so legacy documents can be fixed as they move instead of one at a time. Assign a content owner in each department and train them, so new pages stay accessible after launch. With CivAll Sites, accessibility checks run as contributors edit, so issues surface before a page goes live.

Timing helps here too. Under the DOJ’s extended Title II web rule, governments serving 50,000 or more residents have until April 26, 2027, and smaller governments and special districts have until April 26, 2028. Be prepared with accessible pages now instead of waiting until a resident reports an issue.

Step 5: How Do You Test in Staging and Launch Safely?

Keep staging out of search indexes, and remember to remove noindex tags and robots blocks at launch, which is a classic mistake. Crawl staging to verify redirects and find broken links. Run keyboard and screen reader checks on your most important resident journeys, such as paying a bill or finding a permit form, using the W3C’s evaluation resources as a guide.

Choose a launch window away from budget season, filing deadlines, or major meetings. Submit the new sitemap and brief every department before launch day, so no one’s surprised by a changed page.

Pre-launch checklist:

  • Every old URL is mapped to a new URL, including PDFs and documents
  • 301 redirects are tested in staging, with no chains or loops
  • Titles, meta descriptions, and canonical tags are carried over
  • Staging blocks and noindex tags are removed from production
  • Alt text, headings, table headers, and link text are verified after import
  • All documents and pages pass WCAG 2.1 AA guidelines and ready for residents using screen readers
  • A complete, dated copy of the old site is captured, and its retention period is confirmed with your records manager
  • The new XML sitemap is ready to submit
  • Departments are briefed, and one owner is named for post-launch issues

What Should You Monitor for the First 90 Days?

Watch search console errors, 404 reports, and traffic against your baseline. Expect some short-term fluctuation, and fix broken links quickly when they appear. Check for accessibility regressions as departments add content, and route resident feedback to a single owner so nothing gets lost.

Keep monitoring beyond 90 days if you can. Your redirects will be doing quiet work for a year or more.

Frequently Asked Questions

Will changing URLs hurt SEO?

Not if every old URL is mapped to the most relevant new page with a 301 redirect. Unmapped URLs are what cause lost traffic and error pages.

How long should redirects stay in place?

At least a year, and longer for URLs with strong inbound links or printed materials.

Do we need to test accessibility again after migrating?

Yes. Future edits may introduce new issues, so you will need a way to check for compliance before publishing new content.

Do we need to keep a copy of our old website?

Yes, in most cases. Web content can be a public record, and once the old platform is shut down, you lose the ability to show what residents saw on a given date. Before you decommission the old site, capture a complete, dated copy and confirm with your records manager how long it needs to be kept under your state’s retention requirements.

How long does a government website migration take?

It depends on content volume and the number of contributors. CivAll implementation typically takes a few months, and we provide a written scope and timeline before you sign.

Protect Both, One Step at a Time

A government can protect both accessibility and search visibility when the migration is planned as a sequence instead of a launch date. Consolidating the website, social publishing, and archiving on one platform also cuts the number of systems to migrate in the future. See how CivAll Sites supports an accessible migration.

Related Resources

Ready to see CivAll in action?

Schedule a personalized demo and see how CivAll can transform civic engagement for your community.