Site architecture for small businesses: organising pages so Google gets it

A service business has a homepage, 12 service pages, 35 articles, eight suburb pages, three old campaign landing pages, several team profiles and a contact page. Everything technically exists. But the homepage links to only four services. Articles link to no commercial pages. Suburb pages repeat the same content. Some services appear only in the footer. Old pages still compete with new ones. The navigation uses vague labels. Several important pages require five or six steps to reach. Nobody knows which page should rank for the main service.

The issue is not missing content. It is missing architecture. Search engines do not experience a website as a list of URLs. They discover a network of pages connected through links, labels and relationships. Our complete SEO guide covers the broader strategy. This article focuses specifically on how to organise the pages so that strategy actually works.

A page can contain excellent content and still underperform if the rest of the website treats it like an afterthought.

The short answer

Site architecture is the system of relationships between your pages: which pages exist, how they are grouped and how they link to one another. Google reads those relationships through links, not URL folders. Give every important search one owning page, link your articles to the commercial pages they support and keep navigation focused on business priorities. The rest of this guide shows how to do exactly that and how to audit what you already have.

What site architecture actually means

Site architecture is the system determining which pages exist, how they are grouped, how users reach them, how pages link to one another, which pages are prioritised, which search intent each page owns and how the structure expands over time.

Site architecture includes: Page hierarchy, primary navigation, secondary navigation, contextual internal links, breadcrumbs, URL conventions, categories and hubs, location structures, page templates, redirects, archive treatment and XML sitemaps.

What it is not: It is not merely the navigation menu, the XML sitemap, the URL folders, a visual sitemap, breadcrumbs, 'SEO silos'or keeping pages within three clicks.

Google recommends organising a site logically so users and search engines can understand how pages relate. It also notes that search engines can generally understand existing sites even where the URL or folder structure is imperfect, so businesses should not rebuild functioning URLs merely for visual neatness.

How Google discovers and interprets a small business website

Google may discover a URL through an internal link, an external link, an XML sitemap, a previous crawl, a redirector another known source. After discovery, Google crawls the page, renders JavaScript where necessary, evaluates content, headings, links, images, canonical signals and duplication, then decides whether the page is suitable for the index.

Architecture can affect:

• Whether URLs are found

• How often important pages are encountered

• Which pages appear central

• Whether similar pages can be distinguished

• Whether authority flows to strategic pages

• Whether visitors understand their next step

Google describes Search as involving crawling, indexing and serving. A technically accessible page is not guaranteed to be indexed or shown merely because it returns a successful response. For a deeper look at how to check this, see our guide on how to use Google Search Console.

Architecture cannot force Google to rank a page, but poor architecture can make a good page harder to find, interpret and prioritise.

Site architecture is not the same as URL structure

A URL such as example.com/services/plumbing/blocked-drains looks hierarchical. But the actual website may never link from Plumbing to Blocked Drains, link directly from the homepage to the child page, place the page under a different menuor leave it completely orphaned.

Conversely, example.com/blocked-drains can still belong clearly within the plumbing service group through navigation, breadcrumbs, contextual links, page headings and service hub links.

Google states that it generally uses link relationships rather than URL structure alone to understand the importance and hierarchy of pages. Descriptive URLs remain helpful to users, but folders are not the architecture by themselves.

This is why Elev8d's support articles can remain at root level URLs. They do not need to sit under /blogs/technical-seo/ to belong to a technical SEO topic cluster. That relationship is established through the Insights hub, pillar links, topic hub links, article breadcrumbs and contextual cross links.

Do not restructure functioning URLs merely to create pretty folders.

Flat versus deep site architecture

Very flat architecture

Most pages sit close to the homepage. This can mean fewer navigation steps and straightforward discovery, but it can also produce enormous main navigation, weak grouping, unclear service relationships, too many pages competing at the same level and no distinction between primary and secondary content.

Deep architecture

