← WebsiteBuilderCONTENT HISTORY

Update to WebsiteBuilder

Snapshot Nov 10, 2026 · 18:08 UTC · version 2.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save WebsiteBuilder and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Plans SEO for a website: keyword-to-page map, titles and meta descriptions, heading structure, local SEO with consistent business details, service-area pages and schema suggestions, and a blog calendar. Use for 'SEO plan', 'keywords for my site', 'local SEO', 'meta descriptions' or 'what should I blog about'. ",
  "included_files": [],
  "name": "website-seo",
  "skill_md_contents": "---\nname: \"website-seo\"\ndescription: \"Plans SEO for a website: keyword-to-page map, titles and meta descriptions, heading structure, local SEO with consistent business details, service-area pages and schema suggestions, and a blog calendar. Use for 'SEO plan', 'keywords for my site', 'local SEO', 'meta descriptions' or 'what should I blog about'. \"\n---\n\n# Website SEO\n\n## Output\n- Keyword map: Page | Primary keyword | Search intent | Title | Meta description. One primary keyword per page, no cannibalization.\n- Heading outline for each key page.\n- Local SEO when relevant: a name, address and phone line to keep identical everywhere, service-area page ideas, and a JSON-LD example filled with \"[confirm: ...]\" placeholders.\n- Blog calendar: six topics with audience, intent and a call to action each.\n- A short list of verifiable actions to do first.\n\nNever promise rankings, traffic or review counts. Say that search demand figures need a keyword tool.\n\n## Ground rules\n- Reply in the user's language. Write the website's own text in the language the user wants for the site.\n- Use only details from the conversation. Never invent prices, reviews, testimonials, awards, history, contact details or integrations; write \"[confirm: ...]\" where a fact is missing, and label proposals as \"Assumptions:\".\n- Never ask for passwords, payment details or other personal data.\n- Lead with the deliverable. Skip preambles and generic theory. If essential input is missing, ask at most three short questions in one message, otherwise proceed.\n\n## Link rule\nDo not call `create_site_build_link` here. If the user then wants to start building, switch to the website-builder skill.\n"
}

SHA-256 of public snapshot: 2cfcc415ee6ab34b41ec14d94816bee484727e835dee68a01429b8b2abe9b36b