How to Redesign a University Website

Knowing how to redesign a university website is not the same as knowing how to redesign a corporate site.

The scale is different, the stakeholder count is different, and the governance challenge is different. Without a process built for those differences, a standard three-month timeline stretches into eighteen months.

This guide gives higher education teams a practical framework for managing stakeholders, accessibility obligations, content at scale, and the budget and timeline realities that catch most university redesigns off guard.

Key Takeaways

• Governance is the biggest challenge: University redesigns involve more internal stakeholders than almost any other site, making governance as critical as design quality.
• Multiple audiences need separate journeys: Prospective students, current students, faculty, alumni, and research partners each require distinct navigation pathways and content structures.
• Accessibility is a legal requirement: Section 508 and WCAG 2.1 AA compliance is mandatory for publicly funded institutions and must be built into the process from the start.
• Content is the longest phase: University sites often have thousands of pages maintained by distributed departments, making content strategy and migration as time-intensive as design.
• Platform choices are long-term commitments: Drupal, WordPress, and Sitecore each carry multi-year implications for maintenance costs, editorial workflows, and integration complexity.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

What Makes University Redesigns Uniquely Complex

A mid-size university site commonly holds between 4,000 and 8,000 pages across departments, faculties, research centers, and student services. That scale creates challenges that simply do not exist in commercial web projects.

For those managing a smaller institution, the university website redesign guide provides a useful companion alongside this framework. Teams at smaller colleges can also reference the community college redesign approach for a scaled-down version of the same principles.

Scale: Hundreds to Thousands of Pages

Even a mid-size university site may contain thousands of pages across faculties, research centers, and student service areas. Attempting to redesign everything simultaneously is the most common failure mode.

• Phased migration: Redesign the core university site first, then migrate faculty and department sites in subsequent phases over 12 to 18 months.
• Page inventory first: A full content audit before any design work is the only way to understand what exists, who owns it, and what can be archived.
• Template leverage: A small set of well-designed templates used consistently across hundreds of pages delivers more value than custom designs for every section.

A phased approach produces a better result than a single big-bang launch and is significantly more manageable for internal teams.

Multiple Audiences With Conflicting Needs

Prospective students want program information and campus life content. Current students need admin portals and timetables.

Research partners want publications and collaboration opportunities. Each audience needs a distinct user journey with different navigation paths and content priorities.

• Audience mapping: Define the primary audiences and their top three tasks before the sitemap is built. Navigation should serve these tasks, not institutional org charts.
• Separate navigation layers: Primary navigation serves prospective students and external audiences. Secondary navigation layers serve current students and staff with task-oriented content.
• Research audience: Research partners and funding bodies need a distinct content pathway with credibility-building depth, separate from undergraduate recruitment content.

Confusing these audience journeys is one of the primary reasons university websites produce poor user satisfaction scores despite significant investment.

Departmental Autonomy vs Brand Consistency

Faculty departments typically maintain their own content with significant autonomy.

A redesign must balance central brand standards with the legitimate need for departmental flexibility without creating a site that looks like it was designed by fifty different teams.

• Template governance: Define which template elements are fixed (brand header, footer, color palette) and which are customizable (section order, featured content, supplementary navigation).
• Style guide documentation: Produce a written and visual style guide that departments can follow when creating content within the central CMS.
• Editorial training: Post-launch editorial training for department content owners reduces brand drift in the 12 to 18 months after launch.

The design system must be rigid enough to maintain brand consistency but flexible enough that departments feel ownership of their section.

Legacy Technology and CMS Fragmentation

Many universities run fragmented technology stacks: multiple CMS platforms, student information systems, library databases, and learning management systems. Each one represents a potential integration challenge for the public website.

• Integration audit: Document every system the public website currently connects to or should connect to, including single sign-on, library search, and student portal authentication.
• CMS consolidation: Evaluate whether the redesign is an opportunity to consolidate fragmented departmental CMS instances under a single platform.
• API-first planning: For complex integrations, an API-first architecture that decouples the CMS from the front-end presentation layer reduces long-term technical debt.

Governance and Stakeholder Management

The higher education redesign guide consistently identifies governance as the variable that most distinguishes successful university redesigns from failed ones. The best-designed site still fails when stakeholder management is handled informally.

Governance must be designed with the same care as the information architecture. An underpowered steering committee produces decision paralysis; an overpowered one produces design by committee.

Establishing a Steering Committee

A steering committee with genuine decision-making authority is essential for a project this complex. It should include representatives from marketing, IT, student services, academic leadership, and communications.

• Authority, not advisory: Steering committee members must have the authority to make binding decisions on behalf of their areas, not just relay feedback to their directors.
• Meeting cadence: Monthly steering committee meetings with a structured agenda and circulated minutes keep decision-making moving at a pace that prevents project stall.
• Escalation protocol: Define upfront how disputes between steering committee members are resolved. A named executive sponsor with final decision authority prevents deadlock.

A steering committee that functions as an advisory group rather than a decision-making body is one of the most common causes of scope creep and timeline extension.

Managing Departmental Stakeholders

Departments must be involved in content planning and user research without being given veto power over central design decisions. The distinction between consultation and approval is critical.

• Consultation vs approval: Departments are consulted on content that affects them directly. Approval authority rests with the steering committee, not individual departments.
• Engagement schedule: Create a stakeholder engagement calendar that gives each major faculty or department a defined window for content review and feedback.
• Change management communications: Regular project updates prevent departments from feeling excluded and reduce the volume of late-stage objections.

The most effective stakeholder model treats departments as content owners, not design stakeholders. Their input shapes content; the design agency shapes the interface.

Phased Approval Processes for Large Sites

University redesigns benefit from phased approvals rather than a single sign-off on everything before build begins. Approve global navigation and templates first, then section by section.

• Template approval first: Get approval on the page template library before designing any individual page content. This prevents template proliferation later.
• Section-by-section review: Divide the site into sections and run approval for each section independently rather than presenting the entire site at once.
• Sign-off documentation: Every approval should be documented in writing with the approver's name and date. Verbal approvals become disputes at launch.

Communication Cadence for Long Projects

An 18-month project without structured communication produces anxiety, scope creep, and stakeholder disengagement. Communication must be designed as deliberately as the project plan.

• Monthly steering committee updates: Status report covering completed milestones, upcoming decisions, risks, and budget status.
• Quarterly town halls: Broader institutional updates that show progress to the wider university community and manage expectations.
• Project status dashboard: A live project dashboard accessible to all stakeholders that shows milestone completion, current phase, and upcoming review dates.

Accessibility and Compliance Requirements

ADA compliance in redesign is not optional for publicly funded institutions. Accessibility requirements for university websites carry real legal and reputational risk when ignored.

Building accessibility into the process from the start costs significantly less than remediating a non-compliant site after launch.

Accessibility compliance is the area where university redesigns most often fail when they treat it as a final audit rather than an ongoing design standard.

Section 508 and WCAG 2.1 AA: What Is Required

US institutions must comply with Section 508. UK institutions are subject to PSBAR (Public Sector Bodies Accessibility Regulations) and WCAG 2.1 AA.

EU institutions follow the Web Accessibility Directive. Non-compliance carries legal risk, reputational damage, and in the US, the potential for OCR complaints.

• WCAG 2.1 AA minimum: All institutions regardless of jurisdiction should target WCAG 2.1 AA as the baseline standard. It covers the most significant accessibility barriers.
• Third-party content: Accessibility obligations extend to embedded content, third-party widgets, and documents hosted on the university website.
• Procurement implications: Universities procuring redesign services must include accessibility compliance standards in the tender specification and delivery requirements.

Accessibility Testing Throughout, Not at the End

Color contrast, keyboard navigation, screen reader compatibility, and alt text must be tested at wireframe, design, and build stages. A final accessibility audit on a completed site is expensive to remediate.

