It designs for a decision that several different people make together, under public scrutiny, with accessibility as a legal requirement instead of a preference. Very few sectors carry all three at once, and each one changes the work.

Four differences that matter.

Nobody decides alone. A student shortlists, a parent evaluates cost and safety, a guidance counsellor recommends, and in higher education faculty and administrators shape what gets said. Four audiences, four sets of questions, one website. Designing for the student alone is the most common mistake we inherit.

The commitment cannot be sampled. Whether it is four years or four weeks, a learner is buying an outcome on the strength of an impression. That puts unusual weight on how credible the institution looks and reads before any claim gets examined.

Everything is public. Institutions are accountable to boards, ministries, accreditors, parents, alumni, and local media. Claims have to be defensible, tone has to survive being quoted, and a page that overpromises becomes somebody's problem at a board meeting. Publicly funded institutions also sit under access to information law, which means a member of the public can request the records behind a claim, and that is the practical reason to keep the evidence for an employment or outcomes figure filed alongside the figure itself.

Accessibility is not optional here. AODA in Ontario, ADA obligations in the United States, and WCAG as the standard being assessed against. For public institutions this is a compliance question with dates attached, which is covered further down.

So Brand Vision's education marketing services cover education branding and the position underneath it, a website organized around what each visitor arrived to do, search visibility at the moments a learner is still deciding, and the channels the recruitment cycle actually needs.

On whether we know this sector, the client list is the honest answer. McGill University, the Toronto District School Board, the University of Toronto, and the University of Chicago, among more than 50 collaborations with educational institutions across a decade. That range matters, because a school board and a research university have almost nothing in common operationally and we have worked inside both.

By building a route for each audience from the first screen, and by testing the labels instead of trusting them. Education sites fail at this more consistently than any other sector, because the internal vocabulary is unusually strong and the people writing the site have used it for years.

The failure looks the same everywhere. Navigation reads Academics, Admissions, Student Life, About, and Resources. A parent looking for tuition and financial aid does not know whether that is Admissions or Resources. A prospective student wanting to know what they would actually study does not know whether that is Academics or Programs. Both start guessing, and guessing is where people leave.

What we do instead.

Route by intention. Explore programs, apply, costs and funding, visit us, current students, faculty and staff. Named for what the person came to do, in their words.

Separate prospective from current. These two groups want almost nothing in common, and mixing them produces a homepage serving neither. Current students need the portal, dates, and services. Prospective students need reasons to choose you. One site, two clearly different doors.

Test the language with real people. Research including card sorting and short task walkthroughs shows exactly where institutional wording breaks down. Program names approved by a committee usually need a plain-language line underneath, and that is not a criticism of the name.

Give parents an honest path. Cost, financial aid and bursaries, safety, outcomes, and how to have a conversation with a human. In K-12 and independent schools the parent is frequently the actual decision-maker, and many school sites treat them as a secondary audience.

Do not make anyone learn the org chart. Nobody outside the institution knows the difference between a faculty, a school, a department, and a centre, and they should not have to.

That separation is mostly an information architecture decision, and the interface work then makes each of those routes short. Education UI/UX design here means building for a wide range of confidence with technology, because the same page serves a seventeen-year-old and a grandparent paying the deposit.

With subtraction, because the problem is almost never missing content. It is that everything ever published is still live and competing with itself. Education websites grow instead of getting designed, and after a decade the structure reflects the history of the institution instead of the needs of a visitor.

How we approach it.

1. Inventory everything and find out what earns its place. Every page against its traffic, its search performance, and its last meaningful update. On a typical institutional site a large share of pages have not been touched in years and receive almost no visits, and they are actively harming the pages that matter by diluting the structure.
2. Decide keep, merge, rewrite, or retire, page by page. Retiring content is the part institutions resist and the part that produces the biggest improvement. Nothing gets deleted without a redirect plan, since old URLs on an education site carry years of accumulated links from schools, associations, and news coverage.
3. Fix program findability first. This is the single highest-value repair on nearly every education site. Learners search by what they want to study and by outcome, not by the department that happens to own it. A real program finder, filterable by subject, level, delivery mode, start date, and length, with each program as its own properly built page, changes enquiry volume more than any campaign.
4. Rebuild around tasks instead of departments, which is where the audit findings turn into a structure.
5. Put governance in place before relaunch, so the site does not return to the same state in three years. That part is the next question.

