The moment a church becomes churches, the website question changes. A family searching in one town needs that location's times, that location's pastor, that location's front door, and they need it without untangling which campus a page is talking about. Networks of outreaches and church plants feel this even more sharply. Here is how to structure it so every location is findable and no location goes stale.
The big decision: one site or many
Default to one site, many location pages. One brand to maintain, one giving system, one sermon archive, and every location inherits the search reputation of the whole. The exceptions are real but rare: campuses with genuinely different names and identities, or plants intended to become independent churches. If a campus has its own name, its own leadership, and its own volunteers to maintain a site, it may deserve one. Otherwise, separate sites multiply the maintenance problem by the number of campuses, and maintenance is already the hard part.
Anatomy of a location page that works
Each location gets a full page, and the test is simple: could a first-time guest attend this campus using only this page? That requires:
- Its own service times, even if identical to the main campus. Stating them here removes all doubt.
- Full address with a tappable map, plus parking notes if arrival is not obvious.
- The campus or location pastor, name, photo, and a warm sentence. A location without a named human feels like a franchise.
- A real photo of that gathering, not the flagship's sanctuary standing in for everyone.
- Kids information for that location, because offerings genuinely differ by campus and parents plan around it.
- A direct contact, so a question about this campus does not route through a central inbox and die.
For networks of outreaches: the directory pattern
Churches with many smaller works (plants, outreaches, mission points) need a different tool: a directory page. One page, locations grouped by region, a card per work showing its name, leader, address, and a link to its Facebook page if that is where its life happens. Two honesty rules make or break it: mark unconfirmed details ("established: coming soon") instead of guessing, and never publish a leader's personal phone number; link the outreach's page instead. Done well, the directory does quiet, powerful work: it honors every small gathering equally, helps a mover find the nearest one, and shows any visitor the true scale of what God is doing through one church. (We productized this exact pattern as our Outreach Directory module after building a 40-community directory, so we can confirm: the hard part is not the page, it is gathering the data. Start collecting names, addresses, and pages now.)
Getting every location found in its own town
Each physical campus can and should have its own Google Business Profile, linked not to your homepage but to that campus's page. That is the difference between campus two appearing on the map in its own neighborhood versus being invisible behind the flagship. Keep each profile's name consistent ("Grace Church - Northside Campus"), enter that location's actual hours, and add photos of that building. Our local SEO guide covers the profile details; multiply by your number of doors.
The multi-site trap: multiplied staleness
One website going out of date is a problem. Five location pages going out of date is five problems wearing one brand. The fix is structural, not motivational: one named owner for location-page accuracy (per campus or central), a monthly two-minute review of each page (times, pastor, kids info still true?), and a standing rule that any campus change (new service time, new pastor) triggers a website update the same week. If nobody owns it, the flagship page stays fresh and every other location quietly rots, which tells guests exactly which campuses matter. This is the multi-site version of the pattern in why church websites go stale, and it deserves the same honest answer about who does the work.