Pages sit beneath several layers. Example: Home, then Services, then Business Services, then Marketing, then Organic Search, then Local SEO, then Google Business Profile. This can mean clear grouping on large sites, but important pages may become buried, users must make too many decisions and deeper pages may be harder to discover.

The three click rule

Do not present 'every page must be reachable within three clicks' as an official Google rule. Google documents link depth and internal link prominence as signals that can help it infer relative importance, but it does not set a universal maximum number of clicks for every website.

One page should own one primary search job

Before creating or reorganising pages, assign an owner to each important search intent.

Common ownership conflicts:

• Homepage and main service page both target the same broad service keyword

• Six suburb pages target the same broad service

• Industry page repeats the generic service page

• Article and service page both target the same cost keyword

• Old and new service pages remain live for the same intent

If the team cannot explain which page should rank for a search, the website probably cannot communicate that distinction clearly either.

The core page types on a service business website

Homepage

Establish the business, communicate its main value, introduce core services, guide different customer types, establish trust and direct visitors to deeper pages. The homepage should not attempt to contain the complete content of every service.

Service hub

Examples: SEO, Web Design, Plumbing, Commercial Law. Explain the broader service category, help users choose a specific service, link to detailed service pages and establish the parent topic.

Detailed service page

Examples: Local SEO, Blocked Drain Repair, Employment Law, Virtual CFO. Answer one focused commercial need. Explain process, fit, proof and next step.

Location page

Represent a genuine office, venueor meaningful service area. Provide location specific information and proof.

Industry page

Explain how a service applies to a specific client type. Show genuine industry experience.

Team profile

Establish the individual professional. Connect expertise, content, services and experience.

Article or guide

Answer informational or comparison questions. Support commercial pages. Develop topical authority.

Case study

Provide evidence. Explain the problem, work and outcome. Support service and industry pages.

Contact or conversion page

Make the next step clear, reduce friction and explain what happens after enquiry. If the website gets traffic but not enquiries, the conversion path may be the problem. See our guide on why website traffic does not convert.

Structuring service pages

Use a parent and child model. The parent page defines the broader service, explains who it is for, compares sub services, links to each detailed page, includes overarching proof and helps customers decide where to continue. Each child page solves a narrower problem, explains its relationship to the parent, links back to the parent, links to related siblings where useful and avoids copying the parent introduction.

When a service deserves its own page

Create a separate page where it has distinct search intent, a distinct customer problem, meaningful delivery information, enough unique evidence and its own commercial pathway.

When it should remain a section

Keep it within another page where it is a minor feature, rarely purchased independently, too similar to another service, impossible to explain without duplicating most contentor unsupported by meaningful demand or business capacity.

A new service page should represent a distinct customer decision, not merely another keyword variation.

Avoid the service page explosion

A small business may begin with five services and expand them into emergency, affordable, same day, local, residential and commercial versions of each, then multiply by every suburb. This can create dozens or hundreds of thin combinations.

Before creating a page, ask:

• Is the search intent distinct from existing pages?

• Does the business deliver something meaningfully different?

• Can the page contain unique proof?

• Will users benefit from landing there directly?

• Can the page be maintained over time?

• Does another page already satisfy the same need?

Better alternatives include sections within a strong service page, comparison tables, FAQs, filters, anchored navigation and contextual internal links rather than automatically generating every possible combination.

Location architecture without suburb page spam

A genuine office page may contain address, phone, hours, team, services available, parking and transport, accessibility, original photography, local reviews, map and office specific contact action. For the broader local search picture, see our guide on Google Maps ranking factors.

Avoid the service times suburb matrix

A plumber creating separate pages for every service in every suburb (Plumber Parramatta, Emergency Plumber Parramatta, Blocked Drains Parramatta, Hot Water Parramatta, repeated across 50 suburbs) produces 250 pages before the business has supplied meaningful local evidence.

Better location models

