Class 75 taught you to earn distribution through honest recommendations with a tracked trail. Search works on the same principle, one step earlier: someone types a question into Google before anyone has recommended anything. If you understand what they actually want in that moment, you can meet them with the right page. If you only chase keywords, you build pages that match words and miss people.

The same phrase can hide four different outcomes

Search intent is the job the searcher wants done. The industry uses four durable buckets:

• Informational: "I want to understand or learn." Example: "how to read a 10-K cash flow statement."
• Navigational: "I want to reach a specific place." Example: "Sonariq login" or "ByeBuy course map."
• Commercial investigation: "I am comparing options before deciding." Example: "best stock research software for filings."
• Transactional: "I am ready to act." Example: "sign up for source-linked research trial."

The same words can mean different jobs. Take "apple research." One person wants to understand Apple's earnings filing. Another wants a comparison of research tools that cover Apple. A third wants to open their existing research workspace and pull Apple's latest 10-K. Same phrase, three different desired outcomes — a taught explanation, a comparison table, a login screen. A page optimized for the wrong outcome loses even if it ranks.

That is why "keywords" alone mislead. A keyword is what was typed. Intent is what would count as success. Google's systems infer that success: which pages satisfied similar searchers and what result format — definition, list, tool, product page — resolved it. Your job is not to stuff the phrase ten times into a mega-page. It is to infer the outcome and build the page that delivers it.

The six parts of the answer journey

Learn the vocabulary once, in plain language:

• Query: what the person typed or spoke.
• Search result: the list Google returns — titles, URLs, snippets, images, video, maps, AI overviews depending on the query.
• Title: the clickable headline of your page in the results. It is a promise, not a label.
• Snippet (meta description plus extracted text): the short preview under the title. You suggest part of it; Google often rewrites it from your page.
• Landing page: where the click arrives. It must continue the promise, not restart it.
• Answer journey: everything after the click — scan, understand, act, return. A search visit that bounces in eight seconds was not a win.

Picture the journey as a chain:

query (job) → result list (options) → title + snippet (promise)
→ landing page (delivery) → next action (proof of satisfaction)

Break any link and search fails. A vague title earns no click. A clickbait title that the page does not honor earns a fast exit — and search engines notice patterns of dissatisfaction. A good page that never gets linked or indexed never enters the list at all (Lesson 76.3 covers that plumbing).

Sonariq: three queries, three different pages

Use the running product — Sonariq / Research Desk, a source-linked research tool — to make intent concrete:

1. "how to research a public company from filings" — informational. The searcher wants a method. The right page teaches the workflow: where filings live, which sections answer which questions, how to cite a claim, a worked example on a real filing. The next action is a saved checklist or template, not a hard signup push.

2. "best stock research software" — commercial investigation. The searcher is comparing. The right page is an honest comparison: what each tool does, where evidence comes from, pricing shape, who each fits, with screenshots and limits. If Sonariq hides its weaknesses here, the reader trusts a competitor's comparison instead.

3. "sign up for source-linked research" — transactional. The searcher has decided on the category. The right page is short, specific, and frictionless: what you get, what it costs, what happens after signup, a sample brief as proof, one form. A 3,000-word explainer here is friction, not thoroughness.

Notice the rule: one intent, one page shape. The informational page teaches. The comparison page compares. The signup page converts. Combining all three into one "ultimate stock research software guide + tutorial + signup" page serves nobody — the learner scrolls past pricing, the buyer scrolls past the tutorial, and both leave.

| Query shape | Likely intent | Right page | Wrong page |

|---|---|---|---|

| how / what / why / guide | Informational | Taught method with example | Product pricing page |

| brand + login / official site | Navigational | Direct destination, fast load | Blog post about the brand |

| best / vs / review / top | Commercial | Honest comparison with evidence | Thin affiliate list with no testing |

| buy / signup / price / trial near me | Transactional | Clear offer + proof + one action | Long essay with buried button |

Navigational intent deserves a special note for local work. "Tailor open Saturday near me" is navigational-transactional: the searcher wants a place, hours, and a booking path. The right page is a verified listing plus a simple booking page — not a blog essay about tailoring history.

Exercise: map ten real queries by intent

Create SEARCH-INTENT-MAP.md. Do not invent queries from imagination. Collect ten real ones from search suggestions, customer messages, community discussions, or support logs for your project:

1. Type your topic into Google and note the autocomplete suggestions and "People also ask" questions. 2. Pull five phrases from real humans — support inbox, Discord, comments, sales notes. 3. Add navigational variants people already use ("[your project] + login / pricing / template").

Then group them:

# SEARCH-INTENT-MAP.md — [Project]

## Informational (teach)
- Query: "___" → Page idea: "___" → Next action: checklist/template
- ...

## Commercial investigation (compare)
- Query: "___" → Page idea: "___" → Next action: comparison + trial link
- ...

## Transactional (act)
- Query: "___" → Page idea: "___" → Next action: signup/booking with proof

## Navigational (reach)
- Query: "___" → Page idea: existing page to fix → Fix: title/loading/link

Worked mini-example for ByeBuy Classroom: "what is RAG in simple terms" → informational lesson page → next action: glossary + next lesson link. "best AI course for building apps" → comparison intent → honest "who this course fits / does not fit" page. "byebuy course map" → navigational → make the map page load fast with a clear title.

Finish line: a SEARCH-INTENT-MAP.md with ten grouped queries and one distinct page idea per intent group — not one mega-page.

Verify quickly: cover the page idea and read only the query. Could a stranger guess which of the four jobs the searcher wants? If two groups point at the same page, split them.

Common failure mode: grouping by topic words instead of jobs — putting "how to cite filings" and "buy filing software" on the same page because both contain "filings." Words match; outcomes do not.

Check your understanding

1. Name the four intent types and give a Sonariq example of each. 2. Why can the same phrase need three different pages? 3. What breaks when a transactional query lands on a long informational essay?

Next

You can read intent. Lesson 76.2 teaches what earns the click and the bookmark — people-first pages with an original contribution, and how AI helps without producing thin filler.