An architecture guide for programmatic SEO systems with 10,000 or more pages. Programmatic SEO creates many pages from structured data, and this guide covers databases, incremental checks, crawl-budget management, content enrichment, and staged delivery.

Designing data-backed page generation, validating only changed content, managing large sitemaps, improving indexing workflows, and planning staged releases for very large sites.

Large sites can run out of memory, validate too much at once, or publish pages faster than search engines can crawl them. The guide replaces small-site approaches with scalable ones.

pseo-scale — Skill for Claude Code by lisbeth718/pseo-skills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add lisbeth718/pseo-skills --skill pseo-scale

Clone the repo

git clone --depth 1 https://github.com/lisbeth718/pseo-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-scale/github.svg)](https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-scale)

Your own site

<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-scale"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-scale/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/pseo-scale"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/pseo-scale.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,275 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00080	$0.06275
Opus 5.5	$0.00032	$0.02510
Sonnet 5.5	$0.00016	$0.01255
Haiku 4.5	$0.00008	$0.00628

Measured 9d ago against content hash f783a04b6191, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pseo-scale scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pseo-scale/SKILL.md · 536 lines

How it starts

The opening of the file, as written. The whole thing — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pSEO Scale Architecture

Scope parameter

Value	Sections
`database`	1
`gating`	2
`enrichment`	3
`validation`	4
`crawl`	5
`monitoring`	6
`cdn`	7, 8
`all`	everything

Architect pSEO systems that work at 10K-100K+ pages. The patterns in the other pseo-* skills are correct at 1K-10K. Beyond 10K, in-memory data layers, full-corpus validation, and single-deploy rollouts break down. This skill provides the architecture changes needed at scale.

Scale Tiers

Tier	Pages	Data Layer	Validation	Rollout	Sitemap
Tiny	< 100	JSON/files, in-memory	Full pairwise	Single deploy	Single file
Small	100-1K	JSON/files, in-memory	Full pairwise	1-4 weeks in batches of 50-200	Single file
Medium	1K-10K	Files or DB, two-tier memory	Fingerprint-based	4-8 weeks in batches	Index + children
Large	10K-50K	Database required	Incremental + sampling	Category-by-category	Index + chunked
Very Large	50K-100K+	Database + cache layer	Delta-only + periodic full	ISR + sitemap waves	Index + streaming

Rollout pacing in this table is an operational heuristic shared with pseo-performance, not a Google rule.

This skill focuses on the Large and Very Large tiers. If the project is under 10K pages, the standard pseo-* skills are sufficient.

1. Database-Backed Data Layer

At 10K+ pages, JSON files and in-memory arrays stop working. The data layer must move to a database with proper indexing.

Why In-Memory Breaks

Pages    PageIndex in memory    Full content (if loaded)
1K       ~1MB                   ~100-500MB
10K      ~10MB                  ~1-5GB (OOM)
50K      ~50MB (borderline)     ~5-25GB (impossible)
100K     ~100MB                 ~10-50GB (impossible)

At 50K+, even holding all PageIndex records in memory is borderline. At 100K, getAllSlugs() returning an array of 100K objects takes ~100MB and seconds to deserialize. You need cursor-based iteration.

Read the full file on GitHub · 536 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago Changed · -76 lines f783a04b6191
26d ago Changed · +32 lines c77cd2001124
2mo ago First seen · 580 lines · 80 tokens per session scan A 01d83e35e8be

Subscribe to this mod's changes

pseo-scale is a skill published in the GitHub repository lisbeth718/pseo-skills (55 stars, last pushed 9d ago), licensed MIT. It adds 80 tokens to every session and 6,275 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Databases Marketing and SEO

pseo-scale next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pseo-scalelisbeth718/pseo-skills	Skill	55	9d ago	MIT	A	80	Claude Code
create-prprisma/orm	Skill	48k	yesterday	Apache-2.0	A	48	Claude Code, Codex
schema-explorationlangchain-ai/deepagents	Skill	31k	yesterday	MIT	A	57	Claude Code, Codex
atlas-mssqlariga/atlas	Skill	8.8k	yesterday	Apache-2.0	A	163	Claude Code
ha-data-storesshiwenwen/hope-agent	Skill	1.9k	yesterday	MIT	A	115	Claude Code, Codex
nornicdb-cypher-queriesorneryd/NornicDB	Skill	923	yesterday	MIT	A	79	Claude Code, Codex
volcengine-rds-postgresqlbytedance/agentkit-samples	Skill	484	today	Apache-2.0	A	63	Claude Code, Codex