Model A: Strong service pages plus selected location hubs. Suitable for most mobile service businesses.

Model B: Genuine office pages plus service pages. Suitable for businesses with several staffed locations.

Model C: High value service location combinations used selectively where the intent is distinct, the market justifies it, local proof exists and the content is not templated.

Before building any location page, run the Local SEO Readiness Checker to see whether the local fundamentals justify it. Consistent local citations across Australian directories should reinforce the same business details that appear on the website and location pages.

A location page should document real local relevance. It should not be a placeholder generated because a suburb exists.

Industry and audience pages

Examples: SEO for Tradies, Accountants for Medical Practices, Commercial Cleaning for Schools. Create these pages where the business can demonstrate relevant services, sector specific problems, terminology, processes, compliance considerations, case studies, team expertise and meaningful differences in delivery.

A service page explains: what we provide. An industry page explains: how we provide it for this particular business type. Do not create disconnected industry pages with no path from core services.

Internal link pattern: Industry pages should link to relevant services, appropriate case studies, specialist team members and useful sector content. Service pages may link back through an 'Industries we commonly support' section.

Hub and spoke content architecture

A hub is a central guide or commercial page covering the broader topic. Spokes are focused resources answering related subtopics.

Example: The SEO guide is the hub. Supporting spokes include Google Maps ranking factors, local citations, schema markup, Core Web Vitals, Search Console, site architecture, GEO and ecommerce SEO.

Recommended linking pattern:

• The hub links to each relevant spoke

• Each spoke links back to the hub

• Related spokes link to one another where the reader genuinely benefits

• Commercial service pages connect to the hub and selected spokes

Avoid the fake hub

A page is not a hub merely because it lists article cards. A strong hub should explain the topic, provide its own value, organise the learning journey, distinguish subtopics, direct readers intentionally and remain updated.

A topic cluster is built through useful relationships, not by attaching the same 'related articles' widget to every page.

Siloing: useful concept, dangerous rule

Traditional siloing says services link only to services, articles link only within one category and cross topic links are restricted.

The useful part: Clear topical grouping, obvious parent child relationships, focused hubs and predictable navigation.

The harmful part: Refusing helpful cross links, isolating related information, creating duplicate explanations inside each silo and making users return to the top before changing topics.

Better model: Maintain strong topic groups but allow contextual links where a customer question crosses topics, one service depends on another, evidence supports several pagesor an article helps a related commercial decision. An ecommerce SEO page can link to product schema, Core Web Vitals, website migration and Australian compliance even though those resources sit across different conceptual groups.

Topic structure should create clarity, not walls.

The types of internal links and what each one does

Not all internal links carry the same weight or serve the same purpose.

Primary navigation: Signals the website's most important customer pathways. Appears on every page.

Secondary or utility navigation: May contain login, support, careers, resources, contact and account access.

Breadcrumbs: Show hierarchical context and allow upward navigation.

Contextual links: Appear inside relevant content and explain why another page is useful. Google recommends crawlable internal links with concise, descriptive anchor text and says every page a site owner cares about should receive a link from at least one other discoverable page.

Card or grid links: Useful for presenting services, categories, related resources and locations.

Related content links: Help continued exploration, but should be selected deliberately rather than generated automatically.

Footer links: Useful for important persistent pages, legal documents, contact and key services or locations. They should not become a dump of every target keyword.

Calls to action: Link to enquiry, booking, quote, consultationor the relevant next step.

A contextual link inside a relevant paragraph usually provides clearer meaning than an isolated link labelled 'Learn more'.

Writing useful internal link anchor text

Good anchor text should communicate the destination.

Avoid forcing the exact same keyword rich anchor into every link. Use natural variations based on context. Google recommends anchor text that is descriptive, concise and natural. It warns against forcing excessive keywords or clustering numerous links without meaningful surrounding context. Use our Meta Title and Description Checker to test how your page titles read when they appear as link text in search results.

