seo-geo-for-saas
Complete SEO + GEO (Generative Engine Optimization) system for SaaS companies wanting to rank on both Google and AI search engines (ChatGPT, Perplexity, Gemini, Claude). Use this skill whenever the user asks about SEO strategy, keyword research, content planning, writing SEO-optimized articles, auditing their search performance, creating a content calendar, analyzing competitors, or optimizing for AI search visibility. Trigger on: "seo", "keyword research", "content calendar", "rank on google", "search traffic", "write an article", "blog post", "serp", "backlinks", "competitor analysis", "content cluster", "seo audit", "geo optimization", "ai search", "search console", "organic traffic", "content strategy", "publish article", "seo setup", "ranking", "impressions", "ctr", "meta description", "schema markup", "faq schema". Also trigger when a user wants to set up their SaaS blog SEO from scratch, analyze their current rankings, or create a publishing workflow.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/berthelol/seo-geoSEO + GEO for SaaS
A battle-tested SEO system built by a bootstrapped SaaS founder who grew from 0 to 30k+ organic sessions/month. This isn't theory — it's the exact methodology, templates, and checklists used to rank a real SaaS product.
This skill covers two modes:
- Setup — onboard a new SaaS, analyze existing SEO, build a strategy, create a content calendar
- Publish — write, optimize, and ship SEO+GEO articles using proven templates
First-time setup
If the user has never used this skill before (no seo/ directory in their project), run the onboarding flow. Read references/onboarding.md for the full step-by-step process.
Onboarding creates these files in the user's project:
seo/
├── overview.md # Site architecture, clusters, competitor landscape — context for spawning new agents
├── keywords.md # Master keyword table — local cache, avoids repeat API calls
├── opportunities.md # Prioritized gaps, CTR fixes, quick wins
├── published.md # Log of every published article — avoids needing a database
├── calendar.md # 5-month content calendar with progress tracking
├── positioning.md # Current rankings snapshot — updated during audits
├── templates.md # Article templates adapted for the user's SaaS
└── screenshots/ # Product screenshots to use as article images
├── positioning.md # Current rankings snapshot
└── templates.md # Article templates adapted for their SaaS
Choosing your SEO data source
This skill works with two data providers. During onboarding, ask the user which they have access to:
Option A: SemRush (preferred if available)
- More accurate keyword data, better competitor intelligence
- If the user has the
semrush-researchskill installed, use it directly - Otherwise, ask the user to export data from SemRush web UI (CSV exports)
Option B: DataForSEO (recommended if no SemRush)
- Cheaper, API-first, good enough for most SaaS
- If the user has the
dataforseoskill installed, use it directly - If the user has an account, help them configure credentials
Option C: Manual data
- User pastes data from Google Search Console, exports, or screenshots
- Works but slower — encourage API setup for ongoing use
Always check which skills are available before asking the user to install anything.
Two operating modes
Mode 1: Strategy & Analysis
Use when the user asks to analyze their SEO, find opportunities, audit performance, or plan content.
Workflow:
- Read the user's
seo/files to understand current state - Pull fresh data (via SemRush, DataForSEO, or user-provided exports)
- Update the relevant files (keywords.md, opportunities.md, positioning.md)
- Recommend next actions based on the data
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-berthelol-seo-geo": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
framer-cms
Framer CMS management via the Server API — list, create, read, update, and delete CMS collections and items, upload images, publish previews, deploy to production, and manage project assets, all without opening Framer. Use when the user asks to manage Framer CMS content, publish a Framer site, push articles to Framer, update CMS items, upload images to Framer, create collections, sync content, or automate any Framer workflow. Trigger on: "framer", "framer cms", "framer publish", "framer deploy", "framer collection", "framer article", "push to framer", "upload to framer", "framer api", "framer server api", "cms item", "cms collection", "publish site", "deploy site", "framer preview", "framer image", "framer content". Do NOT trigger for: Framer design/layout work, Framer Motion animation library, building Framer plugins.
scrapping
Use this skill whenever a user wants to get, pull, grab, fetch, or look up public data from social media platforms — profiles, posts, videos, comments, followers, engagement stats, transcripts, trending content, hashtags, or creator info from TikTok, Instagram, YouTube, Twitter/X, LinkedIn, Facebook, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, or link-in-bio sites (Linktree, Komi, Pillar). Also covers ad library lookups (Meta, Google, LinkedIn, Reddit) and TikTok Shop data. Trigger even when users say "scrape", "monitor", "search", or "check" a platform. Do NOT trigger for building apps, using official platform SDKs/APIs (like PRAW, tweepy, YouTube Data API), analyzing local files, or creating dashboards — only when the user needs to retrieve data directly from a social platform.
gleap
Gleap REST API integration for customer support analytics and ticket management. Use when the user asks to fetch support tickets, analyze customer support metrics, track team performance, measure response times, generate support reports, monitor ticket volume, check SLA compliance, analyze busiest hours, export team stats, or interact with Gleap data in any way. Trigger on: "gleap", "support tickets", "support metrics", "support report", "team performance", "response time", "time to close", "ticket analysis", "customer support", "support dashboard", "agent performance", "ticket volume", "SLA", "first response time", "reply time", "busiest hours", "ticket topics", "support trends". Also trigger when a user wants to build a support reporting pipeline, automate support analytics, or connect Gleap to other tools (Notion, Slack, etc.).