Every page on a SaaS site should have one job.
A SaaS website structure is the set of pages on your site, how they link together, and the job each one does for a buyer. At launch, most SaaS sites get by with six to eight core pages: homepage, product, pricing, customers, about, a demo or signup page, and the legal pages. It grows from there as you take on new audiences and products.
We'll go through the job of every page (we call this the Page Job Map), sitemaps for three stages of growth, when it makes sense to split features from solutions, and a template you can drop into your planning doc.

Key takeaways
Plan pages around the job they do for a buyer. Your org chart shouldn’t come into it.
Six to eight pages is enough to launch. Add one when a new audience or product needs its own argument, and not before.
Features pages are about what the product does. Solutions pages are about who it’s for. Don’t build both until you’ve got more than one buyer.
Keep your important pages one or two clicks from the homepage, and link to them from pages people already read.
One search job, one page. Two pages chasing the same query just split the traffic.
What is a SaaS website structure?
It’s the map, or sitemap, of your marketing site. Some people call it SaaS website architecture. It covers which pages exist, how the navigation groups them and how they link to one another. And it decides two things that matter a lot: whether a stranger can find the answer they came for, and whether search engines and AI assistants can work out what you sell.
Structure and design aren’t the same thing. Two sites can look identical and be organised completely differently. Structure asks a blunter question. When a buyer turns up with a question, is there one page that answers it?
There’s an old study we still bring up with clients. Hiten Shah’s SaaS DNA study, published on the Amplitude blog in 2016, had users try 30 SaaS marketing sites and write one sentence on what each company did. The focused sites were easy to describe. The ones with lots of products left people confused, and one tester rated their own confidence highly while describing the company wrongly. Yes, it’s from 2016. The point still stands: structure is part of your messaging.
Which SaaS website pages do you need, and what does each one do?
We use one rule on every site project: each page does one job for one reader. If nobody can say what the job is, the page can wait. Here’s the map we start from, the Page Job Map.
Page | Its job | Who reads it | When you need it |
|---|---|---|---|
Homepage | Say what the product is, who it is for and what to do next | Everyone, first | Launch |
Product (or Platform) | Show how the product works and what it does | Evaluators, users | Launch |
Pricing | Let buyers sort themselves into a plan, or into a sales call | Buyers, finance | Launch |
Demo or signup | Turn interest into a booked call or an account | Ready buyers | Launch |
Customers | Prove that people like the buyer use it and get results | Buyers, sceptics | Launch, even with one story |
About | Show who is behind it and why they can be trusted | Buyers, candidates, investors | Launch |
Legal (privacy, terms) | Meet legal and procurement needs | Procurement | Launch |
Solutions (by role, industry or use case) | Make the argument for one audience | One audience | Growth, when you sell to more than one buyer |
Integrations | Show what it connects to | Technical evaluators | Growth |
Security or trust | Answer security review questions before they are asked | IT, procurement | Growth, often the first enterprise deal |
Compare (vs competitors) | Win the buyer who is choosing between you and another tool | Late-stage buyers | Growth |
Blog and resources | Answer questions buyers search before they look for a vendor | Researchers | Growth |
Docs and changelog | Help users succeed and show the product is moving | Users, developers | When the product needs them |
Careers | Hire | Candidates | When you hire |
Two quick notes. The homepage, pricing and demo pages each get their own deeper guide on our blog: what goes above the fold, AI SaaS pricing page design and demo request page design. This post is about how they fit together. And by “launch” we mean the first version you’d be happy to show a buyer, which isn’t always the first page you push live.
How the structure changes as you grow
Most SaaS sites we see go through three shapes. The page counts are our rule of thumb, not research, so use them as a starting point and nothing more.
1. Launch site (about 6 to 8 pages). One product, one main buyer. The homepage does most of the arguing, and the product page shows how it works.
/
/product
/pricing
/customers
/about
/demo (or /signup)
/privacy
/terms
2. Growth site (about 15 to 30 pages). Still one product, but now two or more buyers or industries. Solutions pages arrive so each audience gets its own argument, along with integrations, security and a blog.
/
/product
/product/feature-a
/product/feature-b
/solutions
/solutions/for-marketing-teams
/solutions/for-healthcare
/integrations
/security
/pricing
/customers
/customers/story-name
/compare/you-vs-competitor
/blog
/about
/careers
/demo
3. Platform site (multi-product). Two or more products, often bought by different teams. Each product gets its own section, and the homepage stops trying to explain any one of them in depth. Its job turns into sending people to the right product.
/
/platform (what ties the products together)
/products
/products/product-one
/products/product-two
/solutions (by role, industry, company size)
/pricing (one page, or one per product)
/customers
/resources (blog, guides, webinars)
/developers (docs, API)
/company (about, careers, press)
/demo
The jump from launch to growth is where most mid-size SaaS sites get messy. Pages get added one request at a time and nobody ever takes anything away. If that sounds familiar, start with the SaaS homepage redesign checklist and the website messaging audit.
Should features and solutions be separate pages?
Only once you’ve got more than one buyer. A features page answers “what does it do?” and a solutions page answers “is it for someone like me?”. Split them too early and you end up with two thin pages saying the same thing.
The test we use:
One buyer, one product: a single product page with clear sections. Skip solutions pages.
Two or more buyers who want different outcomes: one solutions page per buyer. Each opens with that buyer’s problem and links to the features that matter to them.
Lots of features people search for by name: give the important ones their own pages, so each can rank for its own query.
The one to avoid is a solutions page that’s just the homepage with a new headline. It’s only worth having when the proof, the example and the objections are genuinely different for that audience.
How should SaaS navigation be organised?
Group the main navigation around the questions visitors have. Your internal team structure is irrelevant to them. Most B2B SaaS sites land on five to seven items. Here’s how three live sites group theirs, as of November 4, 2026:
Site | Top navigation, in order |
|---|---|
Attio | Platform, Resources, Developers, Customers, Pricing |
Ramp | Products, Solutions, Partners, Resources, Pricing |
PostHog | Products, Pricing, Docs, Community, Company, More |
A few things stand out. Pricing is top level on all three. “Resources” is where the blog and guides live. Developer content gets its own item when developers are the buyers, as at Attio and PostHog. Ramp has Solutions because it sells to several audiences.
What we’d tell most teams:
Five to seven top items. Go past that and nothing stands out.
Pricing in the top navigation. Buyers look for it early. Hide it and it reads like a warning sign.
One main button in the header. “Book a demo” or “Start free”. Not both at the same weight.
Let the footer take the rest. Legal pages, careers, press, the full integrations list.
Keep important pages shallow. One level below the homepage, two at most, with links from the pages people already visit.
What should your URL structure look like?
URLs should mirror the sitemap, so someone can tell where they are just from the address.
Use folders that match the navigation groups:
/product/,/solutions/,/customers/,/blog/.Plain words, lowercase, hyphens:
/solutions/for-healthcare, not/sol?id=7.No dates in URLs. You’ll want to update the page later.
Never change a URL without a redirect. When you restructure, map every old URL to its new home before launch day.
How does site structure help with search and AI answers?
Search engines and AI assistants read structure much like people do. They look for one clear page per topic, and they follow links to understand how pages relate.
Three habits do most of the work:
One search job, one page. If two pages both go after “SaaS pricing page design”, they compete with each other. Pick one owner and point the other at it.
Link pages on the same topic to each other. A blog post about pricing should link to your pricing page and to related posts, with plain anchor text.
Answer the question near the top. A direct answer in the first paragraph is easier for an AI assistant to quote, and easier for a skimming reader to trust.
Where SaaS site structure goes wrong
Building around the org chart. A navigation item per team (“Platform team”, “Data team”) when it should be per buyer question.
Adding pages and never removing any. Old campaign pages, duplicate feature pages, dead integrations. They pile up.
Solutions pages with nothing new. Same copy, new headline, a stock photo.
Hiding pricing. Even “contact us” pricing deserves a page explaining how pricing works.
No customers page. One honest story beats a wall of logos with no context.
Changing URLs without redirects. Losing your ranking pages in a restructure is an expensive way to tidy up.
A sitemap template you can copy
Paste this into your planning doc and delete whatever you don’t need yet. Fill in the job and the reader for each page before anyone writes copy.
Page | Job (one sentence) | Reader | Main action | Status
/ (homepage) | | | |
/product | | | |
/pricing | | | |
/customers | | | |
/about | | | |
/demo | | | |
/solutions/… | | | |
/integrations | | | |
/security | | | |
/blog | | | |
Also read: How to Brief a Design Agency for a SaaS Website, SaaS Website Redesign Cost, Framer vs Webflow for B2B SaaS.
Is your sitemap doing its job?
Send us your sitemap or your live site. We’ll fill in the Page Job Map for you: which pages earn their place, which overlap, and what’s missing. Book a site review · See our work
SaaS website structure FAQs
At launch, six to eight core pages covers most companies: homepage, product, pricing, customers, about, a demo or signup page, and legal. Growth-stage sites tend to sit somewhere between 15 and 30 once solutions, integrations, security, comparison pages and a blog arrive. Our rule: a new page needs a job no other page is already doing.
The minimum is a homepage, product page, pricing page, demo or signup page, customers page, about page and the legal pages. After that it depends. Solutions pages come in when you sell to more than one buyer, a security page when enterprise buyers start asking security questions, and a blog once you're ready to answer what buyers search for.
Anything people might look for that doesn't belong in the main navigation: legal pages, careers, press, the full product and integrations list, contact details, the status page, social links. It's also a second shot at linking to key pages like pricing and the demo page.
Not until you sell to more than one buyer. Features pages say what the product does, and solutions pages say who it's for and why it matters to them. With a single buyer, one product page with clear sections beats two thin ones.
Not on day one. A blog starts paying off once you can publish regularly and answer questions your buyers actually search. Until then, the homepage, product and pricing pages, plus one customer story, are a better use of the time.
Who started the company and why, who's on the team, where you're based, who backs you if that helps with trust, and how to get in touch. People read about pages to decide whether you'll still be around in two years, so be specific and drop the mission-statement filler.
Keep the important pages one or two levels below the homepage. Usually that means five to seven items in the main navigation, one level of dropdowns at most, and the footer for everything else. Clear labels matter more than depth. People will click further if each step tells them they're getting closer.
When a new buyer or product comes along, when visitors can't find pricing or the demo page, or when several of your pages are competing for the same search. Before you launch the new structure, map every old URL to its new home and set up the redirects.
About the author
Jenish is a designer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
What We Learned About SaaS Sites (SaaS DNA study, Hiten Shah), Amplitude blog, April 18, 2016 (amplitude.com/en-us/blog/what-we-learned-about-saas-sites)
Navigation of attio.com, ramp.com and posthog.com, read November 4, 2026
Page Job Map and stage sitemaps: Kraftbase framework and recommendations, not a published standard
Site review
Is your sitemap doing its job?
Send us your sitemap or live site and we will fill in the Page Job Map for you.
Every page on a SaaS site should have one job.
A SaaS website structure is the set of pages on your site, how they link together, and the job each one does for a buyer. At launch, most SaaS sites get by with six to eight core pages: homepage, product, pricing, customers, about, a demo or signup page, and the legal pages. It grows from there as you take on new audiences and products.
We'll go through the job of every page (we call this the Page Job Map), sitemaps for three stages of growth, when it makes sense to split features from solutions, and a template you can drop into your planning doc.