Navigation is a business priority decision

A primary menu should not attempt to show every URL. It should answer: What does the business offer? Who does it help? Where does it operate? Why should it be trusted? How does someone contact it?

Prefer language customers understand. The appropriate wording depends on the business and audience, but generic labels like 'Solutions' and 'Capabilities' make visitors guess.

Mega menus

A mega menu may help when a business has several major service groups, many product categoriesor multiple audience types. It may cause problems when every article appears inside it, the same link is repeated many times, users face dozens of choicesor mobile implementation becomes difficult. For a business with eight pages, a mega menu is probably unnecessary.

Mobile navigation must remain crawlable and usable

A desktop menu can work perfectly while the mobile version removes important links, loads menu items only after a script event, uses buttons without proper destination URLs, hides nested servicesor becomes difficult to operate. Google generally expects discoverable links to use an HTML anchor element with an href destination. Menus that load slowly or shift the layout around also drag down the metrics covered in our Core Web Vitals guide. See our guide on mobile SEO for small businesses for the broader mobile picture.

Mobile navigation checklist:

• Important links remain present in the mobile menu

• Menu can be opened reliably

• Labels are readable and tap targets are usable

• Nested levels are manageable

• Keyboard and screen reader access is considered

• Every destination has a stable URL

• The rendered HTML can be inspected in Search Console

Page depth and internal importance

Click depth is the number of internal navigation steps needed to reach a page from the homepage. A deep page is not automatically bad. Historical reports, old case studies, specialist support articles and former product manuals may reasonably sit deeper. But main services, high value product categories, locations, contact, major tools and current pillar resources should normally be prominent.

Google says the number of links required to reach a page and the number of internal links pointing to it can help indicate relative importance. The goal is not to give every important page 100 links. It is to ensure users encounter it at sensible decision points and the site consistently treats it as important.

Breadcrumbs: hierarchy for people first

Example: Home, then SEO, then Technical SEO, then Site Architecture. Breadcrumbs help visitors understand where they are, move to a broader section and explore related content. Google says breadcrumbs indicate a page's position within a hierarchy and recommends representing a typical user path. Include visible breadcrumb navigation, crawlable links, appropriate BreadcrumbList structured data and consistent hierarchy across templates. See our guide on schema markup explained for how to implement breadcrumb schema correctly.

Where a page may logically belong to several topics, choose the breadcrumb path most useful to a typical reader rather than attempting to display every possible relationship.

URL structure: clear, stable and boring is good

Recommended URL qualities: readable, short enough to understand, stable, lowercase, consistent, free from unnecessary parameters and descriptive without stuffing.

Good examples: /local-seo, /blocked-drain-repairs, /business-accounting, /private-dining.

Avoid: /page?id=48392, /services/services-2-final, /seo-melbourne-best-agency, dates in evergreen URLs where unnecessary and folders that change every time the navigation changes.

Google recommends logical, human readable URLs. Folders can help with large ecommerce catalogues, multi language sections and major content types, but they are not required for every small business. Only change established URLs where the long term benefit justifies the cost of redirects, recrawling, analytics disruption and broken links.

XML sitemap, HTML sitemap and navigation are different

An XML sitemap is designed primarily for search engines. It should list canonical, indexable, valuable URLs and can support discovery of new or updated pages. An HTML sitemap is a user facing page listing important sections and destinations. Navigation is the everyday pathway users follow through the site.

Critical distinction: An XML sitemap does not replace internal links. Google recommends ensuring pages can be reached through links from other findable pages. It describes sitemaps as an additional discovery mechanism rather than a guarantee of crawling or indexing.

A sitemap can tell Google a URL exists. The website's links explain where that URL belongs and why it matters.

Orphan pages: published but disconnected

An orphan page has no meaningful internal link from the rest of the website. It may still be discovered through an XML sitemap, external link, historic crawl, direct URLor Google Search Console, but users cannot naturally navigate to it.

