Two clicks from the homepage?
The skill opens with one test. Could a first time visitor, landing on your homepage with no context, reach your most important page in two clicks? If not, the structure has a depth problem. It treats important pages that sit four or five clicks deep as something to fix, either by moving them up or by linking to them from higher pages.
A sitemap before any design work
This sitemap is a planning document, not the XML file for search engines. The skill builds it in four steps. It crawls the current site and exports every address with its status, title, and count of internal links. It maps the three to five journeys that matter most, such as Homepage to Product to Pricing to Free Trial.
Then it gives every topic exactly one primary page, and it sorts all pages into tiers. The result comes back as a diagram rather than a spreadsheet, because relationships are easier to discuss when you can see them.
Tiers and menus
The homepage is tier one. Section pages form tier two, and the skill caps them at eight to ten. Pillar and product pages sit in tier three, and posts or detail pages sit in tier four. Anything deeper should be rare.
The main menu holds five or six items plus one clear call to action. Dropdowns appear only when a section has three or more subsections, and a dropdown inside a dropdown sends the skill back to the structure. The footer surfaces pages such as contact, careers, and your policies instead of copying the header.
URL rules for the long term
Addresses are hard to change later, so the skill decides them early. It keeps them short and lowercase, separates words with hyphens, and drops dates from evergreen guides. It mirrors the hierarchy, as in /solutions/manufacturing/, removes filler words such as “the” and “for”, and keeps the blog in a subdirectory rather than on a subdomain.
Breadcrumbs and internal links
Breadcrumbs go on posts, product pages, location pages, and anything more than two levels deep, but not on the homepage or on flat pages such as Pricing. Each trail gets BreadcrumbList markup, and every crumb must lead to a live page.
Internal links follow a hub and spoke pattern. A pillar page links to each subtopic page, and each subtopic page links back. The skill also links from the pages with the most outside links, uses anchor text that names the destination, and hunts for orphaned pages that nothing links to.
The architecture method on GitHub
Tiers, menu rules, URL principles, and the pillar and cluster model are all in the site-architecture skill file. It is released under the MIT License, “Copyright (c) 2026 ScayverGraphix.” The skills follow the Agent Skills spec published by vercel-labs/skills.
Rebuild, or reorganize?
The skill rebuilds only for deep problems. Important content sits more than four levels down, the URLs would need sitewide redirects anyway, the menu has grown past 10 top level items, or analytics show people cannot find key pages. Otherwise it reorganizes one section and leaves the rest alone.
Either way, it writes down the intended structure, the URL mapping, the redirect plan, and the link updates before a single page moves. Ask your agent to plan a sitemap or fix your page hierarchy, and it applies this skill. Add the breadcrumb markup partner with npx skills add scayver/marketing-skills --skill site-architecture schema.
Test the labels with real people.
Menus fail when they use internal names. If customers say “analytics” and your menu says “Insights Hub,” they will not find it. The skill tells you to take labels from support logs and site search, then run a tree test, where people find items in a text only version of the menu, before launch.
Structure built around customer tasks
Our Information Architecture service maps your content and the tasks customers come to complete before it defines the hierarchy. That keeps a new menu from repeating the problem an old one had.