The blueprint
Build an enquiry pipeline you actually own
The complete method I use to turn search demand into a compounding admission enquiry engine — architecture, timeline, tooling and cost. Roughly a 15-minute read.
Last updated September 2026
01 / Orientation
Who this is written for
Colleges & groups
Multiple courses, affiliated institutions, management quota seats to fill each cycle.
Coaching institutes
Multiple exam categories across cities, where parents compare for weeks before enrolling.
Consultancies
Counselling operations competing for the same searches as every other consultant in the state.
This is the method I use when an institution wants admission enquiries that keep arriving after the ad budget stops. It is written in full, including the costs, because the decision to commit to this takes months of conversation and you should be able to evaluate it properly before we speak.
It applies wherever the buying decision is high-consideration: months of research, several family members involved, a significant fee at the end.
The mechanics are identical. Only the inputs change — and section 07 shows exactly how those inputs change the scope.
02 / The problem
Paid ads buy attention. They don't build anything.
Every cycle costs more.
Competition for admission keywords grows each year and cost per enquiry grows with it.
Pause the spend, lose the pipeline.
Ad-driven enquiries stop within days. Nothing you paid for last cycle still works today.
You meet them too late.
Parents research for months. Ads reach the decision point; search reaches them while they are still deciding what to decide.
Performance marketing works. It delivers enquiries this month, measurably, and no serious institution should stop running it. The problem is what it leaves behind, which is nothing.
Every rupee spent on ads buys a visitor once. When the cycle ends and the budget pauses, the pipeline stops within days. The next cycle starts from zero, at a higher cost per click than the last one, because competition for admission keywords increases every year.
You are renting visibility. The rent goes up, and you never own the property.
03 / The maths
What a paid enquiry actually costs you
Monthly cost
Paid channel
Scales with volume, every cycle
Scales with volume, every cycle
Organic at maturity
Fixed retainer, independent of volume
Fixed retainer, independent of volume
Cost per enquiry
Paid channel
Rises each cycle
Rises each cycle
Organic at maturity
Falls as pages mature
Falls as pages mature
If you stop paying
Paid channel
Enquiries end within 48 hours
Enquiries end within 48 hours
Organic at maturity
Pages keep ranking and producing
Pages keep ranking and producing
Value after 3 years
Paid channel
Zero — spend is expensed
Zero — spend is expensed
Organic at maturity
A ranking property you own
A ranking property you own
Competitive moat
Paid channel
None — outbid at any time
None — outbid at any time
Organic at maturity
Years of topical authority to displace
Years of topical authority to displace
The comparison that matters is not cost per enquiry this month. It is what you hold at the end of three years of spending.
Bring your own numbers to this table. In a first conversation I will ask what you currently spend per cycle and what your cost per enquiry is, and we will fill these cells with your figures. Your own numbers make the case far better than mine.
04 / Expectations
This compounds. It does not spike.
If you are used to paid campaigns, the first three months of this will feel like nothing is happening. That is expected, not a shortfall, and it is worth agreeing on before we start rather than discovering at month three.
Build and index.
Architecture, content and technical work go live. Organic enquiries near zero.
Early rankings.
Long-tail pages land. Enquiry trickle begins alongside your existing paid channels.
Compounding.
Volume climbs, cost per enquiry falls, and the curve never resets to zero.
Keep running your ads throughout. This is not a replacement for paid acquisition in year one; it is what makes paid acquisition optional in year three.
05 / The model
What this engagement is, structurally
Domain knowledge
Typical agency
Generalist SEO applied to education
Generalist SEO applied to education
This engagement
12+ years inside admissions — counselling, cutoffs, seat allotment
12+ years inside admissions — counselling, cutoffs, seat allotment
Who does your strategy
Typical agency
Senior in the pitch, junior on the account
Senior in the pitch, junior on the account
This engagement
The same person, pitch to delivery
The same person, pitch to delivery
Cost structure
Typical agency
Bundled — you fund overhead and margin on execution
Bundled — you fund overhead and margin on execution
This engagement
Strategy only — you source execution at market rate
Strategy only — you source execution at market rate
Incentive
Typical agency
Paid on retainer regardless of outcome
Paid on retainer regardless of outcome
This engagement
Retainer plus a success share on closed admissions
Retainer plus a success share on closed admissions
What you keep
Typical agency
Knowledge leaves with the agency
Knowledge leaves with the agency
This engagement
Blueprints, briefs and schema stay with you
Blueprints, briefs and schema stay with you
This is a structural difference, not a claim that agencies do poor work. Many do excellent work. But an agency has to fund a team, which means the person who designed your strategy is rarely the person executing it six months later.
I work with a small number of institutions at a time, as the strategic lead. I provide the architecture, the briefs and the governance. Your developer and writers execute against them — or I help you find people who can.
06 / The method
Ten stages, in order
Each stage depends on the one before it. Running them in parallel to save time is the most common reason large education portals fail to rank.
Keyword layer
Demand mapped, intent-tagged, clustered
URL taxonomy
Silo structure and URL patterns locked
Data model
CMS fields and page templates defined
Technical layer
Schema, speed, crawl controls
Content system
Briefs, production line, QA gates
Link architecture
Internal authority flow engineered
Indexation
Phased release, crawl budget managed
Conversion layer
Traffic turned into tracked enquiries
Measurement
Attribution wired end to end
Optimization loop
Continuous refresh and expansion
Stages 1–4 are mine to design. Stages 5–8 are mine to specify and govern, yours to execute. Stages 9–10 run jointly for the life of the engagement.
Keyword layer
Every search a parent or student makes about your courses, your city and your competitors — harvested from Search Console, competitor gap analysis, autocomplete, and the phrasing families actually use on the counselling floor. Typically 800 to 2,500 terms, each tagged by intent and mapped to exactly one page. One keyword, one page: two pages chasing the same term both rank worse.
URL taxonomy and data model
Six to eight URL patterns, fixed before a single page is built. College pages are generated from structured records of 35 to 50 fields — approvals, intake, fees by quota, placements, infrastructure — not written one at a time. A fee revision then updates one record and corrects every page it appears on. Without this layer a 400-page portal becomes unmaintainable within one admission cycle.
Content system
Brief anatomy
- Target keyword
- Secondary terms
- Full heading outline
- Data points to include
- Internal links, exact anchors
- Meta description
Writers do not decide what a page says; the brief does. Each brief carries the target keyword, secondary terms, a full heading outline, the data points to include, internal links with exact anchors, and the meta description. Nothing publishes without passing a QA gate: brief compliance, factual verification of every fee and intake figure against source, and schema validation.
Indexation
Publishing 400 pages on one day consumes crawl budget on thin pages and stalls indexation. Pages release in four waves — core hubs, priority profiles, full directory, then long-tail — with each wave gated on the previous clearing 90% indexation.
Link architecture
Every spoke page links up to its hub using the hub's exact target keyword as anchor text. That single rule is what concentrates ranking authority on the pages that actually produce enquiries. Minimum three and maximum eight contextual links per page, zero orphan pages, click depth capped at three.
07 / Scope
The page count is calculated, not guessed
Institutions per course in your region × courses to be ranked = core page count
| Scenario | Typical page count | Primary search intent | What a conversion is |
|---|---|---|---|
| College or group, 4 courses, 50 affiliated institutions | 200–250 | “top [course] colleges in [city]” | Seat enquiry or counselling call |
| Coaching institute, 6 exam categories, 3 cities | 120–200 | “[exam] coaching in [area]” | Demo class booking or callback |
| Admissions consultancy, statewide | 150–400 | “[exam] counselling”, “cutoff [year]” | Counselling consultation |
Scenario
College or group, 4 courses, 50 affiliated institutions
Typical page count
200–250
Primary search intent
“top [course] colleges in [city]”
What a conversion is
Seat enquiry or counselling call
Scenario
Coaching institute, 6 exam categories, 3 cities
Typical page count
120–200
Primary search intent
“[exam] coaching in [area]”
What a conversion is
Demo class booking or callback
Scenario
Admissions consultancy, statewide
Typical page count
150–400
Primary search intent
“[exam] counselling”, “cutoff [year]”
What a conversion is
Counselling consultation
Three reasons the number lands where it does. Google ranks one page per intent, so “top BAMS colleges in Bangalore” and “[college] BAMS admission” need separate pages. Two pages chasing one keyword both underperform. And a directory listing 10 institutions where 50 exist reads as incomplete, which weakens even the hub page.
How you verify I'm not overbuilding
- Every page maps to a real search term with volume attached
- The count is locked during the scoping sprint, from your actual course list
- No page ships without a brief naming its target keyword, so you can audit page by page
08 / Tooling
What runs the build, and what it costs
Free where possible, paid where it scales
Free tools handle verification and baseline research throughout. Paid tools appear only where manual work stops scaling — crawling past 500 URLs, clustering past a few hundred keywords, tracking rankings across tiers.
| Stage | Tools | Cost |
|---|---|---|
| Keyword research | Keyword PlannerSearch ConsoleTrends | Free |
| Keyword clustering | AhrefsSEMrush | Paid |
| Site structure | SheetsSupabase | Free tier |
| Crawling and audit | Screaming FrogSitebulb | Paid |
| Technical validation | PageSpeedRich Results Test | Free |
| Content scoring | SurferClearscope | Paid |
| Drafting | LLM | Paid API |
| Lead capture | FormsTag ManagerSheets | Free |
| Measurement | GA4Search ConsoleLooker Studio | Free |
| Rank tracking | AhrefsSEMrush | Paid |
Drafting runs from locked briefs, and every fee, intake figure and cutoff still passes human verification against source. AI drafts. It never substitutes for the fact-check.
09 / Timeline
Sixteen weeks, with gates
Keyword layer
Clustered keyword master sheet, competitor gap report
Sign-off on target course list
Taxonomy and data model
Full sitemap, URL patterns, CMS field schema
Page count locked; dev signs off
CMS build
Templates coded, wireframes implemented
Staging renders all templates
Technical layer
Schema, Core Web Vitals, sitemaps, canonicals
Rich Results valid; CWV green on mobile
Brief production
All SEO briefs written and released in batches
Your data handover complete
Wave 1 content
Core hub pages live, database populated
Hubs indexed before wave 2
Waves 2–3
Priority and full directory pages
90% indexation per wave
Link architecture
Internal linking pass, orphan sweep
Zero orphans, depth ≤ 3
Conversion layer
Enquiry points, WhatsApp hooks, forms
Test enquiry arrives tagged
Measurement
GA4, Search Console, tracking live
Attribution verified end to end
Week 17 onward, the optimization loop runs under the monthly retainer.
10 / How I show up
What the retainer actually buys
Sprint review
60-minute sprint review with your developer and content leads. Blockers cleared, next briefs released, QA sign-off on delivered pages.
Technical audit
Technical audit against a 40-point checklist: indexation, Core Web Vitals, schema validity, broken links, orphan pages, duplicate metas.
Leadership report
Written report to leadership: indexation coverage, ranking movement by keyword tier, enquiry volume, cost per enquiry trend.
Strategy reset
Keyword gaps re-scanned, competitor movement reviewed, next quarter's page roadmap re-prioritised.
11 / Attribution
No CRM required, no software to buy
Form submit
Hidden fields fire
Row appended
Sheet, 3 tabs
A CRM is not a prerequisite. Every enquiry can be captured, tagged and logged into a single Google Sheet at zero licence cost, set up as part of week 15.
Every form carries hidden fields — source, campaign, landing page, course and timestamp — written into the sheet on submission. WhatsApp click-to-chat links carry the page and course in the pre-filled message, so enquiries arrive self-labelled. Calls are logged by your counselling team against the same columns.
If you already run a CRM, the same tags write into it instead. Nothing about the method changes.
12 / Risk
What could go wrong, and what happens then
| Risk | How it's handled |
|---|---|
| Google algorithm update mid-build | Architecture is built on topical depth and genuine utility, not tactics. Quarterly reset absorbs updates |
| Your writer or developer under-delivers | Weekly reviews surface slippage early; briefs are specific enough that a replacement picks up mid-stream |
| Rankings slower than projected | Long-tail pages are sequenced first to produce early wins while competitive hub terms mature |
| Enquiries arrive but don't convert | The monthly report separates enquiry volume from close rate, so the bottleneck is visible rather than argued about |
| A competitor builds the same asset | Indexed authority takes years to displace. Delay is the expensive option |
| Engagement ends early | All blueprints, briefs, keyword maps and schema documentation remain yours |
Risk
Google algorithm update mid-build
How it's handled
Architecture is built on topical depth and genuine utility, not tactics. Quarterly reset absorbs updates
Risk
Your writer or developer under-delivers
How it's handled
Weekly reviews surface slippage early; briefs are specific enough that a replacement picks up mid-stream
Risk
Rankings slower than projected
How it's handled
Long-tail pages are sequenced first to produce early wins while competitive hub terms mature
Risk
Enquiries arrive but don't convert
How it's handled
The monthly report separates enquiry volume from close rate, so the bottleneck is visible rather than argued about
Risk
A competitor builds the same asset
How it's handled
Indexed authority takes years to displace. Delay is the expensive option
Risk
Engagement ends early
How it's handled
All blueprints, briefs, keyword maps and schema documentation remain yours
I will not promise specific keyword rankings by specific dates. Anyone who does is guessing.
13 / Boundaries
Enquiry generation is mine. Admissions closing is yours.
My metric of success
Month-over-month growth in organic enquiries: WhatsApp messages, inbound calls and form fills originating from search. Plus full indexation of the portal and passing Core Web Vitals.
Your metric of success
Closed admissions. Converting an enquiry into a confirmed seat depends entirely on your counselling team's speed, pricing and follow-up persistence.
| Role | Responsibility | Provided by |
|---|---|---|
| Project head / architect | Strategy, blueprints, quality control | Chirag |
| Full-stack developer | CMS, coding, site speed | You or your agency |
| SEO content writers | Long-form writing, data entry | You or your agency |
| UI/UX designer | Conversion layouts, graphics | You or your agency |
| Admissions team | Enquiry follow-up and closing | You |
Role
Project head / architect
Responsibility
Strategy, blueprints, quality control
Provided by
Chirag
Role
Full-stack developer
Responsibility
CMS, coding, site speed
Provided by
You or your agency
Role
SEO content writers
Responsibility
Long-form writing, data entry
Provided by
You or your agency
Role
UI/UX designer
Responsibility
Conversion layouts, graphics
Provided by
You or your agency
Role
Admissions team
Responsibility
Enquiry follow-up and closing
Provided by
You
No developer or writers in place? Not a blocker — I can help you source and brief them.
14 / Investment
Priced by scope, not by guess
Small
- Courses
- 1–2
- Institutions
- Up to 25
- Pages
- 80–120
- One-time setup
- ₹75,000–₹1,20,000
- Monthly retainer
- ₹35,000–₹50,000
- Success share
- 5–7% per seat
Most common fit
Medium
- Courses
- 3–5
- Institutions
- 25–50
- Pages
- 150–250
- One-time setup
- ₹1,20,000–₹2,00,000
- Monthly retainer
- ₹50,000–₹80,000
- Success share
- 6–8% per seat
Large
- Courses
- 6+
- Institutions
- 50+
- Pages
- 300–500
- One-time setup
- ₹2,00,000–₹3,50,000
- Monthly retainer
- ₹80,000–₹1,20,000
- Success share
- 7–10% per seat
Setup scales with pages.
Keyword research, sitemap, schema plan and briefs each grow directly with page count.
Retainer steps by tier.
Governance effort holds flat within a tier, then jumps.
Success share rises with moat.
A larger, more defensible portal justifies sharing more upside.
Development, content writing and design execution, budgeted separately. Cornerstone content writing and the lead-tracking build are available as separate add-ons.
Exact tier is locked after the scoping sprint, from your real course list and institution count.
15 / Next
A small first step, not a large commitment
Before either of us commits to a 16-week build, a scoping sprint of one to two weeks replaces every estimate on this page with your actual numbers: the exact keyword count, the exact page count, the schema plan and a fixed scope document.
It costs ₹15,000–₹25,000, credited in full against the setup fee if you proceed. If the sprint shows the opportunity is not there at the volume required, I will tell you — and you will have paid a small fee instead of a large one.
A conversation
Tell me what you are running now and what you spend.
Scoping sprint
One to two weeks, real numbers, fixed scope.
Resource alignment
Introduce your developer and writers, or I help you find them.
Kickoff
Sign-off and week 1 begins.