Good municipal website design starts from what residents and visitors come to do, such as pay a bill, find trash day, get a beach sticker or check meeting times, and makes each of those tasks findable in a few taps on a phone. Department org charts, mayor's welcome letters and news archives come second.
Town and city websites are hard. They serve residents, businesses, visitors, job seekers and the press. Content comes from a dozen departments, each with its own priorities and its own idea of what belongs on the homepage. Budgets are small, redesigns come once a decade, and the federal accessibility rule now sets a hard deadline. This guide covers the design principles that matter most, for clerks, IT directors, communications staff and town managers planning a redesign or just trying to improve what they have.
Start with tasks, not departments
Most government websites are organized like the government: a menu of departments, each with its own pages. Residents don't think that way. They think "I need to renew my dog license", not "that's probably the Clerk's office".
Find your top tasks. Look at your site search logs, your analytics, the calls the front counter gets and the emails departments answer. For most towns the top tasks are a short list:
- Pay a bill: taxes, water, sewer, parking tickets
- Trash, recycling and transfer station schedules
- Permits and licenses: what's needed and where to apply
- Meetings, agendas and minutes
- Parks, beaches, recreation programs and facility rentals
- Report a problem, such as a pothole or a streetlight
- Contact a department, with hours
- Jobs
- Events and community news
Put them on the homepage. A short "I want to…" or "How do I…" list of the top 8 to 12 tasks, in plain words, is the single most useful element on a municipal homepage.
Keep departments, but second. A department directory is still needed for people who know where they're going, and for staff.
Make search work
Many residents skip the menus and search. Test your site search with the 20 questions the front counter hears most. If "trash day" returns a 2017 press release, the search needs tuning, better page titles, or a few pages written to answer those questions directly.
Write in plain language
Government pages are often written for the people who wrote the bylaw. Write for the person asking:
- Put the answer first: "Resident beach stickers cost $40 and are sold at the Recreation Office, Monday to Friday, 8:30 to 4:30."
- Use headings that match questions: "Who needs a permit?", "How much does it cost?", "Where do I apply?"
- Replace PDFs with web pages where you can. PDFs are hard to read on phones and often inaccessible.
- Date seasonal content, and take last season's notices down.
Plainlanguage.gov has practical federal guidance that works just as well for towns.
Design for phones first
Most residents will visit on a phone, often in a hurry. That means:
- Large tap targets and short menus
- Fast pages with compressed images
- Phone numbers that tap to call and addresses that open maps
- No tables or PDFs for information people need on the go, such as hours
Accessibility is now a deadline
Under the Department of Justice's ADA Title II rule, state and local government web content, including content and tools provided by vendors, must meet WCAG 2.1 Level AA. The first compliance dates for larger governments arrive in 2027. Our post on ADA Title II and website chatbots covers the dates and what to ask vendors.
In practice, a redesign should include:
- Sufficient color contrast and readable text sizes
- Alt text for meaningful images
- Captions for video and accessible meeting recordings
- Forms and menus that work with a keyboard and screen readers
- Accessible versions of documents residents need, not scanned PDFs
- A way to report an accessibility problem
Build accessibility checks into the content workflow, not just the launch. Most accessibility problems on government sites come from new content added after the redesign.
Serve residents in their language
Millions of US residents speak a language other than English at home; the Census Bureau counted 67.8 million in 2022. A translation widget helps, but the most important pages, such as emergencies, taxes, trash and voting, deserve reviewed translations. An AI assistant that answers in the language a resident asks in can cover the long tail of questions.
Keep it current with a content owner in each department
A website goes stale one department at a time. Name a content owner in each department, give them a short checklist, and set a simple review calendar: seasonal pages before each season, everything else at least once a year. A web coordinator can then focus on structure and quality instead of chasing updates.
Answer questions when the counter is closed
Even a well-designed site leaves residents with questions, and many arrive when town hall is closed. A municipal chatbot on the website can answer from the pages your departments publish, in a sentence, with a link to the source page. It can point residents to the right form or office for permits and payments rather than handling them itself, and it should say when it isn't sure instead of guessing.
A useful side effect: the questions it couldn't answer become a list of what the website is missing.
A municipal website redesign checklist
- List your top 10 resident tasks from search logs, analytics and front-counter calls.
- Put those tasks on the homepage in plain words.
- Test site search with the top 20 questions.
- Rewrite the top 25 pages in plain language, answer first.
- Replace PDFs residents need with web pages.
- Check color contrast, alt text, captions and keyboard navigation.
- Translate the most important pages.
- Name a content owner in each department and set a review calendar.
- Decide how residents get answers after hours.
- Measure: top searches, top questions and pages with high exit rates, reviewed monthly.
For examples of what good looks like, see our roundup of the best city government websites.
Where VisitorDesk.ai fits
VisitorDesk.ai is a city and town chatbot for local government. It sits on your existing website with one line of code, answers residents' and visitors' questions 24/7 from the pages your departments publish, links to the source, and sends anything it can't answer to staff for review. A monthly report shows what people asked and which answers your website is missing. It does not process permits, payments or records requests, and it doesn't connect to town systems.
See VisitorDesk.ai for local government or view pricing.