On whether this needs a full rebuild, sometimes it does not. A significant share of institutional sites we review need the program section rebuilt, the navigation reorganized, and several hundred pages retired, which is meaningfully cheaper than replacing everything. Where the platform itself is the constraint, that becomes a redesign conversation, and we will tell you honestly which of the two you are looking at instead of quoting the larger one by default. Either way the outcome is a university website design, or a school website design, that a small central team can actually maintain. That is what the build has to deliver here.

With a system that gives departments real autonomy inside limits they cannot break, because the alternative is either a bottleneck nobody accepts or a site that stops being one institution. Decentralized web ownership is the defining structural problem in higher education marketing and it is a governance problem long before it is a design one.

What usually exists by the time we arrive. Dozens or hundreds of subdomains and microsites. Several content systems running at once. Faculties and departments with their own budgets, their own agencies, and a reasonable belief that they know their audience better than central marketing does. Three generations of visual identity live simultaneously. And a central team held responsible for a site they do not control.

What we build.

A component library instead of a blank canvas. Defined blocks with defined rules, so a department can build a page that looks right without a designer and cannot build one that looks wrong.

Templates for the page types that repeat. Program, faculty profile, research centre, news, event, and landing page. Consistency where consistency matters and latitude where it does not.

An identity system with explicit permissions. What a faculty can change, what it cannot, and where sub-brands are genuinely allowed. Most institutional identity chaos comes from guidelines that never said what was permitted, only what was ideal.

Written governance. Who publishes, what needs review, how a new pattern gets requested, and who decides. Unwritten governance is no governance.

A migration path off the microsites, sequenced and negotiated instead of mandated, because a policy that departments have not agreed to gets ignored.

At scale this is the same discipline as large-site search and content management, and it is worth saying that the technical part is the easy half. The harder half is bringing faculty and department stakeholders along, which we plan for from the start with working sessions instead of a launch announcement. Where the brand itself needs to flex across faculties, the architecture for that gets decided at the beginning.

There are real dates attached, and for public institutions in the United States one of them has already passed. This is the most time-sensitive item on this page and the one institutions most often discover late.

In the United States. Under Title II of the Americans with Disabilities Act, a Department of Justice rule requires web content and mobile apps of state and local government entities to conform to WCAG 2.1 Level AA. Public school districts, public colleges, and public universities are covered. Larger entities, meaning those serving populations of fifty thousand or more, along with special district governments, had a compliance date of April 2026, which has now passed. Smaller entities have until April 2027. Federal agencies and their contractors sit under Section 508, and institutions procuring educational technology increasingly require a conformance report from vendors.

In Ontario. AODA requires public-facing websites to meet WCAG 2.0 Level AA for organizations above a staff threshold, with limited exceptions such as live captioning. School boards, universities, and colleges also carry obligations under the information and communications standards regarding accessible educational materials and training.

Private institutions. Independent schools, private career colleges, and training providers frequently sit outside the specific public-entity rules while remaining subject to broader duties not to discriminate, and to provincial accessibility legislation where it applies. Complaints in this sector are common regardless of which rule applies.

What compliance actually involves on an education site. Keyboard access through every interactive element including application forms and program finders. Real contrast, which is where campus photography overlays usually fail. Accurate captions and transcripts on video, which matters more here than almost anywhere given how much education content is video. Alt text that describes purpose. Correct heading structure and semantic markup. Accessible PDFs, which is the item institutions underestimate most, since course calendars, viewbooks, and policy documents are frequently untagged scans. Forms with proper labels and useful error messages. And an accessibility statement with a feedback route.

