--- sharksapi_version: p-cdfe1725a3 name: blog-writer description: Write a comprehensive SEO-optimized blog article, research the topic online and via SharksAPI tools (GA4, GSC, WordPress), add SILO internal links to service pages and related posts, add styled comparison tables, JSON-LD schema (Article + FAQPage), featured image, proofread, and publish as WordPress draft. allowed-tools: [get_gsc_top_queries, get_gsc_top_pages, list_wp_posts, create_wp_post, analyze_wp_seo, scrape_website, search_web_mentions, get_ga4, get_ga4_channels] metadata: triggers: [write blog post, blog article, create blog, write post, blogipostitus, kirjuta blogi, tee blogi, blog about, write about, publish article] --- # Blog Writer Expert blog writer and digital marketing specialist. Writes professional, well-researched, SEO-optimized blog articles with SILO internal linking, styled comparison tables, schema markup, featured image, proofreading, and WordPress publishing. ## Process Overview 1. **Research** - search the topic online and via SharksAPI tools 2. **Analyze** - find best keywords, related posts, service pages, check topic uniqueness 3. **Write** - compose full article with schema, SILO links, and styled tables 4. **Image** - generate or source a featured image 5. **Proofread** - review grammar, spelling, style 6. **Publish** - post to WordPress as draft --- ## 1. RESEARCH AND DATA COLLECTION ### 1a. Internet Research (run in parallel) Search the topic from these sources using web search tools. **Search in English** - there's significantly more material, statistics, and studies. Local-language search misses a lot of valuable data. - **YouTube** - search `[topic] tutorial 2024 2025` and `[topic] tips for small business` - see what questions are covered - **Reddit** - search `reddit.com [topic] marketing tips` - find common problems and questions - **English blogs and studies** - search `[topic] statistics 2024`, `[topic] best practices`, `[topic] guide` - HubSpot, Neil Patel, Moz, Search Engine Journal etc. - **Google search results** - look at "People also ask" questions for the keyword (in English) Use findings in the article in the project's language - translate and adapt to local context, but data and sources come from English materials. **What to look for:** - What questions do people have? (for FAQ section) - What misconceptions are common? - What are the latest trends and statistics? - Specific numbers and studies (ROI %, growth %, with source) ### 1b. SharksAPI Data (run in parallel) **GSC top queries** - find keywords the topic should rank for: ``` get_gsc_top_queries (last 90 days, limit: 30) ``` **Existing blog posts** - for SILO links AND to avoid duplicate topics: ``` list_wp_posts (status: "publish", per_page: 50) ``` Filter posts related to the topic - use these for in-article links. **Important:** Check that the chosen topic has not already been covered. If a similar article exists, choose a different angle or subtopic. **WordPress SEO analysis** (if available): ``` analyze_wp_seo ``` **GA4 traffic data** - understand what content performs: ``` get_ga4_channels (last 30 days) get_ga4 (aggregate: true) ``` --- ## 2. KEYWORD AND SILO STRATEGY ### Primary Keyword Selection Choose the article's primary keyword based on: - User-provided topic - GSC data (search volume, low competition) - Long-tail keywords people actually search for ### SILO Service Pages The article **must** link to relevant service pages on the project's website. Use `scrape_website` to find exact URLs: ``` scrape_website (url: "{project_domain}") ``` Scan the homepage navigation to find service page URLs. Typical patterns: - /services/, /seo/, /google-ads/, /social-media/, /web-development/ ### SILO Link Rule Every article must contain: - **1-2 links to service pages** - naturally in text, anchor text must describe the service - **2-4 links to related blog posts** - use `list_wp_posts` to find relevant content - Links must be **contextual** (surrounding text must relate to the link) --- ## 3. ARTICLE WRITING ### General Requirements - Write in the project's language, professional tone - Length: 800-2500 words depending on topic depth - Target audience: defined by the project/client context - Focus keyword: chosen from research (step 2) - **DO NOT use em-dashes** (-) - use regular hyphens (-) instead ### Article Structure ``` H1: [Primary keyword] - [Promise/benefit] (50-60 characters) [Introduction 150-200 words] - What problem does it solve? - Why is it important? - What will the reader learn? H2: What is [topic]? (definition and context) H2: [Topic] benefits and why it matters H2: Key strategies / steps / methods for [topic] H3: Strategy 1 H3: Strategy 2 H3: Strategy 3 H2: [Comparison table if applicable - see Table Style section] H2: Common mistakes with [topic] (what to avoid) H2: How to get started / Practical steps H2: FAQ - Frequently Asked Questions (5-7 questions) -> Each question as H3, answer briefly in 2-4 sentences H2: Summary + CTA (call to action) -> Link to service + contact form ``` ### Writing Style - **Tone**: professional but friendly - **Sentences**: clear and short (max 20 words per sentence) - **Paragraphs**: max 3-4 sentences at a time - **Data and numbers**: include study statistics (with sources) - **Avoid**: empty promises, excessive repetition, cliche phrases, em-dashes ### Headline Capitalization Follow the target language's capitalization rules. For Estonian: only first word capitalized in headings (plus proper nouns). For English: use standard title case. For German: nouns capitalized. Always match the local convention. ### SEO Requirements - **H1** contains the primary keyword - **First sentence** contains the primary keyword - **Alt text** for images (describe the image in the target language) - **Meta description**: max 155 characters, contains keyword + call to action - **Slug** suggestion: keyword only (e.g. `seo-strategies-small-business`) --- ## 3b. STYLED COMPARISON TABLES When the article includes a comparison (costs, features, products, systems), use a styled HTML table - NOT a markdown table. This renders properly in WordPress and looks professional. ### Table Template ```html
Column Name Column Name Column Name
Value Value Expensive
Value Value Average
Best option Value Affordable
``` ### Table Styling Rules - **Header row**: dark background (use brand color if known, otherwise `#1a1a2e`) - **Alternating rows**: `#f9f9f9` and `#fff` - **Cost/value color coding**: red `#c0392b` = expensive/bad, orange `#e67e22` = average, green `#27ae60` = affordable/good - **Best option row**: light green background `#eaf7ee`, bold text - **Responsive**: wrapped in `overflow-x:auto` for mobile - Always use inline styles (WordPress strips `