SEO Implement
indranilbanerjee/digital-marketing-pro
Execute approved SEO changes on a connected WordPress or Webflow CMS — meta title/description updates, JSON-LD schema deployment, canonical URLs, 301/302 redirects, and Search Console indexing…
Connects WordPress, Strapi, Contentful or Ghost to the notfair SEO tools by collecting credentials, testing the connection and saving them to .env.local.
$ npx skills add nowork-studio/notfair-plugin --skill setup-cms -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nowork-studio/notfair-plugin setup-cms --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/seo/setup-cms .claude/skills/setup-cms && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "setup-cms" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cms into .claude/skills/setup-cms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-cms", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cmsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nowork-studio/notfair-plugin --skill setup-cms -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nowork-studio/notfair-plugin setup-cms --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/seo/setup-cms .agents/skills/setup-cms && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "setup-cms" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cms into .agents/skills/setup-cms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-cms", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nowork-studio/notfair-plugin --skill setup-cms -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nowork-studio/notfair-plugin setup-cms --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/seo/setup-cms .cursor/skills/setup-cms && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "setup-cms" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cms into .cursor/skills/setup-cms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-cms", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nowork-studio/notfair-plugin.git --path seo/setup-cms--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nowork-studio/notfair-plugin --skill setup-cms -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nowork-studio/notfair-plugin setup-cms --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/seo/setup-cms .gemini/skills/setup-cms && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "setup-cms" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cms into .gemini/skills/setup-cms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-cms", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nowork-studio/notfair-plugin setup-cmsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nowork-studio/notfair-plugin --skill setup-cms -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/seo/setup-cms .github/skills/setup-cms && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "setup-cms" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cms into .github/skills/setup-cms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-cms", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nowork-studio/notfair-plugin --skill setup-cms -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nowork-studio/notfair-plugin setup-cms --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/seo/setup-cms .opencode/skills/setup-cms && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "setup-cms" agent skill from https://github.com/nowork-studio/notfair-plugin/tree/main/seo/setup-cms into .opencode/skills/setup-cms/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "setup-cms", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
setup-cmsConnects WordPress, Strapi, Contentful or Ghost to the notfair SEO tools by collecting credentials, testing the connection and saving them to .env.local.
This skill walks you through linking a CMS to the notfair SEO analysis tools, so that seo-analysis can pull published content and compare it with Google Search Console data to find invisible pages, content gaps, stale articles and missing SEO fields. It first runs a detection script to see whether a CMS is already configured, and if one is, offers to reconfigure it, switch to another or just test the connection.
If nothing is set up, it asks which of four systems you use. WordPress needs the site URL, a username and an Application Password created in the admin profile, which can be revoked later and never exposes your main password. Strapi uses an API token, Contentful a Delivery API key and Ghost a Content API key. Values are collected one at a time, tested against the CMS and written to `.env.local`. The skill relies on the plugin's shared SEO scripts, found through its preamble file, and on python3.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1a53d4e. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadWriteAskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
WP_APP_PASSWORDSTRAPI_API_KEYCONTENTFUL_DELIVERY_TOKENGHOST_CONTENT_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
CMS Connection Setup for SEO Analysis loads about 2.2k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 882 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
credentials to .env.local. Once set up, seo-analysis automatically cross-Write to `.env.local`:Write to `.env.local`:Write to `.env.local`:Write to `.env.local`:## Step 4 — Write .env.localFind the project's `.env.local` file. Search for it:for candidate in ".env.local" "$HOME/.env.local"; do[ -z "$ENV_FILE" ] && ENV_FILE=".env.local"IT=2`** → credentials were removed from `.env.local` between steps. Restart from Step 3.Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from nowork-studio/notfair-plugin at commit 1a53d4e, republished under its MIT licence (© nowork-studio). 882 words, ~2,168 tokens.
.claude/skills/setup-cms/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Guide the user through connecting their CMS to notfair's SEO analysis tools.
Once configured, /seo-analysis automatically pulls published content from
the CMS and cross-references it against Google Search Console data — finding
invisible pages, content gaps, stale articles, and missing SEO fields.
Read and follow ../shared/preamble.md — it locates the SEO scripts directory. Use $SKILL_SCRIPTS from the preamble for all script calls below.
CMS_TYPE=$(python3 "$SKILL_SCRIPTS/cms_detect.py" 2>/dev/null)
CMS_STATUS=$?
echo "CMS_TYPE=$CMS_TYPE EXIT=$CMS_STATUS"CMS_STATUS=0 → a CMS is already configured ($CMS_TYPE is the name).
Show the user: "You already have [$CMS_TYPE] connected. Would you like to
reconfigure it, or switch to a different CMS?"
Wait for their reply. If they say reconfigure/switch, continue to Step 2.
If they say test or verify, jump to Step 5 (skip to connection test).
CMS_STATUS=2 → nothing configured yet. Continue to Step 2.
Ask the user:
"Which CMS are you connecting? I support:
- WordPress — self-hosted or WordPress.com (uses REST API + Application Password)
- Strapi — v4 or v5, self-hosted (uses API Token)
- Contentful — cloud headless CMS (uses Delivery API key)
- Ghost — Ghost.org or self-hosted (uses Content API key)
Reply with the name or number."
Wait for their answer. Map to: wordpress, strapi, contentful, ghost.
Jump to the sub-section for the chosen CMS.
WordPress uses the built-in Application Passwords feature (introduced in WP 5.6). This is the safest way to grant API access — it never exposes your main password and can be revoked at any time.
Tell the user:
"I need three things to connect WordPress:
- Your WordPress URL (e.g.
https://myblog.com)- Your WordPress username (the one you log in with)
- An Application Password — create one in: WordPress Admin → Users → Profile → scroll to Application Passwords → enter a name like "notfair" → click Add New → copy the generated password
Paste each value when ready."
Collect values one at a time:
WP_URL → validate it starts with http:// or https://WP_USERNAMEWP_APP_PASSWORDWP_CONTENT_TYPE:"What content type should I analyze? Common values:
posts,pages. Press Enter to useposts(default), or enter a custom post type slug."
Once all four are collected, continue to Step 4 (test connection).
Write to .env.local:
WP_URL=<value>
WP_USERNAME=<value>
WP_APP_PASSWORD=<value>
WP_CONTENT_TYPE=<value or posts>Tell the user:
"I need two things to connect Strapi:
- Your Strapi URL (e.g.
https://cms.example.com)- A Full-access API Token — create one in: Strapi Admin → Settings → Global settings → API Tokens → Create new API Token → Type: Full access → copy the token
Optionally:
- Content type — the plural API ID of your content collection (default:
articles). Find it in: Content-Type Builder → [your type] → API ID (plural)- Strapi version —
4or5(auto-detected if omitted)Paste each value when ready."
Collect:
STRAPI_URLSTRAPI_API_KEYSTRAPI_CONTENT_TYPE (optional, default: articles)STRAPI_VERSION (optional)Write to .env.local:
STRAPI_URL=<value>
STRAPI_API_KEY=<value>
STRAPI_CONTENT_TYPE=<value or articles>Include STRAPI_VERSION=<value> only if the user specified it.
Tell the user:
"I need three things to connect Contentful:
- Space ID — find it in: Contentful → Settings → General Settings → Space ID
- Content Delivery API token — find it in: Settings → API Keys → [your key] → Content Delivery API - access token (If no key exists, create one under Settings → API Keys → Add API Key)
- Content type ID — the API identifier for your content type. Find it in: Content model → [your type] → API Identifier
Optionally:
- Environment (default:
master)Paste each value when ready."
Collect:
CONTENTFUL_SPACE_IDCONTENTFUL_DELIVERY_TOKENCONTENTFUL_CONTENT_TYPECONTENTFUL_ENVIRONMENT (optional, default: master)Write to .env.local:
CONTENTFUL_SPACE_ID=<value>
CONTENTFUL_DELIVERY_TOKEN=<value>
CONTENTFUL_CONTENT_TYPE=<value>
CONTENTFUL_ENVIRONMENT=<value or master>Tell the user:
"I need two things to connect Ghost:
- Your Ghost URL (e.g.
https://myblog.ghost.io)- Content API key — create one in: Ghost Admin → Settings → Integrations → Add custom integration → copy the Content API Key
Optionally:
- Content type:
posts(default) orpagesPaste each value when ready."
Collect:
GHOST_URLGHOST_CONTENT_KEYGHOST_CONTENT_TYPE (optional, default: posts)Write to .env.local:
GHOST_URL=<value>
GHOST_CONTENT_KEY=<value>
GHOST_CONTENT_TYPE=<value or posts>Find the project's .env.local file. Search for it:
ENV_FILE=""
for candidate in ".env.local" "$HOME/.env.local"; do
[ -f "$candidate" ] && ENV_FILE="$candidate" && break
done
[ -z "$ENV_FILE" ] && ENV_FILE=".env.local"
echo "Writing to: $ENV_FILE"Merge strategy — do not overwrite the entire file. For each env var:
Read the file first (if it exists), then update key by key, then write back.
If the file doesn't exist yet, create it.
After writing, confirm:
"Credentials written to
[path]. Testing connection now..."
Run the appropriate preflight script and capture the exit code:
# WordPress
python3 "$SKILL_SCRIPTS/preflight_wordpress.py" 2>&1; PREFLIGHT_EXIT=$?
# Strapi
python3 "$SKILL_SCRIPTS/preflight_strapi.py" 2>&1; PREFLIGHT_EXIT=$?
# Contentful
python3 "$SKILL_SCRIPTS/preflight_contentful.py" 2>&1; PREFLIGHT_EXIT=$?
# Ghost
python3 "$SKILL_SCRIPTS/preflight_ghost.py" 2>&1; PREFLIGHT_EXIT=$?The 2>&1 redirect surfaces error messages in the output so you can show them.
PREFLIGHT_EXIT=0 — connection successful. Show the "OK: …" line to the user,
then continue to Step 6.
PREFLIGHT_EXIT=1 — connection failed. Show the full error output verbatim.
Help the user diagnose:
401 Unauthorized → wrong token/password — suggest regenerating403 Forbidden → token lacks permission — suggest a Full Access / unrestricted token404 Not Found → wrong URL or wrong content type slugAsk: "Want to fix the credentials and try again (I'll go back to Step 3), or skip CMS setup for now?"
PREFLIGHT_EXIT=2 → credentials were removed from .env.local between steps. Restart from Step 3.
Once the connection succeeds, show a summary:
CMS connected successfully!
CMS: [WordPress/Strapi/Contentful/Ghost]
URL: [cms_url]
Content type: [content_type]
Published: [N] entries found
What this enables in /seo-analysis:
• Cross-reference [N] published articles against Google Search Console data
• Find published content with zero GSC impressions (unindexed or invisible)
• Identify content gaps: queries ranking 11-30 with no matching article
• Flag stale content: articles >6 months old with declining clicks
• Audit SEO fields: missing meta titles/descriptions, length violationsThen offer:
"Run
/seo-analysisto see a full audit with your CMS content included, or type/setup-cmsagain to connect a different CMS."
© nowork-studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in seo/setup-cms of nowork-studio/notfair-plugin.
Open the folder on GitHubat commit 1a53d4e
CMS Connection Setup for SEO Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CMS Connection Setup for SEO Analysis this skillnowork-studio/notfair-plugin | 3.9k | — | ~2.2k | Automated safety check: Notes | MIT | |
| SEO Implementindranilbanerjee/digital-marketing-pro | 854 | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Google SEO APIsAgriciDaniel/claude-seo | 18k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Blog GoogleAgriciDaniel/claude-blog | 2.3k | 1 repos | ~3.3k | Automated safety check: Notes | MIT | |
| SEO GodAKCodez/seo-god | 111 | — | ~2.2k | Automated safety check: Pass | MIT | |
| SEO Coachakseolabs-seo/seo-coach | 145 | — | ~2.8k | Automated safety check: Pass | None |
indranilbanerjee/digital-marketing-pro
Execute approved SEO changes on a connected WordPress or Webflow CMS — meta title/description updates, JSON-LD schema deployment, canonical URLs, 301/302 redirects, and Search Console indexing…
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
AKCodez/seo-god
Agentic SEO operator for your own website: audits and fixes your site with OpenSEO, measures rankings + Google Search Console, works to get ChatGPT and other AI engines citing you, and schedules the…
akseolabs-seo/seo-coach
Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
nowork-studio/notfair-plugin
Finds, scores and groups keywords from a seed term or niche for SEO and AI search content strategies, with intent labels, difficulty estimates and topic clusters.
nowork-studio/notfair-plugin
Runs a full SEO audit that combines Google Search Console, URL Inspection, PageSpeed Insights and a technical crawl, then ranks quick wins and a 30-day plan.
nowork-studio/notfair-plugin
Crawls a website with a bundled Python script to find broken internal and outbound links, then reports them by status code with the pages they appear on.
nowork-studio/notfair-plugin
Writes and improves title tags, meta descriptions, Open Graph and Twitter card tags for click-through, with character counts and A/B test variants.
nowork-studio/notfair-plugin
Audits one URL for content quality, E-E-A-T, search intent, on-page and technical signals, and produces a scored report with fixes.
nowork-studio/notfair-plugin
Turns Google Search Console data into a dated content calendar by finding striking-distance queries and unanswered intent, ready to hand to a writer.
Works with
Categories
Connects WordPress, Strapi, Contentful or Ghost to the notfair SEO tools by collecting credentials, testing the connection and saving them to .env.local. This skill walks you through linking a CMS to the notfair SEO analysis tools, so that seo-analysis can pull published content and compare it with Google Search Console data to find invisible pages, content gaps, stale articles and missing SEO fields. It first runs a detection script to see whether a CMS is already configured, and if one is, offers to reconfigure it, switch to another or just test the connection.
CMS Connection Setup for SEO Analysis fits situations like: connecting a WordPress site to the SEO analysis tools; adding a Strapi, Contentful or Ghost CMS as a content source; finding out why a seo-analysis report shows no CMS data; switching the connected CMS or re-testing an existing connection.
Run `npx skills add nowork-studio/notfair-plugin --skill setup-cms -a claude-code`. Or copy the skill folder (seo/setup-cms in nowork-studio/notfair-plugin) into .claude/skills/setup-cms in your project. Claude Code loads it when a task matches its description.
Run `npx skills add nowork-studio/notfair-plugin --skill setup-cms -a codex`. Or copy the skill folder (seo/setup-cms in nowork-studio/notfair-plugin) into .agents/skills/setup-cms in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nowork-studio/notfair-plugin --skill setup-cms -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setup-cms, .gemini/skills/setup-cms, .github/skills/setup-cms and .opencode/skills/setup-cms in your project.
Going by SKILL.md and its folder, CMS Connection Setup for SEO Analysis needs the command-line tools its instructions call (python3) and credentials named WP_APP_PASSWORD, STRAPI_API_KEY, CONTENTFUL_DELIVERY_TOKEN and GHOST_CONTENT_KEY. Our summary lists: Python 3; The notfair SEO scripts and shared preamble from the same plugin; Admin access to the CMS to create an application password or API key. Its frontmatter pre-approves these tools: Bash, Read, Write, AskUserQuestion.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
CMS Connection Setup for SEO Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with CMS Connection Setup for SEO Analysis: SEO Implement (indranilbanerjee/digital-marketing-pro, 854 stars), Google SEO APIs (AgriciDaniel/claude-seo, 18k stars), Blog Google (AgriciDaniel/claude-blog, 2.3k stars) and SEO God (AKCodez/seo-god, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
nowork-studio (a GitHub organization) maintains it in nowork-studio/notfair-plugin, which has 3,904 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 1, 2026.
Source: nowork-studio/notfair-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.