Agent skill

SEO Wordpress Manager

Batch update Yoast SEO metadata (titles, descriptions, focus keyphrases) in WordPress via GraphQL.

Install SEO Wordpress Manager

skills CLI

$ npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow seo-wordpress-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager .claude/skills/seo-wordpress-manager && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "seo-wordpress-manager" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager into .claude/skills/seo-wordpress-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-wordpress-manager", 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

$skill-installer install https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager

Type 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.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow seo-wordpress-manager --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager .agents/skills/seo-wordpress-manager && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "seo-wordpress-manager" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager into .agents/skills/seo-wordpress-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-wordpress-manager", 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.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow seo-wordpress-manager --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager .cursor/skills/seo-wordpress-manager && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "seo-wordpress-manager" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager into .cursor/skills/seo-wordpress-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-wordpress-manager", 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

$ gemini skills install https://github.com/nicepkg/ai-workflow.git --path workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow seo-wordpress-manager --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager .gemini/skills/seo-wordpress-manager && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "seo-wordpress-manager" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager into .gemini/skills/seo-wordpress-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-wordpress-manager", 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.

GitHub CLI

$ gh skill install nicepkg/ai-workflow seo-wordpress-manager

Installs 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).

skills CLI

$ npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager .github/skills/seo-wordpress-manager && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "seo-wordpress-manager" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager into .github/skills/seo-wordpress-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-wordpress-manager", 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.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow seo-wordpress-manager --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager .opencode/skills/seo-wordpress-manager && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "seo-wordpress-manager" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager into .opencode/skills/seo-wordpress-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-wordpress-manager", 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.

Facts

Skill name: seo-wordpress-manager
GitHub stars: 285
Token cost: ~1.4k tokens
SKILL.md length: 343 words
Files: 7 (incl. scripts)
Skills in repo: 61
Repo updated: Jan 20, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Batch update Yoast SEO metadata (titles, descriptions, focus keyphrases) in WordPress via GraphQL.

Works in 5 steps: Analyze Posts for SEO Issues → Generate Optimized SEO Content → Preview Changes (Dry Run) → …
The user wants to update SEO metadata
SKILL.md covers Purpose, When to Use This Skill, Prerequisites and Configuration, plus 5 more sections
Runs Python scripts from its folder; calls python; needs WP_APP_PASSWORD

What it does

SEO Wordpress Manager is an agent skill from nicepkg/ai-workflow. Batch update Yoast SEO metadata (titles, descriptions, focus keyphrases) in WordPress via GraphQL. Use when the user wants to update SEO metadata, optimize titles, fix meta descriptions, or manage Yoast SEO fields across multiple posts. Supports preview mode, progress tracking, and resume capability.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `config.example.json`, `reference.md` and `scripts/analyze_seo.py`).

It sits in Backend & APIs, covering On-page SEO and GraphQL. It works with WordPress and GraphQL. The repository describes itself as: 🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading… The licence is MIT.

When your agent uses it

The user wants to update SEO metadata
Optimize titles
Fix meta descriptions
Manage Yoast SEO fields across multiple posts

Example prompts

“/seo-wordpress-manager”

Requirements

Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Analyze Posts for SEO Issues
Generate Optimized SEO Content
Preview Changes (Dry Run)
Apply Updates
Resume if Interrupted

What it can do on your machine

Read from SKILL.md and the folder at commit d167b41. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- WP_APP_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

SEO Wordpress Manager loads about 1.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 343 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~81
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

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.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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); the scripts in this folder are not scanned.

SKILL.md

The full file from nicepkg/ai-workflow at commit d167b41, republished under its MIT licence (© nicepkg). 343 words, ~1,355 tokens.

Download SKILL.mdSave it as .claude/skills/seo-wordpress-manager/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

name: seo-wordpress-manager
description: Batch update Yoast SEO metadata (titles, descriptions, focus keyphrases) in WordPress via GraphQL. Use when the user wants to update SEO metadata, optimize titles, fix meta descriptions, or manage Yoast SEO fields across multiple posts. Supports preview mode, progress tracking, and resume capability.

SEO WordPress Manager Skill

Purpose

This skill manages Yoast SEO metadata in WordPress sites via the WPGraphQL API. It enables batch updates of:

SEO titles
Meta descriptions
Focus keyphrases
Open Graph metadata

When to Use This Skill

User asks to "update SEO titles" or "fix meta descriptions"
User wants to batch process WordPress posts for SEO
User mentions Yoast SEO optimization
User needs to update SEO metadata across multiple posts

Prerequisites

WordPress Setup Required

WPGraphQL plugin installed and activated
WPGraphQL for Yoast SEO extension installed
Application Password created for authentication