Common orphan page causes:

• Redesign removed the old menu

• Article hub excludes older posts

• Service was removed from navigation

• Campaign page was never connected to the site

• Location page exists only in the sitemap

• Internal link was deleted during copy updates

For each orphan page, decide: Add relevant links, merge with another page, redirect, archive, noindexor remove. Do not link an orphan page randomly from the footer just to make an audit tool turn green.

An orphan page is often evidence that the business has not decided whether the page still matters.

Duplicate and overlapping pages

Common duplication patterns include two versions of the same service, old and new location pages, HTTP and HTTPS variants, URLs with tracking parameters, category and tag archives, multiple campaign pages, separate pages for tiny keyword variations and slash versus non slash versions.

Google can choose a canonical version where duplicate pages exist, but conflicting signals may produce unexpected selections. Duplicate content is not automatically a spam violation, but it can create poor user experience and waste attention on URLs the business does not care about.

Consolidation options:

• Keep separately: where intent and content are genuinely different

• Merge: where both pages serve the same decision

• Redirect: where one page fully replaces another

• Canonicalise: where duplicate access is operationally necessary

• Noindex: where a page should remain accessible but not appear in search

• Remove: where it has no continuing value

Cannibalisation is not solved by changing one keyword. It is solved by deciding whether the website genuinely needs both pages.

Internal search, filters, tags and archive pages

Small service sites can still generate large numbers of weak URLs through internal search results, tags, date archives, author archives, filters, sorting, calendars, booking parameters and query strings.

Google generally does not type queries into a site's search box to discover pages. Important pages should remain reachable through ordinary links. Tag archives may be useful where they represent a genuine topic with enough high quality resources, but they may be low value where each tag contains one article, several tags mean the same thingor hundreds were generated casually.

Uncontrolled parameters can create effectively endless URL combinations. Google recommends controlling problematic search, filter, sorting and calendar URLs where they create unnecessary crawl spaces.

Pagination and 'load more'

A 'Load more' button may work for a user but fail to provide crawler accessible links to deeper pages. Google says crawlers generally do not click buttons or trigger user action JavaScript. For paginated collections, it recommends stable URLs and sequential crawlable links.

Pagination checklist:

• Every page of results has a URL

• Next pages use crawlable links

• Products or articles remain individually linkable

• Page number URLs are stable

• Empty pages return appropriate responses

• Canonical handling is correct

• Infinite scroll has a crawlable paginated fallback

Page lifecycle: architecture includes what happens later

Every page type should have a lifecycle rule. A page should not enter the website without a plan for what happens when its information stops being current.

Most temporary campaign pages exist to catch paid clicks. Given what Google Ads costs per click in competitive industries, a campaign page deserves a lifecycle decision before launch, not after the budget runs out.

Service business architecture example: Adelaide tradie

Example: Adelaide Plumbing. For the broader tradie SEO landscape, see our SEO for trades industry page.

Recommended structure

Homepage: Core entry point.

Plumbing Services (hub): Links to Emergency Plumbing, Blocked Drains, Hot Water Systems, Gas Plumbing, Leak Detection and Commercial Plumbing.

Service Areas (hub): Links only to meaningful location pages: Prospect, Norwood, Glenelg, Unley.

Resources: Blocked drain warning signs, hot water repair versus replacement, emergency shut off guide, plumbing callout cost guide.

About: Team, licences, vehicles, operating model.

Contact: Emergency call, quote request, service availability.

Internal link model

• Blocked drain articles link to the Blocked Drains service page

• Service pages link to relevant location proof

• Location pages link to services genuinely available

• Case studies link to the relevant service and location

• Homepage links to the highest priority services

• Emergency page links to a direct call action

Avoid creating one page for every service in every suburb, fake suburb offices, homepage carrying every plumbing keyword, blog articles with no pathway to bookingor service areas hidden only inside a dropdown.

Professional services architecture example

