Technote

SEO Intro

Series Technical SEO for marketers Part 1 of 8

How a page reaches search: crawl, render, index

"We are not in search" is not one problem. Each stage fails differently, and only by naming the stage do you get a request an engineer can act on.

You publish a new page and days later it is still nowhere in search. The conversation usually ends at “our SEO must be broken”, and that sentence tells nobody what to do. A search engine handles a page in several distinct stages, and each one fails in its own way. Name the stage where it stopped and your request instantly becomes a piece of work someone can pick up.

Discovery, crawl, render, index

The gates a page passes on its way to a results page — fail one and the next never begins

Discovery is simply knowing the address exists. A page listed in your sitemap, or linked from somewhere else, gets discovered. A page with no inbound link and no sitemap entry never reaches the starting line, however well it is written.

Crawling is actually requesting that address and receiving the HTML. If the server does not answer, answers too slowly, or is configured to keep crawlers out, the journey ends here.

Rendering runs that HTML the way a browser would, producing the final screen. If your content is drawn by scripts, nothing is visible until this stage completes. WordPress has an advantage here because it assembles the page on the server before sending it — though that is no guarantee: if stylesheets or scripts are blocked, the rendered result differs from what you see.

Indexing stores the result and makes it eligible to appear. One fact matters more than any other here: being crawled is not being indexed. Search engines do not keep everything they fetch; they decide separately whether a page is worth storing.

The same symptom, different failures

“We are not in search” describes one symptom with several possible causes — and each cause is addressed to a different person. Some are server settings, some are internal linking, and some are not technical at all.

What belongs in your request is not the symptom but one of these lines

“Crawled — currently not indexed”

This status turns up constantly in Search Console. It reads like a fault, but it is a judgement, not a breakage: the page was fetched, it was read, and for now it is not being stored.

Handing that to an engineer as “indexing is broken” usually produces nothing, because the server is fine and the tags are fine. What the page normally needs is on the content side — something that exists only here, rather than a near-repeat of another page. The exception is when several addresses carry the same content, which is a genuinely technical problem and gets its own part later in this series.

What you can check yourself

Five minutes before you raise anything: put the address into URL Inspection in Search Console. It shows how far the page got, what the crawler saw, and the indexing verdict, all on one screen. Attaching that screen to your request settles half the conversation before it starts.

The SEO archive continues these mechanics in more depth, and a full technical review of a site’s indexing state is part of our optimization program.

Next part

Once a page is indexed, the next question is how it looks in the results. The next part covers titles and descriptions — and how often the sentence you wrote is not the one that appears.

More on this topic

All technotes
₩270,000 · Join the program