Yoast SEO GraphQL Mutations

Add this to your theme's functions.php to enable mutations:

php

// Enable Yoast SEO mutations via WPGraphQL
add_action('graphql_register_types', function() {
    register_graphql_mutation('updatePostSeo', [
        'inputFields' => [
            'postId' => ['type' => 'Int', 'description' => 'Post ID'],
            'title' => ['type' => 'String', 'description' => 'SEO Title'],
            'metaDesc' => ['type' => 'String', 'description' => 'Meta Description'],
            'focusKeyphrase' => ['type' => 'String', 'description' => 'Focus Keyphrase'],
        ],
        'outputFields' => [
            'success' => ['type' => 'Boolean'],
            'post' => ['type' => 'Post'],
        ],
        'mutateAndGetPayload' => function($input) {
            $post_id = absint($input['postId']);

            if (!current_user_can('edit_post', $post_id)) {
                throw new \GraphQL\Error\UserError('You do not have permission to edit this post.');
            }

            if (isset($input['title'])) {
                update_post_meta($post_id, '_yoast_wpseo_title', sanitize_text_field($input['title']));
            }
            if (isset($input['metaDesc'])) {
                update_post_meta($post_id, '_yoast_wpseo_metadesc', sanitize_textarea_field($input['metaDesc']));
            }
            if (isset($input['focusKeyphrase'])) {
                update_post_meta($post_id, '_yoast_wpseo_focuskw', sanitize_text_field($input['focusKeyphrase']));
            }

            return [
                'success' => true,
                'post' => get_post($post_id),
            ];
        }
    ]);
});

Configuration

Create a config.json in the skill directory:

json

{
  "wordpress": {
    "graphql_url": "https://your-site.com/graphql",
    "username": "your-username",
    "app_password": "your-app-password"
  },
  "batch": {
    "size": 10,
    "delay_seconds": 1
  },
  "state_file": "./seo_update_progress.json"
}

Or use environment variables:

WP_GRAPHQL_URL
WP_USERNAME
WP_APP_PASSWORD

Workflow

Step 1: Analyze Posts for SEO Issues

bash

python scripts/analyze_seo.py --all --output analysis.json

This fetches posts and identifies SEO issues (missing titles, too long descriptions, etc.). Output includes instructions for Claude to generate optimized SEO content.

Claude analyzes the analysis.json output and generates a changes.json file with:

Optimized SEO titles (50-60 chars)
Compelling meta descriptions (150-160 chars)
Relevant focus keyphrases

Step 3: Preview Changes (Dry Run)

bash

python scripts/preview_changes.py --input changes.json

Step 4: Apply Updates

bash

python scripts/yoast_batch_updater.py --input changes.json --apply

Step 5: Resume if Interrupted

bash

python scripts/yoast_batch_updater.py --resume

Input Format

The skill expects a JSON file with changes:

json

{
  "updates": [
    {
      "post_id": 123,
      "post_title": "Original Post Title",
      "current": {
        "seo_title": "Old Title | Site Name",
        "meta_desc": "Old description"
      },
      "new": {
        "seo_title": "New Optimized Title | Site Name",
        "meta_desc": "New compelling meta description under 160 chars"
      }
    }
  ]
}

Output

The skill produces:

Preview report showing before/after for each post
Progress state file for resuming interrupted batches
Final report with success/failure counts

Safety Features

Dry-run mode by default - preview before applying
Confirmation prompt before batch updates
Progress tracking - resume interrupted sessions
Rate limiting - configurable delay between API calls
Backup - logs current values before changing

Example Usage

User: "Update the meta descriptions for all posts in the 'tutorials' category to be more compelling"

Claude will:

Run analyze_seo.py to fetch posts and identify SEO issues
Analyze each post's content and current SEO data
Generate optimized titles, descriptions, and keyphrases
Create a changes.json file with the improvements
Run preview_changes.py to show before/after comparison
Ask for confirmation
Run yoast_batch_updater.py --apply to apply changes
Report results with success/failure counts

Files

SKILL.md and 6 other files (scripts) in workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager of nicepkg/ai-workflow.

SKILL.md
config.example.json
reference.md
scripts/analyze_seo.py
scripts/preview_changes.py
scripts/wp_graphql_client.py
scripts/yoast_batch_updater.py

Open the folder on GitHubat commit d167b41

Compare with similar skills

SEO Wordpress Manager 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.

