القائمة
Google Search Console MCP wrapper. Activate for SEO analytics — search queries, indexing status, sitemaps, keyword rankings. Routes to MCP tools if available, else manual CSV export fallback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need to plan technical solutions that are scalable, secure, and maintainable.
Conversion Rate Optimization — landing pages, signup flows, popups, A/B tests. 25-point framework.
WordPress REST API client — connect to a live WP site to publish/update posts & pages (draft→publish), upload media, manage categories/tags, write Yoast/RankMath SEO meta, and audit existing content. Use when pushing generated marketing content to WordPress or auditing live WP articles. Auth via Application Passwords (env vars only). Consumer/client skill (not for building WP plugin endpoints).
WordPress MCP wrapper. Activate for WordPress content ops via an MCP server when available; else falls back to the wordpress-rest curl path. Manages posts, pages, media, taxonomies, SEO meta.
Multi-MCP marketing orchestrator. Activated by /mk:campaign and Phase 9 (Measure) of the marketing workflow. Coordinates across GA4, GSC, SendGrid/Resend, and ReviewWeb MCP wrappers for full-funnel campaign execution + measurement.
Google Analytics 4 MCP wrapper. Activate when user needs traffic reports, real-time data, attribution, or any GA4 metrics. Routes to MCP tools if available, else falls back to manual CSV export.
| name | mcp-gsc |
| description | Google Search Console MCP wrapper. Activate for SEO analytics — search queries, indexing status, sitemaps, keyword rankings. Routes to MCP tools if available, else manual CSV export fallback. |
| allowed-tools | Read, Bash, Glob |
Google Search Console integration. Bring your own MCP server — this skill documents the tools + manual fallback.
Server command: npx -y @modelcontextprotocol/server-google-search-console (or community equivalent)
Required env: GSC_SITE_URL (e.g., https://example.com), GOOGLE_APPLICATION_CREDENTIALS
Setup: GSC API quickstart
| Tool | Purpose |
|---|---|
mcp__gsc__searchAnalytics | Search queries, clicks, impressions, CTR, position |
mcp__gsc__listSitemaps | All sitemaps + status |
mcp__gsc__submitSitemap | Submit new sitemap |
mcp__gsc__inspectUrl | Indexing status for a specific URL |
mcp__gsc__listSites | Verified sites in GSC |
mcp__gsc__getCoverage | Index coverage issues |
Tool: mcp__gsc__searchAnalytics
Args: { siteUrl: "https://example.com", startDate: "2026-05-09", endDate: "2026-06-06", dimensions: ["query"], rowLimit: 50 }
Tool: mcp__gsc__searchAnalytics
Args: { siteUrl, dimensions: ["page"], metrics: ["clicks", "impressions", "ctr", "position"], filter: "ctr < 0.02 AND impressions > 1000" }
Tool: mcp__gsc__inspectUrl
Args: { siteUrl, inspectionUrl: "https://example.com/page" }
| Error | Cause | Fix |
|---|---|---|
403 PERMISSION_DENIED | Service account not added to GSC | Add in GSC → Settings → Users |
404 NOT_FOUND | Wrong GSC_SITE_URL (must include protocol, exact match) | Verify site URL prefix |
400 INVALID_ARGUMENT | Date range too long (>16 months) | Reduce to 16 months or less |
If mcp__gsc__* tools not available:
plans/marketing/<campaign>/gsc-export.csvCommon exports:
skills/marketing/seo-technical/SKILL.md — technical SEO (uses GSC indexing data)skills/marketing/seo-content/SKILL.md — content SEO (uses GSC query data)skills/marketing/seo-schema/SKILL.md — schema (uses GSC rich results)