Key takeaways
Plan pages around the job they do for a buyer. Your org chart shouldn’t come into it.
Six to eight pages is enough to launch. Add one when a new audience or product needs its own argument, and not before.
Features pages are about what the product does. Solutions pages are about who it’s for. Don’t build both until you’ve got more than one buyer.
Keep your important pages one or two clicks from the homepage, and link to them from pages people already read.
One search job, one page. Two pages chasing the same query just split the traffic.
What is a SaaS website structure?
It’s the map, or sitemap, of your marketing site. Some people call it SaaS website architecture. It covers which pages exist, how the navigation groups them and how they link to one another. And it decides two things that matter a lot: whether a stranger can find the answer they came for, and whether search engines and AI assistants can work out what you sell.
Structure and design aren’t the same thing. Two sites can look identical and be organised completely differently. Structure asks a blunter question. When a buyer turns up with a question, is there one page that answers it?
There’s an old study we still bring up with clients. Hiten Shah’s SaaS DNA study, published on the Amplitude blog in 2016, had users try 30 SaaS marketing sites and write one sentence on what each company did. The focused sites were easy to describe. The ones with lots of products left people confused, and one tester rated their own confidence highly while describing the company wrongly. Yes, it’s from 2016. The point still stands: structure is part of your messaging.
Which SaaS website pages do you need, and what does each one do?
We use one rule on every site project: each page does one job for one reader. If nobody can say what the job is, the page can wait. Here’s the map we start from, the Page Job Map.
Page | Its job | Who reads it | When you need it |
|---|---|---|---|
Homepage | Say what the product is, who it is for and what to do next | Everyone, first | Launch |
Product (or Platform) | Show how the product works and what it does | Evaluators, users | Launch |
Pricing | Let buyers sort themselves into a plan, or into a sales call | Buyers, finance | Launch |
Demo or signup | Turn interest into a booked call or an account | Ready buyers | Launch |
Customers | Prove that people like the buyer use it and get results | Buyers, sceptics | Launch, even with one story |
About | Show who is behind it and why they can be trusted | Buyers, candidates, investors | Launch |
Legal (privacy, terms) | Meet legal and procurement needs | Procurement | Launch |
Solutions (by role, industry or use case) | Make the argument for one audience | One audience | Growth, when you sell to more than one buyer |
Integrations | Show what it connects to | Technical evaluators | Growth |
Security or trust | Answer security review questions before they are asked | IT, procurement | Growth, often the first enterprise deal |
Compare (vs competitors) | Win the buyer who is choosing between you and another tool | Late-stage buyers | Growth |
Blog and resources | Answer questions buyers search before they look for a vendor | Researchers | Growth |
Docs and changelog | Help users succeed and show the product is moving | Users, developers | When the product needs them |
Careers | Hire | Candidates | When you hire |
Two quick notes. The homepage, pricing and demo pages each get their own deeper guide on our blog: what goes above the fold, AI SaaS pricing page design and demo request page design. This post is about how they fit together. And by “launch” we mean the first version you’d be happy to show a buyer, which isn’t always the first page you push live.
How the structure changes as you grow
Most SaaS sites we see go through three shapes. The page counts are our rule of thumb, not research, so use them as a starting point and nothing more.
1. Launch site (about 6 to 8 pages). One product, one main buyer. The homepage does most of the arguing, and the product page shows how it works.
/
/product
/pricing
/customers
/about
/demo (or /signup)
/privacy
/terms
2. Growth site (about 15 to 30 pages). Still one product, but now two or more buyers or industries. Solutions pages arrive so each audience gets its own argument, along with integrations, security and a blog.
/
/product
/product/feature-a
/product/feature-b
/solutions
/solutions/for-marketing-teams
/solutions/for-healthcare
/integrations
/security
/pricing
/customers
/customers/story-name
/compare/you-vs-competitor
/blog
/about
/careers
/demo
3. Platform site (multi-product). Two or more products, often bought by different teams. Each product gets its own section, and the homepage stops trying to explain any one of them in depth. Its job turns into sending people to the right product.
/
/platform (what ties the products together)
/products
/products/product-one
/products/product-two
/solutions (by role, industry, company size)
/pricing (one page, or one per product)
/customers
/resources (blog, guides, webinars)
/developers (docs, API)
/company (about, careers, press)
/demo
The jump from launch to growth is where most mid-size SaaS sites get messy. Pages get added one request at a time and nobody ever takes anything away. If that sounds familiar, start with the SaaS homepage redesign checklist and the website messaging audit.
Should features and solutions be separate pages?
Only once you’ve got more than one buyer. A features page answers “what does it do?” and a solutions page answers “is it for someone like me?”. Split them too early and you end up with two thin pages saying the same thing.
The test we use:
One buyer, one product: a single product page with clear sections. Skip solutions pages.
Two or more buyers who want different outcomes: one solutions page per buyer. Each opens with that buyer’s problem and links to the features that matter to them.
Lots of features people search for by name: give the important ones their own pages, so each can rank for its own query.
The one to avoid is a solutions page that’s just the homepage with a new headline. It’s only worth having when the proof, the example and the objections are genuinely different for that audience.
How should SaaS navigation be organised?
Group the main navigation around the questions visitors have. Your internal team structure is irrelevant to them. Most B2B SaaS sites land on five to seven items. Here’s how three live sites group theirs, as of November 4, 2026:
Site | Top navigation, in order |
|---|---|
Attio | Platform, Resources, Developers, Customers, Pricing |
Ramp | Products, Solutions, Partners, Resources, Pricing |
PostHog | Products, Pricing, Docs, Community, Company, More |
A few things stand out. Pricing is top level on all three. “Resources” is where the blog and guides live. Developer content gets its own item when developers are the buyers, as at Attio and PostHog. Ramp has Solutions because it sells to several audiences.
What we’d tell most teams:
Five to seven top items. Go past that and nothing stands out.
Pricing in the top navigation. Buyers look for it early. Hide it and it reads like a warning sign.
One main button in the header. “Book a demo” or “Start free”. Not both at the same weight.
Let the footer take the rest. Legal pages, careers, press, the full integrations list.
Keep important pages shallow. One level below the homepage, two at most, with links from the pages people already visit.
What should your URL structure look like?
URLs should mirror the sitemap, so someone can tell where they are just from the address.
Use folders that match the navigation groups:
/product/,/solutions/,/customers/,/blog/.Plain words, lowercase, hyphens:
/solutions/for-healthcare, not/sol?id=7.No dates in URLs. You’ll want to update the page later.
Never change a URL without a redirect. When you restructure, map every old URL to its new home before launch day.
How does site structure help with search and AI answers?
Search engines and AI assistants read structure much like people do. They look for one clear page per topic, and they follow links to understand how pages relate.
Three habits do most of the work:
One search job, one page. If two pages both go after “SaaS pricing page design”, they compete with each other. Pick one owner and point the other at it.
Link pages on the same topic to each other. A blog post about pricing should link to your pricing page and to related posts, with plain anchor text.
Answer the question near the top. A direct answer in the first paragraph is easier for an AI assistant to quote, and easier for a skimming reader to trust.
Where SaaS site structure goes wrong
Building around the org chart. A navigation item per team (“Platform team”, “Data team”) when it should be per buyer question.
Adding pages and never removing any. Old campaign pages, duplicate feature pages, dead integrations. They pile up.
Solutions pages with nothing new. Same copy, new headline, a stock photo.
Hiding pricing. Even “contact us” pricing deserves a page explaining how pricing works.
No customers page. One honest story beats a wall of logos with no context.
Changing URLs without redirects. Losing your ranking pages in a restructure is an expensive way to tidy up.
A sitemap template you can copy
Paste this into your planning doc and delete whatever you don’t need yet. Fill in the job and the reader for each page before anyone writes copy.
Page | Job (one sentence) | Reader | Main action | Status
/ (homepage) | | | |
/product | | | |
/pricing | | | |
/customers | | | |
/about | | | |
/demo | | | |
/solutions/… | | | |
/integrations | | | |
/security | | | |
/blog | | | |
Also read: How to Brief a Design Agency for a SaaS Website, SaaS Website Redesign Cost, Framer vs Webflow for B2B SaaS.
Is your sitemap doing its job?
Send us your sitemap or your live site. We’ll fill in the Page Job Map for you: which pages earn their place, which overlap, and what’s missing. Book a site review · See our work
SaaS website structure FAQs
At launch, six to eight core pages covers most companies: homepage, product, pricing, customers, about, a demo or signup page, and legal. Growth-stage sites tend to sit somewhere between 15 and 30 once solutions, integrations, security, comparison pages and a blog arrive. Our rule: a new page needs a job no other page is already doing.
The minimum is a homepage, product page, pricing page, demo or signup page, customers page, about page and the legal pages. After that it depends. Solutions pages come in when you sell to more than one buyer, a security page when enterprise buyers start asking security questions, and a blog once you're ready to answer what buyers search for.
Anything people might look for that doesn't belong in the main navigation: legal pages, careers, press, the full product and integrations list, contact details, the status page, social links. It's also a second shot at linking to key pages like pricing and the demo page.
Not until you sell to more than one buyer. Features pages say what the product does, and solutions pages say who it's for and why it matters to them. With a single buyer, one product page with clear sections beats two thin ones.
Not on day one. A blog starts paying off once you can publish regularly and answer questions your buyers actually search. Until then, the homepage, product and pricing pages, plus one customer story, are a better use of the time.
Who started the company and why, who's on the team, where you're based, who backs you if that helps with trust, and how to get in touch. People read about pages to decide whether you'll still be around in two years, so be specific and drop the mission-statement filler.
Keep the important pages one or two levels below the homepage. Usually that means five to seven items in the main navigation, one level of dropdowns at most, and the footer for everything else. Clear labels matter more than depth. People will click further if each step tells them they're getting closer.
When a new buyer or product comes along, when visitors can't find pricing or the demo page, or when several of your pages are competing for the same search. Before you launch the new structure, map every old URL to its new home and set up the redirects.
About the author
Jenish is a designer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.
Sources
What We Learned About SaaS Sites (SaaS DNA study, Hiten Shah), Amplitude blog, April 18, 2016 (amplitude.com/en-us/blog/what-we-learned-about-saas-sites)
Navigation of attio.com, ramp.com and posthog.com, read November 4, 2026
Page Job Map and stage sitemaps: Kraftbase framework and recommendations, not a published standard
Site review
Is your sitemap doing its job?
Send us your sitemap or live site and we will fill in the Page Job Map for you.
