Expert Tutorials

This is the site I describe elsewhere as Expert Tutorials, a CBSE commerce coaching center in West Delhi, built around Class 11 and 12 accountancy, business studies, and economics. The business itself is straightforward: local students need a tutor for commerce subjects, and they search for one the way everyone searches for anything local now, by typing their neighborhood into Google along with what they need. The site exists to be the answer to that search, for as many actual neighborhoods around the coaching center as it's worth competing for.

That's the entire strategic idea underneath the build, and it shows up structurally as eight nearly-identical landing pages, one per neighborhood: Dwarka Sector 7, 9, 10, 11, and 12, Bagdola, Palam, Raj Nagar, each its own folder, each its own roughly sixteen-kilobyte page, each essentially the same page with the location swapped. That's not laziness. It's the standard, well-understood local-SEO pattern: search engines rank a page for "commerce tuition Dwarka Sector 9" better when there's an actual page built around that exact phrase than when there's one generic page hoping to rank for eight different location searches at once. The tradeoff is real and I won't pretend it isn't. Eight pages that are ninety percent identical is a maintenance burden, because a change to the shared layout has to be made eight times instead of once, and a content update to the pricing or the course list means touching every location page individually unless you're careful. For a small business with a fixed local footprint that isn't expanding into new neighborhoods every month, that tradeoff is worth it. It wouldn't be if this business had ambitions to cover fifty locations.

What's around the landing pages

The location pages get the SEO attention, but they're not the whole site. Courses split into five real subject folders, accountancy, business studies, both Class 11 and Class 12 commerce broadly, and economics, each with its own dedicated page rather than one generic "courses" page trying to cover everything at once. A full blog with ten real, substantive articles: CBSE syllabus breakdowns, a genuinely useful piece on what comes after Class 12 commerce if a student wants to pursue CA, a parent-facing guide to the Class 11/12 commerce track. Those aren't filler posts written to hit a word count for SEO's sake. They're the kind of content an actual parent or student researching a coaching decision would want to read before committing, which is the difference between content marketing that works and content marketing that's just noise search engines eventually learn to ignore.

Beyond that: about, faculty, FAQ, student life, study resources, testimonials, and the unglamorous but necessary pages, privacy policy, terms of service, that a lot of small local business sites skip and shouldn't. A sitemap.xml listing thirty-eight real URLs and a proper robots.txt round it out, plus a genuinely custom 404 page instead of a bare server default, because a dead link on a site trying to look established shouldn't dump a visitor onto an ugly, generic error screen.

What the README gets wrong, briefly

Same story as a couple of the other client sites in this batch: the README claims a Next.js, React, Tailwind stack, and what's actually in the folder is plain static HTML with a CSS folder alongside it, no framework in sight. I've stopped being surprised by finding this particular mismatch across my own projects, which probably says something about how I write READMEs versus how I actually build things when I'm moving fast on a client site that doesn't need a framework's overhead. I write the boilerplate description first, from habit, and the actual implementation choice, usually the simpler one, happens later and doesn't always make it back into the docs.

Why static HTML was the right call here too

A coaching center's website is not an application. It doesn't need client-side state, it doesn't need a component tree, it doesn't need hot module reloading during development because the "development" here is mostly writing content and adjusting layout, not building interactive features. A static site is also, not incidentally, the fastest possible thing to serve and the easiest possible thing for a search engine to crawl completely and immediately: no hydration delay, no JavaScript execution required before the actual text content is visible. For a business whose entire growth strategy runs through local search rankings, serving content in the format search engines parse most reliably and quickly isn't a technical footnote. It's close to the actual product.

The honest tradeoff, stated plainly

Eight duplicated location pages is a real structural decision with a real cost attached, not a clean architectural pattern I'd defend as elegant. A more dynamic system, one template, a data file per location, rendered at build time, would be more maintainable long-term and is the version I'd build if this business were adding new locations regularly. It isn't, currently, and building the more sophisticated version for a business that doesn't need it yet would have been solving a problem that didn't exist yet at the cost of time that mattered more spent elsewhere. I chose the simpler, slightly uglier-to-maintain version because it matched the actual scale of the actual business in front of me, not the scale I could have imagined it growing into.

Why the blog isn't just there for search engines

It would have been easy to treat the ten blog articles as pure SEO bait, thin content stuffed with keywords, written to rank rather than to be read. I didn't build them that way, and it's worth explaining why that distinction actually matters commercially, not just ethically. Search engines have gotten meaningfully better at recognizing content written for algorithms instead of people, and thin SEO filler increasingly ranks worse than genuinely useful content does, not better. A real article walking a parent through what commerce students should expect after Class 12, written to actually answer that question well, does double duty: it ranks because it's genuinely relevant to real searches, and it converts because a parent who reads it and finds it useful trusts the tutoring center that wrote it more than one whose only content is location pages repeating the phrase "commerce tuition" as many times as possible.

The maintenance cost I'm honest with the client about

Eight near-identical location pages means eight places a pricing change, a new course offering, or an updated schedule has to be manually applied instead of one. I've flagged that tradeoff directly to whoever maintains this site going forward, because it's the kind of debt that's invisible on day one and expensive by year two if nobody's tracking it. The fix, when it's worth building, is a single templated location page rendered from a small data file per neighborhood: one change updates all eight instantly. I didn't build that version now because eight manual updates a year is a real but manageable cost for a business this size, and building the templated version today would have meant spending time on infrastructure the business doesn't need yet, instead of on the content and pages that were actually driving business results this month.

Full stack developer. Founder of Yashveer Labs. Eight neighborhoods, one business, and a site built to be found by exactly the people already looking for it.