sergekostenchuk/ui-ux-agent-skill-system

information-architecture-seo

Convert a semantic core into crawlable SEO and LLM-friendly information architecture.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill information-architecture-seo

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Information Architecture SEO

Use this skill after semantic-core-architect and before internal linking, schema, or LLM-readable layers.

Read references/url-architecture.md before producing a full URL map.

Owns

  • URL strategy;
  • page taxonomy;
  • page roles and content ownership;
  • canonical model;
  • hreflang groups;
  • index/noindex policy;
  • pillar/topic/news/article/blog/project role separation;
  • duplicate-content prevention.

Does Not Own

  • semantic core creation;
  • final page copy;
  • internal link graph details;
  • JSON-LD implementation;
  • rendered UI design;
  • external backlinks.

Workflow

  1. Read the semantic core, entity-topic map, site constraints, languages, and content model.
  2. Identify the canonical page role for each cluster/entity/topic.
  3. Define route patterns before individual URLs.
  4. Set canonical policy per page role.
  5. Define hreflang groups for localized equivalents.
  6. Mark page status: planned, draft, published, noindex, or deferred.
  7. Record duplicate-content risks and ownership boundaries.
  8. Produce url-map.yaml using assets/url-map.template.yaml.
  9. Hand off to internal-link-graph-architect and technical-seo-schema-engineer.

Canonical Rules

  • A page can be self-canonical when it has a distinct user/search role and visible content.
  • A short news brief and one expanded longform article can both be self-canonical when the brief is the fast news surface and the longform is the durable explanation surface.
  • Do not canonicalize a standalone brief to its longform by default.
  • Do not create extra public story variants beyond the declared model.
  • Topic and pillar pages must summarize and organize; they must not duplicate article bodies.
  • Locale alternates use hreflang; they do not replace canonical self-reference.

Multilingual Rules

  • Default language owns x-default unless the site has a separate language selector page.
  • Every localized page must declare its own canonical URL.
  • Hreflang groups must contain only true equivalents, not loosely related pages.
  • If translation quality is unknown, mark the localized page as draft or deferred, not published.

Safety And Privacy Boundaries

  • Do not expose admin, API, private dashboards, raw analytics, raw IP logs, secret files, or staging URLs as public indexable pages.
  • Use noindex or blocked internal routing for low-value utility pages; do not rely on public navigation hiding.
  • Do not weaken authentication, access control, or security headers for crawlability.
  • Do not place private source URLs, credentials, tokens, unpublished drafts, or internal notes in url-map.yaml, sitemap plans, or public LLM-facing artifacts.

Validation

Before marking work complete:

  • every page has URL, page type, locale, canonical, index policy, and rationale;
  • every language alternate has a coherent hreflang group;
  • every story has at most one brief and one longform per language;
  • topic pages do not duplicate article bodies;
  • final link graph details are left for internal-link-graph-architect;
  • schema implementation is left for technical-seo-schema-engineer.

Validate skill edits with:

bash
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $HOME/SKILL/skills/information-architecture-seo
python3 $HOME/SKILL/plans/seo-llm-skill-cluster/scripts/lint_skill_cluster.py $HOME/SKILL

Forward tests live in evals.json.

Output Shape

Return:

  1. URL strategy summary.
  2. Page role table.
  3. Canonical and hreflang policy.
  4. Duplicate-content risks.
  5. Handoff notes for internal linking and technical SEO/schema.

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
sergekostenchuk
社区

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

1小时安装量
1
GitHub Stars
35
最近更新
9月13日
sergekostenchuk
社区

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

1小时安装量
1
GitHub Stars
35
最近更新
9月13日
sergekostenchuk
社区

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

1小时安装量
1
GitHub Stars
35
最近更新
9月13日
sergekostenchuk
社区

editorial-quality-gate

Review public site content for editorial quality, source support, prompt residue, duplicate blocks, translation drift, hidden filler, and human usefulness before SEO or LLM-friendly publication. Use this skill when the user asks to quality-gate news briefs, longform explainers, blog posts, topic pages, project pages, translated content, or generated article drafts without changing the live publishing pipeline.

1小时安装量
1
GitHub Stars
35
最近更新
9月13日