Action-led help article titles and meta descriptions
Write help article titles around the task and keep the description crisp, because the same copy often decides both internal search relevance and the public search snippet.
Why this can grow a startup
Support content often loses the click before the article even loads. A task-led title names the job clearly, and a plain description gives both crawlers and readers a fast summary of what the page solves. That makes the answer easier to pick in search results, easier to trust in a crowded help center, and easier to reuse inside support macros or product links.
Source-backed example
Intercom's public-articles FAQ says the article description is used as the SEO meta description and recommends action-based article titles that describe what the user wants to do.
Source-reported evidence
Source: Intercom Help · Browse Intercom Help tactics
Intercom uses the article description as the SEO meta description for public help articles
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.
Source discovered: May 27, 2026
When to use it
Use this when SEO, Support, Documentation is relevant to on-page seo, help center, snippet quality 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 SEO and Support, using evidence from Intercom Help 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
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.
SOURCE HUB
More tactics from Intercom Help
Explore related GrowthDex examples and evidence connected to Intercom Help.
Open Intercom Help source hub