How search works
How search engines workThe five steps from discovery to rankingComponentsThe parts that make a search engine runCrawlingHow bots find and fetch your pagesIndexingHow a page gets stored so it can be foundCheck if indexedFour ways to confirm a page is on GoogleCrawling and indexing
Web crawlersGooglebot, Bingbot and the new AI botsGooglebotHow Google's crawler reads your siteRobots.txtRules, examples and a free testerXML sitemapCreate one, then submit it to GoogleCanonical tagPick the main version of a pageNoindex tagKeep a page out of search resultsRanking and results
Search engine rankingWhy one page appears above anotherGoogle ranking factorsWhat really matters, grouped simplyPageRankHow links pass value between pagesAlgorithmsTF-IDF, PageRank and modern rankingResults page (SERP)What each block on the page is forAI searchHow AI answers are built from the indexUnderstand
What is a search engineA plain definition with real examplesTypes of search enginesCrawler, meta, vertical, private and AIBrowser vs search engineTwo tools that people often mix upExplore
Best search enginesGoogle, Bing, DuckDuckGo and moreUses of search enginesThe everyday jobs that search handlesHistory of search enginesFrom Archie in 1990 to AI answersSearch engine indexing is the step where a search engine reads a page it has fetched, then files the useful parts in a giant database. Only pages that make it into that database can appear in results. This guide explains what happens inside the index, why some pages are left out and how to check your own.
Indexing means a search engine has processed a page and saved it in its index, the searchable library it uses to answer queries. A page that is crawled but never indexed cannot rank, which is why indexing problems make pages invisible.
The basics
Think of the index as the catalogue of a very large library. Crawling brings the books through the door, while indexing decides which shelf each one goes on.
In SEO, indexing describes the moment a search engine accepts a page into its stored collection. Before that point the engine may know the address exists, or it may even have downloaded the page, yet nobody searching can find it. After indexing, the page becomes one of the candidates the engine can pull up when a query matches.
Indexing sits in the middle of the wider process. A page is first discovered, then crawled by a bot, rendered so scripts can run, indexed, then ranked against other pages. Our guide on how search engines work walks through each of those stages, while this page stays focused on the index itself.
Being indexed is a requirement for ranking, although it guarantees nothing about position. An indexed page can still sit far down the results if stronger pages answer the query better.
Step by step
Once a crawler hands over a page, the indexing system breaks it apart into pieces it can search later. The work happens in a fairly predictable order.
Parsing is where the engine reads the page code to find the title, headings, body text, link anchors and image alt text. It also reads structured data, which is extra code that labels things like prices or recipes.
Tokenizing means splitting sentences into single words or short units. The engine then normalises those tokens, so Running, running and runs can all be treated as forms of the same word. This step is why a search for one word form usually finds pages that use another.
Finally the processed page is written into the index. Google describes this stage as analysing the text, images and video on a page, then storing that information in a large database spread across many computers.
Under the hood
Reading every stored page for every search would take far too long. Search engines solve that problem with a structure called an inverted index.
A normal document lists the words it contains. An inverted index flips that around, so it lists every word along with the documents that contain it. When you search, the engine jumps straight to the entries for your words instead of scanning pages one by one.
Here is a tiny example with three pages. Page A says cheap flights to Rome, page B says Rome travel guide, while page C says cheap hotels in Paris.
Edit any of the three pages below and watch the index rebuild itself, word by word. Then type a search to see which pages the engine can return straight from the index.
| Word | Pages | Position |
|---|
Every word is lowercased first, so Rome and rome share one entry. Greyed words are common stop words. Simple search systems often skip them, while modern engines like Google still read them because they can change the meaning.
Now imagine someone searches for cheap Rome. The engine looks up both entries, sees that only page A appears in each list, then passes page A forward as the strongest match. Stored positions also help, because words that sit close together usually signal a better match for a phrase.
Real indexes also keep extra details for each entry, such as whether the word appeared in a heading or a link.
Duplicates
The same content often lives at several addresses. Search engines try to keep one version in the index rather than storing every copy.
Duplicate URLs appear more often than most site owners expect. A product page might load with tracking parameters, a printer-friendly version or both HTTP and HTTPS addresses. Google groups these copies into a cluster, then picks one as the canonical URL, which is the version it shows in results.
A rel=canonical link in the page head tells engines which URL you consider the main one. Google treats it as a strong hint rather than a strict rule.
Redirects, internal links, sitemap entries plus a preference for HTTPS all help Google decide which version to keep as the canonical.
If your tag points to one URL while your internal links favour another, Google may choose a canonical you did not expect.
Google says duplicate content alone is not penalised. The main cost is that only one version appears, so make sure it is the right one.
Search Console
Search engines do not index everything they crawl. Google Search Console lists the reasons in its Page indexing report, and each label has a plain meaning.
| Status in Search Console | What it means in plain words |
|---|---|
| Crawled, currently not indexed | Google fetched the page but chose not to store it for now |
| Discovered, currently not indexed | Google knows the URL exists but has not crawled it yet |
| Excluded by noindex tag | The page itself asked to be left out of the index |
| Blocked by robots.txt | Your robots.txt file stopped Google from fetching the page |
| Duplicate without user-selected canonical | Google sees copies of this page but you have not named a main one |
| Duplicate, Google chose different canonical than user | Your canonical tag was overruled by other signals |
| Alternate page with proper canonical tag | This copy correctly points to the main version, which is fine |
| Page with redirect | The URL forwards visitors elsewhere, so the target is indexed instead |
| Not found (404) or Soft 404 | The page is missing, or it looks empty enough to be treated as missing |
Crawled currently not indexed is the status that worries people most. It usually means Google saw the page but did not judge it valuable enough yet, often because the content is thin or very close to other pages. Improving the page, then linking to it from stronger pages, is usually a better fix than asking for reindexing again and again.
Some of these exclusions are completely normal. Redirected URLs, alternate versions with a proper canonical tag and pages you deliberately set to noindex are meant to stay out.
Two different tools
Both can keep pages out of search, which is why they are easy to confuse. They work at different stages, so using the wrong one can backfire.
A noindex rule sits in a robots meta tag or in an X-Robots-Tag HTTP header. When Google crawls the page and sees it, the page is dropped from the index.
A Disallow line in robots.txt asks bots not to fetch a URL. It manages crawling, so it is useful for saving server load on endless filter pages.
The common mistake is combining the two. If robots.txt blocks a page, Google cannot crawl it, which means it never sees the noindex tag. A blocked URL can even appear in results without a description when other sites link to it. Google knows the address in that case, yet it cannot read the page.
So the rule of thumb is simple to remember. To keep a page out of search results, allow crawling while adding noindex. To stop bots wasting time on pages that do not matter, use robots.txt. Our crawling guide covers robots.txt rules in more depth.
Testing
There are quick checks anyone can run, along with a precise one for site owners. Each one tells you something slightly different about the page.
The fastest rough check is a site: search. Type site:example.com/your-page into Google, replacing the address with your own. If the page appears, it is very likely indexed. If it does not, that is a clue, although it is not proof, because Google says site: results are not a complete list of indexed pages.
For a reliable answer, use the URL Inspection tool in Google Search Console. Paste the full address, then read the verdict at the top of the report:
Bing Webmaster Tools offers its own URL Inspection feature for Bing results. If you want to learn more search tricks like site:, our guide to search skills lists the operators that still work.
Practical steps
You cannot force any engine to index a page. You can, however, remove obstacles while giving it clear reasons to keep your content.
After indexing comes ranking, where indexed pages compete for position. Our ranking guide explains what happens next, while the full search engine basics guide connects every stage.
Scale
Exact numbers are rarely published, so it is worth sticking to what the engines say themselves.
Google states on its own How Search Works pages that its index contains hundreds of billions of web pages. It also says the index is well over 100,000,000 gigabytes in size. Google has not published an exact page count in recent years, so any precise figure you see elsewhere is an estimate.
The index also changes constantly, since pages are added, refreshed or dropped every day. That is why a page that ranked last month can disappear after a site change, then return once the problem is fixed and the page is crawled again.
FAQ
Google crawls a page, renders it if scripts are needed, then analyses the text, images and links. It groups duplicates, picks a canonical version, then stores the result in its index.
It can take a few hours for pages on established sites, while new sites may wait days or weeks. Strong internal links along with a sitemap entry usually help.
Google fetched the page but decided not to store it yet. Thin content, near duplicates or weak internal links are the most common causes.
A noindex tag only affects the page that carries it, so the rest of your site is indexed as normal.
Google does not accept payment for crawling or indexing, so paid ads are kept separate from the organic index.
Keep learning