sergekostenchuk/seo-llm-skill-cluster / skills/information-architecture-seo
information-architecture-seo
VerifiedConvert a semantic core into crawlable SEO and LLM-friendly information architecture. Use this skill when the user asks for URL structure, page taxonomy, canonical rules, hreflang groups, page roles, pillar/topic/news/article/blog/project separation, multilingual route strategy, or a durable content model such as one short brief plus one longform article. It prevents duplicate public content bodies and hands link-graph work to internal-link-graph-architect.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.1 KB |
| agents/openai.yaml | config | 401 B |
| assets/url-map.template.yaml | config | 3.1 KB |
| evals.json | config | 2.2 KB |
| references/url-architecture.md | markdown | 3.2 KB |
| validation-report.md | markdown | 1.4 KB |
references/url-architecture.md
View on GitHub# URL Architecture Reference
## Purpose
Information architecture turns semantic demand and entities into crawlable, understandable, maintainable public URLs.
The output should help humans, search engines, and LLM agents understand what each page is for and how it relates to the rest of the site.
## Page Role Model
| Page Role | Job | Canonical Pattern |
| --- | --- | --- |
| `home` | Position the site, route readers, expose fresh and durable sections. | self-canonical |
| `news_index` | List short news briefs for a language or topic. | self-canonical |
| `news_brief` | One short news surface for one story. | self-canonical when distinct from longform |
| `longform_article` | One expanded explanation for one story. | self-canonical when distinct from brief |
| `topic` | Evergreen organization page for a topic/entity cluster. | self-canonical |
| `project` | Public project/entity page. | self-canonical |
| `blog` | Author essay or working note. | self-canonical |
| `author` | Person/entity profile and trust page. | self-canonical |
| `community` | Social/community link hub. | self-canonical or noindex depending value |
| `utility` | RSS, sitemap, llms.txt, robots, admin, API. | index only when public useful |
## One Brief Plus One Longform
For a publication model with a short news brief and one expanded article:
- the brief answers what happened quickly;
- the longform explains context, sources, implications, and related entities;
- each page can be self-canonical because the page roles differ;
- each page should link to the other;
- there should not be a third public story body except a homepage teaser or index excerpt;
- topic pages can link and summarize, but not reproduce the story body.
## Canonical Decisions
Use self-canonical when:
- the page has unique visible value;
- the page serves a different role from a related page;
- the page is meant to be indexed.
Use canonical to another URL when:
- the page is a duplicate or near-duplicate technical variant;
- the page is a print/filter/query/session variant;
- the page is not intended as a standalone search result.
Use noindex when:
- the page is useful for users but low-value or private for search;
- the page is staging, admin, internal API, or duplicate filter output.
## Hreflang Rules
Hreflang groups must connect true language equivalents.
For each localized page:
- canonical points to itself;
- `hreflang` points to alternate language equivalents;
- `x-default` points to the default language or language selector;
- localized slugs are allowed when stable and maintainable.
## Duplicate-Content Checks
Flag these:
- brief canonicalized to longform despite distinct page role;
- topic page copying article body;
- homepage carrying full news body instead of teaser;
- translated page published before translation quality is known;
- multiple public URLs for the same story body;
- tag/category pages with no unique value.
## Handoff
After URL architecture:
- `internal-link-graph-architect` designs links, anchors, breadcrumbs, and source trails;
- `technical-seo-schema-engineer` designs metadata, schema, sitemap, RSS, robots, and llms.txt;
- `llm-friendly-site-architect` designs direct answers, entity surfaces, markdown alternates, and AI crawler-readable layers.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |