Higher Education University GEO Case Study: Earning AI Citations for Program & Admissions Queries

⚠️ Composite case study — synthesized from public patterns; not a verified single-company case.

TL;DR

Prospective students increasingly ask AI assistants "what's the best in-state engineering program with co-op?" instead of typing into Google. Most universities are invisible in those answers because their program pages are narrative-heavy, their LLM crawler policy is misconfigured, and their content is not seeded into the third-party sources AI engines preferentially cite. This case study walks through how a regional research university ("Lakeside University," an illustrative composite) reorganized its content stack and lifted citation share from 4% to 39% in two semesters.

Why this case matters

Higher-ed marketing teams are facing two simultaneous shifts. First, organic traffic to .edu sites is declining as AI Overviews answer informational queries directly. Search Engine Land's reporting on Princeton's 28% organic decline reflects a broader pattern across research-heavy institutions, with steeper declines on fact-style queries. Second, the prospects who do convert are arriving with AI-shaped questions — "compare these three programs," "which schools accept transfer credits from CC X for nursing" — that demand structured answers, not viewbook prose.

Universities that adapt by writing for AI extraction and seeding the right third-party surfaces are recovering visibility on the queries that matter most for enrollment. Lakeside's program (composite) is a worked example of how to do that without breaking accreditation messaging or compliance.

Background

• Institution profile (illustrative composite): Mid-sized US regional research university, ~14,000 enrolled, 90+ undergraduate programs, 60+ graduate programs, marketing team of 11, decentralized college-level web ownership.
• Starting baseline (Aug 2025): ~3.2M monthly organic sessions; AI citation share ~4% on a tracked basket of 320 program- and admissions-related queries (manual ChatGPT panel + Perplexity + AI Overviews + Claude).
• Goal: Become a routinely cited source on program comparison, admissions requirements, financial-aid, transfer-credit, and outcomes queries across ChatGPT, Perplexity, Google AI Overviews, and Claude over two semesters.
• Constraint: Federal compliance (Title IX, Clery, Title IV, ADA), accreditation messaging fidelity, and decentralized publishing across 11 colleges.

Diagnostic: what AI engines were citing instead

The team ran a tracked-prompt audit across 320 higher-ed queries on ChatGPT (with web), Perplexity, Google AI Overviews, and Claude. Findings:

• 41% of citations went to editorial: U.S. News, Niche, College Factual, Princeton Review, Forbes Education.
• 22% went to community: Reddit r/ApplyingToCollege, r/college, r/gradadmissions; Quora; CollegeConfidential.
• 14% went to YouTube (mostly student-perspective videos and program walkthroughs).
• 9% went to Wikipedia (institutional and program entries).
• 8% went to peer .edu sites — but skewed heavily toward five elite institutions per topic.
• 4% went to government (Department of Education College Scorecard, BLS occupation pages).
• 2% went to Lakeside, almost all branded queries.

Diagnosis: Lakeside's program pages were prose-heavy viewbook content with strong narrative but few extractable answer blocks, no FAQPage schema, and no canonical place in Reddit, YouTube, or Wikipedia for non-branded discovery.

Strategy: the four-layer higher-ed GEO stack

The team treated each citation source as a layer with its own optimization motion, mirroring the patterns Coalmarch and U-Tech document for university GEO programs.

Layer 1 — Owned: extractable program & admissions pages

Lakeside rebuilt 142 program landing pages, 28 admissions pages, and 18 financial-aid pages around extractable answer blocks. Each page now contains:

• A 60-120-word direct-answer block above the fold answering the canonical question ("What does the BS in Mechanical Engineering at Lakeside cover, and who is it for?").
• A standardized FAQ section of 6-10 questions per page (curriculum, prerequisites, transfer credit, outcomes, deadlines, cost), each answer 60-140 words.
• An accreditation, last-reviewed-on date, and named department contact at the top.
• FAQPage and CollegeOrUniversity schema with sameAs to Wikipedia, IPEDS, and the institutional Crunchbase entry.
• Two outbound contextual links: one to a credible third-party source (BLS, the relevant accreditor, or a peer-reviewed paper), one to a sibling Lakeside program.

Layer 2 — Earned editorial mentions

The team pitched eight bylined data stories to The Chronicle of Higher Education, Inside Higher Ed, EAB Insights, and U.S. News — each anchored on aggregated outcomes data Lakeside already collected (placement, time-to-degree, transfer outcomes). Coalmarch's data shows AI search drives a smaller absolute share of higher-ed traffic than commercial verticals but with strong intent quality, so even a few editorial mentions disproportionately move citation share.

Layer 3 — Community and YouTube source seeding

Lakeside opened a verified university Reddit account in r/ApplyingToCollege and r/college, with two staff (a current admissions counselor and a program-coordinator faculty member) posting practical answers. They published a weekly "Day-in-the-Life" YouTube series in collaboration with student creators and posted full transcripts on the relevant program pages. Wikipedia entries for the institution and major programs were audited and updated with cited improvements.

Layer 4 — LLM crawler & llms.txt policy

