SEO is the practice of making a website easy for search engines to find, understand and trust, so that it appears when people search for things the site genuinely answers. That is the whole definition. Everything else, from title tags to Core Web Vitals to link building, is a detail of how you do it.
This guide is the hub for the SEO basics section of the site. It covers the mechanism (how Google turns a URL into a result), the concept that matters most (intent), the three areas every programme has to cover, and a realistic plan for the first 90 days. The sub-guides linked at the end go deeper on each piece.
What SEO actually is
Search engines are matching systems. On one side is a person with a question, typed or spoken, often badly phrased. On the other side is an index of pages. The engine's job is to pick the handful of pages most likely to satisfy that person, in that moment, on that device. SEO is the work of making your pages the obvious pick.
That framing matters because it rules out a lot of nonsense. You cannot trick a matching system for long. You can only become a better match: clearer about what a page is for, easier to retrieve, and more credible than the alternatives. When I say I build SEO systems that compound, this is what I mean. Every page you add that is a clean match makes the site easier to understand as a whole, and that understanding carries over to the next page.
In India the practical picture is simple: Google dominates search, most sessions are on mobile, and a growing share of queries are in Hindi or a regional language, or in a mix of English and a regional language typed in Latin script.
How Google works: crawl, render, index, rank
A search engine has to do four separate jobs before your page can appear for a query. Each one can fail independently, and each failure has a different symptom. If you learn nothing else from this guide, learn this chain.
- Crawl
- Render
- Index
- Rank
Crawl
Googlebot discovers URLs through links, sitemaps and previously known addresses, then fetches them. Crawling is limited by budget: a server can only serve so many requests, and Google will not spend unlimited effort on a site. Pages nobody links to, pages blocked in robots.txt, and pages buried behind endless faceted URLs often never get fetched at all. The symptom is "Discovered, currently not indexed" or simply absence from Search Console. I cover the mechanics in the crawlability and indexability guide.
Render
Fetching HTML is not the same as seeing the page. Modern sites build content with JavaScript, so Google runs the page in a headless browser to execute that code. This happens in a second wave, later than the initial crawl, and with limits. If your main content, links or canonical tags only exist after JavaScript runs, there is a window in which Google sees an empty shell. The JavaScript SEO guide walks through how to test this.
Index
Once Google has the rendered page, it decides whether to store it and under which URL. Duplicates get folded into a canonical. Thin pages, near-copies and pages that look like low-value templates may be fetched and then dropped. Indexing is a judgement call, not a right. The symptom here is "Crawled, currently not indexed", which is one of the most misread reports in Search Console. It usually means quality or duplication, not a technical block.
Rank
Only indexed pages compete. At query time Google retrieves candidates and orders them using signals about relevance (does the page answer this?), quality (is it trustworthy and useful?), and context (location, language, device, freshness). Ranking is the only step most beginners think about, yet it is the last step in the chain. A page that is not indexed has no ranking to improve.
Search intent: the concept that decides everything
Every query carries an intent, meaning the outcome the searcher wants. Google's ranking systems are tuned to satisfy that outcome, which is why a beautifully written article can sit on page three for a query where every result is a product listing. The page is not bad; it is the wrong type of answer.
The common classification is informational (learn something), navigational (get to a specific site), commercial (compare options before buying), and transactional (buy or do something now). That is a useful start, but I find a second axis more practical: what format does the searcher expect? A query like "best UPI apps" wants a comparison list. "UPI transaction limit" wants a short factual answer, probably with a table. "UPI app download" wants an app store link. The words overlap; the intent does not.
The simplest way to read intent is to look at what already ranks. If the top results are all guides, write a guide. If they are all category pages, you need a category page. If the results are mixed, the intent is mixed and you have a choice. The search intent guide goes into how to classify queries at scale, and the keyword research guide shows how to build that into a plan.
SERP features: the page is no longer ten blue links
A modern results page is a composite. Depending on the query you may see featured snippets, People Also Ask boxes, AI-generated overviews, local packs with maps, product grids, video carousels, image blocks, knowledge panels and sitelinks, all before or around the organic results. Each feature is a signal about intent, and each one changes how much traffic a given position actually sends.
| SERP feature | What it tells you about intent | What it means for your page |
|---|---|---|
| Featured snippet | A direct factual or definitional answer is wanted | Lead with a concise answer; structure it as a list, table or short paragraph |
| People Also Ask | The topic has a cluster of related questions | Cover those questions explicitly; they often map to H2s or an FAQ |
| Local pack | The searcher wants something nearby | This is a local SEO problem: Business Profile, reviews, location pages |
| Product grid / shopping | Transactional, comparison-stage | Product and category pages with structured data, not blog posts |
| Video carousel | Showing beats telling for this query | Consider video, or at least a page that includes one |
| AI overview | Google believes it can synthesise an answer | Make your page the most extractable, citable source; see AI SEO |
I treat the SERP as the brief. Before writing or building anything, I look at the live results for the target queries, in the right country and on mobile, and note which features appear. That tells me the format, the depth and the realistic click-through before I spend anything.
The three pillars: technical, content, authority
Every SEO programme has to cover three areas. They are not equally important for every site, but a serious weakness in any one of them caps what the other two can do.
Technical
Can search engines reach, render and index the right pages efficiently? This covers crawlability, site architecture, internal linking, canonicals, speed and structured data. It is the plumbing. When it is broken, nothing else flows. The technical SEO guide is the full treatment.
Content
Do you have pages that match real intents, cover topics completely, and are organised so that the site is obviously about something? This is where most of the long-term growth lives. See the content SEO guide and the topical authority guide.
Authority
Do other credible sites, people and entities reference you? Links are still the most visible form, but mentions, citations and brand searches count. This is the slowest pillar to build and the easiest to fake badly. The link building guide covers what actually works.
How they interact
Technical work has a ceiling: once the site is clean, more technical work does not add traffic. Content has a floor: without enough coverage, links have nothing to lift. Authority is a multiplier on both. I plan programmes in that order: fix, build, then amplify.
Technical SEO has a ceiling, content has a floor, and authority multiplies whatever is left.
What a beginner should do in the first 90 days
If you are starting from zero on a real site, here is the sequence I would follow. The goal of the first quarter is not traffic. It is a site that can be measured, is fully indexable, and has a plan worth executing. Traffic follows from those three things; it rarely precedes them.
Days 1–10: set up measurement
Verify Google Search Console for every property variant, connect analytics, and record a baseline of indexed pages, impressions, clicks and the queries you already appear for. Without this, you will never know whether anything you do later worked.
Days 10–30: fix what blocks the chain
Run a crawl of the site. Look for pages blocked by robots.txt, noindex tags left over from staging, redirect chains, broken internal links, missing or self-contradicting canonicals, and important content that only appears after JavaScript. Fix the issues that stop crawl, render or index first. A structured audit is the fastest way to get this list if you cannot build it yourself.
Days 30–50: understand demand
Do keyword research with intent in mind. Group queries into topics, identify which existing pages map to which topics, and list the gaps. In India, expect search volume numbers to be small or missing for many useful queries; trust the SERP and your Search Console data more than the tool estimate.
Days 50–75: fix and build the obvious pages
Improve the pages that already get impressions but rank poorly: sharpen titles, lead with the answer, add missing sections, link to them from relevant pages. Then build the two or three highest-value missing pages. Quality over count.
Days 75–90: connect and review
Audit internal links so every important page is reachable within a few clicks and is linked from pages that are topically related. Compare against your baseline. Decide what the next quarter's plan is based on what moved, not on what you hoped would move.
Common myths that waste beginners' time
"SEO is about keywords on the page"
Keyword density was a weak signal twenty years ago and is noise today. Search engines model meaning, entities and relationships, not word counts. A page that covers a topic clearly and completely will contain the relevant terms naturally. The semantic SEO guide explains how this works under the hood.
"More pages means more traffic"
More pages means more things for Google to evaluate. If those pages are thin or near-duplicate, they dilute the site and can drag down pages that were doing fine. I have written about this in publishing more is not the answer. Coverage of a topic matters; volume for its own sake does not.
"Submit your site to Google and wait"
Submitting a sitemap helps discovery. It does not guarantee crawling, and it never guarantees indexing. Pages get indexed because they are reachable, distinct and worth storing. If a sitemap full of URLs is sitting at "Discovered, currently not indexed", the fix is architecture and quality, not resubmitting.
"Rankings are the goal"
Rankings are an intermediate metric. They vary by location, device, personalisation and the SERP features around them. A position-one result under an AI overview and four ads may send fewer clicks than a position-three result on a clean page. Measure clicks, conversions and the business outcome. I wrote more on this in rankings are not the goal.
"AI search makes SEO irrelevant"
AI-driven answers in Google and in assistants still retrieve from an index of crawled, rendered, indexed pages. The fundamentals are the entry ticket. What changes is that extractability, clarity and entity-level credibility matter more, which is an argument for doing the basics better, not for abandoning them.
Go deeper
The sub-guides in this section take each foundational idea further than a hub can.
- What is SEO? A fuller definition, how it differs from paid search, and where it fits in a business.
- How Google Search works. The crawl, render, index and rank chain in detail, with the Search Console reports that show each stage.
- Search intent. How to classify queries, read the SERP as a brief, and avoid building the wrong kind of page.
From here, the natural next hubs are keyword research and technical SEO. If you want a suggested order for all of it, the SEO roadmap lays one out.
Frequently asked questions
How long does SEO take to show results?
It depends on what is broken. If a site has technical problems that block crawling or indexing, fixing them can show in weeks. Building content coverage and authority on a competitive topic is a multi-month programme. Be suspicious of any fixed timeline given before someone has looked at the site.
Do I need to know how to code to do SEO?
Not to start, but you need to read HTML, understand what a redirect and a canonical tag do, and be able to inspect a rendered page. The further you go into technical SEO, the more useful it is to understand how the site is built so you can specify fixes a developer can implement without guessing.
Is SEO different in India?
The mechanics are the same. The context differs: Google's share is very high, most traffic is mobile, search volumes for specific queries are often small or unreported in tools, and many queries are in Hindi or regional languages, sometimes in Latin script. Plans built on US desktop assumptions tend to miss all of that.
What is the difference between SEO and paid search?
Paid search buys placement for as long as you pay. SEO earns placement by being the best available match, and the results persist and compound as the site grows. They complement each other: paid data is a fast way to test which queries convert before investing in organic pages for them.
Which single thing should a beginner fix first?
Make sure the important pages are crawlable, render their content without depending on JavaScript, and are indexed under one canonical URL. Everything else assumes this. Check it with Search Console's URL inspection tool rather than assuming.
Where this connects
This guide is the starting point for everything else on the site. The thinking behind it is formalised in the SEO strategy framework, tested in experiments like indexing orphan pages, and applied in the technical SEO and content architecture case study. If you would rather have someone build the system with you, that is what I do as an SEO consultant.