A web presence that had outgrown its structure.
A full crawl found 119,670 URLs across 89 subdomains — 71 of them blogs — including 36,770 redirects and 2,423 broken links. Thousands of PDFs and office documents stood in for web pages, and 105 pages competed for attention at the top level of navigation.
On the pages that mattered most, the problems were plain: 38% of priority pages read as fairly hard to very hard, local navigation didn’t match the site’s structure, and key paths dead-ended. The apply page had the lowest engagement rate of any top page, at 34%.¹
Findings from the site crawl, file crawl, and priority-page audit.
Show, don’t tell.
The experience brief reframed the site around one idea: show prospective students how they would get more out of college, rather than telling them. Six imperatives guided the work, and five perception shifts defined what the site had to change.
- i.Show, don’t tell.
- ii.Sophisticated simplification.
- iii.Clear navigation from any entry point.
- iv.Your experience, your way.
- v.Demonstrate the return on investment.
- vi.Be brave, but deliver the basics.
- Rural→Close to the metro
- Expensive→A proven return
- Exclusive→A place to belong
- A career network→A life network
- Little known→A hidden gem
Six sections instead of 105 front doors.
The new sitemap organizes 1,267 pages under six top-level sections, with every legacy URL mapped to a new home or a redirect. Hundreds of thin pages were consolidated into richer ones instead of being migrated as-is.
Pages per level in the new sitemap. The top three levels carry the navigation; deeper levels hold detail.
A kit the college’s team can actually use.
Six page templates and 22 widgets give authors a flexible kit — including an interest-based program finder and a taxonomy-driven feed that surfaces related stories, news, and events automatically. Every existing page was triaged with one question: is it web-ready?
- Foundation
- Ideation
- Mapping
- Migration
Clear roles keep a big site healthy.
A role-based model separates who can submit, write, approve, and publish. Anyone on campus can submit an event; subject-matter approvers publish within their own sections; a central team owns taxonomy, navigation, and user access.
- Events submitterAnyone with a campus login; submits, can’t publish
- Events coordinatorManages the shared calendar
- Contributor / authorDrafts and edits; can’t publish
- Contributor / tech supportTechnical help for authors
- ApproverSection subject experts; reviews and publishesPublishes
- Owner / adminCentral team; taxonomy, navigation, usersPublishes
Post-launch performance data will be added as it becomes available.