← All insights
churchNov 17, 2026By Mission Lab team

The content monster: every campus page you add is a page you'll maintain

Multi-campus churches want a unique page for every campus and ministry, and each one becomes a page someone has to keep current. Here's how to decide what really needs to be campus-specific, and what to do when pages start to drift.

Somewhere in the planning of every multi-campus church website, someone asks for each campus to have its own version of every page. It's a reasonable request. Each campus has its own people, its own rhythms and its own neighborhood, and nobody wants a guest at the smaller campus reading a description of a ministry that only exists at the larger one.

The trouble doesn't show up at launch. It shows up a year or two later, when the person who updates the website is staring at a page list several times longer than anyone planned, and half of it is out of date.

The multiplication problem

Unique pages multiply faster than people expect. Craig Van Korlaar, our UX lead, put it plainly on one project: "When you have each campus and then each campus has eight service areas, well, that's now 24 pages. Once you add another campus in five years, it just starts to balloon."

Do the same math for ministries, groups, care and next steps, and a three-campus church can end up with well over a hundred pages, many nearly identical. Each has its own photos, contacts and dates, and its own chance to fall behind.

That's the cost to keep in mind. In Craig's words, "Every unique page is then a page that has to be managed." Someone has to remember it exists, notice when it's wrong and fix it.

Who actually maintains campus pages

The usual plan is that each campus will own its own pages. It's sensible on paper and hard in practice. Campus staff have very different amounts of time and comfort with the website, and it's rarely anyone's main job. We've seen the work drift back to the central communications team again and again, often to one or two people who now maintain far more pages than they expected to.

So before you decide how many unique pages to build, ask who will update each one, by name, and how often. If the honest answer is "probably the comms office," plan the site for the comms office's capacity.

What really needs to be campus-specific

Most of what differs between campuses is information, not whole pages. A useful way to sort it:

Usually worth a unique page for each campus:

  • The campus home page. It's where a visitor lands after choosing a location, and it can rank in local search.
  • The visit page. Service times, address, parking, what Sunday is like. These are the details a first-time guest needs, and they differ by campus.
  • Kids and youth. This is where families compare campuses and decide. Photos and details should be honest about what each campus actually offers, so a parent doesn't arrive expecting the larger campus's program.

Usually better as one shared page with campus-specific sections:

  • Staff and contacts. One page layout, with the right people pulled in for each campus.
  • Events and groups. A list that filters to the campus the visitor is viewing.
  • Ministry, serve and care pages. One description written once, with the campus contact, the right sign-up form and that campus's upcoming events filled in automatically.

A shared page doesn't have to feel generic. Done well, someone browsing a campus stays inside that campus's version of the site, with its name in the header and its events on the page. Behind the scenes, though, there's one page to edit. On the most streamlined multi-campus site we've built, roughly four out of five pages work this way.

If you're still choosing your site's overall structure, start with our overview of the types of multi-site church websites. This article is about the page-by-page decisions that come after.

When unique pages are the honest choice

Shared content only works when campuses really do run a ministry the same way. Sometimes they don't. If what one campus calls a host team does something different at another campus, a shared page ends up either vague or constantly renegotiated as each campus asks for its own wording. Three honest pages are better than one compromise nobody likes.

Even then, look for a middle path. Instead of a page for every serve area at every campus, build one serve page per campus with cards for each area, a few example roles and a single sign-up button. That's three pages instead of 24, and each campus still describes its own teams in its own words.

Questions to ask before adding a page

When a ministry or campus asks for a new page, run it through a few questions:

  • Would a guest choose a campus based on this content? If yes, it may deserve a unique page.
  • Does it differ between campuses by more than names, times and links? If not, share it and fill in those details per campus.
  • Who will update it, and when will they look at it next?
  • What happens to this page when you add another campus?

Two years later: drift and consolidation

Even with good decisions at launch, unique pages drift. One campus updates its kids page after a new curriculum, another doesn't. A volunteer contact changes at one location and the old name stays up at the others. Soon the versions stop matching, and visitors can't tell which is right.

When that happens, it's time to consolidate. This is a normal part of a site growing up. At launch, nobody knows exactly how alike the campuses will turn out to be. A couple of years of running them answers that question. Some ministries prove genuinely different, and their pages should stay separate. Others turn out to differ only in a name and a meeting time, and those pages can be merged.

We've done this work on long-running multi-campus sites, and it goes best when tied to a change you're already making. Launching another campus is the classic moment. Instead of copying every page one more time for the new location, use the launch to build one page that works for all your campuses, then retire the old copies.

A simple way to start:

  1. List every campus-specific page and put each set of versions side by side.
  2. Mark the real differences. Often they're just a contact, a time and a form link.
  3. Merge the sets where the differences are just details, moving those details into campus-specific sections of one shared page.
  4. Redirect the old URLs to the new page so links in old emails, bulletins and search results still work.
  5. Leave alone the pages that really are different. The aim is fewer pages to keep current, so merge only where it helps.

You won't get a new feature out of this work. You'll get a site that's easier to keep accurate, which matters more to the guest reading it on a Saturday night.

If your campus pages have started to drift, we're glad to take a look as part of our free website review.

From the team behind ChurchPlugins

Want this kind of thinking applied to your site?

Get a free review of your current site, or see how we build for churches.