Higher Education Websites. Governance at campus scale.

A university site is not one website. It is hundreds of publishers, thousands of pages, an admissions funnel that carries real revenue, and program content that goes stale the moment a department stops looking at it. We build the system that holds all of that together.

We grow your business with

CROturn traffic into leads

SEOrank & get found

GEOwin generative search

AEOget cited by AI answers

The problem

Scale is the whole problem

Every campus web team is outnumbered. A hundred or more people can publish, most of them have another job, and none of them were hired to think about heading structure or alt text. The result is a site that is inconsistent, partly inaccessible, and full of program pages nobody has read in three years.

You cannot solve that with a redesign alone. It takes a component system that makes the accessible option the easy option, a content model that gives program and course data one source, and a governance policy that says who owns what — which is why we treat governance as part of the build rather than a document delivered afterwards.

Scope

Where the work usually goes

Admissions funnels

The path from a program search to an enquiry or application, designed and measured as a funnel rather than a set of pages.

Program and course pages

Structured program data with one source, so a change to a credential requirement does not need editing in nine places.

Governance for many publishers

Roles, components and review workflows that keep quality up without routing every edit through the central team.

Accessibility at scale

A component library where accessibility is inherited rather than re-implemented per department — see Section 508 compliance for federally funded obligations.

🔬

Faculty and research profiles

Directories and research output that stay current and are actually findable by prospective students and press.

Portals and custom systems

Where a portal sits behind the site, our education software development work covers the application side.

Non-negotiables

What we build in

✓

A component system where the accessible option is the default option

✓

Program and course data with a single source of truth

✓

WCAG 2.2 AA accessibility inherited by every department site

✓

Editorial governance defined during the build, not documented afterwards

✓

Migration that preserves program, faculty and news URLs at scale

✓

Answer-engine accuracy for admissions facts — deadlines, tuition, eligibility

✓

A written handover the central web team can actually operate from

Questions

Campus questions

How is this different from your university web design page?

University web design covers the build itself. This page is about doing it at scale — governance, program data and accessibility across many publishers. Most campuses need both conversations.

Can you work with our existing CMS?

Often, yes. Tell us the platform and its constraints. A governance and component problem is frequently solvable without replacing the CMS, and we will say so if that is the case.

Do you work with community and career colleges?

Yes — see college web design. The governance problem is smaller but the admissions funnel matters just as much.