The idea, in plain English
Start here.
A search engine finds pages, fetches and processes their content, stores selected information in an index, and chooses results for a person’s search. These are separate steps. A page can work perfectly in your browser and still need investigation before you know how it appears in search.
Imagine you publish a useful repair guide today. It is tempting to search its title immediately and expect to see it. Before deciding that something is wrong, it helps to understand what has to happen between publishing the page and someone discovering it. This lesson gives you a practical model you can use without knowing how to code.
A few words you’ll meet.
OPEN WHAT YOU NEED ↙Query
The words someone enters into a search engine, such as ‘why is my faucet dripping?’
Crawler
Software that requests webpages and follows links to find information. Google’s main search crawler is called Googlebot.
Index
A search engine’s organized collection of information about content it has processed. Being accessible is different from being included in it.
Rendering
Processing a page’s code to work out the content a browser would display. This can matter when scripts supply important information.
Start with the person’s question
A search begins with a task. Someone may want to understand a dripping faucet, compare repair with replacement, or find a local business that can help. A result is useful when it helps with that particular task. The same website can contain a good explanation for one question and an unsuitable answer for another.
Search results are therefore not one permanent league table of websites. Think about a specific page and a specific query. Your first job is to make the page useful and understandable; your investigation then asks whether a search engine can find, process and select it. You do not need to memorize a list of supposed ranking factors to start.
Follow a page before someone searches
First, the engine needs to learn that a URL exists. A URL is simply the address of a page. A link from an already known page can reveal a new address. A sitemap — a file listing pages a site wants to make known — can also help communicate it. Knowing the address does not mean the page has already been visited.
During crawling, software requests the page’s content. The engine processes what comes back and may render it to understand content produced by scripts. Indexing concerns the information it processes and includes in its organized collection. Later, when a person searches, the engine selects results for that query. Each stage answers a different question, so evidence from one stage should not be used as proof of the next. A later technical lesson explains how to check rendered content.
- Discovery: does the system know the address?
- Crawling and processing: can it retrieve and understand the content?
- Indexing: what information is included in the index?
- Serving: what is selected for this particular search?
A page’s route into search
Read the evidence before choosing a fix
Suppose Harbor Workshop publishes a fictional faucet-repair page. You can open its address, but cannot find a link to it from the website. That is a useful observation about navigation. It suggests checking the discovery route; it does not prove that Google has never seen the page, because another route may exist.
Now suppose you open the same address and see a ‘page not found’ response. That is a different problem: the request did not return the intended page. Rewriting its description will not repair the missing destination. Finally, seeing a page for one search tells you something about that search, at that time. It does not establish how every other query behaves.
Make one small, repeatable check
Choose one important page rather than trying to inspect an entire website at once. Open it from a sensible starting point, such as the relevant service or category page. Confirm that the link goes to the intended address and that the main information is present. Record what you actually observed in a short note.
If you have authorized access to Search Console, its URL Inspection information can add evidence about Google’s view of a page. You can learn the model here without an account: the important habit is to keep a browser observation, a search-system observation and a guess in separate columns. That makes the next action easier to explain to another person.
- Record the exact page address and the question it should answer.
- Follow the link route and inspect the content that arrives.
- Write down the observation, one unknown and the next check.
Three observations, three different next steps
These are fictional observations about Harbor Workshop. Notice how a useful action follows the evidence instead of starting with a generic ‘do more SEO’ instruction.
| What you observe | A useful next check | What it does not prove |
|---|---|---|
| The repair page has no link from its service parent. | Look for other discovery routes; consider a clear link from the relevant parent. | That no search engine knows the URL. |
| The old address returns ‘page not found’. | Check whether the page moved and where the intended content now lives. | That the page needs more keywords. |
| The guide appears for one exact search. | Record that query and investigate other relevant queries separately. | That it appears for every customer question. |
Put it into practice
Turn three observations into a useful check
Use the three fictional observations in the worked example. You do not need a live site, a paid tool or a Search Console account.
- For each row, name the part of the process you can actually observe: discovery route, delivery or query selection.
- Write one sentence beginning ‘This does not yet tell me…’.
- Choose one next action that someone else could repeat. Avoid a general task such as ‘optimize the page’.
Keep your working notes in your own document. This page saves only your completion check, not your answers or customer data.
Check your understanding
Make the call.
Choose an answer for each question. Then compare the reasoning.
You have a useful next step.
- Discovery, crawling, indexing and query selection answer different questions.
- A working browser request is useful evidence, with a limited meaning.
- Choose a next check that follows from what you actually observed.
Completion is your own learning record. Quiz scores and practice checks are saved separately, on this browser.
Sources & context
The sources below explain the factual foundations and editorial methods used in this lesson. Worked examples, planning models and exercises are illustrative teaching material.
- Google: How Search works
The factual basis for crawling, indexing and serving results.
- Google SEO Starter Guide
Discovery through links, useful content and the limits of inclusion promises.
- How Google organizes information
Official context for link discovery, processing and index organization.