Key takeaways

  • A municipal website is a service counter that never closes: agendas, minutes, permits, payments, and notices should be findable in two clicks.
  • Accessibility is not optional for local government sites, so plan for ADA and WCAG conformance from the start.
  • Residents search Google first, which means clear page titles and plain-language content decide whether they find your hall or call it.
  • Wisconsin towns and villages can get a professional, secure site without big-city agency pricing.

What should a Wisconsin municipal website do for residents?

A municipal website should let residents finish common tasks without a phone call: find meeting agendas and minutes, pay a bill, apply for a permit, report an issue, and check garbage, recycling, or snow routes. When the website handles the routine questions, staff time goes to the work that actually needs a person.

That standard applies to every size of government, from a township of a few hundred people to a county seat. The Town of Chilton website we built is a working example: services, notices, and contacts organized around what residents look for, not around departments.

What pages does a town or village website need?

Most Wisconsin municipal sites need the same core set: government (board, committees, staff), agendas and minutes, ordinances and policies, permits and licenses, public works and utilities, elections, parks, news and notices, and a contact page with office hours. Beyond the core, add what your community actually uses.

  • An emergency or alert banner the clerk can turn on in seconds
  • A public notices page that satisfies posting requirements
  • A calendar for meetings and community events
  • Forms residents can submit online instead of printing

Why does accessibility matter so much for local government?

Government services must be usable by everyone, including residents who rely on screen readers, keyboard navigation, or captions. Public entities are covered by the Americans with Disabilities Act, and the Department of Justice has published a web accessibility rule for state and local governments based on WCAG 2.1. Building to that standard from day one costs far less than fixing a site after a complaint.

We cover the details in our plain-English guide to ADA-compliant municipal websites, but the short version is: readable contrast, keyboard-friendly menus, labeled forms, alt text, and documents that are not scanned images.

How should a municipality handle agendas, minutes, and notices?

Post them as accessible pages or tagged PDFs, in one predictable place, with the newest items first and an archive by year. Residents and reporters should never have to guess where this week’s agenda lives. A consistent posting routine also builds a public record you can point to when questions come up.

Who updates the website after launch?

Your clerk or staff should be able to post a notice, update hours, or add an agenda without calling a developer. We build municipal sites on WordPress with an editor staff can learn in an afternoon, and we stay on call for the changes you would rather hand off. Hosting, backups, security updates, and support come from the same Wisconsin-based team that built the site.

How should a municipal site be organized so residents find things?

Organize by task, not by org chart. Residents think pay my water bill, reserve a shelter, when is my recycling day; they do not think Department of Administration. Group the homepage around the ten most common tasks, keep a full A to Z services index for everything else, and put a working search box in the header. Test the structure by asking someone outside the office to find three things; if they hesitate, rename the menus in plainer words.

  • Homepage: top tasks, alerts, next meeting, contact hours
  • One predictable home for agendas, minutes, and notices
  • An A to Z index so nothing depends on guessing a department
  • Search that actually searches documents as well as pages

What security does a government website need?

Local government sites are routine targets, so the basics are not optional: SSL on every page, a hosting stack that gets security updates on a schedule, offsite backups tested by restoring them, limited admin accounts with strong authentication, and a plan for who to call when something looks wrong. Our managed hosting handles updates, monitoring, and backups for the municipal sites we build, so a clerk never has to think about server patches. Ask any vendor who is responsible for security updates by name; if the answer is vague, the risk is yours.

Frequently asked questions

How long does a municipal website project take?

Most town and village sites launch in four to eight weeks, depending on how much content needs to be gathered, rewritten, and organized. Migrating years of minutes and agendas adds time, and we plan that with you up front.

Can residents pay bills or fees through the site?

Yes. We connect your site to the payment provider your municipality already uses, or help you choose one, so utility payments, permits, and licenses can be handled online.

Do you work with small townships or only cities?

We build for townships, villages, cities, sanitary districts, and county departments across Wisconsin. The structure scales down as well as up.

Is the website hosted in the United States?

Yes. Hosting is PCI-compliant, American-based cloud infrastructure with backups, monitoring, and updates handled for you.

Bring your municipal website up to what residents expect

Fox Valley Web Design builds and supports government and community websites across Wisconsin, from design and development to hosting, photography, and ongoing updates. Request a quote and we will walk your board through a clear, flat-rate proposal.