SEO Wordpress Manager compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
SEO Wordpress Manager this skillnicepkg/ai-workflow	285	—	~1.4k	Automated safety check: Pass	MIT	8 mo ago
Wp Headless And Wpgraphqljorgerosal/wordpress-skills	100	—	~1.7k	Automated safety check: Pass	MIT	4 mo ago
Blog TaxonomyAgriciDaniel/claude-blog	2.3k	1 repos	~2.5k	Automated safety check: Pass	MIT	5 days ago
API DesignerJeffallan/claude-skills	12k	2 repos	~2k	Automated safety check: Pass	MIT	4 days ago
Nodejs Backend Patternsever-works/ever-works	158	17 repos	~4k	Automated safety check: Pass	AGPL-3.0	2 days ago
GraphQL Operations with CodegenChrisWiles/claude-code-showcase	6.1k	3 repos	~1.5k	Automated safety check: Pass	None	9 mo ago

Similar skills

Wp Headless And Wpgraphql
jorgerosal/wordpress-skills
Headless WordPress and WPGraphQL review guidance. An agent skill from jorgerosal/wordpress-skills.
100 GitHub stars~1.7k tokensUpdated 4 mo ago
Backend & APIsAuto-check passed
Blog Taxonomy
AgriciDaniel/claude-blog
Extract, suggest, and sync tags and categories for blog posts across all major CMS platforms.
2.3k GitHub starsUsed in 1 repo~2.5k tokens
Backend & APIsAuto-check passed
API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
12k GitHub starsUsed in 2 repos~2k tokens
Backend & APIsAuto-check passed
Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
158 GitHub starsUsed in 17 repos~4k tokens
Backend & APIsAuto-check passed
GraphQL Operations with Codegen
ChrisWiles/claude-code-showcase
Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.
6.1k GitHub starsUsed in 3 repos~1.5k tokens
Backend & APIsAuto-check passed
API And Interface Design
dzhalaevd/Donatello
Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.
135 GitHub starsUsed in 9 repos~2.6k tokens
Backend & APIsAuto-check passed

Questions about SEO Wordpress Manager

What does SEO Wordpress Manager do?

Batch update Yoast SEO metadata (titles, descriptions, focus keyphrases) in WordPress via GraphQL. SEO Wordpress Manager is an agent skill from nicepkg/ai-workflow. Batch update Yoast SEO metadata (titles, descriptions, focus keyphrases) in WordPress via GraphQL.

When should I use SEO Wordpress Manager?

SEO Wordpress Manager fits situations like: the user wants to update SEO metadata; optimize titles; fix meta descriptions; manage Yoast SEO fields across multiple posts.

How do I install SEO Wordpress Manager in Claude Code?

Run `npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a claude-code`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager in nicepkg/ai-workflow) into .claude/skills/seo-wordpress-manager in your project. Claude Code loads it when a task matches its description.

How do I install SEO Wordpress Manager in Codex?

Run `npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a codex`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/seo-wordpress-manager in nicepkg/ai-workflow) into .agents/skills/seo-wordpress-manager in your project. Codex loads it when a task matches its description.

Can I use SEO Wordpress Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nicepkg/ai-workflow --skill seo-wordpress-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-wordpress-manager, .gemini/skills/seo-wordpress-manager, .github/skills/seo-wordpress-manager and .opencode/skills/seo-wordpress-manager in your project.

What does SEO Wordpress Manager need to run?

Going by SKILL.md and its folder, SEO Wordpress Manager needs Python for the scripts in its folder, the command-line tools its instructions call (python) and credentials named WP_APP_PASSWORD. Our summary lists: Python 3.

Does SEO Wordpress Manager access the network?

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.

Is SEO Wordpress Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does SEO Wordpress Manager use?

SEO Wordpress Manager is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does SEO Wordpress Manager use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to SEO Wordpress Manager?

Skills that share tags, products or a category with SEO Wordpress Manager: Wp Headless And Wpgraphql (jorgerosal/wordpress-skills, 100 stars), Blog Taxonomy (AgriciDaniel/claude-blog, 2.3k stars), API Designer (Jeffallan/claude-skills, 12k stars) and Nodejs Backend Patterns (ever-works/ever-works, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SEO Wordpress Manager?

nicepkg (a GitHub organization) maintains it in nicepkg/ai-workflow, which has 285 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on January 20, 2026.

Source: nicepkg/ai-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install SEO Wordpress Manager

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SEO WordPress Manager Skill

Purpose

When to Use This Skill

Prerequisites

WordPress Setup Required

Yoast SEO GraphQL Mutations

Configuration

Workflow

Step 1: Analyze Posts for SEO Issues

Step 2: Generate Optimized SEO Content

Step 3: Preview Changes (Dry Run)

Step 4: Apply Updates

Step 5: Resume if Interrupted

Input Format

Output

Safety Features

Example Usage

Files

Compare with similar skills

Similar skills

More from nicepkg/ai-workflow

Related

Questions about SEO Wordpress Manager