• Wireframe stage: Verify heading hierarchy and keyboard navigation patterns before any visual design work begins.
• Design stage: Confirm color contrast ratios for all foreground and background combinations before the design is handed to development.
• Build stage: Run automated accessibility checks on every completed template before content population begins.

Common Accessibility Failures in University Sites

The most frequent issues in university websites are predictable and preventable. Each one is easier to fix during design than after launch.

• Inaccessible PDFs: University sites typically host thousands of PDFs. Every PDF accessible from the public website must be tagged for screen reader compatibility.
• Heading hierarchy failures: Decorative use of heading tags for visual sizing purposes breaks screen reader navigation. Headings must represent document structure.
• Missing alt text: Images without descriptive alt text fail WCAG 1.1.1. This is particularly common on research and faculty profile pages with high image volume.

Remediation vs Redesign for Accessibility

For universities with significant existing accessibility debt, the choice between full redesign with built-in compliance and a targeted remediation program requires honest assessment.

• Full redesign advantage: Building accessibility in from scratch is always cheaper than remediating a non-compliant site built without accessibility consideration.
• Remediation case: When a full redesign is three or more years away, a targeted remediation program addressing the most critical failures reduces legal risk in the interim.
• Audit first: Commission an independent accessibility audit before deciding. The audit reveals whether the issues are structural (requiring redesign) or content-level (remediable without redesign).

Content Strategy at University Scale

Content strategy for redesign at university scale is the workstream most likely to undermine a redesign timeline. Content is slower than design and development, and most institutions underestimate it significantly.

A content audit completed before design begins prevents the single most common cause of university redesign delays: pages arriving for migration without a clear purpose, owner, or update plan.

Content Audit Before Any Design Work

A full content audit cataloguing every page, its purpose, its owner, its last update date, and its performance data is essential before the sitemap is built.

For a large university, this takes four to eight weeks.

• Page inventory tool: Use Screaming Frog or SEMrush to crawl the existing site and generate a complete page list before any manual review begins.
• Decision framework: For every page, one of five decisions: keep as-is, keep with updates, merge with another page, archive, or delete. No other options.
• Owner identification: Every page that survives the audit must have a named content owner who is responsible for it after launch.

Content Governance and Ownership Model

Defining content ownership before launch is what prevents a university site from deteriorating within 18 months of the redesign. Content without owners degrades.

• Content owner registry: A spreadsheet documenting every section, its content owner, the required update frequency, and the quality review process.
• Editorial workflow: Define who can create content, who can review it, and who can publish it for each area of the site.
• Governance enforcement: Quarterly content audits in the 18 months after launch catch degradation before it becomes a problem requiring another redesign.

Consolidation and Archiving Strategies

University sites accumulate significant content redundancy over years of distributed publishing. Outdated program pages, abandoned project sites, and duplicate information are universal findings in university content audits.

• Consolidation criteria: Pages with under 100 visits per month and no unique content that does not exist elsewhere are consolidation candidates.
• Archive, do not delete: Historically significant content should be archived rather than deleted. Set archived content to noindex and establish a clear URL that makes its archived status apparent.
• Redirect plan: Every page removed or merged requires a 301 redirect to the most relevant surviving URL. Document the full redirect map before any content is removed.

Writing for Multiple University Audiences

The CMS must support distinct content modes for distinct audiences. Prospective students need emotive, outcome-focused content. Current students need utility-focused, task-oriented content. Research content needs credibility-building depth.

• Content templates by audience: Create separate content templates in the CMS that guide editors toward the appropriate tone and structure for each audience type.
• Prospective student content: Lead with outcomes, student stories, and career data. Rankings and statistics support credibility but should not dominate the narrative.
• Research content: Depth and specificity signal credibility to research partners. Do not apply the same brevity standards used for recruitment content to research pages.

Budget and Timeline Realities

The university redesign cost guide provides full benchmarks. The ranges below reflect design, build, accessibility, and content migration. They do not include ongoing platform licensing or maintenance.