Standards are treated as requirements from day one in everything we build instead of as an enhancement traded away when a launch date tightens, and the same applies to the design work itself. To be clear about scope, we build and document to a defensible standard and the legal read belongs with your counsel. If you want to know where you currently stand before deciding anything, start there.

By competing where the aggregators are generic and you are specific, which means programs, questions, and place instead of category terms. You will not outrank a national rankings site for a broad subject query and you do not need to.

Where the opportunity actually sits.

Program-level searches. A named subject, at a named level, in a named city or delivery mode. Directories list programs. They cannot tell somebody what the second year is actually like, who teaches it, what the placement arrangement is, or what graduates went on to do. Every program page written properly is a competitive asset, and most institutions have hundreds sitting empty.

Decision-stage questions. What can I do with this degree, do I need this prerequisite, what is the difference between these two credentials, can I study part time, what does it cost in total. These are the searches happening while somebody is still deciding what to study, which is earlier and more winnable than where to study.

Comparison searches. Institution against institution, credential against credential, and college against university. Rankings sites and forums currently own these. An honest, well-made comparison page written by the institution performs surprisingly well and almost nobody attempts it.

Local and commuter intent. Programs near a place, evening and weekend delivery, and transit-adjacent searches. Genuine local search territory that campus marketing usually ignores.

Continuing education and micro-credentials. Adult learners search very differently from school leavers, with far more outcome and cost intent, and these programs are often the least marketed and the fastest to fill.

Two technical notes specific to this sector. Program pages generated from a database need to be genuinely indexable and not assembled by script after load. And course calendars locked inside PDFs are invisible to search, which is a large amount of an institution's best content sitting where nobody can find it. The content side is where the sector has the biggest untapped advantage, because institutions hold real expertise and publish almost none of it in a findable form. How all of it fits together sits inside our search practice.

They are, and it matters more in education than in most sectors, because choosing a program is exactly the kind of multi-condition question these tools handle well. A learner asks for a two-year diploma in a named field, in a named city, with a co-op placement, that accepts a specific set of prerequisites. The answer is assembled from sources, and if your program is not in those sources it does not exist in the conversation.

What determines whether you appear.

Program facts stated as text on a page. Length, credential, delivery mode, start dates, prerequisites, tuition, placement or co-op arrangements, and accreditation. Stated plainly, in words, on the program page. Locked inside a PDF calendar, a table image, or a filter widget, none of it can be read.

Consistent naming. Institutions describe the same program three different ways across the website, the calendar, and the application system, and they use internal credential language nobody outside recognizes. That ambiguity is exactly what gets a program left out of an answer.

Entity clarity. The institution, its faculties and schools, its campuses, and the programs each one runs, described consistently everywhere they appear including third-party listings.

Structured data that agrees with the prose. Credential, length, delivery mode, start dates, and tuition tagged in the structured markup these systems read directly, and written out in words on the same page, so the two versions never contradict each other. Where the student information system holds the truth, that record should be what publishes the page, and not a copy somebody updates by hand each August.

Third-party corroboration. Directories, government program listings, accreditation bodies, and news coverage. These systems weigh what independent sources say, which makes earned coverage a recruitment input.

Answers to the questions learners actually ask, written as a clear question with the answer directly underneath. A program page that opens with two paragraphs of institutional history before saying the length and the cost loses to one that answers first.

There is a defensive reason to care as well. When an AI tool describes your program from outdated calendar data or a third-party directory that has your tuition wrong, the correction is publishing better structured information yourself. That is early work in any AI search engagement, and for institutions it is usually the cheapest visibility gain available.

More carefully than on a commercial site, because the audience includes minors and the institution holds obligations that a retailer does not. This gets raised late in most education projects and it is far cheaper to design for at the start.

What is in play, depending on where you sit.

Student record privacy. In the United States, FERPA governs education records and shapes what can appear publicly and what a portal can expose. In Ontario, school boards sit under municipal freedom of information legislation and universities and colleges under the provincial equivalent, both of which carry access and privacy duties. Private institutions generally fall under federal or provincial private-sector privacy law.