A misconfigured robots.txt was blocking GPTBot and ClaudeBot from indexing several program pages. The team:

• Audited robots.txt and unblocked GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, and Google-Extended on public marketing pages while keeping login walls and student-record systems blocked. Mark Williams-Cook's Reddit thread on AI Overviews crawler behavior shows that gating these bots is a frequent root cause of "why isn't AI citing us" complaints.
• Added a hand-curated llms.txt at the root pointing AI crawlers to the highest-quality source pages and excluding low-quality sections, following the pattern emerging across .edu sites.
• Added Article and FAQPage schema across 188 pages.

Implementation timeline

Results (two semesters)

• AI citation share on tracked basket: 4% → 39% (manual panel + Perplexity API + AI Overviews logging).
• Inquiry form starts attributed to AI search referrals (per session source + intake survey "how did you hear about us?"): 0 → ~1,400/semester.
• Application starts from AI-cited program pages: +18% YoY on rebuilt programs vs. flat on non-rebuilt.
• Branded query share-of-voice (Google AI Overviews): +22 pts.
• Notable laggards: graduate-program citation share moved less (4% → 21%) because peer institutions in graduate-research domains have stronger Wikipedia and editorial gravity.

Why this worked: source mix > template tweaks

The biggest lever was matching where each engine pulled citations from. ChatGPT rewarded the Wikipedia and editorial work most. Perplexity rewarded Reddit and on-site FAQ density. AI Overviews rewarded YouTube transcripts and Reddit. Claude lifted last but most consistently — it disproportionately rewards well-formatted FAQ blocks with explicit Q—A markup and frequent mention of the entity name.

Pitfalls to avoid

• Blocking GPTBot/ClaudeBot on the same robots.txt as Googlebot — LLM crawlers obey their own user-agent, and blocking by mistake collapses citation share to near zero. Audit by grep, not by assumption.
• Over-marketing on Reddit — verified, helpful answers from named staff only. Mods will ban marketing accounts and Perplexity will deweight the subreddit.
• Faculty bylines without on-page schema — Person + sameAs to ORCID and Google Scholar materially lifts citation odds for graduate programs.
• Generic FAQ copy — questions like "Why choose us?" rarely get cited; specific transfer-credit, outcomes, and accreditation Qs do.
• Outdated outcome stats — placement and salary numbers older than 18 months are scored as low-trust by Perplexity and Claude.

Replication checklist

1. Run a tracked-prompt audit of 200-400 program/admissions queries before changing anything; measure source mix per engine.
2. Audit robots.txt and llms.txt; allow major LLM crawlers on public marketing pages; publish a curated llms.txt.
3. Build a program-page template with: 60-120-word direct-answer block, 6-10 FAQ Qs, FAQPage + CollegeOrUniversity schema, last-reviewed date, named department contact, two contextual outbound links.
4. Pitch 6-10 bylined data stories to top higher-ed editorial outlets per academic year.
5. Stand up a weekly student-perspective YouTube series with transcripts published on the relevant program pages.
6. Open a verified institutional Reddit presence with staff (not marketers) answering authentically.
7. Audit institutional and major-program Wikipedia entries; submit cited improvements.
8. Re-measure citation share at weeks 12, 20, and 32; reallocate budget to whichever layer moved most.

FAQ

Q: How long does a higher-ed GEO program take to show citation lift?

First measurable lift typically appears at weeks 8-12 once program pages are rebuilt and at least one editorial placement has run. Material citation share (above 25%) usually arrives by month 5-6 because Perplexity and AI Overviews need community and YouTube content to age before they treat it as authoritative.

Q: Should universities allow GPTBot and ClaudeBot to crawl their sites?

Yes, on public marketing and program pages, with explicit blocks on student-record, login-walled, and FERPA-sensitive sections. Blocking LLM crawlers wholesale is the single most common root cause of "we're invisible in AI search" findings in higher-ed audits.

Q: What schema types matter most for university content?

CollegeOrUniversity, EducationalOccupationalProgram, Course, FAQPage, and Person (for faculty bylines) with sameAs to ORCID, IPEDS, and Wikipedia. Schema improves discovery; the on-page answer blocks do the citation work.

Q: How is a higher-ed GEO playbook different from a SaaS or local-business one?

Higher-ed has unusually strong editorial gravity (U.S. News, Niche, CHE, IHE), unusually strong Reddit gravity (r/ApplyingToCollege, r/college), and a heavy YouTube tail driven by student-perspective content. Owned content matters less in proportion than in SaaS; community and editorial layers matter more.

Q: What's the right way to handle outcomes data?

Publish placement and salary data with a clear methodology, the cohort year, and a last-reviewed-on date. Use ranges where individual numbers are noisy. Avoid headline averages without disclosure of methodology — Perplexity and Claude both deweight outcome claims that lack provenance.

Q: Should we publish an llms.txt?

Yes. A curated llms.txt at the site root that points to your highest-quality program pages, accreditor links, and outcomes data raises the odds that LLM crawlers prioritize them. Treat it like a sitemap-of-record for AI rather than a permission system.