본문으로 건너뛰기
cccskills
무료GitHub에 공개

programmatic-seo

Use when planning many similar pages from a template and a data set: choosing the pattern, deciding whether the data can carry it, and avoiding the thin-content failure that gets page sets deindexed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md4.9 KB
  • references/playbooks.md5.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Programmatic SEO

Building pages from a template and a data set works when each page answers a real query with something only your data can say. It fails the same way every time: a template with the variable swapped, published at volume, on queries nobody searches. That is the definition of a doorway page, and Google's spam policies name it.

So the question to settle before any of the mechanics is whether the data is worth a page.

Does the data carry it

Defensibility runs in this order, strongest first:

  1. Proprietary, because you generated it.
  2. Product-derived, from how your own users behave.
  3. User-generated, from your community.
  4. Licensed, where the license is exclusive.
  5. Public, which anyone can use and everyone already has.

A set built on public data competes with every other set built on the same public data, so it has to win on presentation, freshness, or aggregation instead. That is possible and it is a much harder brief. Say so rather than shipping 5,000 pages that restate a public API.

Then check demand actually exists: aggregate volume across the pattern, how it splits between head and long tail, and whether the trend is going anywhere. A pattern with 10,000 combinations and no searches for 9,000 of them is a 1,000-page opportunity.

Choosing a pattern

You haveConsider
Proprietary data setDirectory, Profiles
A product with integrationsIntegrations
A design or creative productTemplates, Examples
Several distinct audience segmentsPersonas
A local footprintLocations
A utility or calculatorConversions
Deep subject expertiseGlossary, Curation
A crowded competitive fieldComparisons

references/playbooks.md covers the twelve patterns, each with its query shape, what data it needs, and how it usually fails.

Patterns layer, and layering is often where the real opportunity is: "best coworking spaces in Austin" is Curation crossed with Locations.

Making each page worth indexing

  • Every page needs something specific to it beyond the substituted variable: a number, a comparison, a list, an image, a genuine answer.
  • Write the introduction per page, or generate it from enough fields that no two read alike. A shared paragraph with one word swapped is the tell.
  • Vary structure by what the data supports. A page with three data points shouldn't use the layout built for thirty; branch the template instead of padding.
  • Give each page a unique title and meta description built from its variables, not one pattern with the variable appended.
  • Match the query's intent. A comparison query wants a comparison, not a signup page.

Structure and indexation

  • Subfolders, not subdomains, so the pages build authority on the same domain rather than splitting it.
  • Hub and spoke: a category page linking to every page in the set, each page linking back, and related pages cross-linking. Otherwise the set is orphaned and only the sitemap points at it.
  • Own sitemap for the set, or a sitemap per pattern, so indexing rates per pattern are readable.
  • Ship the strongest slice first rather than the whole set. Publish the highest-demand pages, confirm they get indexed and ranked, then expand. A set that goes out all at once gives no signal about which part worked.
  • Leave the thinnest variations out entirely. That is better than publishing them and noindexing them later, since crawl spent on pages you didn't want is crawl not spent on pages you did.

Before it ships

Check that each page has unique value and answers its query, that titles and descriptions are unique, that heading structure and schema are in place, that the set is linked from the site rather than only the sitemap, that no page has a conflicting noindex, and that nothing in the set competes with an existing page for the same query.

After launch, watch what fraction of the set gets indexed, which patterns rank, and whether engagement holds up. Thin-content warnings, a drop across the set, or an indexing rate that stalls well below 100% all mean the same thing: cut, don't add.

What this hands off

Programmatic SEO decides the pattern, the data, the URL shape, the template's sections, and the linking. The words inside a template section are copy: hand the content marketer the template, the target query, and the fields available per page.

Sources

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/claude-codex-settings1.2천2026년 10월 20일 업데이트

Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/claude-codex-settings1.2천2026년 10월 20일 업데이트

Build, debug, or review Cloudflare Agents SDK applications using the agents package.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/claude-codex-settings1.2천2026년 10월 20일 업데이트

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/claude-codex-settings1.2천2026년 10월 20일 업데이트

This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/claude-codex-settings1.2천2026년 10월 20일 업데이트

basin

무료

Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fcakyon/claude-codex-settings1.2천2026년 10월 20일 업데이트

fcakyon의 스킬 모두 보기

이 스킬의 문제 신고