Marketing & SEO Workflows

Use when adding JSON-LD structured data to a page — Article, BlogPosting, Product, FAQPage, HowTo, BreadcrumbList, Organization, WebSite, TouristTrip. Picks the right schema type for the page, populates required + key recommended fields from the actual content, validates against schema.org, and ships in a single PR. Triggers on "add schema", "add JSON-LD", "structured data", "rich results", "FAQ schema", "Article schema", "Product schema", "BreadcrumbList", "schema markup for [page]", or any time per-page schema is being added or audited.

Use when running a competitor SERP diff, asking why a competitor outranks you, building a content brief, or auditing what top-3 ranking pages cover that yours doesn't. Auto-triggers on "content gap analysis", "competitor SERP", "why does X outrank us", "what are competitors covering that we aren't", "content brief", "SERP analysis". Takes a target query + your URL, scrapes top-3 via Firecrawl, diffs entities/H2s/schema/depth/freshness/AIO presence, and ships CONTENTBRIEF.md with gaps ranked by impact. Pairs with optimizing-on-page (fills the gaps) and planning-topic-clusters (when gaps span sub-topics).

Use when running a technical SEO audit, debugging Core Web Vitals regressions, checking indexability, validating schema and sitemaps, diagnosing why a site isn't ranking, or preparing a site for AI-search visibility (GPTBot, ClaudeBot, PerplexityBot). Covers crawlability, indexability, rendering, Core Web Vitals, schema, AI-search readiness, mobile, security, and meta basics. Lifecycle-aware — pre-launch, growth, mature. Produces a prioritized SEOAUDIT.md and a low-risk fix PR.

Use when building Google E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals, writing author bios, planning thought-leadership SEO, hardening trust on YMYL (Your Money Your Life) content, getting cited as an authority by AI engines, or building a long-term authority moat from zero. Triggers on phrases like "E-E-A-T", "author bios", "build authority", "thought leadership SEO", "Google trust signals", "YMYL", "how to get cited as an authority". Long-game skill — invest 6+ months before you need it.

Use when optimizing existing pages for SEO, hunting low-hanging keyword opportunities, analyzing pages that get impressions in Google Search Console but few clicks, or planning a content refresh. Covers the full content lifecycle (initial → growth → mature) and integrates with Generative Engine Optimization (GEO) for AI-search visibility. Applies to any site with GSC access.

Use when generating hundreds or thousands of unique landing pages from a structured data source (Supabase table, CSV, Sanity collection) — city pages, category pages, "[X] for [Y]" matrices, integration pages, directory listings. Wires data + template + LLM enrichment + per-page schema + sitemap inclusion + internal-link graph, with quality gates that keep output on the Tripadvisor/Zapier side and away from Google's scaled-content-abuse policy. Auto-triggers on "programmatic SEO", "generate landing pages from data", "scale content", "city pages", "category pages", "[X] for [Y] pages", or "directory site SEO".

Use when optimizing content for AI search ("GEO"), getting cited in ChatGPT, Claude, Perplexity, or Gemini, ranking in Google AI Overviews, making a page LLM-citable, defending against AI-citation decay, or running an "AI SEO" pass on existing content. Triggers on phrases like "optimize for AI search", "GEO", "get cited in ChatGPT", "Perplexity ranking", "AI Overview optimization", "make this LLM-citable", "AI SEO". Cross-cuts the content lifecycle — fires per-page on growth content, becomes critical on mature pages for citation defense.

Use when optimizing a single page for SEO — fixing title and meta, tightening H1/H2 hierarchy, improving internal linking and anchor text, auditing alt text, capturing featured snippets, or aligning a page with search intent. Auto-triggers on "optimize this page", "fix the SEO on this URL", "polish this blog post", "title and meta", "improve internal linking", "alt text audit". Per-page workhorse — takes a URL or markdown/MDX file path, ships ONE focused PR with title/meta/H/link/alt edits. Pairs with finding-underserved-keywords (feeds keywords in), auditing-technical-seo (clears blockers first), and adding-schema-markup (hands JSON-LD off).

Use when planning a content architecture from a keyword map, designing pillar pages and supporting spokes, drawing an internal-link graph, deciding what to write next, building a content calendar, or reorganizing legacy posts into topical authority clusters. Triggers on "topic clusters", "content architecture", "pillar pages", "internal link graph", "what should I write next", "content calendar", "SEO content plan". Produces CONTENTPLAN.md with cluster map, slugs, link matrix, and publishing order.

Use when content is losing traffic, dropping in rankings, or showing decay signals in Google Search Console — impressions down >20% YoY, position sliding, CTR rotting, or LLM citations falling. Auto-triggers on phrases like "refresh this content", "fix the decay", "traffic is dropping on /blog/X", "update old post", "content refresh". Pairs with gsc-mcp for decay detection and opens a single PR with updated copy, schema (dateModified), internal links, and an IndexNow ping. Mature-phase only — page must have >6 months of GSC data.

Use when starting keyword research for a brand-new site with no Google Search Console history yet — pre-launch, just-launched, or first 90 days. Covers cold-start discovery via Google autocomplete / People Also Ask / related searches, Google Trends, Reddit/HN/Indie Hackers demand mining, competitor SERP overlap, and AI-search query patterns. Produces a clustered KEYWORDMAP.md to seed the first content slate. Auto-triggers on "what should I write about", "keyword research from scratch", "no GSC data yet", "cold start SEO", "what keywords should I target", "pre-launch keyword research", "topic ideas for new site".

Use on day 1 of a project to ship sitemap, robots.txt, OG image, and JSON-LD schema in a single PR. Auto-detects Next.js, Astro, or SvelteKit, audits what's already there, and only generates what's missing. Triggers on "set up SEO", "SEO bootstrap", "configure SEO", "add sitemap", "add robots.txt", "make my site SEO-ready", or "I just shipped a site, help me with SEO.

Meta-router for SEO work. Use when the user asks vaguely for SEO help — "improve my SEO", "audit my site", "traffic is dropping", "what should I write about", "help my site rank", "is my site set up right for Google", "AI isn't citing my product". Diagnoses site state and routes to the right child skill (finding-underserved-keywords, seo-bootstrap, auditing-technical-seo, etc.) plus MCP tools (gsc-mcp, lighthouse-mcp). Loses ties on purpose: if the user names a specific skill territory ("striking distance keywords", "GSC query analysis", "technical audit", "schema markup", "sitemap"), let that skill win. Do NOT trigger when the request is already specific.

Use when bootstrapping SEO measurement on a new or existing site — verifying Google Search Console, submitting a sitemap, wiring GA4 or Plausible analytics, enabling Bing Webmaster Tools, or laying groundwork for AI-citation (GEO) tracking. Triggers on "set up Google Search Console", "verify domain", "submit sitemap", "GA4 setup", "measure SEO", "track AI citations", "connect GSC". Pairs with /seo-setup (credentials) and runs once at site bootstrap; every other skill in this plugin assumes GSC is already streaming data.