site-architecture
by alirezarezvanisite-architecture helps AI agents audit and plan website structure, URL hierarchy, navigation, crawl paths, breadcrumbs, and internal linking for Technical SEO. It includes URL design and internal linking guides plus a sitemap analyzer script for evidence-based architecture recommendations.
This skill scores 84/100, making it a solid listing candidate for directory users who want an agent to audit or redesign website information architecture and internal linking. The repository evidence shows enough trigger clarity, workflow depth, reference material, and a usable analysis script to provide materially more leverage than a generic SEO prompt, though packaging could be clearer for installation and onboarding.
- Clear trigger surface in frontmatter covers site architecture, URL structure, navigation, breadcrumbs, topic clusters, orphan pages, and structural SEO issues, with exclusions for content strategy and schema markup.
- Operational substance is supported by a long SKILL.md, context-gathering prompts, 11 H2 sections, 20 H3 sections, and practical references for internal linking and URL design.
- Includes a stdlib Python sitemap analyzer that can inspect sitemap.xml files for depth, URL patterns, duplicate paths, orphan candidates, and JSON summary output.
- No install command or README is present in the skill folder, so directory users may need to infer installation from the parent repository conventions.
- The available evidence shows strong SEO architecture guidance, but the workflow excerpts are partially truncated, so review confidence about full end-to-end execution details is not absolute.
Overview of site-architecture skill
What site-architecture is built to do
The site-architecture skill helps an AI assistant audit, redesign, or plan a website’s structure for technical SEO, crawlability, navigation, URL hygiene, and internal linking. It is most useful when the problem is structural: messy URL folders, weak hub pages, orphan pages, unclear navigation, poor crawl paths, or a site migration that needs an SEO-safe information architecture.
Best-fit users and projects
This site-architecture skill fits SEO consultants, technical SEO teams, content leads, founders, and developers who need practical architecture recommendations rather than broad marketing advice. It is especially relevant for SaaS, B2B, content sites, documentation sites, e-commerce category structures, local service sites, and sites reorganizing around topic clusters or hub-and-spoke models.
What makes it stronger than a generic prompt
A generic prompt can say “improve internal linking,” but this skill gives the assistant a defined workflow: collect current state, goals, and constraints; evaluate URL patterns; map navigation depth; and recommend internal linking models. The repository also includes references/internal-linking-playbook.md, references/url-design-guide.md, and scripts/sitemap_analyzer.py, so the skill is more operational than a short SEO checklist.
When this skill is not the right fit
Do not use site-architecture as the main tool for deciding what new articles to publish, writing page copy, implementing schema markup, or doing keyword research from scratch. It can support those workflows by clarifying where pages should live and how they should connect, but its core value is architecture, not content ideation or structured data.
How to Use site-architecture skill
site-architecture install and repository path
Install from the GitHub skill repository with:
npx skills add alirezarezvani/claude-skills --skill site-architecture
The source lives at marketing-skill/skills/site-architecture in alirezarezvani/claude-skills. After install, read SKILL.md first, then inspect:
references/internal-linking-playbook.mdreferences/url-design-guide.mdscripts/sitemap_analyzer.py
There is no separate README or metadata file in this skill folder, so the main operating instructions are in SKILL.md and the two reference guides.
Inputs that improve site-architecture usage
For strong site-architecture usage, give the assistant more than “fix my SEO structure.” The skill works best with:
- Website URL and CMS or framework
sitemap.xmlURL or exported sitemap- Approximate number of pages by section
- Main business model: lead gen, SaaS, e-commerce, media, local, documentation
- Known issues: orphan pages, duplicate pages, thin category pages, crawl bloat, poor rankings
- Priority pages you want to rank or protect
- Constraints: no URL changes, migration deadline, CMS limits, engineering capacity
A stronger prompt looks like:
Use the
site-architectureskill to audit our B2B SaaS site. Sitemap:https://example.com/sitemap.xml. We have feature pages, solution pages, integrations, docs, and 250 blog posts. Our priority is ranking solution pages without changing existing high-performing blog URLs. Identify structural issues, recommend URL folder rules, navigation changes, hub pages, and internal links. Flag anything that needs redirects or developer work.
Suggested workflow for an architecture audit
Start with evidence. If you have a sitemap, run or ask the assistant to use scripts/sitemap_analyzer.py to inspect URL depth, section distribution, duplicate path patterns, and possible orphan candidates. Then compare the results against url-design-guide.md to find inconsistent slugs, over-deep folders, date-based blog paths, mixed trailing slash conventions, or unclear section naming.
Next, use internal-linking-playbook.md to choose a linking pattern. Hub-and-spoke is usually better for topic authority; linear linking fits courses and documentation; category-to-product models fit e-commerce. Ask for a prioritized fix list instead of a full redesign if resources are limited.
Practical prompt pattern
A complete site-architecture guide prompt should include the desired output format. For example:
Produce: 1) current architecture diagnosis, 2) URL rule recommendations, 3) proposed navigation model, 4) internal linking plan by page type, 5) redirect/migration risks, 6) 30-day implementation plan, 7) open questions.
This reduces vague advice and pushes the assistant toward decisions you can hand to SEO, content, and engineering teams.
site-architecture skill FAQ
Is site-architecture for Technical Seo work?
Yes. site-architecture for Technical Seo is a strong fit when the task involves crawl paths, indexable URL patterns, site depth, internal linking, breadcrumbs, duplicate structural patterns, or migration-safe URL decisions. It is less suited to log-file analysis, Core Web Vitals debugging, or schema implementation unless those issues are connected to architecture.
Can beginners use this skill?
Yes, but beginners should provide concrete site details and ask for explanations. The skill includes practical references, so you can request “explain each recommendation and why it matters for crawlability or rankings.” For a first pass, ask for a diagnosis before asking for a full redesign.
How does it compare with a normal SEO prompt?
A normal SEO prompt often produces broad recommendations such as “add internal links” or “make URLs shorter.” This skill is more structured: it separates current state, goals, constraints, URL design, navigation, and linking architecture. The included sitemap analyzer also gives it a better path from raw sitemap data to actionable findings.
When should I avoid installing it?
Avoid installing site-architecture if you only need blog topic ideas, metadata rewrites, product descriptions, or schema snippets. Also avoid using it as the sole source of truth for a high-risk migration; use it to generate the architecture plan, then validate redirects, canonicals, analytics, and crawl data with your SEO tools.
How to Improve site-architecture skill
Give the skill real site evidence
The best way to improve site-architecture output is to provide a sitemap, current navigation, key page types, and ranking priorities. If you cannot share the domain, give anonymized URL examples by section. Real examples help the assistant detect whether the issue is depth, naming, duplication, weak hubs, or missing links.
Ask for decisions, not only observations
A weak request asks, “What do you think of our structure?” A better request asks:
Recommend the preferred URL structure for features, integrations, solutions, blog, and docs. Keep existing ranking blog URLs unchanged unless there is a clear SEO reason to migrate. Mark each recommendation as keep, change, merge, redirect, or investigate.
This forces the skill to produce implementation-ready architecture guidance.
Watch for common failure modes
Common failure modes include recommending URL changes without migration risk, creating too many hub pages, flattening every URL regardless of meaning, or suggesting internal links that are not contextually useful. Ask the assistant to separate “safe quick wins” from “migration-level changes” and to explain the SEO tradeoff for each structural recommendation.
Iterate after the first output
Use the first answer as a draft architecture map, not the final plan. Follow up with crawl data, Search Console exports, analytics priorities, CMS restrictions, or developer feedback. Then ask the site-architecture skill to revise the plan into a phased roadmap: immediate internal links, navigation cleanup, URL governance rules, and longer-term restructuring.