Children's privacy. In the United States, COPPA governs online services directed at children under thirteen and requires verifiable parental consent for collecting personal information. For K-12 sites and anything a young student uses directly, this changes what tracking and what forms are acceptable.

Third-party tracking on pages minors visit. This is the practical issue nobody plans for. Advertising pixels on program pages, application funnels, and student-facing content can create exposure and reputational risk, and remarketing audiences built from those pages are worth thinking about carefully. We map which pages carry which tracking and recommend where it should come off, which occasionally means giving up a retargeting audience.

Forms and data minimization. Enquiry forms that collect only what is needed, clear statements of what happens to the information, and retention rules that somebody actually owns.

Consent and cookie handling that works properly instead of a banner that sets everything before anyone clicks.

Vendor review. Chat tools, video platforms, tour software, and analytics all process data on your behalf, and institutional procurement will ask about each one.

None of this stops effective marketing. It changes where the lines sit, and knowing them early avoids the version where a campaign gets built and then blocked in review. Where the current setup needs assessing, that is a natural part of a consultation, and the technical implementation sits with development. We are not lawyers, and the compliance read belongs with your counsel and your privacy office.

That is where most of the loss happens, and it is the least marketed stage in the entire sector. An institution can win the enquiry, win the application, make the offer, and still lose the student, and nobody notices because marketing reporting usually ends at application volume.

The stages after the application, and what each one needs.

Application to decision. Silence is the enemy. Applicants who hear nothing assume nothing is happening, and a portal that shows no status is worse than an email. Clear expectations about timing, what happens next, and who to ask.

Offer to acceptance. This is a persuasion moment, not an administrative one. The offer usually arrives when the student is holding two or three others, and the institution that helps them picture actually being there wins. Housing, first-year specifics, the person they will study with, and a route to talk to a current student or a faculty member.

Acceptance to arrival. The gap where accepted students quietly disappear, and it is a real and measurable number. Deposit deadlines, course selection, funding confirmation, and residence steps are each a place someone drops out silently. Sequenced communication and a genuinely usable set of next-step pages recover more students than any additional recruitment spend.

Arrival to the first weeks, which shapes retention and the word of mouth that feeds the next cycle.

What that requires practically. A portal or applicant experience that a nervous eighteen-year-old and a parent can both follow. Communication mapped to the calendar instead of sent when somebody remembers. The interaction detail that makes a status page feel reassuring instead of ambiguous. And content that answers the questions applicants are asking each other and not the ones the institution finds convenient.

The arithmetic argument is straightforward. Recovering a share of accepted students who currently fall away costs a fraction of generating the equivalent number of new applications, which is why we look at this before recommending more spend at the top. That framing is part of how Brand Vision builds the wider education marketing strategy, and it is why the channel plan gets set against the funnel rather than against the calendar alone.

Almost everything about how the decision gets made, and the site usually has not been built for any of it. International recruitment is not the same funnel translated. It runs on different questions, different sources of trust, and a longer chain of people.

What actually changes.

The questions come earlier and are more practical. Study permit and visa requirements, whether the institution is designated to host international students, total cost including everything, work rights during and after study, housing, and what happens on arrival. Those questions decide whether a program makes the shortlist, and on most institutional sites they are buried three levels deep or scattered across four pages.

Proof of outcomes matters more. Families investing at that scale want graduate outcomes, employer names, and post-study pathways, stated specifically and not implied.

Trust is borrowed from elsewhere. Government listings, accreditation bodies, agent networks, alumni communities, and diaspora word of mouth. Which means the authority and coverage that exists off your own site carries unusual weight.

Language goes well past translation. Parent-facing material in the family's language, currency shown honestly, date formats, and examples that make sense outside your own country. A machine-translated page reads as carelessness to exactly the audience you are trying to reassure.