Example: Sydney accounting and advisory practice. For the broader professional services SEO picture, see our SEO for professional services industry page.

Primary structure

Accounting Services (hub): Small Business Accounting, Tax Compliance, Bookkeeping, Payroll, Virtual CFO, Business Advisory.

Who We Help: Tradies, Medical Practices, Ecommerce Businesses, Professional Services.

Resources: Tax calendar, accounting cost guide, business structure guides, cash flow resources, compliance updates.

People: Partner profiles, tax agents, accounting specialists.

About: Entity, registrations, process, values.

Contact: Consultation, secure onboarding guidance.

Key relationship model

Service pages explain the work. Industry pages explain the sector application. Team pages connect relevant professionals. Articles support services without duplicating them. Cost guides link to consultation pages. Regulatory updates link back to the affected service. The architecture should visibly connect: Person, then expertise, then article, then service, then organisation.

Do not place all expertise inside articles under a company byline while keeping professional profiles thin.

Hospitality architecture example

Example: Brisbane restaurant with private dining and events. For the broader hospitality SEO picture, see our SEO for hospitality industry page.

Recommended structure

Menu: Lunch, Dinner, Drinks, Dietary Information.

Visit: Location, opening hours, parking, public transport, accessibility.

Bookings: Online reservation or booking integration.

Private Dining and Functions: Group dining, corporate events, celebrations, function menus.

Events: Recurring seasonal events, special menus, local festival participation.

Journal or Guides: Seasonal menu stories, local dining guides, supplier features, event information.

Internal links

Seasonal menu page links to current menu and booking. Local event guide links to pre event dining. Private dining article links to functions page. Chef profile links to menu and supplier content. Dietary information links to relevant menu sections.

Avoid sending users to Instagram for all essential information, menus available only as images, a new URL for every weekly special, expired booking pages remaining liveor event pages disconnected from location and booking information.

Homepage architecture: not everything deserves equal prominence

The homepage should prioritise core proposition, primary services or categories, proof, relevant audience pathways, key resources and enquiry action. Avoid turning it into a complete sitemap, a feed of every article, a long list of suburbs, a keyword catalogueor a wall of identical service cards.

Homepage linking questions:

• Are the most profitable services visible?

• Can users recognise which pathway fits them?

• Are the links descriptive?

• Are important locations or industries represented?

• Does the page link to proof?

• Does every section support a decision?

The homepage should not automatically link every page equally. Its links should reflect business priorities.

Footer architecture

A useful footer may contain core services, priority locations, contact details, About, Insights, privacy, terms, accessibility and social profiles.

Avoid listing hundreds of suburbs, repeating every keyword variation, hiding all important navigation only in the footer, linking to outdated pages, maintaining different business details from the contact pageor stuffing exact match anchors.

Footer test: Would this still be useful if Google did not exist? If not, the footer may have been designed for keywords rather than customers.

Architecture during a redesign or migration

A redesign frequently changes navigation, URL paths, internal links, breadcrumbs, page hierarchy, footer links, article categories and template components. Even where all old copy is copied across, the site's relationships can change substantially.

Before redesign

Create a full URL inventory, page ownership map, current internal link crawl, traffic and backlink data, proposed hierarchy, redirect map, navigation wireframe and orphan page report.

During development

Confirm links use real URLs, mobile navigation matches priorities, breadcrumbs work, staging remains blocked appropriately, canonical tags are correct, redirects are tested, no essential pages were omitted and articles retain relevant commercial links.

Before launch

Crawl staging. Compare old URLs, new URLs, status codes, link depth, inbound internal links, metadata, canonicalisation and index directives. Use the Website Launch Checklist to make sure nothing critical is missed.

After launch

Monitor Page indexing, URL Inspection, Search performance, 404s, redirects, sitemap and important page visibility.

Preserving the words while changing every link around them does not preserve the architecture.

How to audit an existing site architecture

