Turn your help center into SEO-optimized blog content

Export your Zendesk help center articles with title, URL, category, article body, views, helpfulness score, and last updated date. If you cannot export everything cleanly, start with your top 50 articles by views or support deflection value. Add a column for SEO potential so you can prioritize later.

Use Google Search Console to identify help center URLs that already receive impressions or clicks from Google. Pull queries, impressions, clicks, average position, and CTR. These pages are your easiest wins because Google already sees some relevance. Mark articles with impressions but low CTR or low average position as expansion candidates.

Use Claude to review the article list and search query data. Ask it to separate articles that should stay as support docs from articles that can become educational blog posts. A support article titled “How to configure SSO” may become a blog post like “How SSO works for enterprise SaaS teams.” The goal is to expand the topic for prospects without duplicating the help article.

Analyze these help center articles and identify which can become SEO blog posts.

Help center articles:
{{help_center_article_list}}

Search Console query data:
{{search_console_data}}

For each article, output:
1. Keep as support-only, refresh support article, or expand into blog post
2. Suggested blog topic if applicable
3. Search intent
4. Target keyword or query cluster
5. Why this has SEO potential
6. What should stay in the help article
7. What should be expanded for a broader blog audience

Prioritize topics that prospects would search before becoming customers.

Use AlsoAsked to gather related questions for each selected blog topic. Capture questions around definitions, comparisons, setup, best practices, mistakes, pricing, alternatives, and implementation. Add these to your blog brief so the expanded article covers the full search intent instead of just rewriting the support doc.

Use Claude to create a structured brief for each blog post. Include target keyword, search intent, title options, outline, internal links, support article link, examples to include, FAQs, and what not to duplicate. The brief should clearly distinguish the blog’s educational purpose from the help center’s product support purpose.

Create an SEO blog brief from this help center topic.

Original help article:
{{help_article}}

Search query data:
{{query_data}}

Related questions:
{{related_questions}}

Company/product context:
{{company_context}}

Output:
1. Target keyword cluster
2. Search intent
3. Recommended title
4. Meta description
5. Article outline with H2s and H3s
6. Questions to answer
7. Internal links to include
8. Link back to original help article
9. Examples or screenshots needed
10. What not to duplicate from the help article

Make the blog useful to prospects and customers, not just a longer support doc.

Use Claude to draft the article from the brief, then edit in Google Docs. Keep the tone educational and practical. Add screenshots, diagrams, or examples where they help. Link back to the original help center article for step-by-step product instructions rather than stuffing those details into the blog post.

Write an SEO blog post from this content brief.

Brief:
{{seo_blog_brief}}

Original help article:
{{help_article}}

Brand voice:
{{brand_voice}}

Rules:
- Write for a broader audience than existing users
- Do not copy the help article word-for-word
- Explain the concept before product-specific instructions
- Include practical examples
- Include internal link suggestions naturally
- Keep the article helpful, not salesy

Output a complete draft with title, meta description, headings, body copy, and FAQ section.

Publish the posts in WordPress and add internal links in both directions: blog to help article, and help article to blog where appropriate. This creates a useful content pathway for prospects and customers. Monitor rankings, impressions, clicks, and support article engagement over time.