# 🚀 Skill: programmatic-SEO-pro (v1.0.0) Human Guide

## What This Is For
Senior Programmatic SEO Architect & Data Engineer for 2026. It gives the agent a clearer input/output frame for search and SEO workflows: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the 🚀 Skill: programmatic-SEO-pro (v1.0.0) agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for 🚀 skill: programmatic-SEO-pro (v1.0.0).
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the 🚀 Skill: programmatic-SEO-pro (v1.0.0) guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- **Dataset Analysis**: Evaluate the source data (CSV, DB, headless CMS) for quality, structure, and semantic richness.
- **Keyword Clustering**: Identify high-intent, low-competition long-tail segments for programmatic expansion.
- **Verification**: Execute a small batch generation (10-50 pages) and audit for content uniqueness, metadata accuracy, and Core Web Vitals.
- **Rule**: Use Next.js 16 `generateMetadata` for every dynamic route.
- **Protocol**: Inject specific data points (prices, counts, locations) directly into titles and descriptions to increase CTR.
- **Rule**: Avoid "thin" programmatic pages. Every page must provide unique value, not just a template swap.
- **Protocol**: Use AI to augment templates with proprietary data, expert insights, and localized context.
- **Rule**: Every programmatic page MUST include JSON-LD (Schema.org) to be eligible for SGE summaries.
- **Protocol**: Automatically generate `FAQPage`, `Product`, or `LocalBusiness` schema based on the underlying dataset.
- **Rule**: Never rebuild the entire site for a data update. Use Next.js 16's refined caching and ISR.
- **Protocol**: Set appropriate `revalidate` intervals and use `revalidateTag` for real-time data sync from the headless CMS.
- **DO NOT** create "doorway pages" that only exist to link elsewhere. Every page must be a destination.

## Decision Points And Nuance
The original skill emphasizes: Executive Summary, 📋 The Conductor's Protocol, 🛠️ Mandatory Protocols (2026 Standards), Dynamic Metadata Mastery, Authority-First Scaling (E-E-A-T), Structured Data as a Requirement, Incremental & Edge Caching, 🚀 Show, Don't Just Tell (Implementation Patterns), Dynamic Routing & Metadata (Next.js 16), Structured Data Injection.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- As of 2026, static metadata is for amateurs. Every programmatic page must have a unique, data-driven identity.
- **Rule**: Avoid "thin" programmatic pages. Every page must provide unique value, not just a template swap.
- **Rule**: Every programmatic page MUST include JSON-LD (Schema.org) to be eligible for SGE summaries.
- **Rule**: Never rebuild the entire site for a data update. Use Next.js 16's refined caching and ISR.
- 🚀 Show, Don't Just Tell (Implementation Patterns)
- 🛡️ The Do Not List (Anti-Patterns)
- **DO NOT** create "doorway pages" that only exist to link elsewhere. Every page must be a destination.
- **DO NOT** generate content that is 90% identical across pages. AI will flag it as "Low Quality."

## Copy-And-Paste Prompt
```text
Use the 🚀 Skill: programmatic-SEO-pro (v1.0.0) human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the yuniorglez/gemini-elite-core skill entry for `programmatic-seo-pro`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# 🚀 Skill: programmatic-seo-pro (v1.0.0)

## Executive Summary
Senior Programmatic SEO Architect & Data Engineer for 2026. Specialized in large-scale page generation using Next.js 16, dynamic metadata orchestration, and database-to-page automation. Expert in scaling content across thousands of long-tail segments while maintaining high E-E-A-T standards and optimizing for AI-driven Search Generative Experiences (SGE).

---

## 📋 The Conductor's Protocol

1.  **Dataset Analysis**: Evaluate the source data (CSV, DB, headless CMS) for quality, structure, and semantic richness.
2.  **Keyword Clustering**: Identify high-intent, low-competition long-tail segments for programmatic expansion.
3.  **Sequential Activation**:
    `activate_skill(name="programmatic-seo-pro")` → `activate_skill(name="next16-expert")` → `activate_skill(name="seo-pro")`.
4.  **Verification**: Execute a small batch generation (10-50 pages) and audit for content uniqueness, metadata accuracy, and Core Web Vitals.

---

## 🛠️ Mandatory Protocols (2026 Standards)

### 1. Dynamic Metadata Mastery
As of 2026, static metadata is for amateurs. Every programmatic page must have a unique, data-driven identity.
- **Rule**: Use Next.js 16 `generateMetadata` for every dynamic route.
- **Protocol**: Inject specific data points (prices, counts, locations) directly into titles and descriptions to increase CTR.

### 2. Authority-First Scaling (E-E-A-T)
- **Rule**: Avoid "thin" programmatic pages. Every page must provide unique value, not just a template swap.
- **Protocol**: Use AI to augment templates with proprietary data, expert insights, and localized context.

### 3. Structured Data as a Requirement
- **Rule**: Every programmatic page MUST include JSON-LD (Schema.org) to be eligible for SGE summaries.
- **Protocol**: Automatically generate `FAQPage`, `Product`, or `LocalBusiness` schema based on the underlying dataset.

### 4. Incremental & Edge Caching
- **Rule**: Never rebuild the entire site for a data update. Use Next.js 16's refined caching and ISR.
- **Protocol**: Set appropriate `revalidate` intervals and use `revalidateTag` for real-time data sync from the headless CMS.

---

## 🚀 Show, Don't Just Tell (Implementation Patterns)

### Dynamic Routing & Metadata (Next.js 16)
`apps/web/src/app/cities/[slug]/page.tsx`:
```tsx
import { Metadata } from 'next';

type Props = { params: Promise<{ slug: string }> };

export async function generateMetadata({ params }: Props): Promise<Metadata> {
  const { slug } = await params;
  const data = await getCityData(slug);

  return {
    title: `Best Coworking Spaces in ${data.name} (2026 Guide)`,
    description: `Discover ${data.count} top-rated spaces in ${data.name}. Average price: ${data.avgPrice}. Verified by local experts.`,
    alternates: { canonical: `https://example.com/cities/${slug}` }
  };
}

export default async function Page({ params }: Props) {
  const { slug } = await params;
  // Render high-value, data-driven content here
}
```

### Structured Data Injection
```tsx
const jsonLd = {
  '@context': 'https://schema.org',
  '@type': 'FAQPage',
  'mainEntity': data.faqs.map(faq => ({
    '@type': 'Question',
    'name': faq.question,
    'acceptedAnswer': { '@type': 'Answer', 'text': faq.answer }
  }))
};

return (
    type="application/ld+json"
    dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
  />