Step 1: Export every known URL

Sources: website crawler, XML sitemap, CMS, Google Search Console, GA4 landing pages, backlink tools and server logs where available.

Step 2: Classify every page

Categories: homepage, service, service hub, location, industry, team, article, case study, tool, report, contact, legal, campaign, archive and system pages.

Step 3: Assign intent and ownership

Record: primary search purpose, intended audience, parent page, child pages, commercial action and content owner.

Step 4: Measure internal support

Record: inbound internal links, outbound internal links, click depth, navigation presence, breadcrumb, orphan status and anchor text patterns.

Step 5: Identify overlap

Look for: identical titles, similar H1s, duplicated service copy, location template patterns, articles targeting commercial terms and historic pages competing with current pages.

Step 6: Identify dead ends

Pages with no useful next step, no links to parent, no commercial pathway, only generic related postsor outdated actions.

Step 7: Decide the architecture action

For each page: retain, strengthen, link, merge, redirect, noindex, removeor rebuild.

Step 8: Draw the intended architecture

Do not begin by moving URLs. First decide what the future site should contain, which page owns each intent, how users should move and which pages deserve prominence.

Architecture audit spreadsheet

Recommended columns for a working architecture audit document.

How to improve architecture without rebuilding the website

Many businesses do not need a full redesign. High impact improvements may include adding a service hub, rewriting navigation labels, linking articles to services, adding breadcrumbs, consolidating duplicate pages, adding links from the homepage, creating an industry hub, fixing mobile navigation, removing dead footer links, strengthening orphan pages, correcting parent child relationships, improving related content selection, updating the XML sitemap and redirecting obsolete pages.

Low risk sequence:

• Document current performance

• Improve contextual links

• Strengthen hubs

• Update navigation carefully

• Consolidate duplicates

• Change URLs only where justified

• Monitor Search Console

Architecture can often be improved by changing relationships before changing addresses.

How to measure whether the new structure is working

Discovery and indexing: Priority pages discovered, important pages indexed, orphan pages reduced, duplicate URLs reduced, sitemap consistency, crawl errors.

Internal structure: Lower depth for priority pages, stronger contextual linking, clear parent child relationships, fewer pages with no inbound links, improved navigation usage.

Search performance: Impressions for priority pages, correct page ranking for intended searches, reduced query page conflicts, growth across topic clusters, stronger non branded clicks. For E-E-A-T signals that support these improvements, see our guide on demonstrating real experience and trust.

Commercial outcomes: Enquiries, qualified leads, bookings, sales, assisted conversions.

Do not judge the architecture only by indexed page count, crawl tool score, number of internal linksor average click depth.

What to send your designer or developer

A useful architecture handoff should contain a page inventory (every page to retain, create, merge, redirector remove), hierarchy (parent pages, child pages, hubs, location structure, content sections), navigation requirements (desktop, mobile, utility menu, footer, breadcrumbs), internal link requirements (examples of which page types should link where), URL map (current URL, new URL, redirect, status), indexation rules (index, noindex, canonical, redirect, remove) and acceptance criteria.

Example acceptance criteria: 'Every priority service must be reachable through a crawlable HTML link from the Services hub and no more than one additional meaningful navigation level beneath the homepage.'

Avoid sending only a visual sitemap without page purpose definitions.

A 90 day site architecture action plan

For a broader technical audit alongside this plan, use our 30 minute SEO audit checklist. Use the Topical Authority Gap Mapper to identify which content topics are missing from your current cluster structure.

Common site architecture mistakes

FAQs

Does website structure affect SEO?

Structure can affect page discovery, contextual understanding, internal prominence and user navigation. Google uses internal links to find pages and understand their relationships.

Should every page be within three clicks of the homepage?

There is no official universal three click requirement. Important pages should be easy to reach, while specialised or historic content may reasonably sit deeper.

Is a flat website structure always better?

