programmatic-seo · fcakyon — скилл для Claude Code: что делает и как установить
Скилл programmatic-seo помогает спланировать генерацию страниц по шаблонам и базам данных, чтобы защитить сайт от санкций поисковиков за бесполезный контент.
MIT ★ 1 216 обновлён 2026-11-09
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install seo-skills@claude-settingsЧто делает programmatic-seo
Скилл задаёт правила запуска страниц на базе шаблонов и структурированных данных. Он оценивает ценность исходных данных по шкале надёжности, от собственных метрик продукта до общедоступных API, и помогает выбрать архитектуру вроде каталогов или сравнений.
Для защиты от деиндексации алгоритмы скилла требуют варьировать разметку страниц под реальный объём полей. Шаблон ветвится, если данных мало, а для списков предписывается использовать Intl.ListFormat. Перелинковка строится по схеме hub-and-spoke в подпапках домена, а не на поддоменах.
Запуск всей пачки в 5000 страниц без проверки спроса приведёт к фильтрам за дорвеи. Лишние страницы тратят краулинговый бюджет впустую. Безопаснее выкатывать сначала самую востребованную часть выборки с отдельным файлом sitemap.
Какие задачи решает
- выбрать шаблон страниц под конкретную структуру базы данных
- проверить устойчивость набора данных перед массовой публикацией
- настроить схему перелинковки hub-and-spoke без страниц-сирот
- предотвратить санкции поисковых систем за дубли и тонкий контент
Примеры запросов агенту
- Разбери базу вакансий и предложи шаблон для страниц категорий
- Проверь структуру шаблона сравнения сервисов, чтобы страницы не склеились в поисковике
- Спланируй запуск каталога интеграций через подпапки и составь схему перелинковки
Как установить programmatic-seo
1Через маркетплейс плагинов
/plugin marketplace add fcakyon/claude-codex-settings/plugin install seo-skills@claude-settingsКоманда ставит плагин seo-skills целиком, со всеми его скиллами
2Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill programmatic-seo -a claude-code3Вручную: положить файлы
~/.claude/skills/programmatic-seo/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/programmatic-seo/
1Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill programmatic-seo -a codex2Вручную: положить файлы
.agents/skills/programmatic-seo/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill programmatic-seo -a cursor2Вручную: положить файлы
.cursor/skills/programmatic-seo/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/seo-skills/skills/programmatic-seo2Вручную: положить файлы
.github/skills/programmatic-seo/SKILL.md1Через Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill programmatic-seo -a gemini-cli2Командой платформы
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/seo-skills/skills/programmatic-seoВручную: положить файлы
.devin/skills/programmatic-seo/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Claude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы о programmatic-seo
Как установить programmatic-seo в Claude Code?
Выполните последовательно две команды: /plugin marketplace add fcakyon/claude-codex-settings, затем /plugin install seo-skills@claude-settings.
Зачем нужен скилл programmatic-seo?
Скилл помогает выстроить архитектуру программных страниц, выбрать модель шаблона и защитить проект от попадания под фильтры Google за пустой контент.
Почему скилл советует публиковать страницы в подпапках, а не на поддоменах?
Подпапки концентрируют авторитет на основном домене, тогда как поддомены дробят поисковый вес и усложняют индексацию всего набора.
Исходный текст
SKILL.md · MIT
--- name: programmatic-seo description: "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." license: MIT --- # 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 have | Consider | | --- | --- | | Proprietary data set | Directory, Profiles | | A product with integrations | Integrations | | A design or creative product | Templates, Examples | | Several distinct audience segments | Personas | | A local footprint | Locations | | A utility or calculator | Conversions | | Deep subject expertise | Glossary, Curation | | A crowded competitive field | Comparisons | `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. ## Linking and copy in generated sets Large sets fail in ways a single page review won't show: - Related-link orphans: a related block ranked by similarity sends most links to a few popular pages and leaves the long tail with none. Count inbound links per page from the template's real links, and make one slot deterministic, such as the next page in catalog order, so every page has at least one. - Location-filtered hubs: Googlebot's [default IP addresses are in the US and it sends no `Accept-Language`](https://developers.google.com/search/docs/specialty/international/locale-adaptive-pages), so a hub that filters by visitor country shows it only the US subset. Pages outside that subset end up linked only from the sitemap unless a crawl path ignores location, such as related links or an unfiltered index. - Parent pages: a summary written for one child, such as an episode or a product variant, misdescribes its parent. Write the parent's description from fields aggregated across its children. - Spam policy names: Google's [spam policies](https://developers.google.com/search/docs/essentials/spam-policies) call the two failures doorway abuse, near-identical pages built for similar queries, and scaled content abuse, many low-value pages made mainly to rank however they were produced. If an LLM writes intros, titles, descriptions, or alt text, Google asks you to [fact check it before publishing](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content), so review a sample from every pattern. - Hosted sets: a third-party set published on an established domain mainly for that host's ranking signals falls under Google's site reputation policy, and moving a demoted set to a new subdomain or folder counts as circumvention. - Empty and list fields: when a list is empty, branch the sentence instead of printing a dangling colon, and join lists with `Intl.ListFormat` in the page's locale so they read natively in each language. ## Sources - Google Search Central, Spam policies: https://developers.google.com/search/docs/essentials/spam-policies - Google Search Central, Creating helpful, reliable, people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content - Google Search Central, Sitemaps overview: https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview
© fcakyon · MIT · fcakyon/claude-codex-settings
Похожие скиллы
Все скиллы по теме «SEO и GEO» →Сначала — programmatic-seo от других авторов.