Best for
- B2B SaaS teams with a useful but under-leveraged help center
- Content teams that need practical SEO topics grounded in customer questions
- Support teams that repeatedly answer the same educational questions
Find support articles with search potential, expand them into useful blog posts, and turn existing customer answers into organic growth assets.
A prioritized list of help center articles that can become SEO blog posts, plus expanded drafts optimized for search intent.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Help centers are full of real customer questions, but they are usually written for existing users rather than prospects searching on Google. By identifying which support topics overlap with search demand, you can turn practical answers into educational blog content. This creates SEO assets that are grounded in actual user needs instead of keyword brainstorming alone.
Expected results
Content opportunities identified
10-30 blog topics
A mature help center usually contains many repeated customer questions, but only a subset will have broad search demand and blog potential.
Production time
1-2 hours per draft
The existing help article provides source material, while AI helps expand it into a broader SEO article with intent-driven structure.
SEO advantage
Customer-validated topics
The topics come from real support demand and Search Console data, reducing the risk of creating content no one needs.
Support benefit
Better internal linking
Blog posts can educate searchers broadly while linking to specific help articles for product instructions, improving both discovery and support navigation.
Step-by-step workflow
The first 3 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
45-60 min
45-60 min
Start with Zendesk articles that solve recurring problems, explain important concepts, or attract meaningful traffic. Work in zendesk, google search console, and google docs and capture the concrete operating details: source page, target query, search intent, audience question, evidence, draft URL, internal links, and review status. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that every claim has a source, every assumption is labeled, and unsupported claims are removed; the expected handoff is A candidate list that combines help-center value, search evidence, exclusions, and ownership.
A candidate list that combines help-center value, search evidence, exclusions, and ownership.
High impressions with low clicks can signal an opportunity, but first check whether the help article is appearing for an intent it was never meant to satisfy.
30-45 min
30-45 min
Use Claude to score each candidate on external audience relevance, search opportunity, business fit, available expertise, risk of duplication, and need for a broader explanation. Work in claude and google search console and capture the concrete operating details: source page, target query, search intent, audience question, evidence, draft URL, internal links, and review status. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A ranked shortlist of help-center topics that justify a separate SEO article.
A ranked shortlist of help-center topics that justify a separate SEO article.
Do not promote a support article into a blog post merely because it already exists. The topic needs a broader reader question.
30-45 min
30-45 min
For each approved topic, use Claude to state what belongs in the blog post and what remains in the help article. Work in claude and zendesk and capture the concrete operating details: source page, target query, search intent, audience question, evidence, draft URL, internal links, and review status. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the output is specific enough for the next person to use without guessing what happened; the expected handoff is A content boundary for every topic that prevents duplication and conflicting product guidance.
A content boundary for every topic that prevents duplication and conflicting product guidance.
Link to the help article for volatile click-by-click instructions. Keep the blog durable enough to survive interface changes.
Pro workflow preview
Previewing 3 of 8 steps
Get the remaining 5 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Score these help-center topics for blog expansion.
Candidate articles and Search Console data:
{{candidate_articles}}
Business priorities:
{{business_priorities}}
Target audience:
{{target_audience}}
Score each topic from 1 to 5 on:
1. External audience relevance
2. Search opportunity
3. Business fit
4. Available expertise and examples
5. Distinct value beyond the help article
6. Duplication risk
7. Accuracy or maintenance risk
Return:
- weighted total
- recommended action: expand, keep as support only, merge, refresh first, or reject
- reason
- primary search intent
- human review needed
Do not infer demand from impressions alone. Do not recommend exposing private, security-sensitive, or account-specific instructions. A content and product owner will approve the final shortlist.Define the editorial boundary for this help-center topic.
Help article:
{{help_article}}
Target reader:
{{target_reader}}
Search evidence:
{{search_evidence}}
Product context:
{{product_context}}
Return:
1. Primary blog question
2. Search intent
3. What the blog should explain
4. What must remain in the help article
5. Product mention limit
6. Examples or evidence needed
7. Recommended link from blog to help
8. Recommended link from help to blog
9. Duplication or maintenance risks
10. Product-owner questions
Do not copy procedural product instructions into the blog unless they are stable and approved. Do not create a second source of truth. Mark any product claim that needs verification.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
A reusable FAQ generation system that turns real customer questions into website FAQ sections and valid FAQPage schema markup.
A scalable system for producing credible comparison pages with search intent research, balanced positioning, proof points, and reusable page templates.
Create a repeatable SEO refresh system that updates old posts with current data, stronger structure, better search alignment, and improved CTAs.