Ghost recommendation button and open-web proof loop
Add Ghost's recommendation modal to signup and navigation, then let the open-web recommendation file turn those picks into discoverable proof.
Why this can grow a startup
Most newsletter recommendation systems disappear after the signup thank-you screen. Ghost lets publishers keep that motion alive in two places: the recommendations modal opens after signup and can also live behind a navigation link. Under the hood, Ghost publishes recommendations to a well-known JSON file and notifies other sites via Webmention. That makes the recommendation surface useful for readers and legible to other publishers at the same time. The page is not only a widget. It is part of the publication's public graph.
Source guidance
Ghost says the recommendations modal appears when a new member signs up, can be opened at /#/portal/recommendations from site navigation, adds recommendations to /.well-known/recommendations.json, and notifies the recommended site via Webmention.
Source-reported evidence
Source: Ghost Developer Docs: Recommendations
Ghost publishes recommendations to /.well-known/recommendations.json and exposes them through a modal at /#/portal/recommendations.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Ghost, Community, SEO is relevant to open web, recommendations, discoverability and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Ghost and Community, using evidence from Ghost Developer Docs: Recommendations as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.