One page, two front doors
SEO and GEO are not two projects. They are one document that has to satisfy two different readers: a ranking function and a retrieval step. One slider shows what they share, what they don't, and what it costs to add the second door a year late.
Stage The page
- 0
- 1
- 2
- 3
- 4
Tap a part of the diagram to open that stage.
Why both at once is the cheap option
The case for doing SEO and GEO together is not that generated answers are the future. It is arithmetic. Most of the work is shared, the differences are small and structural, the retrofit makes you pay for the shared part twice, and the delay costs visibility that never comes back. Done separately, this is not two projects. It is one project done twice.
What's inside
- 1 Everything starts from a single document — If those are two separate projects on your board, they will eventually produce two conflicting pages.
- 2 Most of the work is the same work — That overlap is not a coincidence. Both machines are trying to work out what the page is about without being able to ask you.
- 3 The differences are small, and they sit at the edges — The gap is real, but it is a fraction of the work — which is exactly why it is cheap to close it now.
- 4 Adding the second door later is not free — The multiplier comes from the task counts on screen and one rework fraction, not from a study. Move the fraction and the number moves.
- 5 The expensive part is the waiting, not the work — Two exponential ramps and one delay. The shape is honest; the exact number of weeks depends on your site.
Explorable Explanations
- How a search engine decides who gets found Ten blue links look like a list. They are the last frame of a pipeline that starts with a crawler and ends with a click curve. One slider walks the whole thing.
- How a generated answer picks the sources it will name An answer engine does not rank pages. It writes a paragraph and then decides which pages to credit for it. One slider follows a single question from fan-out to citation.
- How a drug is smuggled past the blood–brain barrier The brain refuses almost every drug molecule, and it is right to. One slider follows the trick the labs are trying instead: wrap the molecule in a bubble the wall already knows how to carry.
- How a robot draws the map of a room it has never seen A lidar returns a few hundred dots per sweep and no idea where it is. One slider walks from that cloud to a floor plan with the robot standing in the right spot.
- How two people type in one line without losing a letter Two cursors, one line, nobody holding the pen in the middle. One slider takes an index-based merge apart and rebuilds it out of addresses that sit between the letters.
- Why a quantum computer stops at a lattice Shor’s algorithm eats RSA in one move. The same machine gets almost nothing on a grid of points with a little noise added. One slider shows the difference.
- Cooling a building by pointing it at space A coating that stays colder than the air around it, in full sun, drawing no power at all. One slider follows the heat from the sun to the far side of the atmosphere.
- How a robot predicts the next second A text model guesses the next word. A world model guesses the next frame — mass, speed and gravity included. One slider walks the whole loop, from the camera to the catch.
- Proving a secret without revealing it One slider walks through the stages, the other adds rounds. Watch certainty climb to almost total while the secret stays a secret.
- Getting lithium out of brine: ponds versus direct extraction Move the slider through five stages and compare two ways of taking the same metal out of the same salt water.
- How a personalised mRNA cancer vaccine works Move the slider through five stages and watch how a tumour’s own mutations become the instructions that teach the immune system to find it.
- The edge of the app Everything arriving from outside is untrusted. Break one link at a time and watch where the chain stops and what the screen shows.
- How search over your documents works Move the sliders and watch a search pipeline decide what the model is allowed to see — and what happens when it is fed the wrong passage.
- Retries and slow responses The network drops in the middle of an operation. Press the button twice and see what ends up in the database — with an idempotency key and without one.
- How a language model writes The weights are frozen and nothing is remembered. Pull the sliders and watch the model pick the next piece of text, over and over.
- How a language model learns Pull one slider and watch a pile of random numbers turn into a prediction over a thousand training steps.
- Where electricity comes from Pull one slider and follow the energy from a river all the way to a pump that lifts water back up.