seo-architecture
Skill6 starsChanged 3 months agoApache-2.0View on GitHub
Use when auditing or designing site architecture, internal-link graphs, crawl depth, orphan pages, hubs, navigation, contextual anchors, pagination, facets, taxonomy, template links, or URL-to-query coverage at scale; require a bounded captured graph and business/user rationale rather than arbitrary click-depth, link-count, or PageRank-like score targets.
In this repository27 other files it gives its agents.
- llms.txtllms.txt
- ai-search-researchSkill
- ai-visibility-monitorSkill
- optimise-seoSkill
- seo-action-planSkill
- seo-aeoSkill
- seo-agenticSkill
- seo-auditSkill
- seo-authoritySkill
- seo-commerceSkill
- seo-competitor-pagesSkill
- seo-contentSkill
- seo-geoSkill
- seo-hreflangSkill
- seo-imagesSkill
- seo-localSkill
- seo-news-discoverSkill
- seo-pageSkill
- seo-performanceSkill
- seo-planSkill
- seo-programmaticSkill
- seo-researchSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-technicalSkill
- seo-videoSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Create and audit a bounded site-graph.json that explains how users and permitted crawlers discover important pages, how templates connect, …
- Distinctive: line 17
Read site-graph-protocol.md before a formal architecture audit.
- Very specific: line 33
After graph validation, package only supported observations as SEO Findings 1.1.0.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SEO Architecture
Markdown delivery contract
Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats. Include concise robots/XML-sitemap discovery comments and llms.txt navigation sentences pointing to actual Markdown answers; preserve the native protocols and verify delivery as described in the local contract.
Lane outputs: site-architecture.md; navigation-map.md (combine small related steps with stable section links). Build llms.txt -> sitemap.md -> topic map -> substantive page.md paths with descriptive direct destinations. Audit orphans, cycles, collisions, dead links and question-to-answer task completion. Avoid forced traversal through irrelevant HTML navigation.
Create and audit a bounded site-graph.json that explains how users and permitted crawlers discover important pages, how templates connect, and where query/entity coverage lives.
Read site-graph-protocol.md before a formal architecture audit.
Procedure
- Define domain/subdomain scope, environments, URL patterns, crawl authorization, seed pages, locale, user tasks, business-critical templates, exclusions, and collection limits.
- Capture nodes and crawlable link edges with source/target URLs, link location, anchor or accessible name, follow state, template/context classification, and observation time.
A supported crawler CSV can be normalized with
python "<suite-root>/scripts/import_seo_exports.py" crawler-csv ...using<suite-root>/docs/DATA-IMPORT-ADAPTERS.md, but that observation envelope is not a Site Graph: bind every node and edge to the raw captures and metadata required by the Site Graph contract. - Let
<suite-root>mean${CLAUDE_PLUGIN_ROOT}in Claude Code. In Codex, read.seo-suite-runtime.jsonbeside thisSKILL.mdwhen present and use itssuite_rootvalue; otherwise use the absolute repository checkout. Validate the graph withpython "<suite-root>/scripts/validate_site_graph.py" validate-graph <bundle>/site-graph.json --bundle <bundle>. - Inspect disconnected/orphan nodes, inbound-path evidence, hubs, crawl paths, pagination, facets, filters, parameter spaces, taxonomy, duplicate routes, canonical/index conflicts, and locale clusters.
- Map the formal Query Corpus and entity/page ownership to nodes. Do not create a page or link merely because a keyword exists.
- Propose the smallest user-meaningful navigation/contextual-link change. Avoid sitewide boilerplate links, manipulative anchors, hidden links, or arbitrary depth/count thresholds.
- Route crawl/index defects to
seo-technical, page/content ownership toseo-page/seo-content, programmatic templates toseo-programmatic, and authority work toseo-authority. - Package findings as SEO Findings
1.1.0withsite_graph,site,template, orweb_pagetargets andarchitecture,technical,content, orinternationalcategories.
Formal evidence handoff
After graph validation, package only supported observations as SEO Findings 1.1.0. Using the same <suite-root> definition above, run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Keep the handoff provisional until both validators pass.
Output
Return the validated graph, scope and coverage, important node/edge findings, orphan/discovery evidence, taxonomy/facet risks, query/entity mapping, owners, verification, rollback, and limitations. Do not publish a composite authority or architecture score.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

