Fluxx Tech
A small website does not need architecture. Forty pages, a clear menu, done. Past a few hundred pages, structure becomes the thing that decides which of your pages rank and which Google never bothers with.
Good architecture does three jobs: helps users find things, helps Google crawl efficiently, and concentrates link value on the pages that matter commercially.
Click depth
Click depth is how many clicks from the homepage a page sits. It correlates strongly with how often Google crawls a page and how well it ranks.
Target: every important page within three clicks of the homepage. Four is acceptable for deep catalogue items. Six means Google will rarely visit.
A flat structure is usually better than a deep one, but not infinitely: a homepage linking directly to 400 pages dilutes every link. The practical shape is a shallow tree with strong hub pages.
The hub-and-spoke shape
Homepage
├── Service category hub (e.g. /services/web-development/)
│ ├── Specific service page
│ ├── Specific service page
│ └── Related blog posts linking back to the hub
├── Industry hub (e.g. /industries/healthcare/)
│ └── Industry-specific pages
├── Location hub (e.g. /locations/)
│ └── City pages
└── Blog
└── Topic hubs → individual posts
Each hub is a substantial page in its own right, linking down to its children and up to the homepage. Children link back to the hub and sideways to siblings where relevant.
This is the same idea as topic clusters, applied to the whole site rather than just the blog.
URL hierarchy
Make URLs mirror the structure:
Good: /services/web-development/ecommerce/
Good: /industries/healthcare/
Poor: /page?id=4471
Poor: /services/web-development-ecommerce-coimbatore-best-company/
Rules:
• Lowercase, hyphens, no underscores or spaces
• Short and readable
• One or two levels of folder for most sites, three at most
• No dates in URLs for evergreen content
• Do not stuff keywords; /sarees/cotton/ beats /best-cotton-sarees-online-shopping-india/
• Do not change URLs without a reason, and always 301 if you do
Navigation
Main menu: your most important eight to ten destinations. If everything is in the menu, nothing is prioritised.
Mega menus work for large catalogues, but keep the links as real <a href> elements, not JavaScript-only.
Footer: secondary pages, policies, main categories. Do not dump 200 links there; it dilutes and looks like spam.
Breadcrumbs: essential on large sites. They reinforce hierarchy for users and search engines, and they can show in search results with breadcrumb schema.
Internal search: useful for users; block its result URLs from crawling.
Internal linking
This is where most large sites underperform. Beyond navigation:
• Link from high-authority pages (homepage, popular blog posts) to pages you want to rank
• Link related products and services to each other
• Link blog posts to the service page they support, and the service page to the two or three best posts
• Use descriptive anchor text: “ecommerce website development”, not “click here”
• Vary anchor text naturally
• Audit for pages with no internal links at all
Orphan pages — pages with no internal links pointing to them — are invisible in practice even if they are in your sitemap. Crawl your own site periodically and list them.
Deciding the structure
Base it on how customers think, not on your internal departments:
Business | Primary structure |
Services company | By service, then by industry |
Ecommerce | By product category, then subcategory |
Multi-location business | By service, with location pages as a separate branch |
Manufacturer | By product range, then application |
Marketplace | By category, then by attribute |
Avoid building the main structure around locations if you offer many services in many cities; you end up with a page for every service-city combination, most of them thin. See the location-pages approach instead.
Signs your architecture is failing
• Pages five or more clicks deep
• Important pages with few internal links
• Several pages targeting the same keyword
• New pages taking weeks to be indexed
• Users relying on site search because the menu does not help
• Breadcrumbs that do not match the URL structure
• A sitemap with far more URLs than your indexed count
Restructuring without losing rankings
If you need to change structure:
1. Crawl the existing site and export every URL
2. Record current traffic and rankings per URL
3. Map every old URL to its new destination; no URL left unmapped
4. Implement 301 redirects, one hop only, no chains
5. Update internal links to point at new URLs directly
6. Update the sitemap and resubmit
7. Keep the old sitemap available briefly so Google re-crawls the old URLs and sees the redirects
8. Monitor Search Console for 404s and crawl errors weekly for a month
9. Expect a short dip; if rankings have not recovered in six to eight weeks, investigate
See our website migration checklist for the full process.
Frequently asked questions
How many pages should a hub link to? Enough to be useful, not so many that each link is meaningless. Twenty to fifty is workable; beyond that, add another level.
Does URL folder depth matter, or only click depth? Click depth matters more. A page at /a/b/c/d/ linked from the homepage is fine; a page at /page/ that takes six clicks is not.
Should I restructure an existing site? Only for a real problem. Restructuring carries risk; do it when the current structure is demonstrably limiting you.
