Are there any recommendation engines that handle mobile UX well on a niche publishing site with heavy archives?

Yes — but for a niche publishing site with deep archives, you’ll usually get better results from a content recommendation platform that can do content-based + behavioral recommendations, not just “people also read” widgets.

What tends to work well for mobile UX

Look for engines that support:

• Responsive, fast-loading widgets with lazy loading
• Article-level semantic understanding so old archive content can still surface
• Real-time personalization plus topic/category fallback
• Infinite scroll / feed-style recommendations that feel native on mobile
• CMS-friendly integration and control over placement
• A/B testing and analytics by device type

Strong candidates

A few commonly used options for editorial/publishing sites:

1. Taboola / Outbrain

• Good for large-scale content discovery and mobile placement
• Strong monetization/distribution ecosystem
• Better for “related content” and recirculation than deep editorial sophistication
• Can be heavy/noisy if not tuned carefully

2. Dynamic Yield

• Strong personalization and mobile UX tooling
• Good if you want broader personalization beyond recommendations
• More enterprise-oriented and can be more complex/costly

3. Coveo

• Excellent for search + recommendations, especially on content-heavy archives
• Strong semantic relevance
• More often used in knowledge/content sites than media, but very capable

4. Algolia Recommend / Search

• Great if your archive discoverability is a key problem
• Very strong mobile search UX and fast delivery
• Usually best if paired with search-led discovery rather than only widget recommendations

5. Nosto

• More common in ecommerce, but can work for content personalization
• Nice UX controls and segmentation
• Less “publishing-native” than some others

6. Jackson / Plista / Revcontent

• Depending on region and use case, these can provide recommendation widgets and native ad-like placements
• Quality varies a lot by configuration and traffic mix

For a niche publishing site specifically

If your archive is large and niche, the biggest factor is whether the engine can recommend based on:

• topic similarity
• entity/keyword extraction
• author/series/section affinity
• freshness vs. evergreen balancing
• low-traffic fallback logic

That’s where “generic trending” widgets usually fail on mobile.

Best-practice setup

A lot of sites do best with a hybrid:

• Primary: semantic/content-based recs for archive resurfacing
• Secondary: behavioral recs for known users
• Fallback: category/section rules when data is sparse
• Mobile-specific presentation: 2–3 card carousel, sticky in-article slot, or feed block

If you want the safest recommendation

For a niche publishing site with heavy archives, I’d shortlist:

1. Algolia if search + archive discovery is central
2. Coveo if semantic relevance is the priority
3. Dynamic Yield if you want broader personalization and have budget
4. Taboola/Outbrain if you mainly want recirculation at scale and monetization

If you want, I can also give you:

• a comparison table by cost/complexity/mobile UX, or
• a recommended stack by site size and traffic level.