--- 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://preview.artificialpoets.com/solutions/mobile-social/ site: Artificial Poets type: page date: 2026-08-09T06:31:06+00:00 modified: 2026-08-18T02:10:14+00:00 --- # Keep the Readers Who Never Stay **Measured on live deployments** "Two-thirds of my traffic is mobile and social one-and-dones — can those readers actually be kept?" Yes, measured on the segments everyone writes off: mobile multi-page sessions rose 48% against a 23% comparison decline, and social's multi-page share roughly doubled, 8.6% to 17.2%. [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 problem, in your numbers Mobile and social are most of your audience, the worst of your yield, and the fastest of your erosion. Discover, now most of Google's traffic to news, is the same story sharpened: spikes you cannot explain or keep. That combination is also where the headroom is. - **61%+** Mobile share of pageviews in every world region (Chartbeat, Q4 2025) - **26s** Average engaged time per pageview, declining quarter over quarter (Chartbeat) - **−50%** Facebook referrals to news sites, 2019–2025; X referrals −75% (Press Gazette / Chartbeat) - **−23%** Mobile multi-page sessions over nine months on titles that change nothing (our panel) ## The segment cut, including the casualty Multi-page change by segment over nine months, Platform titles against unchanged titles. One segment fell on both sides: direct, down 19% with the Platform against 35% without. We print it rather than footnote it. - **+48% vs −23%** Mobile multi-page sessions, with the Artificial Poets Platform against without it - **+99% vs −4%** Social arrivals, with the Artificial Poets Platform against without it - **8.6% → 17.2%** Social multi-page share with the Platform ## The evidence, at its honest tier - **Social arrivals** — multi-page share 8.6% → 17.2% (+99%) vs −4% without the Platform - **Mobile** — +48% multi-page sessions with the Artificial Poets Platform vs −23% without it, over nine months - **Direct** — −19% with the Platform vs −35% without it — the one segment that fell, printed, not footnoted - **The lift was not mobile-only** — search arrivals +59%, tablet +88%, desktop +29% — it simply landed hardest where the headroom was - **Network context** — multi-page sessions overall +46% (10.3% → 15.1%) with the Platform vs −16% (12.0% → 10.1%) without it, same nine months. Traffic did not grow — this is a depth result, and we say so **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://preview.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://preview.artificialpoets.com/use-cases/infinite-article-feed/) — "What happens after a reader finishes an article — can the next one just be there?" - [Internal Traffic Went From 38% to 41%. That’s the Whole Strategy.](https://preview.artificialpoets.com/blog/internal-traffic-strategy/) — While publishers fought over shrinking external channels, the largest single "referrer" in the industry quietly became the publisher's own site: internal traffic rose from 38% to 41% of total publisher traffic as search and social receded. Three points of share sounds incremental. It is not — it is the only channel that grew, and the only one you own outright. - [Session Depth Assessment](https://preview.artificialpoets.com/resources/session-depth-assessment/) — Two numbers from your analytics place your single-page rate and depth distribution against a continuously measured publisher panel. ## See how this works on your titles Thirty minutes on your analytics. We tell you what share of your sessions stop at the first page, and what this would realistically move first for a setup like yours. You leave with the annotated read. No deck. [See it on my numbers](/request-a-demo/) How these numbers are made: [the measurement method](/solutions/measurement/). Figures from a multi-title publisher network measured continuously, August 2025 to May 2026. Last updated August 15, 2026. ## 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.