81 件 ・ 関連度順
概要と使いどころ
[DEPRECATED — merged into gingiris-seo-geo-agent] SEO/GEO agent-ops SOP: daily 4-phase audit automation, GSC pipeline, AI traffic tracking, schema validation, IndexNow. Use the gingiris-seo-geo-agent skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Suggest content topics ranked by opportunity score. Analyzes GSC keyword data and cross-references with personas to find high-potential topics.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a strategic content brief from format + site + keyword. Auto-resolves persona, pulls GSC data, generates hooks, angles, and competitor weakness via LLM.
日本語の概要は準備中です。原文の説明を表示しています。
Instruments Anthropic API calls to log token usage, latency, and cost per request using the Anthropic TypeScript SDK. Wraps the anthropic.messages.create method to capture usage.input_tokens, usage.output_tokens, and timing from the API response. Writes structured logs to CloudWatch Logs via the AWS SDK v3 CloudWatchLogsClient.
日本語の概要は準備中です。原文の説明を表示しています。
Triage the content corpus against the latest GSC snapshot and produce a prioritized refresh report. Read-only: reports, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Bind this repo to an OpenSEO project and prepare the local SEO state directories. Use this skill when starting SEO work on a fresh project, when `.seo/openseo.json` does not exist yet, when the OpenSEO project id is unknown, or when Google Search Console needs connecting before keyword or rank work can start. Triggers: "set up openseo", "link seo project", "connect gsc", "start seo for this site", "openseo project id".
日本語の概要は準備中です。原文の説明を表示しています。
Cluster keywords by search intent and map each cluster to an existing or proposed page, with cannibalization detection from Search Console. Use this skill when the user has a keyword list (saved set, brand/keyword-plan.md, GSC export, or seed topic) and needs page targets, content briefs, or a site map for SEO pages — especially before seo-content or seo-machine page generation. Triggers: "cluster keywords", "keyword mapping", "map keywords to pages", "keyword cannibalization", "which page should target".
日本語の概要は準備中です。原文の説明を表示しています。
Technical SEO audit across 8 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, and JavaScript rendering. Enhanced with live GSC (indexing status, crawl data) and Ahrefs (backlink profile) data when MCPs are available. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".
日本語の概要は準備中です。原文の説明を表示しています。
Analyze existing XML sitemaps or generate new ones with GSC indexing cross-reference. Validates format, URLs, and structure against actual indexing status. Use when user says "sitemap", "generate sitemap", "sitemap issues", "XML sitemap", or "sitemap indexing".
日本語の概要は準備中です。原文の説明を表示しています。
Deep single-page SEO analysis covering on-page elements, content quality, technical meta tags, schema, images, and performance. Enhanced with live Ahrefs (page authority, referring domains) and GSC (search performance, top keywords) data when MCPs are available. Use when user says "analyze this page", "check page SEO", or provides a single URL for review.
日本語の概要は準備中です。原文の説明を表示しています。
Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 7 specialists, generates health score. Enhanced with live Ahrefs (DR, backlinks, traffic) and GSC (indexing, top pages) data when MCPs are available. Use when user says "audit", "full SEO check", "analyze my site", or "website health check".
日本語の概要は準備中です。原文の説明を表示しています。
Detect keyword cannibalization by identifying queries where multiple pages are competing for the same ranking. Uses Google Search Console data to find queries appearing across 2 or more pages. Use when user says "keyword cannibalization", "same keyword multiple pages", "cannibalizing keywords", or "duplicate rankings".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a structured SEO content brief for a keyword using live Ahrefs SERP data and optional GSC overlay. Use when user says "content brief", "write a brief for", "content plan for keyword", "what should I write about", "brief for article", "content strategy for keyword", "help me write content for", or "create a brief for".
日本語の概要は準備中です。原文の説明を表示しています。
Content quality and E-E-A-T analysis with AI citation readiness assessment. Enhanced with live Ahrefs (actual keyword rankings, positions) and GSC (search query performance) data to validate static E-E-A-T analysis with real user behavior. Use when user says "content quality", "E-E-A-T", "content analysis", "readability check", "thin content", or "content audit".
日本語の概要は準備中です。原文の説明を表示しています。
Analyze branded vs non-branded traffic split using Google Search Console data. Shows what percentage of organic clicks come from brand name searches vs generic queries. Requires user to confirm brand terms before analysis. Use when user says "brand vs nonbrand", "branded traffic", "brand queries", "non-brand traffic", or "branded vs generic".
日本語の概要は準備中です。原文の説明を表示しています。
Detect content decay by identifying pages that are losing both clicks and impressions over a 90-day comparison window in Google Search Console. Surfaces pages with true long-term decline (not seasonal variation) and assigns decay severity ratings. Use when user says "content decay", "declining pages", "losing rankings", "pages losing traffic over time", or "90 day decline".
日本語の概要は準備中です。原文の説明を表示しています。
Identify indexing problems and coverage issues using Google Search Console URL inspection data. Checks up to 20 pages for indexing status, coverage state, robots.txt state, and last crawl date. Use when user says "index issues", "indexing problems", "not indexed", "indexing coverage", or "why is my page not indexed".
日本語の概要は準備中です。原文の説明を表示しています。
Discover newly ranking keywords using Google Search Console data. Finds queries that had zero clicks or impressions in the prior 28 days but started appearing in the current period, revealing emerging content opportunities. Use when user says "new keywords", "new rankings", "keywords started ranking", "recently ranking", or "new queries".
日本語の概要は準備中です。原文の説明を表示しています。
Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".
日本語の概要は準備中です。原文の説明を表示しています。
Detect content decay from Google Search Console exports by comparing current and previous page performance, flagging quarter-over-quarter traffic drops, dropped pages, and refresh, consolidate, prune, or query-shift actions. Use when the user says "/blog decay", "content decay", "traffic drop", "QoQ decline", "GSC decay", or "refresh declining posts".
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered SEO operations: keyword intelligence, competitor gap analysis, Google Search Console optimization, and trend detection. Use when asked to research keywords, analyze competitor content gaps, audit GSC performance, or detect trending topics. For growth experiments see growth-engine; for content optimization see autoresearch.
日本語の概要は準備中です。原文の説明を表示しています。
Aligns sample metadata with count matrices and constructs design matrices for downstream DE, handling the alphabetical-reference-level trap (relevel BEFORE DESeq), LRT reduced-model rules, the interaction-term resultsNames trap, continuous-covariate scaling and splines, repeated measures via duplicateCorrelation or dream, high-cardinality categorical pseudo-singular designs, sample swap detection via XIST/RPS4Y1 expression and somalier/NGSCheckMate genotypes, SABV (sex-as-biological-variable) mandate, Simpson's-paradox collapsing of technical replicates, and the `~ 0 + group` parameterization for clean contrasts. Use when building a design matrix, troubleshooting reversed fold-change direction, encoding paired or repeated-measures designs, detecting sample swaps, deciding sex-as-covariate, or aggregating technical replicates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "measure how our narrative is landing", "track echo rate against our canon lexicon", or "check how AI answer engines describe our brand"; produces a resonance report — echo rate (overlap of market language with the narrative-registry canon lexicon, method declared), AI-answer perception via tavily.py --answer (proxy-labeled), share-of-voice on a locked competitor panel (reusing share-of-voice-tracker), and resonance signals from bluesky.py / gdelt.py / pageviews.py — every number labeled Measured / proxy / User-provided, feeding the TALE E dimension and the upstream of the E1 evidence-integrity veto. Not for rebuilding share-of-voice machinery — use share-of-voice-tracker; not for own-site GA4/GSC analytics — use performance-monitor; not for scoring TALE profile result — use narrative-quality-auditor; not for adjudicating claims — use offer-claims-registry. 回声率/AI回答感知/份额之声/共鸣信号
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "analyze backlinks", "analyze my off-site signals", or "track AI traffic / ChatGPT / Perplexity referrals"; profiles referring domains, anchor-text mix, toxic links, and disavow candidates (backlinks mode) or isolates AI-assistant referral sessions in GA4/GSC/logs and reports their trend, landing pages, and AI-vs-organic conversion (ai-referrals mode). Not for internal links — use site-structure-optimizer; not for keyword positions — use rank-tracker; not for multi-metric stakeholder reports — use performance-monitor. 外链分析/反向链接/AI流量/AI引荐/ChatGPT流量/AI转化
日本語の概要は準備中です。原文の説明を表示しています。