home / skills / phrazzld / claude-config / pseo-generator

pseo-generator skill

safe

This skill generates scalable programmatic SEO pages from JSON data using Next.js templates, with sitemap and validation tooling.

npx playbooks add skill phrazzld/claude-config --skill pseo-generator

Review the files below or copy the command above to add this skill to your agents.

Files (6)

SKILL.md

1.5 KB

---
name: pseo-generator
description: Generate programmatic SEO pages from JSON data using Next.js/React templates, plus sitemap + validation tooling. Use when creating comparison pages, alternatives lists, or “best for [persona]” pages at scale, or when asked to scaffold pSEO data schemas, generate pages, build sitemaps, or check for duplicate/thin content.
effort: high
---

# pSEO Generator

Create pSEO pages from JSON data and template files. This skill ships a Click CLI plus three Next.js/React templates.

## Quick Start

```bash
./scripts/generate.py init --pattern comparison
./scripts/generate.py generate --data ./data.json --template comparison --output ./pages/
./scripts/generate.py sitemap --output ./public/sitemap.xml
./scripts/generate.py validate
```

## Templates

- `templates/comparison.tsx` → X vs Y (features, pricing, verdict)
- `templates/alternative.tsx` → “[X] alternatives” list page
- `templates/best-for.tsx` → “Best [category] for [persona]”

## Playbooks Reference

Use the 12 programmatic SEO playbooks in `../programmatic-seo/SKILL.md` to pick the right pattern. Relevant playbooks: Templates, Curation, Conversions, Comparisons, Examples, Locations, Personas, Integrations, Glossary, Translations, Directory, Profiles.

## Notes

- `init` writes a starter `data.json` schema for the chosen pattern.
- `generate` replaces placeholders in the template with per-page JSON data.
- `sitemap` scans the pages dir and emits a sitemap XML.
- `validate` flags duplicate or thin generated pages.

Overview

This skill generates programmatic SEO (pSEO) pages from structured JSON using Next.js/React templates and a small CLI. It produces comparison, alternatives, and "best for" pages at scale, and includes sitemap generation and validation tools for duplicate or thin content. Use it to automate page scaffolding, rendering, and basic quality checks for large content sets.

How this skill works

The CLI initializes a starter JSON schema for a chosen pattern, then reads per-page JSON records and injects them into React/Next.js templates to produce static page files. It can emit a sitemap by scanning the output directory and runs validation to flag duplicates or thin pages. Templates include comparison, alternative lists, and persona-focused "best for" pages, and placeholders are replaced per JSON entry.

When to use it

Building large sets of comparison or alternatives pages from a structured dataset.
Generating "best for [persona]" pages for different audience segments at scale.
Scaffolding pSEO data schemas before bulk content generation.
Creating a sitemap automatically for generated pages.
Running quick validation checks to catch duplicates or thin content before publishing.

Best practices

Design a clean, consistent JSON schema with required fields for title, meta, slug, and key content blocks.
Include unique, substantive descriptions and feature lists per item to avoid thin or duplicate pages.
Use canonical URLs and consistent slug patterns to prevent index bloat.
Run validate after generation and before deploy to catch issues early.
Limit per-page template complexity to keep rendering predictable and easy to validate.

Example use cases

Generate 500 product comparison pages from a product dataset with pricing and feature arrays.
Create localized alternatives pages by swapping data files for different regions or languages.
Produce persona-focused landing pages like "Best project management tools for small teams" from a single template.
Automatically create a sitemap.xml after generation to feed to search consoles.
Validate a batch of generated pages to surface duplicates and low-content pages prior to publishing.

FAQ

What templates are included?

The skill ships comparison (X vs Y), alternative lists ("[X] alternatives"), and "best for" (Best [category] for [persona]) templates.

How does validation work?

Validation scans generated pages for duplicate titles/slugs and flags pages with low word count or missing key fields so you can fix content before publishing.