Ranking on page one is a prerequisite for snippet eligibility, but snippet selection itself is a separate extraction step layered on top of ranking, and that extraction step is sensitive to formatting and clarity in ways that ranking position alone doesn’t determine. This means a lower-authority page that has already earned a page-one ranking can win the featured snippet over a higher-authority competitor by providing content that Google’s extraction system can isolate as a cleaner, more self-contained, more directly matching answer. Authority gets you into the qualifying pool; it doesn’t guarantee you win the extraction once you’re there.
Why extraction and ranking are separate mechanisms
Snippet extraction is a distinct evaluation layered on top of ranking, rewarding a clear heading matching the query’s phrasing followed immediately by a self-contained, genuinely-marked-up answer (a real <ol>/<ul>/<table>, not a styled paragraph) over the raw authority of the domain it sits on. Because extraction rewards structural clarity rather than authority directly, a page ranking fifth or sixth can still win the snippet over a higher-authority page ranking first or second, if its answer is easier for Google’s system to isolate cleanly. What’s specific to the higher-authority-competitor scenario is what that gap actually looks like in practice and how stable a win against it tends to be.
Snippet ownership is unstable, and that instability is informative
Because extraction is re-evaluated against the current state of the qualifying pool rather than locked in once awarded, a snippet won on formatting alone tends to churn more visibly than one won on a combination of formatting and authority. If a competitor notices they’ve lost a snippet and restructures their own answer to match the winning pattern (adding the missing heading, converting prose to a real list, tightening the lead sentence), the extraction decision can flip back on the next crawl and re-evaluation cycle, often without any change in either page’s ranking position. This is a useful diagnostic in itself: if you’re tracking snippet ownership over time and see it moving back and forth between two URLs whose ranking positions haven’t changed, that’s a strong signal the contest is being decided on formatting and extraction clarity, not on authority or ranking shifts, since the ranking inputs are stable while the snippet outcome isn’t.
This has a practical consequence for how much monitoring effort a snippet win deserves. A snippet held against a genuinely higher-authority competitor is more fragile than one held against a competitor with comparable authority, precisely because the higher-authority competitor usually only needs a small structural fix to contest it back, whereas closing an authority gap takes considerably longer. Treating a low-authority snippet win as a stable asset, rather than checking periodically whether the competitor has since restructured their content, tends to produce silent snippet loss that isn’t noticed until a broader rankings or traffic review, well after the competitor’s formatting fix has already taken effect.
There’s also a query-type difference in how much this volatility matters. Definition-style snippets, a single sentence answering “what is X,” tend to be more contested and more volatile than list-based or table-based snippets, because a single competing sentence is a low-effort thing for a competitor to rewrite and resubmit for re-crawling, whereas a genuine table of comparative data or a multi-step ordered list represents more production effort to replicate well, and a competitor is less likely to invest in matching it purely to contest a snippet. This means the formatting investment described above tends to produce a more durable win on list and table-eligible queries than on single-sentence definition queries, which is worth factoring into which query types get prioritized when a team only has bandwidth to restructure a subset of pages competing for snippets against higher-authority domains.
A hypothetical illustration of an authority gap not mattering
Consider a hypothetical independent gardening blog, “Thistle & Bramble,” ranking sixth for a competitive query about soil pH testing, well behind a well-known national gardening brand holding the top position and the featured snippet. The national brand’s ranking page answers the question in the middle of a long, narrative paragraph with no dedicated heading matching the query’s phrasing. The smaller blog restructures its own already-ranking page with a heading closely matching the query and a tight, self-contained answer immediately beneath it, formatted as a real ordered list where the steps clearly warrant one. In this scenario, the snippet could plausibly transfer to the smaller blog despite the enormous authority gap, purely because Google’s extraction step rewarded the clearer, more isolatable answer, though the blog would still need to keep an eye on whether the national brand notices and restructures its own page in response, since a fix that simple could just as easily flip the snippet back on the next crawl.
Practical implication
Don’t treat “beat a higher-authority competitor for the snippet” as requiring outranking them first. It requires ranking well enough to be in the qualifying set (page one, ideally though not exclusively the top several positions) and then out-formatting them for extraction specifically. Audit the current snippet holder’s actual content structure around their answer: is it a clean, immediately-adjacent, well-marked-up answer, or is it buried in prose with a mismatched or absent heading. If it’s the latter, restructuring your own content with a heading that closely matches the query’s exact phrasing, followed immediately by a concise, semantically correct answer (a real list, real table, or a single self-contained sentence, depending on query type), is the highest-leverage formatting change available, and it doesn’t require closing the underlying authority gap to work. It does still require that your page is genuinely ranking on page one for the query first; formatting improvements on a page that isn’t in the qualifying set at all won’t produce a snippet regardless of how well-structured the content is.
