Private corporate batches, live online cohorts and 1-on-1 mentoring in organic search engineering — crawlability, indexation, Core Web Vitals, content quality and structured data — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches SEO as an engineering discipline first: crawl, render and index as three separate stages that fail for different reasons, robots and canonical directives that quietly deindex whole sections, redirect chains and status codes verified from server logs rather than assumed, and JavaScript rendering diagnosed with the URL Inspection tool instead of guessed at. Sessions cover Core Web Vitals as real front-end work with field data, information architecture and internal linking, schema.org structured data for the SERP features that now sit above the blue links, and Search Console and log analysis used to separate an algorithm update from a deployment regression — with every technique demonstrated against a live site rather than described.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For SEO that means a trainer who has run it in production — organic search engineering — crawlability, indexation, Core Web Vitals, content quality and structured data — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private SEO batchSEO — search engine optimisation — is the practice of making a site discoverable, understandable and preferable to search engines so that it earns organic traffic without paying per click. It is not a marketing activity bolted onto a website; it is a property of how the site is built, structured, served and written, which is why the work splits between engineering and content and rarely succeeds when only one of those is involved.
The discipline has three layers. Technical SEO governs whether a page can be reached and indexed at all: robots directives, status codes, canonicalisation, redirect chains, XML sitemaps, JavaScript rendering, pagination, crawl budget on large sites, and site speed as measured by Core Web Vitals. On-page and content SEO governs whether the page deserves to rank for a query: matching search intent rather than a keyword string, information architecture and internal linking, title and heading structure, and the experience, expertise, authoritativeness and trust signals search quality guidelines describe. Off-page SEO governs external corroboration — links earned through genuinely useful work and digital PR rather than bought from a directory.
Modern SEO also has to account for how results are presented. A query may return featured snippets, People Also Ask panels, image and video packs, local results, product grids and AI-generated summaries before a conventional blue link. Structured data using schema.org markup is how a site describes itself in terms those surfaces can consume, and measurement in Google Search Console has to be read against that reality rather than against a simple ranking position.
Organic search is still the largest source of trackable, non-paid traffic for most businesses, and it is the one channel whose cost does not scale linearly with volume. That makes it the obvious place to invest when paid acquisition costs rise, which they consistently have.
At the same time, the ground moved. Search results now include AI-generated answers and expanded features that absorb clicks that used to reach sites, which has changed which queries are worth pursuing and which are not. Helpful-content and spam updates repeatedly removed traffic from sites built on thin, mass-produced pages, and the arrival of cheap generative writing made that failure mode far more common. Meanwhile Core Web Vitals turned a share of the ranking discussion into a genuine front-end engineering problem measured with field data, not opinion.
The result is that the profile of a valuable SEO practitioner changed. Keyword stuffing and directory submissions have been dead for over a decade; what pays now is somebody who can read a log file and prove what a crawler actually fetched, diagnose why a JavaScript-rendered route never gets indexed, fix a largest contentful paint regression with the front-end team, design an information architecture and internal linking model, mark up entities correctly, and tell an executive honestly which traffic loss was an algorithm update and which was a deployment.
The pipeline everything else attaches to. Discovery, crawling, rendering, indexing and ranking as five distinct stages that fail independently, what a modern results page actually contains, and an honest statement of what is known, what is inferred and what is folklore.
Topics: Discovery, crawl, render, index, rank — five stages, five failure modes · Crawlers, crawl budget and what actually limits it · The index: what gets stored, what gets dropped · Ranking systems, core updates and how change is communicated · SERP anatomy: features, panels, AI summaries and the shrinking blue link · Google, Bing and the practical differences · Separating documented behaviour from SEO folklore · Setting an honest expectation of timescale
The layer where the largest and cheapest wins usually sit. robots.txt and meta directives, status codes and redirect chains, canonicalisation and duplication, XML sitemaps, faceted navigation and pagination — and the deindexation accidents that follow a bad deployment.
Topics: robots.txt syntax, precedence and the crawl-versus-index distinction · noindex, nofollow, and why a blocked page cannot be deindexed · Status codes: 200, 301, 302, 304, 404, 410, 5xx and what each signals · Redirect chains, loops and migration mistakes · Canonical tags, duplicate content and parameter handling · XML sitemaps, index sitemaps and submission · Faceted navigation, filters and infinite crawl spaces · Pagination, hreflang basics and subdomain versus subdirectory decisions · Crawl budget management on large sites
Where modern sites break and traditional SEO advice stops helping. How rendering works as a deferred second pass, client-side versus server-side versus static rendering, and log file analysis as the only way to know what a crawler actually requested rather than what you assume it did.
Topics: The rendering queue and why indexation lags on JavaScript sites · Client-side, server-side, static and dynamic rendering compared · Hydration, routing and links that a crawler cannot follow · URL Inspection and rendered HTML versus source HTML · Single-page applications and history API routing · Server log collection, parsing and crawler verification · Reading crawl frequency, wasted crawl and orphan pages from logs · Diagnosing a site where the content is present but never indexed
Site speed as engineering work rather than a score to chase. Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, the difference between lab and field data, the front-end causes behind each metric, and how to raise the issue with engineers in terms they can act on.
Topics: LCP, INP and CLS: what each measures and what moves it · Field data versus lab data, and why they disagree · Chrome UX Report, PageSpeed Insights and Search Console reporting · Image formats, sizing, lazy loading and preloading · Render-blocking resources, critical CSS and font loading · JavaScript execution cost and main-thread blocking · Layout shift causes: ads, embeds, fonts and unsized media · CDN, caching and server response time · Writing a performance ticket a front-end engineer will accept
Deciding what the site should be about. Query research from multiple sources, classifying by intent, mapping queries to page types, designing a URL and category structure that scales, and building an internal linking model that distributes authority deliberately rather than by accident.
Topics: Research sources: Search Console, keyword tools, competitors, internal site search · Intent classification: informational, navigational, commercial, transactional · Reading the SERP to infer what the engine thinks the query means · Mapping queries to page types and avoiding cannibalisation · Topic clusters and content hubs · URL structure, taxonomy and category design · Internal linking: anchor text, depth, hub pages and orphan detection · Prioritising by opportunity rather than by volume
Why pages rank once they can be indexed. Satisfying intent rather than matching a string, title and heading structure, the experience-expertise-authority-trust framing from the quality rater guidelines, content refresh and pruning, and an honest position on generative writing.
Topics: Search intent satisfaction and content depth versus length · Title tags, meta descriptions and click-through behaviour · Heading hierarchy and scannable document structure · Image optimisation: alt text, file naming, sizing and formats · E-E-A-T signals: authorship, sourcing, citations and site reputation · Helpful content and the failure modes of mass-produced pages · Content refresh, consolidation and pruning decisions · Generative AI in content production: where it helps and where it causes damage · Accessibility overlap: semantic HTML that helps both users and crawlers
Describing the site in terms the results page can consume, then the variants most organisations eventually need. Schema.org markup and rich result eligibility, plus local, ecommerce, international and site migration work — the areas where mistakes are most expensive.
Topics: Schema.org vocabulary and JSON-LD implementation · Article, Product, FAQ, Organization, LocalBusiness and Breadcrumb types · Entity markup, sameAs and knowledge panel association · Rich result eligibility, validation and testing tools · Featured snippets, People Also Ask and AI summary optimisation · Local SEO: business profiles, citations, reviews and proximity · Ecommerce: faceted navigation, product variants and out-of-stock handling · International SEO: hreflang, ccTLD versus subdirectory, and duplicate risk · Site migrations: mapping, redirects, staging validation and rollback
Making it a repeatable function rather than a project. Earning links through work worth citing, Search Console and analytics as diagnostic instruments, distinguishing an algorithm update from a deployment regression, reporting to non-specialists, and running SEO alongside a release cycle.
Topics: How links are earned: original data, tools, digital PR and genuine utility · Evaluating link quality and recognising tactics that carry penalty risk · Search Console: performance, indexing, enhancements and their limits · Analytics integration and organic attribution honestly stated · Rank tracking: what it tells you and what it does not · Detecting a regression: deployment, algorithm update or seasonality · Recovering from a traffic loss with a systematic diagnosis · Reporting to executives without vanity metrics · Embedding SEO checks into the release process and CI
We rebuild the agenda around the tools you actually run.
Request a custom agendaCrawl a real site, find the pages that cannot be indexed and trace each one to the exact directive, status code or canonical responsible.
Compare source against rendered HTML on a JavaScript route, identify what is missing and choose a rendering strategy with its trade-offs stated.
Parse a server log sample, verify genuine crawler traffic and quantify wasted crawl by URL pattern instead of guessing at crawl budget.
Profile a slow page, attribute largest contentful paint to a specific resource, remove a layout shift and prove the change in field data.
Implement JSON-LD for two page types, validate it, and confirm eligibility for the SERP features those pages should be competing in.
Deliver a complete technical, content and authority audit for a real site with prioritised fixes, a diagnosis of any traffic loss and an ongoing operating rhythm.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.