スキルを探す

Find quick SEO wins by identifying high-impression, low-CTR keywords using Google Search Console data. Surfaces keywords already ranking where better titles or content expansion could quickly boost traffic. Use when user says "GSC opportunities", "quick wins", "low CTR keywords", "high impressions low clicks", or "easy SEO wins".

日本語の概要は準備中です。原文の説明を表示しています。

Autonomous SEO + AI-search optimization agent for 2026. Audits and fixes technical SEO, on-page metadata, structured data, Core Web Vitals (LCP/INP/CLS), llms.txt, Generative Engine Optimization (GEO) for ChatGPT/Perplexity/AI Overviews, E-E-A-T author signals.

日本語の概要は準備中です。原文の説明を表示しています。

Pull and analyze Google Search Console data via the GSC API. Produces: weekly query × page performance with WoW/MoM/YoY deltas, top movers report (winners + losers ranked by absolute click change), click-loss attribution (lost rank? Triggers: "GSC", "Google Search Console".

日本語の概要は準備中です。原文の説明を表示しています。

Audit technical SEO across crawlability, indexability, security, URLs, mobile, Core Web Vitals, rendering, structured data, and IndexNow. Exclude content strategy and backlinks.

日本語の概要は準備中です。原文の説明を表示しています。

Build a blog-level strategy for a niche or business: audience segments, 3-5 content pillars with hub-and-spoke clusters, competitive gaps, measurement plan, and a 90-day roadmap. Use when the user says "blog strategy", "content strategy", "blog positioning", "content pillars", "what should I blog about". Not for a dated publishing schedule (blog-calendar), SERP-validated cluster maps (blog-cluster), or a brief or outline for one post (blog-brief, blog-outline). Makes no promise of rankings or AI citations.

日本語の概要は準備中です。原文の説明を表示しています。

Detect, validate, or generate Schema.org JSON-LD for a supplied page or entity. Use only when structured data or rich-result markup is requested.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and improve content for AI Overviews and answer engines, including citability, entity clarity, crawler access, brand signals, and passage structure.

日本語の概要は準備中です。原文の説明を表示しています。

Hreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language/region codes, and generates correct hreflang implementations. Use when user says "hreflang", "i18n SEO", "international SEO", "multi-language", "multi-region", or "language tags".

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Build a dated monthly or quarterly editorial calendar: which posts to publish or review when, content mix, templates, distribution timing, and a material-change review queue. Use when the user says "editorial calendar", "content calendar", "publishing schedule", "what should I write this month". Not for positioning or pillars (blog-strategy), SERP-validated cluster maps (blog-cluster), or detecting declining pages from Search Console exports (blog-decay). Publication frequency is not a ranking signal.

日本語の概要は準備中です。原文の説明を表示しています。

Turn an existing blog post into draft text for other channels: X threads, LinkedIn posts, Threads/Bluesky, short-video scripts, YouTube scripts, Reddit posts, newsletter excerpts, podcast scripts. Saves drafts to files; it never posts anywhere. Never invents personal stories or results: first-hand framing appears only when the user supplies it. Use when the user says "repurpose", "turn this post into a thread", "linkedin post from blog", "youtube script from post". Not for writing the blog post itself (blog-write) or scheduling.

日本語の概要は準備中です。原文の説明を表示しています。

Credentialed Google API calls for a blog: PageSpeed Insights, CrUX history, Search Console performance and URL Inspection, GA4 organic traffic, Cloud NLP entities, YouTube video search, Google Ads Keyword Planner, and the Indexing API (job and livestream pages only). Uses the user's Google credentials, quotas, and sometimes billing, and asks for consent before the first call. Runs only on an explicit request: /blog google, "run PageSpeed on this blog URL", "pull my Search Console data", "inspect this URL's index status", "set up Google API credentials". Shares config with claude-seo at ~/.config/claude-seo/google-api.json.

日本語の概要は準備中です。原文の説明を表示しています。

Compare two Google Search Console page exports (current vs previous period) to flag pages whose clicks or impressions fell by a chosen threshold, with a triage hint (refresh, query shift, consolidate, prune). The 20% default is a screening heuristic, not proof of decay. Use for "/blog decay", "content decay", "QoQ decline", "refresh declining posts". Needs two GSC exports; not for diagnosing a single traffic drop live (blog-google) or rewriting posts (blog-rewrite).

日本語の概要は準備中です。原文の説明を表示しています。

SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

日本語の概要は準備中です。原文の説明を表示しています。

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

日本語の概要は準備中です。原文の説明を表示しています。

Fundamentos de SEO, E-E-A-T, Core Web Vitals e princípios do algoritmo do Google.

日本語の概要は準備中です。原文の説明を表示しています。

Quando o usuário quer auditar, revisar ou diagnosticar problemas de SEO no seu site. Também use quando o usuário menciona "auditoria de SEO," "SEO técnico," "por que não estou ranqueando," "problemas de SEO," "SEO on-page," "revisão de meta tags," ou "verificação de saúde de SEO." Para construir páginas em escala visando palavras-chave, veja programmatic-seo. Para adicionar dados estruturados, veja schema-markup.

日本語の概要は準備中です。原文の説明を表示しています。

Geração de demanda multi-canal, otimização de mídia paga, estratégia de SEO e programas de parcerias para startups Series A+. Inclui calculadora de CAC, playbooks de canal, integração com HubSpot e táticas de expansão internacional. Use ao planejar campanhas de geração de demanda, otimizar mídia paga, construir estratégias de SEO, estabelecer parcerias, ou quando o usuário menciona demand gen, anúncios pagos, LinkedIn ads, Google ads, CAC, aquisição, geração de leads ou pipeline.

日本語の概要は準備中です。原文の説明を表示しています。