--- title: "Mobile & Social Engagement for Publishers: Keep One-and-Done Traffic" description: "Mobile engagement for publishers, measured: mobile multi-page sessions +48% vs −23% comparison, social share doubled. The one segment that fell is printed too." url: https://www.artificialpoets.com/solutions/mobile-social/ site: Artificial Poets type: page date: 2026-08-09T06:31:06+00:00 modified: 2026-08-25T19:31:56+00:00 --- # Keep the Readers Who Never Stay "Two-thirds of my traffic is mobile and social one-and-dones — can those readers actually be kept?" [See it on my numbers](/request-a-demo/) · [Read the segment case study](/customers/equine-network-segments/) Horse & Rider · Ride TV · Equine Network · Equus Magazine · The Score · Equine Network Lockup ## The traffic that arrives does not stay The problem - **Facebook sends half what it did** — Referrals from Facebook to news sites fell 50% in twelve months, and X fell further. Social traffic is drive-by when it arrives at all. - **Engaged time is falling** — Average engaged time per mobile pageview has been declining quarter over quarter. The reader is already leaving when they land. - **One tap, one page, gone** — A mobile social visit is a single tap into a single article. Nothing on the page is built for what happens after they finish it. ## How we keep the readers who were never going to stay - **Built for one tap** The next article loads as the reader nears the end of this one, on mobile, with no click. The visit continues before they decide to leave. - **+48% on mobile** Mobile multi-page sessions rose 48% on enabled titles against a 23% fall on comparison titles. Social more than doubled. - **No added weight** One script, no layout shift, no hit to Core Web Vitals. The page is as fast as it was before the engine ran on it. ## The one-tap mobile visit can be kept. It has to be kept on the page. What changes on mobile Two-thirds of publisher traffic now arrives on a phone from social, Discover or search, reads one article, and leaves. That visit will not click a related-links box. It will not scroll to a footer. The Artificial Poets Platform loads the next article below the current one as the reader approaches the end, chosen for that reader in that session, with no tap required. The visit simply continues. It is one script, with no layout shift and no cost to Core Web Vitals, because a slower page would lose the exact readers it is meant to keep. On enabled titles, mobile multi-page sessions rose 48% against a 23% fall on unchanged titles, and social arrivals roughly doubled their multi-page share.[1] The segment everyone writes off is the one with the most headroom. **Introducing** ## Artificial Poets Platform One engine behind every solution on this site. It learns your archive and your readers, then acts inside your CMS, your templates and your ad stack. - It learns your archive: **Every story you have published, current again** — The engine understands each piece by what it is about, not when it ran or where it was filed. A feature from 2019 competes for the next slot on merit with one from this morning. - It reads the visit: **What a reader wants, without asking** — Interest builds from what someone actually does in the session. No login, no third-party cookies, nothing leaving your domain. Useful on the second pageview, not the tenth visit. - It chooses: **The right next read, not the popular one** — Someone comparing products and someone following a running story want different things. A most-read list gives both the same five links and serves neither. - It serves: **There before the reader leaves** — The feed, the recommendations, the search answer and the signup ask all run on the same engine, in your templates and your ad stack. Any slot that arrives with them is yours to sell. - It proves: **A lift you can defend, or we say so** — Every deployment runs beside titles that did not get it, plus a serving pause. That is how a result becomes a number you can take to a board instead of a vendor claim. ## FAQ ### Our widgets already move these metrics — how do I know this lift is causal, not a traffic-mix shift? The comparison is within-segment: mobile with the Platform against mobile without it, social against social, same network, same weeks. A mix shift toward mobile cannot manufacture a within-mobile change. And during a four-week pause in serving, the lift went from +12.2% to −2.7%, then recovered to +6.9% when serving resumed — the metric follows the mechanism. ### Discover and social swing wildly. Does this still pay off when a channel dries up? Depth is the hedge, not a bet on any channel. The mechanism runs on your pages after the click, so it does not depend on a referrer's algorithm; it makes whatever arrives worth more. Measured on mobile: +48% multi-page sessions while the comparison group fell 23%. ### What do you know about a first-time visitor mid-scroll, and what powers the first recommendation? Nothing when they land; enough by the time it matters. Interest builds from what the reader does in the session, no login and no third-party cookies, and it is useful on the second pageview, not the tenth visit. The first recommendation is matched on meaning from your own library. ### Does a deeper first session become a second visit? We do not claim it: our measured record is within-session depth, and we say so. The trade's numbers point the right way, Chartbeat finds two-page first visits return at 2.75 times the rate of one-page visits, but return frequency belongs to your newsletter and push loops, which stay yours. ### Every engagement widget we've tried degraded Core Web Vitals on mobile. What does yours do? Readers continue voluntarily — continuation past the fourth served article runs 70–82%, a curve forced pageviews don't produce. On the measured deployments, mobile page experience improved over the same window (not claimed as caused; claimed as not harmed). The baseline month exists partly so your own vitals data can arbitrate. ### We spent years unwinding platform dependency. Isn't this another algorithm we don't control? The recirculation happens on your domain, inside your session, measured in your analytics — internal traffic is the one channel a platform cannot repossess, and it is the channel growing across publishers (38% → 41% of arrivals, per Chartbeat). If serving stops, your pages are your pages. See internal traffic as a channel. ### Readers distrust feeds. Will visible personalization read as one? It renders as your site doing its job: your templates, your library only, no external links and no bait pressure. The optimization target is readers finishing articles, not clicking them, and editors can pin, exclude and constrain what may serve. Nothing about it looks or behaves like a feed. ## Related - [Mobile Multi-Page Sessions Rose 48%. The Comparison Titles Fell 23%.](https://www.artificialpoets.com/customers/equine-network-segments/) — Mobile readers are the hardest to keep. Six of seven segments improved. The one that didn't is printed. - [Serve the Next Article Before They Leave](https://www.artificialpoets.com/use-cases/infinite-article-feed/) — "What happens after a reader finishes an article — can the next one just be there?" ## Unlock new revenue with our AI Artificial Poets Platform can help you with [Book a demo](/request-a-demo/) ## Questions this page answers ### Can one-and-done mobile and social visitors be kept? Yes, and it is measured. Mobile multi-page sessions rose 48% on enabled titles while the comparison group's mobile fell 23%. Social arrivals, the definitional one-and-done, roughly doubled their multi-page share, 8.6% to 17.2%. The mechanism works inside the first visit, so drive-by traffic is exactly where it applies. ### How does it keep readers who arrive from feeds? Interest builds from what the reader does in the session: no login, no third-party cookies, nothing leaving your domain. The profile is useful by the second pageview, not the tenth visit, which is what makes algorithmic arrivals keepable. The next article loads as the reader scrolls, in your templates, at a mobile weight your own vitals can arbitrate. ### How much does it cost? There is no public price list; pricing follows network size and formats. The baseline month exists partly so your own Core Web Vitals and analytics can arbitrate the mobile question, before and after. A JavaScript tag, four baseline weeks, and a quarter is the full cost of knowing. ### Who is this for? Publishers whose traffic mix went algorithmic: 60%+ mobile share, social and Discover arrivals that spike and vanish, engaged time eroding quarter over quarter. If most of your audience is one-and-done, the headroom is exactly there: the hardest segments moved most, and the one that still fell is printed. ### What are the alternatives for keeping drive-by traffic? App-install banners and newsletter interstitials ask for commitment before interest exists. Engagement widgets that chase clicks degrade the mobile experience they depend on. The within-segment comparison is the test that matters: mobile against mobile, social against social, same network, same weeks. ### How do I get started? The integration is one JavaScript tag per title, carried out by our team; your templates and vitals budgets stay yours. Four weeks of measurement-only baseline, then enablement on a named day, with the segment cut, mobile, social, search, direct, part of the published record. Eight weeks from authorization to a measurable effect.