How do prospective students research?
Prospective students research programmes in search engines and, increasingly, in AI assistants, asking questions like what does this course cover, what are the entry requirements, and what can I do afterwards. The institution whose pages answer those questions clearly, with facts, is the one that gets cited and visited.
Many programme pages are written for the institution rather than the enquirer. A Search Visibility Digital FTE rewrites that relationship by starting from the questions.
What does the Digital FTE do for programme marketing?
The Search Visibility Digital FTE identifies the questions asked about each programme and its subject, checks which are worth answering against the institution's own data with a worth-it verdict, and proposes pages or improvements that answer them from real programme facts: modules, requirements, fees, dates, and accreditation as documented.
Drafts go through the fact gate and then to Approvals. The programme lead or marketing team approves, edits, or sends back with a reason, and approved pages publish through the CMS you use or as a pull request to your site repository.
Why does the fact gate matter in education?
The fact gate matters in education because marketing claims about outcomes, employment rates, accreditation, and rankings are regulated or scrutinised in many jurisdictions, and an unsourced claim can be a compliance problem rather than just an inaccuracy. The gate blocks any such claim that lacks a source in the approved documents.
A page that says graduates work at leading firms without a source does not pass. A page that cites the institution's published outcomes data, with the year and method, does. The gate turns a compliance rule into a mechanical check.
- Outcome and employment claims: blocked without a published source
- Accreditation and recognition: cited to the accrediting body's listing
- Fees and dates: cited to the current fee schedule and calendar
- Comparative or ranking claims: cited to the named ranking and year
How is publication controlled?
Publication is controlled by the approval gate and by the publishing route. Nothing goes live without a named approver, and the route is either the CMS the institution already uses, with the FTE's draft appearing as a pending item, or a pull request to the site repository, reviewed like any other change.
Autonomy for publishing is rarely appropriate in education marketing, and the remit can keep it gated indefinitely. The FTE's value is in the proposals and the measurement, not in publishing unattended.
How do you measure it?
Measure per programme: visibility for the target questions in search and AI answers where measurable, page visits from search, and enquiries or applications attributed to those pages. Record the baseline before the first page publishes, and compare over an admissions cycle rather than a month.
The performance view reports honestly: what improved, what did not, and what is unmeasured. A programme whose pages gained visibility but not enquiries is a signal about the programme's positioning, which is useful to know.
What does a programme page proposal contain?
A programme page proposal in Approvals contains the topic's worth-it verdict, meaning why this programme's questions are worth answering now from the institution's own search data, the draft page structured around the questions prospective students actually ask, with each section answering one of them directly, and the sources behind every factual claim: the module list from the programme specification, the entry requirements page, the fee schedule, the accrediting body's listing, and any published outcomes data with its year and method.
The fact-gate result is attached, showing which claims were checked and, if a draft was revised, which claims were blocked and how the revision resolved them. The programme lead reviews the substance, the marketing team reviews the tone, and either sends back with a reason or approves; the approval is logged with a name. Publication goes through the institution's CMS or a pull request to its site repository, never unattended. After publication the page's target questions join the sampled prompt set, and its visibility is reported in the performance view against the baseline taken before it went live.