Future scope: Programmatic college pillar pages

Status: FUTURE SCOPE — not scheduled, nothing built. Added by Ravneet, 4 Oct 2026. Owner bot: Purva (admissions). Follows ARCHITECTURE.md (bot isolation, opacity) and MIGRATION.md (never break existing Google rankings).

Goal

Turn college data in Supabase into one rich, heavily linked page per college (e.g. /colleges/jbims). One strong page per college collects all ranking power, and clear sections let Google show "Jump to" links straight in search results.

Phase 1: Database (Supabase)

Relational, so one query returns everything for a college.

• colleges: id, slug (jbims), name, description, location, official website.
• cutoffs: college_id → colleges, year, exam (CET / CAT / …), category (Open, OBC, SC, ST, …), score.
• fees: college_id → colleges, program, category, amount.
• Public read-only data; RLS on, writes only by staff tools.

Phase 2: Next.js page assembly

• Dynamic route app/colleges/[slug]/page.tsx, built ahead of time and refreshed on a schedule (static/ISR), so pages are fast and crawlable.
• The server fetches the college with all its cutoffs and fees in one query.
• Quality gate: a college without enough data (e.g. a name but no cutoffs) is not published in sitemap.xml and is marked noindex, to avoid thin-content penalties.

Phase 3: Section links for Google "Jump to"

• Each category section has a fixed, readable id, e.g. <section id="obc-category"><h2>JBIMS OBC Category Cutoffs & Seat Matrix</h2>…</section>.
• A table of contents at the top uses plain links (<a href="#obc-category">).
• Headings use scroll-margin-top (Tailwind scroll-mt-*) so the sticky nav never covers a section after a jump.

Phase 4: Automatic structured data (JSON-LD)

• EducationalOrganization: college name, location, official website.
• FAQPage: generated from the real cutoff rows, e.g. "What is the OBC cutoff for JBIMS?" → "The latest OBC cutoff is …" — only from verified data, never invented.

Rules that apply

• Purva owns these pages and their data access (bot isolation rule 1).
• Numbers come only from the database; the LLM may phrase text, never make up a cutoff.
• No user counts or student data on these pages (opacity rule).
• Existing WordPress college URLs get 301 redirects to the new pages (MIGRATION.md).

Open questions (decide when this is scheduled)

• Source of cutoff and fee data, and who updates it each year.
• Which colleges and exams go first.
• Whether the same pattern also covers exam pages (/cat, /cet) and formula pages.