Education SEO

Automated SEO analysis and reporting for education

A university website is forty websites in a trench coat. Departments publish independently, subdomains multiply, and three faculties have their own version of the same course page. GSC Wizard reports per department and per subdomain, so the central team can finally see what is actually out there.

Try for free (no creditcard needed) See the governance setup

Subdomain and folder reporting, duplicate detection and admissions-cycle comparisons.

Distributed publishing

Nobody has ever seen the whole institution's search performance in one place.

The central web team owns the homepage and the templates. Departments own their own content, their own subdomains, and increasingly their own microsites. Nobody has a single view, so the same course gets three pages, they compete with each other, and the applicant lands on the least maintained one.

The problem

The specific problems of an institutional website

Governance problems that look like SEO problems.

The same programme has three pages in three departments

The faculty page, the department page and the central prospectus entry all describe the same course. Google picks one, usually not the one with the application form, and applicants land on a page last updated four years ago.

Subdomain sprawl nobody has an inventory of

Research groups, conferences, legacy project sites and lab pages accumulate over decades on their own subdomains. Some rank for institutionally important terms. Nobody knows which ones exist, and abandoned ones quietly become a liability.

The admissions cycle makes every normal comparison wrong

Traffic is driven by application deadlines, clearing and term dates, not by the calendar month. Comparing October to September is meaningless; the only valid comparison is this year's cycle against last year's cycle at the same point.

The setup

How to set it up

Get the inventory first. Everything else is easier afterwards.

Step 1

Report by subdomain and folder

The subdomain and folder breakdown rolls performance up your URL hierarchy, which for an institution is effectively an org chart. It is usually the first time anyone sees the whole estate in one table.

Subdomain and folder report →

Step 2

Find the duplicate programme pages

Cannibalization analysis identifies where multiple institutional pages compete for the same course query and which one Google actually shows. That converts an SEO finding into a clear content-ownership decision.

Cannibalization report →

Step 3

Give each faculty its own view

Content groups per faculty, plus shared report links, mean departments can see their own performance without central IT provisioning Search Console access for two hundred people.

Sharing reports →

Step 4

Compare cycle to cycle, not month to month

Comparison date ranges aligned to the admissions cycle, with multi-year retention behind them, make 'week 6 of clearing this year versus last year' a normal question to ask.

Filters and date ranges →

The output

The institutional overview

The view the central web team has never had.

INSTITUTIONAL SEARCH REPORT - cycle week 6 vs same week last year

BY FACULTY / SUBDOMAIN        clicks     vs last cycle
  www (central + prospectus) 412,900          +4%
  eng.                        88,140          -2%
  med.                        76,220         +11%
  business.                   61,010         -19%   <- investigate
  law.                        44,880          +3%
  research groups (37 subs)    31,440         -8%
  legacy / unowned (14 subs)    9,110        -34%

DUPLICATE PROGRAMME PAGES
  'msc data science' - 3 institutional URLs compete.
  Google shows the department page (no application link).
  The prospectus page with the form ranks 3 positions lower.

UNOWNED SUBDOMAINS
  14 subdomains with no maintainer still ranking for
  institutional terms. 4 have not been updated since 2019.

ADMISSIONS QUERIES  'entry requirements' up 22% vs last cycle

The duplicate programme finding is the one that converts directly into applications: Google is ranking the page without the application form above the page with it.

What to watch

Metrics for a distributed institution

Performance by faculty

Clicks and position rolled up to department level. It turns an unowned sitewide number into something a faculty head is accountable for.

Duplicate programme count

How many courses have more than one institutional page competing. Each one is an applicant landing on the wrong version.

Cycle-aligned comparison

This year's week 6 against last year's week 6. In education the calendar month is not a meaningful unit and never was.

Unowned subdomain inventory

Legacy sites still ranking with no maintainer. A governance risk that only becomes visible when you report by subdomain.

Frequently asked questions

Can we see performance for each department separately?

Yes. Report by subdomain and folder to match your URL structure to the org chart, and use content groups where departments share a domain. Shared report links then let each faculty see its own numbers without central access provisioning.

How do we handle the same course having several pages?

Cannibalization analysis shows which institutional URL Google actually ranks for the course query. The typical fix is to designate the prospectus page with the application form as canonical and have the departmental pages link to it rather than compete with it.

Our traffic follows the admissions cycle, not the calendar. Can reporting match that?

Use comparison ranges aligned to your cycle, with enough retained history behind them. Full storage properties keep up to 10 years, which matters because a meaningful cycle comparison usually needs more than the sixteen months Google keeps.

We have dozens of subdomains and no inventory. Where do we start?

The subdomain breakdown across your Search Console properties gives you the ranked list of what is actually getting search traffic. Start with the ones ranking for institutionally important terms and no known maintainer - that is where the risk is concentrated.