SEO Architecture: Build a Site Around Buyer Questions

SEO architecture is how you organize and connect website pages so buyers can find useful answers and search engines can discover and understand them. It includes page hierarchy, navigation, internal links, URL conventions and decisions about which version of a page should appear in search.

For a B2B company, the practical goal is to connect a buyer’s question to a relevant service, evidence of fit and a next step. A growing blog without those connections is a publishing schedule, not a complete architecture.

You can often improve that structure within an existing website. Start with page roles and links—not a redesign or wholesale URL changes.

1. Map buyer needs to page roles

Before drawing a site hierarchy, list what buyers need to understand before they enquire. Use sales questions, customer interviews and search-query data to identify those needs. Then assign each distinct need to a page.

Here is an illustrative structure for a company selling managed IT services:

Buyer question	Page role	Useful next step
“Can you manage our IT?”	Core managed IT service page	Review scope and request a consultation
“Do you support businesses like ours?”	Industry page, where the offering genuinely differs	Read a relevant case study
“What will switching providers involve?”	Transition guide	Explore the onboarding process
“What does managed IT cost?”	Pricing explainer	Review packages or request a scoped quote
“Have you solved this problem before?”	Case study	Visit the relevant service page

This is a planning example, not a requirement to build five page types. A small business may answer several questions well on one service page.

Create a separate page when it has a distinct purpose and enough useful information to justify the visit. Don’t create new pages merely because two keyword phrases differ. Conversely, don’t force an educational guide and a service offer into one page if buyers need substantially different answers.

If existing pages overlap, decide whether to clarify their roles or consolidate pages serving the same intent.

2. Design the link structure before the folders

Give important services a clear route from the main navigation. Where a service has several genuinely distinct offerings, use a parent page that explains the options and links to each one. Use breadcrumbs when they help visitors understand where they are.

The critical distinction is that URL folders are not the same as site architecture. Google’s ecommerce guidance explains that it generally uses relationships between linked pages, rather than URL structure, to understand a site’s organization and relative page importance. Although the examples concern shops, the distinction is useful when planning a service website too. Google’s site-structure guidance

A tidy /services/managed-it/ path cannot compensate for a service page that no useful page links to. Equally, a page at /managed-it/ can sit within a clear service hierarchy through navigation and contextual links.

Use descriptive, stable URLs for new pages. Google recommends readable words, hyphens between words and avoiding unnecessary parameters. Don’t rename working URLs solely to make the folder diagram look cleaner. Google’s URL guidance

3. Connect answers to services and proof

Build links around the reader’s next question:

• A transition guide links to the onboarding process and relevant service.
• A service page links to supporting case studies and detailed scope information.
• A case study links back to the service demonstrated.
• A topic hub links to its useful guides, rather than merely listing recent posts.

Cross-link between topic groups when the connection helps the buyer. Strict silos that prohibit useful links are not the goal.

Use descriptive link text, such as “managed IT onboarding process,” rather than repeated “click here” labels. Ensure navigation uses standard, crawlable anchor links with valid destinations. Google recommends that every page you care about have a link from at least one other page on your site. Google’s link best practices

Also give each page an appropriate conversion path. An early-stage explainer might offer a related guide before a consultation; a service page can make an enquiry more prominent. This is a buyer-journey choice, not a ranking trick.

4. Audit the existing site before adding pages

Run a crawl starting from the homepage and following internal links, without adding URLs from a sitemap or page list. Compare the discovered pages with your CMS page inventory and XML sitemap. Investigate valuable pages present in the inventory but absent from the crawl: they may lack internal links, or the crawler may be unable to follow the navigation. Check the crawler’s settings before treating an omission as a site problem.

Record each important page’s purpose, incoming internal links, status code, indexing directives and canonical destination. Prioritize:

1. Important pages that cannot be reached or accessed.
2. Broken links and accidental indexing exclusions.
3. Conflicting duplicate-page signals.
4. Missing connections between useful content and commercial pages.
5. New pages for unmet buyer questions.

For search eligibility, Google’s minimum technical requirements include accessible crawling, an HTTP 200 response and indexable content. Use Search Console’s URL Inspection tool to investigate individual pages. Google’s technical requirements

For duplicate or very similar pages that must remain available, use a rel="canonical" annotation to indicate the preferred version, include that version in your sitemap and link internally to it. These signals express a preference; Google may choose a different canonical. Canonicalization is not a substitute for deciding what different pages should do. Google’s canonical guidance

An XML sitemap supports discovery; it does not replace navigation. Google says properly linked sites can usually have most pages discovered through links. Google’s sitemap guidance

5. Ship changes with a business baseline

Before implementation, record search clicks, impressions, organic enquiries and lead quality for affected pages. Annotate the release date, then compare equivalent periods, accounting for seasonality and other campaigns. Assess whether buyers reach relevant services and whether those visits produce qualified conversations—not just whether total traffic rises. A before-and-after change alone does not establish what caused the result.

If URL changes are necessary, map old URLs to relevant replacements, implement server-side permanent redirects where possible, and update internal links, canonicals and sitemaps. Google warns that significant site changes can cause temporary ranking fluctuations while pages are recrawled and reindexed. Google’s migration guidance

Keep the architecture map as a working publishing rule: every proposed page should have a buyer question, a distinct role, an incoming-link plan and a next step. Use a post-launch measurement loop to decide what needs improving after publication.