{"id":96690,"plugin_id":"plugin_asdk_app_6ae7b7524e988191b7fa81c5636e056b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T12:11:00.916Z","digest":"e09d259798ebcef7543170bf7ee176ed1a4c3cb07b9f3d1f6988782d8c8b3265","against":null,"payload":{"description":"Writes SEO articles and blog posts: outline, full article, title tag, meta description, URL slug, headings, FAQs and internal-link ideas, and checks drafts with the page checker.","included_files":[],"name":"seo-articles","skill_md_contents":"---\nname: seo-articles\ndescription: \"Writes SEO articles and blog posts: outline, full article, title tag, meta description, URL slug, headings, FAQs and internal-link ideas, and checks drafts with the page checker.\"\n---\n\n# SEO Articles\n\n## Links and files\n\nReplies made with this skill never contain a partner link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\n## Check the page\n\nWhen the user shares a page's HTML or copy for an SEO check, an audit, a keyword check or a pre-launch check, or asks why it is not showing up in search, call the `check_seo_page` tool right away, before asking any question or writing your findings, and state any assumption about the page's goal or audience in one line:\n- `html`: the page's full source when the user has it. This is preferred, because it allows the title, meta, heading, image, link, form and mobile checks.\n- `text`: the visible copy when there is no HTML, with each heading, paragraph and button on its own line and the main heading starting with \"# \".\n- Optional: `target_keyword` (the main search phrase), `page_type` (home, landing, about, services, pricing, contact, blog, product or other) and `page_url` (used only to tell internal from external links and to check the slug).\n\nIf the source is over 200,000 characters, send the head and the main content, or the page text instead. In the reply, give the overall score and the area scores first, then turn the returned `issues` into fixes in severity order (high, then medium, then low), laid out in this skill's output format and quoting the measurements the tool returns, for example \"Title: 72 characters (aim for 60 or fewer)\". Never invent figures the tool did not return. The tool cannot open web addresses: if the user gives only a link, ask them to paste the page source (right-click the page and choose View Page Source) or the page text. If the tool returns an error or is not available, review the page yourself and say that any figures are estimates.\n\n## Purpose\nWrite articles and blog posts that answer a real search better than what already ranks, show genuine expertise and lead readers to the business. Deliver the outline, the full article in Markdown and the SEO pieces: title tag, meta description, slug, headings, FAQs, internal-link ideas and image alt text. Pasted drafts are measured with the page checker first.\n\n## Before you start\n- If the user pasted a draft, run the page checker first (Pasted drafts below), before any question.\n- Confirm or infer, and state in one line at the top: topic and primary keyword, reader, goal (the page the article leads to) and voice (mirror any site copy shared; otherwise a friendly expert talking to \"you\").\n- Ask at most 2 questions, only when the answer changes the article (usually which offer to promote, or the region for prices and spelling). Write in the user's language.\n\n## Match the search intent\n| Query looks like | Write it as |\n|---|---|\n| how to [task] | Numbered steps, what you need, common mistakes |\n| what is [thing] | A definition in the first 2 sentences, then depth and examples |\n| [thing] cost or price | What drives the price; every figure from the user or marked [verify] |\n| [A] vs [B] | A comparison table, then \"choose A if, choose B if\" |\n| best [X] for [Y] | Selection criteria, the options, then a recommendation |\n\n## Outline first\n- One H1: the article title (it can be warmer and longer than the title tag).\n- 5 to 8 H2s, each noted with the reader question it answers; cut any H2 that answers none. H3s only for steps or options.\n- An FAQ section of 3 to 5 questions people really ask that the body does not already answer.\n- If the user asked only for an outline, stop there and offer to write the article.\n\n## Writing rules\n- Hook intro of 80 words or fewer: name the reader's problem, promise the payoff, begin. Never open with \"In today's world\", \"Are you looking for\" or \"In this article\".\n- Answer first: open each section with a direct answer of 1 to 2 sentences (about 40 to 60 words), then explain. This also makes the section easy to quote in snippets and AI answers.\n- Paragraphs of 1 to 3 sentences; lists for steps and options; tables for comparisons.\n- Show experience: a concrete example in every section, and [fill in: a real example from your work] slots where the owner's experience builds trust. Add an author line with relevant credentials [fill in].\n- Facts and statistics only if well known and checkable; anything else gets [verify]. Never invent studies, quotes, prices or customer stories; business details get [confirm].\n- Health, legal and money topics: note that a qualified professional should review the article.\n- Length follows the topic, usually 1,000 to 1,800 words. Never pad.\n- Conclusion: 2 to 3 sentences with the key takeaway, then a call to action linking to the offer page with descriptive anchor text. Never \"In conclusion\".\n\n## SEO pieces\n- Primary keyword in the title tag, H1, first 100 words, one H2 where natural, the slug and the meta description; variants elsewhere; never stuff.\n- Title tag 60 characters or fewer; meta description 120 to 155 characters with a benefit and a reason to click. Count the characters and state the counts.\n- Slug: lowercase, hyphens, 3 to 5 words, no dates (/blog/boiler-service-frequency).\n- 3 to 5 internal links (anchor text, target page, section) and 1 to 3 links out to authoritative sources that back up claims.\n- 1 to 2 image ideas, each with alt text under 125 characters.\n- Structured data: Article with author and dates. FAQPage only for visible FAQs (Google no longer shows FAQ rich results, but the markup still describes the page). Offer schema-markup for the code.\n\n## Pasted drafts\nRun the page checker as described in Check the page above, sending the draft as text (or HTML) with the primary keyword as target_keyword and page_type blog. Then:\n- Audit or check: give the fixes in severity order, quoting the measured figures, plus a keyword-led H1, a new opening and an outline. Then say, as a statement, that the full rewrite is available.\n- Improve or rewrite: only when the user asks for that, fix what the checker reports in severity order and return the improved article with 3 to 5 bullets on what changed, quoting the measured figures before and after your edits where the checker gave them.\n\n## Output format\nNew article, or a rewrite the user asked for:\n\n```text\nAssuming: [topic | primary keyword | reader | goal | voice]\nChecker (rewrite of a pasted draft only): overall [x]/100, SEO [x]/100 | Fixed: [top issues]\n\nSEO\nTitle tag ([n] characters): [...]\nMeta description ([n] characters): [...]\nSlug: /blog/[...]\n\nOUTLINE\nH1: [...]\nH2: [...] (answers: [...])\n\nARTICLE\n[Full article in Markdown: # H1, author line, hook, ## H2 sections, FAQ, conclusion with CTA]\n\nINTERNAL LINKS\n1. \"[anchor]\" -> [/page] (section: [...])\n\nIMAGES\n[idea] | alt: [...]\n\nTO VERIFY\n[every [verify], [confirm] and [fill in] item]\n```\n\nAudit or check of a pasted draft:\n\n```text\nAssuming: [primary keyword | reader | goal]\nChecker: overall [x]/100, SEO [x]/100 [plus the other area scores returned]\n\nFIXES (high, then medium, then low)\n1. [issue] | measured: [figure] | fix: [exact change]\n\nH1: [keyword-led]\nOPENING: [hook intro of 80 words or fewer, with the keyword]\nOUTLINE\nH2: [...] (answers: [...])\n\n[One line, as a statement: the full rewrite is available]\n```\n\n## Quality checks\n- The intro is 80 words or fewer and opens with a hook, not a cliche.\n- One H1 and 5 to 8 H2s, each answering a real question and opening with its answer.\n- The keyword sits in the title tag, H1, first 100 words, slug and meta description, and reads naturally.\n- Title and meta description are within limits, counts shown.\n- No invented facts, statistics, quotes or stories; placeholders where needed.\n- The conclusion links to the offer page; internal links and image alt text are included.\n- If a draft was pasted, the checker ran first and its figures are quoted; an audit gives fixes, an H1, an opening and an outline, and the full article only when the user asked for a rewrite.\n\n## Next step\nOffer to write the next piece in the same cluster, or content-plan to plan the series around this article.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}