product-led-seo
Use when asked to "product-led SEO", "programmatic SEO", "build programmatic pages", "organic acquisition for product", "decide if SEO is worth it", or "optimize for AI search". Helps evaluate whether SEO fits your business model and how to approach it as a product, not just marketing. The Product-Led SEO framework (created by Eli Schwartz) treats SEO as building products for search users.
What this skill does
## Domain Context This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work. ## Input Requirements - Context about your product, feature, or problem - Relevant data, research, or constraints (recommended but optional) - Clear articulation of what you're trying to achieve # Product-Led SEO ## What It Is Product-Led SEO is a framework that treats SEO as a product discipline, not just a marketing tactic. The core insight: **SEO success comes from building products that serve searcher intent, not from creating content optimized for keywords.** The traditional approach to SEO is "find keywords, write content, build links." Product-Led SEO asks: "What is the user searching for, and what product experience will satisfy that search?" This framework was developed by Eli Schwartz, who helped companies like Zapier, Tinder, Quora, and SurveyMonkey build SEO strategies that generated hundreds of millions in revenue. The key shift: Move from "How do we rank for this keyword?" to "What product does this searcher need?" ## When to Use It Use Product-Led SEO when you need to: - **Decide if SEO is worth investing in** for your business model - **Develop an SEO strategy** that actually converts (not just drives traffic) - **Build programmatic pages** at scale (like Zapier, Zillow, or TripAdvisor) - **Evaluate your SEO approach** in the age of AI Overviews and LLMs - **Shift from top-of-funnel content** to mid-funnel conversion - **Get product and marketing aligned** on search strategy - **Understand the real ROI** of your SEO investment ## When Not to Use It - **No SEO journey exists**: If users don't search for your solution (most B2B SaaS) - **Committee decisions**: Enterprise sales with long buying cycles rarely convert from SEO - **Brand-driven discovery**: If your product requires brand awareness first - **You need fast results**: SEO takes months to years - **Local businesses with no online transaction ## Resources **Books:** - *Product-Led SEO* by Eli Schwartz **Podcasts:** - Lenny's Podcast: Eli Schwartz episode - Lenny's Podcast: Ethan Smith episode on AEO and AI search ## Further Reading - [Product Led Seo](https://www.productcompass.pm/p/product-led-seo)
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".