Last time you followed a message from your browser out to a server and back. Today the question is different: when you type words into a search box, how does the computer decide which pages to show you, and in what order?
You will act as the search engine yourself, then try real searches and notice what changes the order of the results.
Quick recap hook: ask one student what a browser does when you type a full web address (it fetches that exact page). Then ask what happens when you type a few words instead. The gap between those two answers is today's lesson.
Keep this under four minutes. Devices stay closed until the exploration step.
A web browser is the app you open pages in (Chrome, Edge, Firefox, Safari). You give it an address, and it fetches that page.
A search engine is a service that finds pages matching the words you type, then puts them in an order it thinks will help you. Google, Bing and DuckDuckGo are search engines. You usually reach them through a browser.
Behind the scenes a search engine roughly does three jobs:
Ranking is the part people argue about, because different goals produce different orders. You are about to try that for yourself.
Name the mix-up up front: many students say "I Googled it on Chrome" and treat browser and search engine as the same thing. Hold up or point to the browser window and the search box inside it as two different tools.
Walk the three jobs (crawl, index, rank) against the diagram. Keep rank at "word match and other signals"; do not list recency, links or keyword stuffing here. Those land in the feed-ranker takeaways once students have felt them.
Misconception to head off: "the first result is always the best page." Ranking is a guess at usefulness for a goal, not a truth ranking.
Someone has searched for how do I start coding. Four pages could answer them. Put the pages in the order you would show them, then compare your order with how a real ranker orders them under two different goals.
For each goal, read the takeaway: it tells you what that ranking was optimising for.
Run this on the board or on student devices. Give two minutes for a first personal ranking before anyone reveals a goal order, so students have a stake in the comparison.
After the "most useful" goal, ask who put the shop page first and why. After the "count the words" goal, name keyword stuffing in plain language: repeating the search words on purpose to climb the list.
Look-fors:
If time is tight, run only the two goals and skip a full class debrief; the takeaways carry the teaching point.
Run 3 short trials; write one line each for the first two. Your teacher leads Trial 1. Then pairs try Trial 2. Trial 3 is extra if you finish early.
Trial 1: search vs address (whole class). Watch your teacher type a full site address (for example www.met.ie) into the address bar and open that page. Then watch them type only the words Irish weather forecast into a search engine. What is different about how the page was reached each time?
When Trial 1 is done, move on:
Write in your copy / on the exit slip:
If you do Trial 3, add one more line: detail added / signal that seemed to matter (words, freshness, location, popularity).
Done looks like:
Devices open now. Prefer a search engine the school does not block; any major one is fine. If filtering is heavy, pick safer queries yourself (school subjects, public data) and put them on the board.
Pacing: Trial 1 whole-class on the board (about 3 minutes) as a fast win on address versus words. Put a visible timer up for Trial 2 (about 3 minutes) and take one shouted observation before anyone starts Trial 3. Trial 3 is optional extension only; do not hold the class for it. Bring everyone back with about two minutes spare so two volunteers can read one capture line each before Make sense.
The done bar is two capture lines (Trial 1 and Trial 2). Circulate and push for specific observations ("the RTÉ page jumped above the forum when I added the year") rather than "it changed".
Common snag: students type a search into the address bar and the browser quietly forwards it to a search engine. If that happens, name it: the browser still did not rank pages itself; it handed the words to a search engine.
A browser fetches the page you name. A search engine finds candidate pages and ranks them for a goal.
Ranking is not a single score of "best page". It weighs signals such as word match, how recent a page is, and who links to it. Change the goal, or change the words, and the order changes with them.
Three cold-call prompts if the room is quiet: (1) browser vs search engine in one sentence each, (2) one signal the ranker used that you had not weighed, (3) why stuffing a page with the search words is a weak long-term strategy.
If anyone still calls the top result "the best page", ask "Best for whose goal?" and point back to the two feed-ranker takeaways by name so the interactive and the live searches feel like one idea.
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.