Keeping university course information consistent for discovery

Treat course information as a controlled record

A prospective student may meet the same course through a course page, subject listing, prospectus, application portal, PDF, translated page or third-party feed. If those surfaces disagree on the award, entry requirements, fees, dates or delivery, the student cannot tell which version is current. Search and AI systems face the same ambiguity; they do not repair an institution's conflicting source material.

Start with one approved course record and map every public surface that repeats it. The record should distinguish facts that must remain identical from explanations that can be adapted for a market or language. The Competition and Markets Authority's guidance states that students have consumer rights and explains how consumer protection law applies to higher education providers. Consistency work therefore supports an informed decision, not just discoverability.

Control eight fields for every course and intake

Use the table as a publication and acceptance record. Give every field a source, owner and last-verified date. Where information legitimately differs by intake, student category, location or study mode, label the difference instead of forcing one value into every page.

Map every surface before changing a fact

For each controlled field, record where it appears: canonical course page, listings, admissions guidance, fee tables, PDFs, application systems, structured data, partner feeds and translated pages. When a fact changes, use that map to assign updates, record deliberate exceptions and test the rendered public result. Do not close the change because the central database was edited if an old prospectus or translated page remains public.

A practical change ticket names the course and intake, old and new values, effective date, authority, affected URLs or feeds, approver and verification evidence. For urgent corrections, also record which assets could not be updated immediately and the temporary notice or removal used to prevent a misleading route.

• Separate the authoritative record from the inventory of places that repeat it.
• Use explicit intake, audience, location and study-mode labels for legitimate differences.
• Check accessible page text, metadata and structured data against the same approved fact.
• Retire or redirect obsolete pages and PDFs when they no longer serve a valid historical purpose.
• Keep screenshots or machine-readable checks as verification evidence, not as the source of truth.

Keep shared facts aligned across languages

English and Simplified Chinese course pages can answer different audience questions and use natural wording for each language. The course identity, award, availability, requirements, fees, dates, delivery and contact route still need to refer to the same approved intake. If a translated page summarises a policy, link to the controlling source and state clearly where the authoritative detail sits.

Google recommends explicitly identifying localized versions. Each page in an hreflang set should list itself and the other versions, and the relationships should be reciprocal. That helps systems associate the pages, but it is not a substitute for translated main content or consistent facts. Give each language version its own canonical URL and test the live return links after publication.

Run a release and review gate

Before an intake is promoted, ask a reviewer who did not make the edits to complete the eight-field table using only the live pages. Record each answer as consistent, justified difference, missing or conflicting. Block promotion for conflicts in material decision information; assign an owner and deadline for every other gap. Repeat the check after a course change and at a defined interval during recruitment.

Google's people-first guidance asks whether content helps an intended audience achieve its goal and whether sourcing and production context are clear. For a course page, that means helping a prospective student understand the offer and next step. Search or AI visibility should be monitored separately from factual acceptance, and no publication checklist can guarantee indexation, citation or enrolment.

• Can a prospective student identify the exact course, award and available intake?
• Are entry requirements, fees and dates current, qualified and traceable?
• Do course listings, detail pages, application routes and PDFs agree?
• Do English and Chinese versions share controlled facts and reciprocal language links?
• Does every material change have an owner, effective date and verification record?

Use the record to scope GEO work

A university commissioning GEO work should provide the course record, surface map, language responsibilities, approval route and priority applicant questions. Ask the provider to distinguish factual corrections, content improvements, technical implementation and monitoring. Acceptance should be based on inspectable changes and records, not a promise that an external platform will cite or recommend the course.

SALIENS provides GEO audits, AI visibility monitoring, content and technical improvements, and ongoing GEO delivery for UK and international organisations. We can audit English and Simplified Chinese course information, build a controlled fact and page map, identify conflicts and establish a repeatable release check. Email info@oxfordintelligence.co.uk with your institution, target markets and languages, representative course URLs and the facts that change most often. SALIENS is operated by Oxford Intelligence Limited.