Website architecture: a method for SEO, UX and migration

Website architecture is neither the menu nor the sitemap

Website architecture is the model connecting pages, intentions and journeys. The menu is one visible interface for that model. URLs provide stable addresses. The XML sitemap supplies a technical list. Confusing these four layers often produces an attractive menu sitting on poorly organized content.

The starting point is therefore not “how many sections do we want?” but “which decisions must our visitors be able to make?” A service business may need four page families: understand the problem, assess an offer, verify credibility and request a conversation. An ecommerce site will add discovery, comparison, availability, delivery and purchase.

Documented fact. Google’s SEO Starter Guide explains that logical organization can help users and search engines understand the relationships between pages. It promises no ranking and prescribes no universal structure.

1. Start with decisions and pages that create value

First, list the desired outcomes: purchase, appointment, quote request, application, sign-up, qualified download or call. A conversion page should not be isolated at the bottom of a silo. It needs paths from the pages that capture intent and from those that provide proof, methods, cases, prices or answers to objections.

Complete five fields for every proposed page:

• Visitor and situation: who arrives, and what do they already know?
• Main question: what answer do they expect at this point?
• Next decision: what should they be able to do without guessing?
• Required proof: case, method, price, demonstration, expertise or verifiable guarantee.
• Owner: who maintains the page, and according to which signal?

A page with no intent, next step or owner is a candidate for merging, removal or remaining outside the index. A strategic page, by contrast, may justify several entry points when each addresses a distinct intent.

2. Inventory before you draw

For an existing site, export URLs from the CMS, sitemap, crawl, analytics data and Search Console. Add the HTTP status, canonical, inbound links, traffic, measured conversions, owner and editorial decision: retain, improve, merge, redirect or remove.

This step prevents three costly mistakes: forgetting a page that still receives visits, recreating two pages for the same intent, or changing a URL without planning its destination. Data does not make the decision, but it makes the risk visible.

Seven Gold recommendation. Do not classify pages only by internal service line. Add persona, intent, journey stage and commercial value. The organization should reflect the visitor’s logic, not the company’s org chart.

3. Build a hierarchy and internal-link network, not sealed silos

Related pages can be grouped in descriptive directories. But the URL hierarchy is not enough: useful relationships must exist in navigation and content. In its link best practices, Google says every important page should receive a link from at least one other page on the site.

A useful internal link meets three conditions:

• an HTML <a> element with a resolvable href;
• concise, descriptive anchor text that makes sense beyond “click here”;
• context explaining why the destination helps the visitor progress.

There is no magic number of links per page either. A page can contain many justified links and remain clear; ten adjacent links with no hierarchy can have the opposite effect.

4. Before-and-after example: move from departments to decisions

A deliberately hypothetical teaching scenario. A small business initially presents its site as follows: Home → Sales Department → Services → Digital → SEO. The “Sales Department” label describes the organization, and the SEO page receives no links from content that addresses objections.

A working architecture could become:

• Solutions → Increase visibility → SEO;
• Industries → pages that explain market constraints without duplicating the offer;
• Results → documented cases linked to the relevant services;
• Resources → guides that answer a precise question and point to the next step;
• Contact → accessible from journeys where a conversation becomes relevant.

This model is not presented as inherently “better.” Hypothesis to test: visitors identify the right offer faster and understand the proof more clearly. Validation requires user tasks and post-launch data, not an aesthetic preference.

5. Replace the three-click rule with a findability test

The three-click rule is a popular guideline, not a Google or W3C standard. Counting clicks without observing their difficulty can flatten menus, multiply choices and create new problems.

Test tasks instead: “find the right offer for a redesign,” “check whether the agency works in your industry,” “identify a comparable case,” “request a diagnosis.” Record the path chosen, hesitations, backtracking, misunderstood terms and abandonment.

In its guide to menu structure, W3C WAI recommends identifying navigation, ideally with nav, and giving menus short, descriptive labels. This semantic structure helps people find areas; it does not choose the sections for you.

6. Secure the migration before the redesign

A new architecture becomes risky as soon as it changes URLs. Google’s site-migration documentation recommends preparing an old-to-new mapping, testing the site, updating links and annotations, redirecting, and then monitoring the old and new scopes.

1. Freeze the inventory: URL, status, canonical, hreflang, traffic, links, conversion and planned destination.
2. Retain what does not need to change: a stable URL avoids risk without sacrificing a benefit.
3. Map page by page: each old URL should lead to the most relevant destination, not automatically to the home page.
4. Implement 301 or 308 redirects for permanent moves and avoid chains when the final destination is known.
5. Update internal links, canonicals, hreflang, sitemap, campaigns and controlled external profiles.
6. Test before launch: HTTP codes, loops, canonicals, rendering, keyboard navigation, forms and priority journeys.
7. Monitor after launch: errors, indexing, traffic by directory, conversions and queries to old URLs.

Fact: Google recommends server-side permanent redirects for a lasting move. Recommendation: validate the mapping with content, SEO, analytics and business stakeholders. Hypothesis: a new section will improve qualified inquiries; measure it over a period suited to the available volume.

The right deliverable: an operational system

A diagram alone is not enough. The deliverable must connect every node to an intent, page type, URL, inbound and outbound links, next action, owner and migration rule. It then becomes usable by design, content, development, SEO and measurement teams.

Plan governance as well: who may create a section, which criteria justify a new page, when to merge two intents and how often to audit orphan pages. Without these rules, the architecture starts drifting again with the first campaigns. A quarterly review is not a standard; it is an example cadence to adapt to the publishing pace and changes in the offer.

Planning a new site or a redesign? Seven Gold can design the architecture before the visual work, preventing orphan pages and dead-end journeys. Build the site on an SEO- and conversion-led architecture.