Recirculate your best content.
Automatically.

Content Recommendation is SUBJCT's automated content recirculation engine. It surfaces the most relevant next article for each reader from your existing archive, using the same entity and semantic intelligence that powers SUBJCT's other optimisation features.

The engine semantically understands your content and matches each reader to the most relevant next article on that basis - not by category, tag, or publish date alone. Recommendations are generated and served automatically; there is no manual selection step.

It reinforces structure. Because recommendations are built from the same entity and semantic relationships SUBJCT uses for internal linking, they follow the same topic clusters and entity pathways already established across your site, rather than operating as a disconnected "related articles" widget. The effect is a more coherent, entity-linked content structure, not just isolated recommendations.

Recirculating content and deciding which related articles to feature, on which pages has traditionally been a manual editorial task, actioned page by page. Content Recommendation automates that decision across your entire archive, removing the ongoing workflow from content and SEO teams.

Your content archive needs to be ingested into SUBJCT, as with the platform's other entity and semantic-driven features. Once ingested, Content Recommendation runs on the same underlying data, there's no separate configuration step to curate recommendations manually.

No. Standard related-articles plugins typically match on category, tag, or recency. Content Recommendation matches on entity and semantic relevance - the same analysis SUBJCT uses for internal linking - so recommendations reflect what content is actually about, and stay consistent with the rest of your site's entity structure.

Yes. It runs on the same entity and semantic intelligence as SUBJCT's internal linking, schema generation and tagging, so recommendations, links and structured data all draw from a consistent view of your content, rather than each feature working from its own separate logic.