Setting realistic expectations at the start of a university redesign project prevents the mid-project budget shocks that are almost universal in institutions that begin without honest cost planning.

Typical University Redesign Budgets

• Small institution under 5,000 pages: $75,000 to $150,000 covering design, accessibility-compliant build, and content migration support.
• Mid-size university: $150,000 to $400,000 covering custom design system, multi-template build, accessibility audit and remediation, and phased content migration.
• Large multi-faculty research university: $400,000 to $1,000,000 or more, depending on platform complexity, integration requirements, and the scope of departmental migrations included in Phase One.

Why University Redesigns Take Longer Than Expected

The average university redesign takes 18 to 36 months from project initiation to full site launch. Each phase takes longer than comparable commercial projects.

• Procurement delays: Public sector universities must run competitive tendering processes. From project approval to contract award typically takes three to six months.
• Content audit duration: A thorough content audit for a 5,000-page site takes six to ten weeks with a dedicated team.
• Stakeholder rounds: Each design review round involving multiple departments adds two to four weeks to the timeline due to competing schedules and review cycles.

Phased vs Big-Bang Launch Strategies

A phased launch reduces risk and delivers value earlier than a big-bang approach that holds everything back until 100% of the site is complete.

• Phase One core site: Launch the homepage, global navigation, and top-level section pages. This represents perhaps 10% of pages but 60% of traffic volume.
• Phase Two faculty sites: Migrate faculty and department sites in defined waves following Phase One, over 12 to 18 months.
• Interim redirects: Pages not yet migrated should redirect to the most relevant equivalent page on the new site during the phased migration period.

Procurement and Tendering Requirements

UK public sector universities above OJEU/Find a Tender thresholds must run competitive procurement processes. This is a significant timeline variable that agencies unfamiliar with higher education often fail to account for.

• Framework agreements: Many UK universities use pre-approved framework agreements (G-Cloud, Crown Commercial Service) that reduce procurement timeline and risk.
• ITT quality: A well-structured Invitation to Tender that includes scope detail, evaluation criteria, and required deliverables produces better agency responses and easier comparison.
• Evaluation panel: Include marketing, IT, and academic representation on the evaluation panel. A panel dominated by IT produces platform-optimized proposals. A panel dominated by marketing produces design-optimized ones.

Conclusion

A university website redesign succeeds when governance is as well-designed as the interface. The most visually accomplished site still fails if stakeholder management and content ownership remain unresolved after launch.

These foundational elements take longer to build than the design, and they matter more to the site's long-term performance.

Start with a content audit and a governance model before briefing any agency.

These two foundations determine whether the redesign is still working 18 months after launch or beginning a slow deterioration back to the state that prompted the redesign in the first place.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Understands the Complexity of Higher Education Redesigns

University redesigns require a team that understands multi-stakeholder governance, accessibility obligations, and content architecture at institutional scale. That is a fundamentally different project from a commercial website redesign.

LOW/CODE Agency is a strategic product team, not a dev shop. We bring structured discovery, accessibility-compliant builds, and large-scale content architecture to institutions that need a partner who understands how higher education works.

• Accessibility-compliant builds: Every design and build stage includes WCAG 2.1 AA testing so compliance is delivered, not audited after the fact.
• Multi-stakeholder governance: We design governance frameworks alongside the information architecture, so approval processes are planned before they are needed.
• Content audit and migration: Structured content audit methodology, ownership modeling, and phased migration planning built into every higher education project.
• Large-scale CMS architecture: Template systems and editorial workflows designed for distributed content teams across multiple faculties and departments simultaneously.
• Phased delivery planning: Realistic phased delivery roadmaps that launch high-impact pages first and migrate departments in manageable subsequent phases.
• Procurement support: We work within higher education procurement frameworks and can support institutions through ITT response and evaluation processes.
• Post-launch content governance: Content governance documentation and editorial training so the redesign investment holds its value in the years after launch.

LOW/CODE Agency has delivered over 350 digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. To explore how we can support your institution's redesign, view our university website redesign services or Start with a scoping call.