Related Posts
Show a few genuinely relevant articles at the end of a post so readers keep going.
What it adds
A block of suggested articles below each post, chosen from tags, topic, and recency.
What your agent is told to do
5
What your agent is told to do
5-
1
Score candidates from signals the app already has: shared tags from Labels and Tags or AI Topic Tagging, the same category, and closeness in publish date. Combine them into one ranking rather than picking the first tag match.
-
2
If the app already has Semantic Search or an AI Recommendation Engine, use it as the similarity source and treat tags as a tiebreaker. Do not build a second relevance system beside the one that already exists.
-
3
Compute relations in the background and store the result. Ranking the whole archive on every page view will be the slowest part of the article page.
-
4
Give the block a graceful fallback: when nothing scores well, show recent posts from the same category, and when there is still nothing, render nothing rather than an empty heading.
-
5
Do not suggest posts purely by popularity. A view-count ranking sends every reader to the same three evergreen articles and the rest of the archive never surfaces.
Edge cases it handles
8
Edge cases it handles
8- A newly published post has no tags and no signal to match on. Fall back to the same category and to recency rather than showing an empty block on every new article.
- The current post must be excluded from its own suggestions. It scores highest against itself on every similarity measure.
- Drafts, scheduled posts, and posts behind a paywall or permission check must never appear as suggestions. Filter by the same visibility rules the index page uses, not just by a published flag.
- Without a diversity rule, a handful of heavily tagged evergreen posts will appear under every article. Cap how often any single post can be suggested, or mix in a slot chosen from less-surfaced content.
- Retagging a large archive triggers recomputation for every affected post. Queue that work in batches so a bulk tag edit does not stall the site or the job queue.
- A deleted or unpublished post must drop out of stored relations immediately, not on the next scheduled recompute.
- Suggestion links need their own tracking or link attribution if the app measures navigation, otherwise there is no way to tell whether the block works.
- Reserve the block's height before the suggestions render so the end of the article does not jump under a reader who has just scrolled there.
Definition of done
9
Definition of done
9- Every published post shows relevant suggestions or nothing at all, never an empty block.
- A post never suggests itself.
- Drafts, scheduled, and access-restricted posts are absent from all suggestions.
- No single post appears in more than a capped share of suggestion blocks across the archive.
- Relations are precomputed and the article page does not run a ranking query on request.
- A bulk retag recomputes affected relations in batches without blocking publishing.
- The block occupies reserved space and does not shift the page when it loads.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Newsletter Archive
Newsletter Archive
Turn sent email issues into browsable web pages that new readers can find and read.
What it does
A public archive of past newsletter issues, each with its own permanent page and a subscribe path.
How it works
- 1 Store the sent version of each issue rather than regenerating it. An archive built by re-rendering a template will drift the moment the template changes, and old issues will stop matching what subscribers actually received.
- 2 Convert the email markup to web markup on the way in: strip the table scaffolding, the fixed pixel widths, and the inline styles that only exist to survive an email client, and render the result in the app's normal article styles.
- 3 Reuse the app's existing publishing states rather than adding a second one. An issue should move from sent to archived through the same Draft and Publish States machinery the rest of the content uses.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/newsletter-archive
Help Center
Help Center
Give customers a searchable help site they can read before they open a support ticket.
What it does
A public help site of articles grouped into collections, with search, browse, and a contact fallback.
How it works
- 1 Treat the article as the single source of help content. If the app already has Contextual Help, Knowledge Base Chat, or an AI knowledge base drafting flow, point them at these same records rather than keeping a second copy of the answers that will drift.
- 2 Index articles into the app's existing search rather than standing up a separate search box with its own ranking. Extend Global Search and reuse the existing match highlighting so a result looks the same wherever it appears.
- 3 Give every article a stable slug and every collection an ordered list of articles, and show breadcrumbs from the collection down to the article so a visitor who landed from search knows where they are.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/help-center
Blog
Blog
Publish articles from inside the app to public pages with authors and categories.
What it does
A blog with authored posts, categories, scheduling, and public article and index pages.
How it works
- 1 Scope this honestly. The minimum coherent version is a post with a title, body, author, category, publish state, and a public page at a stable URL, plus an index and a feed. Defer multi-language content, per-post custom layouts, and a general page builder rather than half-building them.
- 2 Do not build a new editor. Extend the app's existing Rich Text Editor or Markdown Editor with whatever a post needs, and inherit its autosave, unsaved-change warning, and undo instead of reinventing them.
- 3 Reuse the app's existing Draft and Publish States and Scheduled Publishing rather than adding a second publish workflow for posts. Reuse SEO Setup for titles, descriptions, and social previews.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/blog
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.