Skip to content

Chapter 1: How Search Engines Actually Work

Entries #1–#45 · 45 entries · 4 sections · Chinese edition
Why this chapter exists Before you optimize anything, you need a working model of what the engine does: crawl, parse, index, rank. This chapter builds that model in plain language and connects each stage to the levers you can actually pull.

1.1 What a search engine actually is

10 entries

1.2 Crawl, index, rank: the three-step loop

10 entries

1.3 How engines read pages and people

15 entries

1.4 Schools of SEO thinking and the quality bar

10 entries

Chapter SOP and interview questions

The four-stage diagnostic, in the order failures actually happen

Most “SEO problems” are a stage problem wearing a costume. Before you touch a title tag, find out which stage is broken. Work down this list in order — never skip ahead.

  1. Is the URL discoverable? Check that it is linked from somewhere the crawler already visits, appears in the XML sitemap, and is not orphaned. If the answer is no, nothing downstream matters.
  2. Is it crawlable? Fetch the URL with curl -I and confirm a 200. Then fetch it with a Googlebot user agent. Then check robots.txt with the URL Inspection tool’s live test — do not trust your own reading of the file.
  3. Is it renderable? Compare the raw HTML to the rendered DOM. If your primary copy, links or prices only exist after JavaScript runs, you are asking the renderer to do work that may be queued for days or skipped entirely.
  4. Is it indexable? Look for noindex, canonical pointing elsewhere, or a duplicate that won the consolidation. The URL Inspection tool tells you the Google-selected canonical, which is the only one that counts.
  5. Does it belong to a query? Search the exact title in quotes plus site:yourdomain.com. If the page does not surface, the page is not associated with that intent — that is a content and internal-linking problem, not a technical one.
  6. Is it competitive for that query? Rank tracking tells you position; the SERP tells you why. Read the top five results and ask what they have that you do not: format, freshness, entity coverage, brand.
  7. Is the click worth it? Impressions without clicks is a title and snippet problem. High position with low CTR means the result is being read and rejected.
  8. Does the click do anything? Sessions that bounce in three seconds are usually an intent mismatch — you ranked for a question and delivered a sales page.

Run this on five URLs per week for a quarter and you will have a real map of where the site loses traffic, instead of a list of tickets copied from an audit tool.

Building the model on a real site

The fastest way to learn how the engine behaves is to watch one page change. Pick a mid-traffic URL, log its status code, canonical, indexation state, position and clicks. Then make one change — a new internal link, a title rewrite, a redirect — and watch the same five numbers for four weeks. Repeat. After a dozen cycles you stop treating rank as a mystical event and start treating it as the output of a pipeline you can inspect.

Interview questions and answer frameworks

Q1: Walk me through what happens between publishing a page and it appearing in search results.

Framework: Four stages, and name the failure mode at each one. Discovery — the crawler has to find a link, from the sitemap, an internal page, or an external source. Failure: the page is orphaned. Crawling — it fetches the URL and gets a status code; failure: 404, 5xx, robots block, crawl budget spent elsewhere. Rendering and indexing — the HTML is parsed, JavaScript may be rendered, content is extracted, canonical is resolved, and the page is stored in the index. Failure: client-side-only content, noindex, duplicate consolidation to the wrong URL. Ranking and serving — the query is matched against indexed documents, results are assembled with ads, maps and AI answers, and the layout is personalised. Failure: the page is indexed but associated with the wrong intent. Saying this in order signals that you debug in order, which is the actual skill.

Q2: A page is indexed but gets no traffic. What are the possible causes, ranked by likelihood?

Framework: Rank by frequency, not by what sounds clever. First, intent mismatch — the page answers a different question than the one people type. Second, position — being indexed at position 40 produces almost no clicks; check rank before blaming the title. Third, snippet — position 8 with a 1% CTR usually means the title and meta are being ignored or the query is answered directly in the SERP. Fourth, cannibalisation — another URL on the same site wins the query and your page is the supporting actor. Fifth, seasonality or a market change. Then say how you would confirm each: GSC query report for intent, rank tracking for position, CTR versus expected CTR for snippet quality, the Pages tab for cannibalisation.

Q3: Explain the difference between crawling, indexing and ranking to someone outside SEO.

Framework: Use a library. Crawling is the van that drives around picking up new books. Indexing is the catalogue that records what each book says, so it can be found without reshelving the library. Ranking is the librarian deciding which five books to put on the desk when you ask a specific question. Then make the practical point: a book can be in the building (crawled) and not in the catalogue (not indexed), and a book can be in the catalogue and still never reach the desk (ranked too low). This is why “we submitted the sitemap” is not an answer to “why is our page not ranking”.

Q4: Why does Google sometimes ignore a canonical tag?

Framework: Because canonical is a hint, not an instruction. The engine weighs the tag against other evidence: internal links, sitemaps, redirects, content similarity, and historical signals. If five internal links use a different URL, or the “canonical” version is slower and thinner, the engine may choose the other one. The reliable fix is to make the signals agree — canonical tag, internal links, sitemap entry, hreflang and redirect all pointing at the same URL — rather than adding a stronger tag. Mention that you can see the chosen canonical in URL Inspection, and that this is the number to argue with, not your own tag.