Dwell Time
Dwell time is the length of time a visitor spends on a page before returning to search results or moving on somewhere else. Analytics tools infer it from the gap between two events, the page loading and whatever click comes next, so it is an estimate rather than a direct reading. Google has never confirmed using it as a ranking factor, but it still tracks fairly well with whether a page actually answered what someone came looking for.
Why dwell time matters
Search engines are trying to guess whether a result satisfied the person who clicked it. If someone stays on your page, reads, scrolls, and clicks onward, that looks like a match between promise and delivery. If almost everyone leaves within a few seconds, that looks like a mismatch. Dwell time is an indirect quality signal for exactly this reason: it doesn't measure whether your writing is good, it measures whether the page kept the promise made by the headline and the snippet that led someone there. A high dwell time is rarely an accident. It comes out of a clear structure, real substance, and content that answers the question the visitor actually had. That is what earns trust from readers, and it's also what tends to earn trust from the systems ranking or citing the page.
How dwell time is measured
Dwell time is usually captured through analytics platforms like Google Analytics, which time the interval between one page loading and the next click or page change. That method has a built-in blind spot: if a visitor closes the tab or the browser after finding their answer, without another click to mark the end of the session, that last visit can't be timed cleanly and often gets dropped or undercounted. Modern analytics setups compensate with extra signals like scroll depth and on-page interactions to approximate attention more honestly. It's worth keeping dwell time and bounce rate separate in your head: a short visit can still be a success if the page delivered the answer immediately, and a long visit isn't automatically a win if the visitor was just struggling to find something.
Common mistakes
The biggest mistake is trying to maximize dwell time as a goal in itself. Padding an article with a long preamble before the answer, or forcing extra clicks to artificially extend a session, produces frustration rather than engagement, and it tends to show up as a worse experience, not a better metric. A second mistake is reading the number in isolation: a long dwell time on a contact page usually means visitors can't find the form, which is a bad sign dressed up as a good one. A third mistake is reversing cause and effect. Strong dwell time is the output of good content, not an input you can dial up directly. Start with readability, load speed, honest subheadings, and a structure that answers the core question quickly and then goes deeper, and the number tends to follow on its own.
Relation to AI visibility
In classic search, dwell time works as an indirect signal of searcher satisfaction. In AI search, the mechanism is different again. Assistants like ChatGPT, Perplexity, and Google's AI Overviews select and summarize source passages up front, they don't wait to see how long someone lingers on a page before citing it. Ahrefs research has found that only around 6 to 8% of URLs cited by ChatGPT overlap with Google's top 10 for the same query, and roughly 80% of ChatGPT's cited URLs don't rank in Google's top 100 at all, which tells you AI citation runs on a meaningfully different selection process than search ranking does. What still carries over is the underlying cause of good dwell time: content that is thorough, clearly organized, and structured so a reader (or a model) can locate the answer fast. Ahrefs has also found that how often a brand gets mentioned across the web correlates with AI citation rate at roughly 0.664, about three times stronger than the correlation for backlinks at roughly 0.218, which makes earning genuine third-party mentions a more reliable lever for AI visibility than optimizing time-on-page ever was. Google's own guidance is consistent with this: no special markup or AI-specific version of your content is required for AI Overviews or AI Mode, so the honest move is still to write for the person reading, not for a metric.
Example
Picture an online shop for hiking gear. A shopper searches "correct shoe size for hiking" and lands on one of the shop's guides. Rather than pitching a product up front, the article walks through how to measure your foot properly, why extra toe room matters on descents, and includes a sizing table. The shopper reads for four minutes, scrolls to the end, and then clicks through to a pair of boots. That long, purposeful dwell time is a sign the page answered the real question, and it also happened to lead to a sale. Both outcomes came from the same source: content that actually helped.
Common questions
What is a good dwell time?
It depends entirely on the type of page. A long guide should hold readers for several minutes; a contact page or a pricing table might reasonably be short because the visitor found what they needed right away. Compare your numbers against similar pages on your own site rather than against some fixed industry benchmark, and pay more attention to whether visitors reach their goal than to the raw seconds on the clock.
Is dwell time a direct ranking factor?
No. Google has never confirmed it as a direct ranking factor, and it functions more as a byproduct of user satisfaction than a lever you can pull. The same applies to AI visibility: Google's own guidance says no special optimization is needed to be surfaced in AI Overviews or AI Mode. Improve the content that naturally produces a longer, more purposeful visit, rather than trying to move the number on its own.