Agents and counsellors are a channel. Where an institution works with recruitment partners, those partners need material that is current, accurate, and easy to use, and it is frequently the most neglected asset in the whole operation. What a partner tells a family in their own language gets attributed back to you, so agent-facing material belongs on the same approval path as the website, with a version date on every document and a route for pulling the ones that have gone stale.

Search behaviour is different by market. The terms, the platforms, and the trusted intermediaries vary considerably country to country, which makes market prioritization a real strategic decision instead of a translation exercise.

So the work starts with deciding which markets genuinely warrant investment, then building for those specifically. That decision belongs in positioning before it becomes a channel plan, and where paid is used in a new market it gets sized as a test until the response justifies more.

Backwards from application deadlines and offer season, because the work that determines a September intake happens the previous autumn and winter. An institution planning campaigns against its own fiscal calendar instead of the learner's decision calendar is spending at the wrong time of year.

How the year gets built.

1. Map the cycle first. Application windows, offer dates, deposit and acceptance deadlines, open house and campus visit dates, and every intake including January and spring starts, which are chronically under-marketed.
2. Work the earlier stage earlier. Awareness and consideration content needs to be live months before applications open, because a learner deciding what to study is already searching.
3. Fund the post-offer stage properly. Covered above, and it is where the cheapest gains are.
4. Treat continuing education on its own calendar. Adult learners decide much faster and closer to a start date, so the same annual rhythm does not apply.
5. Prepare creative before the window, since a campaign built during the window has already missed the earliest and most decided applicants.

On reporting, the metrics we lead with.

• Enquiries, applications, offers, acceptances, and enrolments by program and by source, which requires the site and the CRM to actually be connected. Where that connection is broken, fixing it comes before judging anything.
• Conversion rate between each stage, because a healthy enquiry number hiding a bad offer-to-acceptance rate is the most common misread in the sector.
• Cost per enquiry and cost per enrolled student by channel, held against program value.
• Program page performance, so you can see which programs are being found and which are invisible.
• Domestic and international split, reported separately because the economics differ.
• Non-branded search demand for programs and subjects, separated from people searching the institution by name.
• Accessibility and technical health, tracked continuously instead of revisited before an audit.

Where paid support is needed for a specific intake or a new program, it gets scoped as a defined push against that deadline instead of an always-on spend, which suits how institutional budgets are approved. The wider program then runs against the cycle and not the quarter.

We are used to institutional procurement, including public RFPs, and the scoping conversation accounts for it instead of treating it as an obstacle. More than 50 collaborations with educational institutions, including McGill University, the University of Toronto, the Toronto District School Board, and the University of Chicago, means school marketing and higher education procurement are both familiar ground for Brand Vision.

What that looks like in practice. Formal RFP and RFQ responses with the documentation, references, and evidence institutional purchasing requires. Accessibility conformance addressed directly in the response instead of promised vaguely, which is increasingly a scored criterion. Insurance, privacy, and security requirements handled through your standard vendor process. Work scoped to fit fiscal year boundaries and multi-year approvals, since a project that must be invoiced inside one budget year is a real constraint and a solvable one. And phased engagements where approval for the whole thing is not available yet.

What moves the cost.

• Site size and how much is being retired. A three-hundred-page consolidation is different work from a nine-hundred-page one.
• Program volume and whether a proper program finder is being built, which is usually the largest single component and the highest return.
• Integrations. Student information systems, application platforms, CRM, and portals. This is where institutional web projects most often get underestimated.
• Accessibility remediation on existing content, including PDFs and video captioning, which is scoped honestly instead of hidden.
• Language requirements and how many audiences need genuinely separate content.
• Whether branding is in scope, and whether faculty-level sub-brands need resolving.
• Governance and training, which is a small line that protects everything else.

On making budget stretch, two things help. Phasing so the highest-value part ships first, which for most institutions is the program section rather than the homepage. And building for your central team to run, so you are not paying an agency for routine edits, which also matters because institutional teams are usually smaller than the site they maintain. Where the honest recommendation is a consultation and roadmap before any build, that is what gets proposed. You can see the range in selected work, and tell us what you are working with for a scoped read.