The SEO Elevator Pitch

Notes on a question most practitioners answer badly: what do you say when someone with budget authority asks what SEO is, and the elevator arrives at their floor in forty seconds? The prompt comes from Moz’s “Best of Whiteboard Friday” episode on the SEO elevator pitch, and the episode’s core observation deserves restating: the pitch fails when it describes the work, and lands when it describes the outcome.

Describing the work sounds like this: keywords, crawling, links, technical audits. Every term invites a follow-up question you cannot answer in an elevator, and the listener files the whole discipline under “mysterious website maintenance”. Describing the outcome inverts it: people are searching for what this company sells, right now, with intent already formed, and the work decides whether they find this company or a competitor. No term in that sentence needs defining.

Three structures survive the forty-second constraint. The demand framing: search is recorded demand, and ranking is market share of it. The compounding framing: paid visibility stops when spending stops, while earned visibility keeps paying (SEO as an asset, advertising as an expense). And the translation framing, useful with technical leadership: search engines are the largest user of the site after customers, and serving that user well happens to make the site faster and clearer for everyone.

Worth expanding on each structure, because they fail in different rooms. The demand framing works with anyone who owns a revenue number: recorded demand is a concept a sales leader already trusts, and “market share of searches” converts an abstract channel into a competitive scoreboard. Its weakness is the listener who asks how big the demand actually is, so know one number for your market before stepping into the elevator, even a rough one. A pitch that survives contact with “how much?” is worth ten that do not.

The compounding framing is the finance pitch, and it wins budget conversations that the demand framing only starts. An expense line competes with every other expense every quarter; an asset justifies patience. But the framing carries an obligation: if you call the work an asset, you must be able to say when it starts paying and roughly how you will know. The honest answer (months, not weeks, with leading indicators before revenue) is fine. The evasive answer undoes the framing on the spot, because assets with unknowable returns are called something else.

The translation framing is the one for a sceptical CTO, and it has the advantage of being verifiably true: the crawler is a user with the strictest patience budget on the site, and almost everything done for it (faster responses, cleaner markup, resolvable links, coherent structure) is indistinguishable from ordinary engineering quality. Pitched this way, the discipline stops sounding like a marketing tax on the roadmap and starts sounding like an unusually well-documented user-experience audit.

Two objections arrive in every elevator, and both have forty-second answers. “Why not just buy ads?” Do both: one rents attention and one earns it, and the rented kind sets the price of the earned kind wherever they overlap. “How long does it take?” Longer than a campaign and shorter than a rebrand, and the leading signs show up long before the revenue does. Neither answer is complete. Neither needs to be: the pitch’s only job is to earn the meeting where completeness belongs.

The episode’s quieter point: the pitch is not marketing fluff, it is prioritisation. A practitioner who cannot compress the discipline into one outcome sentence will also struggle to rank its tasks; the compression and the strategy are the same skill exercised at different lengths. The test recommended here for any pitch draft: read it aloud, count the words that would need defining for a smart outsider, and rewrite until that count is zero. The pitch that survives is also, usually, the strategy memo’s first paragraph.