No. An excessively flat site can produce overcrowded navigation and weak topical grouping. Use enough hierarchy to make relationships understandable.

Do URL folders improve rankings?

Folders can make URLs easier to organise and understand, but Google primarily analyses links between pages to infer site relationships.

Do articles need to sit inside a /blog/ folder?

No. Articles can exist at root level URLs and still belong to a clear topic through hubs, breadcrumbs and internal links.

What is an orphan page?

An orphan page has no meaningful internal link from other discoverable pages on the website.

Does an XML sitemap fix orphan pages?

A sitemap may help Google discover the URL, but it does not provide the same navigational and contextual relationships as internal links.

What is a hub and spoke content model?

A broad hub page organises a topic and links to focused supporting pages. The supporting pages link back to the hub and to one another where relevant.

Are content silos good for SEO?

Clear topic groups can be useful. Rigid silos that prohibit helpful cross links can make the site less useful and create duplicate explanations.

How many internal links should a page have?

Google does not publish a universal ideal number. Links should be useful, crawlable, contextually relevant and manageable.

Should every service have its own page?

Only where the service represents a distinct customer need and can support genuinely useful, differentiated content.

Should every suburb have a location page?

No. Create location pages where the business has genuine relevance, proof and useful local information.

Are breadcrumbs necessary?

They are not mandatory, but they can help visitors understand and navigate the site hierarchy. Google can also use valid breadcrumb markup in search presentation.

Do small businesses need to worry about crawl budget?

Most do not. Google's current crawl budget guidance is primarily intended for very large or rapidly changing sites. Small businesses should focus on clear internal links, current sitemaps and sensible indexation.

Should old pages be deleted?

Only after reviewing traffic, links, ongoing usefulness and replacement options. Pages may be updated, merged, redirected, archivedor removed depending on their value.

What we recommend at Elev8d

When we work with a business on SEO, the first thing we audit is the page architecture. Not the design, not the content, not the keywords. The relationships between pages. Which pages exist, which ones compete with each other, which ones have no internal support and which search intents have no clear owner. That is the foundation behind our SEO approach for businesses.

For most small businesses, the biggest architecture wins come from three things: assigning one clear owner to each important search intent, linking articles to the commercial pages they should support and removing or consolidating the pages that add clutter without adding value. Those three changes often improve rankings more than publishing ten new blog posts into an unsupported structure. If you are planning a redesign, we can also work alongside your web design and development team to make sure the new build preserves and strengthens the architecture rather than accidentally destroying it.

Next steps: pick your path

Path 1: Run the architecture audit yourself

Follow the eight step audit process in this article. Export your URLs, classify every page, assign intent, measure internal support, identify overlaps, find dead ends and decide the action for each page.

Path 2: Improve without a full rebuild

Many businesses can improve architecture significantly by strengthening contextual links, creating service hubs, fixing orphan pages and consolidating duplicates, without changing URLs or redesigning anything. Start with the low risk sequence above and measure as you go.

Path 3: Get expert help

If your site has dozens of overlapping pages, orphaned content, competing servicesor a migration on the horizon, reach out to the team. We will audit your current architecture, map the page ownership and build a plan that gives every important page a clear purpose, a logical home and the internal support it needs.

Good site architecture gives every important page a clear purpose, a logical home and enough relevant internal support for customers and search engines to understand why it matters.

Sources and further reading

• Google: SEO Starter Guide - Foundational guidance on site organisation and internal linking.

• Google: Link Best Practices - How Google discovers and interprets links.

• Google: URL Structure - Guidance on readable, logical URL design.

• Google: Sitemaps Documentation - How sitemaps support discovery.

• Google: Breadcrumb Structured Data - Breadcrumb markup implementation.

• Google: Crawl Budget Management - Crawl budget guidance for large and complex sites.

General information only. Rules vary by situation, particularly around advertising claims, privacy, reviews and consumer law. If you're unsure about compliance, get professional advice.