Start Here: What Does a Page Type Actually Mean?
Many websites do not have a content problem. They have a page architecture problem.
They create:
- several URLs for the same search task
- articles for queries that need commercial pages
- location pages that differ only by city name
- service pages that compete with capability pages
- industry pages with no industry-specific information
- glossary pages too thin to justify individual URLs
- comparison pages that provide no useful comparison
- hundreds of programmatic pages before proving that the underlying pattern deserves separate URLs
The result is more inventory without more coverage.
This library explains the major SEO page types, what each page is supposed to do, when it deserves its own URL, what information belongs on it, how it should connect to other pages, and when you should not create it at all.
The goal is not to build every page type listed here.
The goal is to give every important URL on your website a clear reason to exist.
A page type is the role a page performs within a website.
It describes the job of the page, not merely its keyword, template, CMS location, or design.
Consider a roofing company.
A roof replacement service page explains what the company provides.
A roof replacement cost guide helps buyers understand expected investment.
A metal roofing page explains a specific roofing system or capability.
A Spokane service-area page explains how the company serves that market.
A metal roof vs asphalt shingles comparison helps someone choose between alternatives.
A Spokane roof replacement project proves that the company has completed relevant work.
A roof replacement calculator helps someone estimate a project.
All of these pages relate to roofing.
They still perform different jobs.
That is the foundation of good website architecture.
The opposite matters too.
Two different keywords do not automatically require two different URLs.
"Commercial cleaning company," "commercial cleaning contractor," and "janitorial services provider" might describe the same commercial task.
"How much does commercial cleaning cost?" and "commercial cleaning pricing" might require the same answer on one site and different answers on another.
The decision depends on the task, entity, information required, buyer stage, and role the page needs to perform.
Page Type, Search Intent, and Search Query Are Not the Same Thing
These concepts overlap, but they answer different questions.
The query tells you what someone typed or expressed.
Search intent describes what the person appears to want.
The search task describes what they are trying to accomplish.
The page type describes the kind of document best suited to completing that task.
A query such as "commercial cleaning cost" may have commercial investigation intent.
The task is to understand expected investment.
The appropriate page might therefore be a cost guide rather than a standard cleaning service page.
A query such as "commercial cleaning Seattle" may express transactional and local intent.
The task is to find a company that serves Seattle.
That could require a service-area page, a physical location page, or a service + location page depending on the business.
Matching keywords without matching page roles creates weak architecture.
The Main Families of SEO Pages
| Page family |
Primary job |
Common page types |
| Core and structural |
Establish the business and organize important entities |
Homepage, hub, category, resource center, About |
| Commercial |
Represent what the company sells, provides, or enables |
Service, capability, product, feature, solution, industry, use case |
| Geographic |
Represent physical locations or legitimate markets |
Location, service-area, service + location, regional market |
| Proof and expertise |
Show why the company or person should be trusted |
Case study, project, profile, credentials, reviews |
| Decision support |
Help buyers evaluate, compare, budget, and choose |
Pricing, cost, comparison, alternatives, process, buyer guide, FAQ |
| Informational and reference |
Answer questions and explain concepts |
Guide, glossary, statistics, documentation, report, template |
| Interactive |
Help the user calculate, diagnose, plan, search, or configure |
Calculator, assessment, planner, estimator, database |
| Conversion |
Complete the next business action |
Contact, booking, consultation, estimate, RFP, demo |
These families should work together.
They should not become isolated silos.
A service page might connect to its supporting capabilities, industries, locations, case studies, cost guide, and consultation page.
A guide might connect the reader toward a service when the commercial relationship is useful.
A case study should support the services and industries that the evidence actually validates.
Architecture becomes useful when the relationships between pages mean something.
How to Know Whether a Topic Deserves Its Own Page
Before creating another URL, ask a harder question than "Does this keyword have search volume?"
Ask:
Does this topic require a page that another existing page cannot serve as well?
Use the following tests.
| Test |
Question |
| Distinct task |
Is the visitor trying to accomplish something meaningfully different? |
| Distinct entity |
Does the URL represent a separate service, product, location, person, industry, technology, problem, or other meaningful entity? |
| Distinct information |
Does the topic require substantial information that would not simply repeat another page? |
| Distinct evaluation criteria |
Does the visitor need different proof, pricing factors, specifications, comparisons, or decision criteria? |
| Business reality |
Does the company genuinely provide, support, serve, or have expertise in the subject? |
| Search pattern |
Do people consistently search for this subject as its own task rather than merely using a wording variation? |
| Architectural role |
Does the page have a logical parent and meaningful connections with the rest of the site? |
| Next action |
Is there a sensible next step after the visitor completes the page's task? |
| Maintainability |
Can the company keep the information accurate and useful over time? |
| Differentiation |
Could you explain why this URL should exist without mentioning keyword volume? |
You do not need every answer to be yes.
You should have enough strong answers to justify adding another indexable document to the site.
If the entire business case is:
> "This keyword has 90 searches per month."
That is usually not enough.
Query Deserves a Page
A useful semantic SEO principle is Query Deserves a Page.
The basic idea is simple:
Create another page when the query represents a sufficiently different entity, task, information requirement, or semantic pattern that the current page cannot satisfy it well.
Do not create another page simply because the wording changes.
Consider:
- commercial cleaning company
- commercial cleaning service
- commercial cleaning contractor
- janitorial services provider
These can describe the same commercial entity and task.
Now compare:
- commercial cleaning company
- commercial cleaning pricing
- medical facility cleaning company
- commercial cleaning case studies
- commercial cleaning company vs in-house janitorial team
These queries share a commercial cleaning context, but the predicates and tasks change.
One asks who provides the service.
One asks about cost.
One adds an industry or audience constraint.
One asks for evidence.
One asks for a comparison.
Those differences can justify different pages.
The goal is not one URL per keyword.
The goal is one strong URL per meaningful task and entity relationship.
Core and Structural Page Types
Homepage
The homepage represents the business or website as a whole.
Its job is to establish what the company is, who it serves, what it provides, why someone should trust it, and where visitors should go next.
For most businesses, the homepage sits above the major page families rather than replacing them.
- Primary job
- Establish the company and distribute users toward the site's most important areas.
- Build it when
- Every business website needs one canonical homepage.
- Include
- Positioning, main audiences, core offerings, proof, differentiation, important navigation paths, and a clear next action.
- Avoid
- Trying to make the homepage rank for every service, city, industry, capability, and question the business targets.
- Usually connects to
- Service hubs, major commercial pages, industries, locations, resources, proof, About, and conversion pages.
The homepage should explain the business clearly enough that visitors know where they are and what path to take next.
It should not become a compressed version of the entire website.
Hub or Collection Page
A hub organizes a meaningful family of pages.
Common examples include:
- Services
- Industries
- Locations
- Capabilities
- Products
- Case Studies
- Resources
A hub owns the broader category while its children handle narrower entities or tasks.
A good hub does more than display a grid of links.
It explains the category, organizes the child entities, and helps users choose the correct path.
- Primary job
- Organize a page family and establish its broader context.
- Build it when
- Several related pages need a meaningful parent or the broader topic deserves its own browsing experience.
- Include
- Category definition, meaningful groupings, child summaries, decision guidance, and contextual navigation.
- Avoid
- Thin pages that contain little more than a heading and list of URLs.
- Usually connects to
- Its parent, important children, related page families, and sometimes supporting resources.
A hub is an architectural page first.
Ranking is useful, but organization is its core responsibility.
Category or Collection Page
A category or collection page organizes items that belong to the same class.
This page type appears frequently in ecommerce, directories, marketplaces, publishing sites, manufacturers, and large resource libraries.
Examples include:
- Commercial Holsters
- Women's Running Shoes
- Industrial Pumps
- Commercial Property Maintenance Guides
- Commercial Cleaning Case Studies
The category must represent a real grouping that helps people browse.
- Primary job
- Help users discover and compare members of a meaningful category.
- Build it when
- The category has enough members and independent demand to justify a browseable destination.
- Include
- A category explanation, useful filtering or grouping, important attributes, child listings, and decision support where appropriate.
- Avoid
- Indexing hundreds of empty or nearly identical taxonomy combinations simply because the CMS creates them.
- Usually connects to
- Parent categories, child products or resources, related categories, guides, and comparison content.
A taxonomy term existing in the CMS does not automatically make it an SEO page.
Resource Center
A resource center acts as the navigational home for substantial informational assets.
It may organize guides, templates, reports, tools, glossary entries, research, and other educational resources.
- Primary job
- Help users find the right educational or decision resource.
- Build it when
- The site has enough useful informational content that users benefit from organized discovery.
- Include
- Useful categories, featured resources, filters where needed, and clear descriptions of what each resource family contains.
- Avoid
- Creating a "Resources" page that simply lists every blog post chronologically.
- Usually connects to
- Guides, tools, research, glossary, templates, reports, and relevant commercial hubs.
About Page
An About page explains the organization behind the website.
Its primary purpose is identity and trust rather than targeting a broad commercial keyword.
- Primary job
- Establish who is behind the business.
- Build it when
- Any legitimate organization should make its ownership, expertise, background, or operating model understandable.
- Include
- Company background, leadership, relevant experience, operating philosophy, markets served, real people, credentials, and appropriate proof.
- Avoid
- Turning the page into a second homepage filled with repeated service copy.
- Usually connects to
- Leadership profiles, services, case studies, credentials, careers, contact information, and the homepage.
For businesses selling expertise, the About page can play an important supporting role in how buyers evaluate credibility.
Commercial Page Types
Service Page
A service page represents something a customer can actually hire the company to perform.
Examples include:
- Roof Repair
- Fractional CFO Services
- Commercial Cleaning
- Penetration Testing
- Immigration Representation
- Fleet Maintenance Services
A service page should help a visitor determine whether the offering matches what they need.
- Primary job
- Capture demand for a commercial offering and help the visitor evaluate whether to inquire.
- Build it when
- The service is genuinely offered and requires enough distinct information to justify a dedicated page.
- Include
- Scope, audience, problems solved, deliverables, process, limitations, relevant proof, FAQs where useful, and a commercial next step.
- Avoid
- Creating separate pages for synonyms of the same service.
- Usually connects to
- Service hub, relevant industries, capabilities, locations, case studies, pricing, guides, and conversion pages.
A service page should answer the questions someone asks before hiring.
It should not read like an encyclopedia entry about the service.
Capability Page
A capability page represents something the organization knows how to do, even when customers do not necessarily buy that competency as a standalone engagement.
Examples include:
- Cash Flow Forecasting
- Failure Mode Analysis
- CNC Machining
- Finite Element Analysis
- Revenue Recognition
- Quality Assurance
- Data Integration
A service describes what the customer buys.
A capability describes what the provider knows how to do.
Sometimes the same concept performs both roles. The correct classification depends on how the business actually sells and how buyers evaluate providers.
- Primary job
- Demonstrate depth in a competency that supports one or more offerings.
- Build it when
- Buyers evaluate the competency separately and the company can demonstrate meaningful expertise.
- Include
- Scope, methodology, applications, technical depth, tools or standards where relevant, evidence, and related services.
- Avoid
- Repeating a service page under another label.
- Usually connects to
- Services using the capability, industries, applications, technologies, evidence, and technical resources.
Product or Product-Family Page
A product page represents a defined commercial product.
Products can include physical goods, equipment, software products, standardized services, or other discrete offerings.
- Primary job
- Help someone evaluate and purchase, request, trial, or inquire about a specific product.
- Build it when
- The product has distinct attributes, demand, applications, specifications, or purchase criteria.
- Include
- Specifications, features, applications, compatibility, options, documentation, availability, images, proof, and purchase or RFQ path.
- Avoid
- Generating separate URLs for trivial variants that add no useful decision information.
- Usually connects to
- Product category, applications, documentation, comparisons, accessories, related products, and conversion paths.
Product Category or Product-Family Page
A product-family page represents a meaningful class of products rather than one individual item.
Examples include:
- Outside-the-Waistband Holsters
- Industrial Air Compressors
- Commercial Generators
- Accounting Software
This page often sits between a broader category and individual products.
- Primary job
- Help buyers narrow a product set.
- Build it when
- The family represents a meaningful buying category with several relevant members.
- Include
- Selection criteria, important differences, product listings, specifications or filters, common applications, and links to deeper guides.
- Avoid
- Thin categories created only because a merchandising filter generated a URL.
- Usually connects to
- Parent category, individual products, related families, applications, comparisons, and buying guides.
Feature Page
A feature page explains a distinct function or capability of a product.
This page type is especially common in software, platforms, equipment, and technology products.
Examples include:
- Automated Invoice Matching
- Real-Time Reporting
- GPS Fleet Tracking
- AI Transcription
- Primary job
- Explain a product function that materially affects the buying decision.
- Build it when
- Buyers search for, evaluate, or compare the functionality separately.
- Include
- What the feature does, problems it solves, how it works, limitations, supported workflows, screenshots or demonstrations, and related use cases.
- Avoid
- Creating a URL for every tiny UI control or feature name.
- Usually connects to
- Product page, solutions, use cases, integrations, documentation, comparisons, and pricing.
Solution Page
A solution page packages products, services, or capabilities around a broader business outcome.
Examples include:
- Revenue Operations Solution
- Employee Onboarding Solution
- Enterprise Search Solution
- Multi-Location Reputation Management
The word "solution" is often used loosely. A real solution page needs a distinct problem and combination of capabilities.
- Primary job
- Explain how several capabilities solve a broader business problem.
- Build it when
- Buyers think about the need at an outcome or solution level rather than around one feature or service.
- Include
- Business problem, affected workflows, required capabilities, approach, proof, implementation, and outcomes.
- Avoid
- Renaming an ordinary service page "Solutions" to sound more sophisticated.
- Usually connects to
- Products, services, capabilities, use cases, industries, case studies, and pricing.
Industry Page
An industry page explains how the company's offering applies to a particular market.
Examples include:
- Employee Benefits for Construction Companies
- Cybersecurity for Healthcare
- Accounting for Manufacturers
- IT Services for Law Firms
The page must contain more than the industry's name.
- Primary job
- Connect the company's offering with the problems, requirements, terminology, buyers, workflows, and evidence specific to an industry.
- Build it when
- The industry materially changes what buyers need to know or how the work gets delivered.
- Include
- Industry problems, relevant services, operational context, regulations where applicable, buyer roles, workflows, proof, and relevant case studies.
- Avoid
- Copying a generic service page and replacing the industry noun.
- Usually connects to
- Industry hub, services, capabilities, compliance pages, use cases, evidence, and decision resources.
A useful test is simple:
If you removed the industry name, would most of the copy still work for another industry?
If yes, the page probably needs more differentiation.
Use-Case or Application Page
A use-case page explains how a product, service, or capability applies to a particular situation or desired outcome.
Examples include:
- Audit Readiness
- Legacy Software Modernization
- Warehouse Automation
- Multi-Location Cleaning Programs
- Aging-in-Place Remodeling
- Reducing Employee Turnover
Unlike an industry, a use case can apply across several verticals.
- Primary job
- Capture demand defined by what the buyer needs to accomplish.
- Build it when
- Buyers describe the need through the situation or outcome rather than the formal service name.
- Include
- Trigger, context, requirements, applicable capabilities, process, constraints, evidence, and expected next step.
- Avoid
- Restating a service without adding application-specific information.
- Usually connects to
- Services, products, capabilities, industries, proof, and related problems.
Problem or Solution Page
A problem page starts with what is wrong.
Examples include:
- AC Not Cooling
- Sewer Backup
- Slow Month-End Close
- High Employee Turnover
- Recurring Equipment Downtime
- Ransomware Readiness
These pages can capture demand before the visitor knows which service they need.
- Primary job
- Help problem-aware users understand what may be happening and identify the appropriate solution.
- Build it when
- People consistently search through the problem and the answer requires enough depth to justify its own page.
- Include
- Symptoms, causes, risk or urgency, diagnostic considerations, potential solutions, when professional help becomes necessary, and relevant service paths.
- Avoid
- Creating separate problem pages when a short section on the corresponding service page answers the task completely.
- Usually connects to
- Relevant services, related problems, guides, proof, and conversion paths.
Technology or Platform Page
A technology page explains expertise involving a particular platform, technical environment, equipment system, or ecosystem.
Examples include:
- AWS Migration
- Microsoft 365 Consulting
- HubSpot Implementation
- Generac Generator Installation
- Enphase Solar Systems
- Primary job
- Demonstrate competence within a technology buyers use to evaluate vendors.
- Build it when
- Platform or technology selection materially affects the buying decision.
- Include
- Supported work, integrations, certifications where applicable, compatibility, related services, technical expertise, examples, and limitations.
- Avoid
- Publishing pages for popular brands the company barely uses.
- Usually connects to
- Services, capabilities, integrations, certifications, applications, and case studies.
Integration Page
An integration page explains how one product connects with another platform, system, or data source.
Examples include:
- Salesforce Integration
- QuickBooks Integration
- Slack Integration
- Shopify Integration
Integration pages are especially useful for software and technical services where compatibility affects adoption.
- Primary job
- Answer whether and how two systems work together.
- Build it when
- The integration is real, supported, useful, and important enough to influence acquisition or product use.
- Include
- Supported workflows, data exchanged, setup, requirements, limitations, screenshots, documentation, and related use cases.
- Avoid
- Publishing pages for integrations that do not actually exist.
- Usually connects to
- Product, feature, documentation, use cases, technology pages, and signup or demo paths.
Compliance or Standard Page
A compliance page explains how an offering relates to a regulatory requirement, certification framework, or technical standard.
Examples include:
- HIPAA IT Support
- CMMC Consulting
- PCI DSS Security Services
- ISO 27001 Readiness
- AS9100 Manufacturing
- Primary job
- Help buyers determine whether the provider can operate within a required compliance context.
- Build it when
- The standard materially changes vendor selection or delivery requirements.
- Include
- Relevant requirements, provider scope, methodology, qualifications, limitations, documentation, services, and evidence.
- Avoid
- Implying certification, legal status, or authorization the company does not possess.
- Usually connects to
- Services, industries, capabilities, credentials, methodology, and case studies.
Material, Component, or Specification Page
Industrial, construction, engineering, manufacturing, and technical sites often need pages organized around materials, components, or specifications.
Examples include:
- Stainless Steel CNC Machining
- EPDM Roofing Systems
- Aerospace Aluminum Fabrication
- 3-Phase Industrial Generators
- Primary job
- Capture technical evaluation demand that depends on a specific material, specification, or component.
- Build it when
- The attribute changes applications, capabilities, performance, pricing, or provider selection.
- Include
- Specifications, tolerances, applications, standards, limitations, compatible processes, documentation, and relevant products or services.
- Avoid
- Generating pages for every possible adjective + product combination without meaningful information.
- Usually connects to
- Products, capabilities, applications, industries, documentation, and RFQ paths.
Geographic Page Types
Geographic pages require more discipline than almost any other SEO family.
The presence of a city keyword does not automatically justify a city page.
The page should represent a genuine geographic relationship.
Location Page
A location page represents a real business location such as an office, branch, clinic, showroom, shop, dealership, or facility.
Examples include:
- Downtown Spokane Dental Clinic
- Denver Engineering Office
- Austin Retail Store
- Primary job
- Represent a real place where the business operates.
- Build it when
- The company has a genuine location with enough customer relevance to deserve its own page.
- Include
- Address, contact information, hours where appropriate, directions, parking or access information, services offered, local staff, imagery, proof, and customer actions.
- Avoid
- Using virtual offices, mailboxes, or fictional locations to create geographic relevance.
- Usually connects to
- Locations hub, services available there, professionals, local evidence, and booking or contact paths.
A physical location page says:
We are here.
That is different from saying:
We serve here.
Service-Area Page
A service-area page represents a market the company legitimately serves without implying that the company has a physical office there.
This page type commonly applies to:
- Plumbers
- Roofers
- Remodelers
- Cleaning companies
- Landscapers
- Wildlife control companies
- Transportation providers
- Mobile services
- Other companies that travel to the customer
- Primary job
- Explain how the company serves customers within a genuine market.
- Build it when
- The market matters to the business and the company can provide enough useful information about serving it.
- Include
- Services available, service boundaries, market-specific considerations, real projects or proof when available, response or travel expectations, and a useful conversion path.
- Avoid
- Replacing one city name across dozens or hundreds of otherwise identical pages.
- Usually connects to
- Geographic parent, services, nearby legitimate markets, local projects, proof, and quote or booking paths.
A service-area page says:
We work here.
It should not say or imply:
We have an office here
unless that is true.
Service + Location Page
A service + location page combines a specific service with a specific market.
Examples include:
- Emergency Plumbing in Spokane
- Commercial Cleaning in Seattle
- Roof Replacement in Coeur d'Alene
These pages can capture highly specific demand.
They can also create uncontrolled architecture very quickly.
- Primary job
- Answer a geographically specific service task that broader service or market pages cannot cover adequately.
- Build it when
- The combination has distinct demand and genuinely differentiated information.
- Include
- Market-specific service considerations, availability, proof, local constraints, applicable pricing factors, process, and next action.
- Avoid
- Automatically multiplying every service by every city.
- Usually connects to
- Parent service, geographic page, projects, related services, and conversion path.
Consider the multiplication before creating this architecture.
20 services × 50 cities = 1,000 URLs.
The spreadsheet takes seconds.
Creating 1,000 useful pages does not.
Regional, State, Provincial, or Country Market Page
Some businesses operate across geographic markets that are broader than cities.
Examples include:
- Industrial Distribution Across Latin America
- Hiring in Brazil
- Commercial Roofing Across North Idaho
- Canadian Payroll Services
These pages are not always traditional "local SEO" pages.
They may represent regulatory, linguistic, cultural, logistical, or market differences.
- Primary job
- Explain how an offering operates within a meaningful geographic market.
- Build it when
- Geography changes buyer requirements, service delivery, terminology, regulation, language, pricing, or other important considerations.
- Include
- Market conditions, service availability, relevant differences, supporting submarkets, proof, and applicable commercial paths.
- Avoid
- Creating country or state pages where geography changes nothing except the keyword.
- Usually connects to
- Geographic parent, city or local child pages, services, market-specific resources, and evidence.
Multi-Location Hub
A multi-location hub organizes genuine branches or operating markets.
Examples include:
- Our Locations
- Areas We Serve
- Clinics
- Stores
- Offices
- Primary job
- Help visitors select the relevant physical location or service market.
- Build it when
- Several legitimate locations or markets need organization.
- Include
- Useful groupings, geographic hierarchy, concise market information, and links to legitimate child pages.
- Avoid
- Turning the hub into an enormous list of every town within driving distance.
- Usually connects to
- All important location or service-area children and relevant business services.
Proof and Expertise Page Types
Case Study Page
A case study explains what happened when the company solved a real problem.
Strong case studies typically connect:
Situation → problem → constraints → approach → execution → result → evidence
A testimonial says the customer was happy.
A case study explains why another buyer should believe the company can solve a similar problem.
- Primary job
- Reduce uncertainty with relevant evidence.
- Build it when
- A real engagement contains enough context, decisions, work, and results to help another buyer evaluate the provider.
- Include
- Customer context, challenge, constraints, work performed, reasoning, evidence, measurable outcomes where available, and implications.
- Avoid
- Publishing pages containing only a logo, short testimonial, and unsupported claim.
- Usually connects to
- Relevant services, industries, capabilities, locations where applicable, and related decision pages.
Project or Portfolio Page
A project page documents work without requiring the deeper outcome narrative of a case study.
Examples include:
- Kitchen Remodel
- Commercial Construction Project
- Roof Replacement
- Landscape Installation
- Engineering Project
- Manufacturing Project
- Primary job
- Show the scope, quality, and relevance of real work.
- Build it when
- Individual projects help buyers judge fit or execution quality.
- Include
- Scope, project type, location where useful, services used, materials, imagery, constraints, team involvement, and outcome.
- Avoid
- Forcing every project into a case-study format when measurable business results do not exist.
- Usually connects to
- Services, project categories, locations, portfolio hub, and related projects.
Professional or Expert Profile Page
A professional profile represents a person whose expertise matters to the buying decision or credibility of published content.
Examples include:
- Attorney
- Doctor
- Dentist
- Engineer
- CPA
- Consultant
- Executive
- Researcher
- Technical specialist
- Author
- Primary job
- Establish the person's identity, qualifications, expertise, and relationship to the organization.
- Build it when
- The individual matters to the service, content, customer decision, or professional credibility of the site.
- Include
- Role, experience, qualifications, licenses, specialties, professional history, publications, speaking, projects, or other relevant contributions.
- Avoid
- Creating thin profile pages for every employee purely to increase URL count.
- Usually connects to
- Services, articles, case studies, projects, locations, credentials, and team pages.
Credentials or Certification Page
A credentials page documents qualifications relevant to provider selection.
These might include:
- Licenses
- Certifications
- Accreditations
- Professional memberships
- Quality standards
- Authorized partnerships
- Awards with legitimate selection criteria
- Primary job
- Make important qualifications easy to understand and verify.
- Build it when
- Credentials materially affect confidence, eligibility, or provider selection.
- Include
- Exact credential, issuer, scope, validity where applicable, meaning, and relationship to the company's services.
- Avoid
- Displaying decorative logos without context or implying relationships that do not exist.
- Usually connects to
- Services, industries, compliance pages, professional profiles, and evidence.
Reviews or Testimonials Page
A testimonials page aggregates customer feedback.
A dedicated page is not always necessary.
Reviews often create more value when placed directly beside the service, market, proof, or decision they support.
- Primary job
- Aggregate customer experiences when testimonial browsing itself helps evaluation.
- Build it when
- The organization has enough authentic and contextual evidence to justify a collection.
- Include
- Feedback, source where appropriate, customer context, related offering or market, and links to deeper proof when available.
- Avoid
- Anonymous praise with no useful context.
- Usually connects to
- Services, case studies, locations, industries, and conversion paths.
Decision-Support Page Types
These pages are often underbuilt.
They matter because search demand does not stop when someone discovers a service.
People still need to evaluate cost, alternatives, methodology, fit, proof, and risk.
Pricing or Cost Page
A pricing page explains what your company charges or how your commercial model works.
Examples include:
- Managed IT Support Pricing
- Software Pricing
- Membership Plans
- Cleaning Packages
- Consulting Rates
- Primary job
- Reduce uncertainty around your specific commercial model.
- Build it when
- Buyers regularly need pricing information before taking the next step.
- Include
- Price ranges where possible, packages, scope, inclusions, exclusions, variables, payment model, examples, and next action.
- Avoid
- Saying only "Contact us for a quote" when you could explain what determines the quote.
- Usually connects to
- Services, plans, comparisons, process, calculators, FAQs, and conversion paths.
Cost Guide
A cost page explains what buyers can expect to invest in a service, product, project, or market.
Examples include:
- How Much Does Commercial Pest Control Cost?
- Roof Replacement Cost
- Fractional CFO Cost
- Commercial Cleaning Cost
A pricing page explains your pricing.
A cost guide explains the economics of the buying decision.
Sometimes one page can answer both.
Sometimes the tasks differ enough to justify separate resources.
- Primary job
- Explain financial ranges and the variables that change them.
- Build it when
- Cost is an independent research task and enough useful information exists to answer it.
- Include
- Ranges, pricing variables, examples, hidden or secondary costs, tradeoffs, and budgeting guidance.
- Avoid
- Fake precision when costs genuinely vary.
- Usually connects to
- Service pages, pricing, calculators, comparisons, process, and consultation.
Comparison Page
A comparison page helps someone choose between meaningful alternatives.
Examples include:
- Heat Pump vs Furnace
- Fractional CFO vs In-House CFO
- Managed IT vs Internal IT
- Metal Roofing vs Asphalt Shingles
- Outsourced Bookkeeping vs In-House Accounting
The alternatives do not need to be competing brands.
- Primary job
- Help the reader make a choice.
- Build it when
- Buyers genuinely compare the options and meaningful differences exist.
- Include
- Evaluation criteria, advantages, limitations, cost considerations, use cases, fit by situation, and a decision framework.
- Avoid
- Writing a disguised sales page where your preferred option wins every category.
- Usually connects to
- Each option page, pricing, relevant use cases, evidence, and conversion paths.
The strongest comparison pages are willing to say when the alternative is the better choice.
That makes the recommendation more useful.
Alternative Page
An alternatives page helps someone evaluate substitutes for a known product, service, provider model, or approach.
Examples include:
- Alternatives to Hiring a Full-Time CFO
- HubSpot Alternatives
- Alternatives to Traditional Recruiting Agencies
This differs from a two-option comparison.
The user has already identified one option and wants to explore the field.
- Primary job
- Present credible substitutes and help the buyer narrow them.
- Build it when
- Searchers consistently evaluate alternatives and your offering legitimately belongs in the consideration set.
- Include
- Selection criteria, suitable options, differences, ideal fit, limitations, and a comparison framework.
- Avoid
- Creating a list where every competitor receives one negative sentence and your company receives the only positive description.
- Usually connects to
- Comparison pages, product or service pages, pricing, buyer guides, and proof.
Process or Methodology Page
A process page explains how the work gets done.
Examples include:
- Our Remodeling Process
- Commercial Cleaning Quality-Control Process
- Recruiting Process
- Engineering Project Delivery
- Implementation Process
- Primary job
- Reduce uncertainty about what happens after engagement.
- Build it when
- The process itself affects provider selection or requires enough explanation to deserve a dedicated page.
- Include
- Stages, inputs, responsibilities, decision points, deliverables, dependencies, timelines where appropriate, and customer responsibilities.
- Avoid
- Creating a separate page for a generic three-step process that fits naturally on the service page.
- Usually connects to
- Services, capabilities, pricing, case studies, FAQs, and consultation.
Buyer's Guide or Selection Guide
A buyer's guide teaches someone how to evaluate a category before choosing a provider or product.
Examples include:
- How to Choose an Engineering Consulting Firm
- How to Choose a Commercial Roofing Contractor
- How to Evaluate Nearshore Staffing Companies
- ERP Buyer's Guide
- Primary job
- Give buyers an evaluation framework before purchase.
- Build it when
- Provider selection requires multiple criteria or buyers face meaningful risk, confusion, or complexity.
- Include
- Requirements, evaluation criteria, questions to ask, warning signs, decision framework, budget considerations, proof requirements, and next steps.
- Avoid
- Making the guide a long advertisement with no useful selection advice.
- Usually connects to
- Services, comparisons, pricing, case studies, methodology, and consultation.
RFP or Procurement Resource
Some B2B purchases involve formal procurement.
An RFP page or resource can explain what buyers should require, how to structure evaluation, or how the vendor handles procurement.
Examples include:
- Managed IT Services RFP Template
- Cybersecurity Vendor Questionnaire
- Commercial Cleaning RFP Guide
- Software Procurement Checklist
- Primary job
- Support a structured purchasing process.
- Build it when
- Procurement, vendor evaluation, or RFPs commonly appear in the buying cycle.
- Include
- Requirements, evaluation criteria, questions, scope guidance, stakeholder input, implementation considerations, and reusable templates where useful.
- Usually connects to
- Services, methodology, case studies, security or compliance, pricing, and contact.
FAQ or Decision-Support Page
An FAQ page answers recurring questions buyers need resolved.
A dedicated FAQ URL is not automatically necessary.
Often the best place for a question is directly on the service, pricing, location, comparison, or process page where the question arises.
- Primary job
- Resolve recurring uncertainty.
- Build a standalone page when
- The questions collectively form a coherent and substantial resource.
- Use a section instead when
- The questions belong directly to another page's task.
- Include
- Specific questions, direct answers, and deeper contextual paths where appropriate.
- Avoid
- Creating dozens of thin question URLs or publishing FAQs only because structured data exists.
FAQ content should serve users even if no special search feature appears.
Contact Page
A contact page provides general ways to reach the organization.
- Primary job
- Make direct communication easy.
- Include
- Appropriate contact methods, expected response information, business details, and routing for different needs where necessary.
- Avoid
- Asking for information you do not need.
- Usually receives links from
- Navigation, commercial pages, About, and sitewide utility areas.
Contact, Booking, Consultation, or RFP Page
These are action-specific conversion pages.
Examples include:
- Request an Estimate
- Schedule a Consultation
- Book an Appointment
- Request a Proposal
- Start a Demo
- Submit an RFP
- Primary job
- Complete a defined business action with minimal friction.
- Include
- Only the information required to complete or qualify the action, expectations, next steps, and appropriate reassurance.
- Avoid
- Making visitors complete a long form before they understand the offering.
- Usually receives links from
- Services, pricing, comparisons, proof, industry pages, and decision resources.
Interactive Page Types
Calculator, Planner, Assessment, or Interactive Tool
A calculator accepts inputs and returns a useful numerical or decision output.
Examples include:
- Equipment Leasing ROI Calculator
- Warehouse Expansion Cost Calculator
- Mortgage Calculator
- Staffing Savings Calculator
- Project Cost Estimator
- Primary job
- Help users answer a question with their own data.
- Build it when
- Calculation materially improves the usefulness of the answer.
- Include
- Clear inputs, assumptions, calculation logic, output explanation, limitations, and sensible next actions.
- Avoid
- Fake calculators that collect contact information without performing the promised calculation.
- Usually connects to
- Pricing, cost guides, services, methodology, and related tools.
Assessment or Diagnostic Tool
An assessment collects information and interprets the result.
Examples include:
- Multi-Location Expansion Readiness Assessment
- Security Maturity Assessment
- Hiring Readiness Assessment
- Fleet Maintenance Risk Diagnostic
- Primary job
- Help someone understand their current condition, fit, risk, or next priority.
- Build it when
- Structured questions can produce a meaningful result.
- Include
- Questions, scoring logic, result explanation, limitations, and next steps.
- Avoid
- Giving a dramatic score solely to force a sales call.
Planner or Configurator
A planner helps users assemble or choose an appropriate configuration.
Examples include:
- Workforce Capacity Planner
- Product Configurator
- Coverage Planner
- Budget Planner
- Equipment Selector
- Primary job
- Turn several variables into a useful plan or recommendation.
- Build it when
- Users need to combine multiple choices before acting.
- Include
- Input definitions, constraints, recommendations, assumptions, and output that users can actually use.
Directory, Database, or Search Tool
A searchable database lets users discover information across a structured collection.
Examples include:
- Provider Directory
- Location Finder
- Product Database
- Salary Database
- Certification Directory
- Industry Benchmark Explorer
- Primary job
- Help users find or filter structured information.
- Build it when
- The dataset itself has enough value and scale to justify interactive discovery.
- Include
- Useful filtering, clear entity pages or result states where appropriate, transparent data sources, and meaningful empty-state handling.
- Avoid
- Creating indexable filter combinations for every possible query unless those result pages provide independent value.
Things People Call Page Types That Actually Are Not
Several SEO terms describe publishing formats, architecture relationships, traffic sources, or production methods rather than true page roles.
Understanding the difference prevents architecture mistakes.
"Landing Page"
A landing page is simply a page someone lands on.
It does not tell you what job that page performs.
A service page can be a landing page.
A comparison page can be a landing page.
A service-area page can be a landing page.
A paid advertising page can be a landing page.
Instead of saying:
"We need a landing page for Dallas."
Ask:
"Do we need a Dallas location page, a Dallas service-area page, or a specific service + Dallas page?"
The second question produces a better website.
"Blog Post"
A blog post describes where or how content gets published.
It does not define the search task.
A post might function as:
- A guide
- A comparison
- A research report
- A case study
- A checklist
- A statistics page
- A news update
- An opinion article
- A methodology resource
Plan the task first.
Choose the CMS publishing format second.
"Pillar Page"
A pillar page describes an architectural relationship.
It usually means a broad page connected to several narrower resources.
The pillar itself might function as:
- A hub
- A service page
- A guide
- A category
- A resource center
"Pillar" tells you where the page sits in a cluster.
It does not fully describe its job.
"Programmatic SEO Page"
Programmatic SEO describes a method of producing pages at scale.
It is not a page type.
A programmatic system may produce:
- Location pages
- Integration pages
- Product pages
- Directory pages
- Comparison pages
- Statistics pages
- Template pages
The underlying pages still need valid tasks and useful information.
Automation does not remove the requirement for differentiation.
It makes bad architecture easier to scale if the underlying page model is wrong.
"AI SEO Page"
There is no universal page type that exists solely because AI search exists.
AI systems can surface information from service pages, research, documentation, comparison pages, profiles, guides, tools, case studies, and other useful documents.
Do not create a new page family merely by adding "AI" to existing SEO terminology.
Build pages that answer real tasks clearly and provide information worth retrieving.
Page Types That Are Often Confused
Service Page vs Capability Page
A service page represents something the customer hires the company to provide.
A capability page represents an ability the company uses to deliver work.
If customers buy the competency directly, the distinction may disappear.
The deciding factor is the page's commercial role, not the vocabulary used internally by the company.
Service Page vs Solution Page
A service page usually represents a defined engagement or deliverable.
A solution page organizes several capabilities around a larger business problem or outcome.
If both pages would contain the same offer, process, proof, and CTA, you probably do not need both.
Product Page vs Feature Page
A product page represents the whole product.
A feature page explains a meaningful part of what that product can do.
Not every feature deserves its own URL.
Industry Page vs Use-Case Page
An industry page answers:
How does this company help organizations like mine?
A use-case page answers:
How does this company help with this situation?
Manufacturing is an industry.
Audit readiness is a use case.
The same use case may apply to multiple industries.
Industry Page vs Service for Industry Page
Sometimes one industry page can explain all relevant offerings.
Other sites may need separate combinations such as:
- Accounting for Construction Companies
- Fractional CFO Services for Construction Companies
Whether both deserve URLs depends on how much the service + industry combination changes the task and information requirements.
Do not multiply services × industries automatically.
Physical Location vs Service-Area Page
A location page represents a real place where the business operates.
A service-area page represents a market the business serves.
One says:
We are here.
The other says:
We serve here.
Do not blur the distinction.
Service-Area Page vs Service + Location Page
A service-area page represents the business's broader relationship with a market.
A service + location page focuses on one particular offering within that market.
The second model creates much greater multiplication risk.
Require stronger evidence before building it.
Pricing Page vs Cost Guide
A pricing page explains your company's commercial model.
A cost guide explains what buyers should expect to invest and what changes the cost.
If those questions require essentially the same answer, combine them.
Case Study vs Project Page
A project page shows what the company did.
A case study explains why the work mattered and what happened as a result.
Every case study can describe a project.
Not every project contains enough evidence to become a useful case study.
Guide vs Service Page
A service page helps someone evaluate whether to hire the provider.
A guide helps someone learn, solve, prepare, or decide.
A service page can educate.
The education should support the buying task rather than bury it.
FAQ Page vs FAQ Section
Use an FAQ section when the questions belong to another page.
Build a dedicated FAQ page only when the collection forms a meaningful standalone resource.
Glossary Entry vs Guide
A glossary entry defines a concept.
A guide helps someone understand, use, evaluate, or act on it.
If the definition keeps expanding into methodology, examples, decisions, and implementation, the concept may deserve a guide rather than a glossary page.
When Should Two Page Ideas Become One URL?
Merge page ideas when the same visitor would expect essentially the same answer.
| Situation |
Usually better approach |
| Two keywords describe the same service |
One service page |
| Two capability names describe the same competency |
One capability page |
| A question only clarifies one service |
Add it to the service page |
| Cost and pricing require the same explanation |
Consider one pricing/cost page |
| Several glossary terms need only short definitions |
Consolidate into a master glossary |
| City pages would differ mostly by place name |
Reconsider separate URLs |
| A guide and commercial page serve different tasks |
Keep separate |
| An industry changes buyer requirements and proof |
Separate industry page may be useful |
| A comparison requires criteria not covered on either option page |
Separate comparison page may be useful |
| A feature changes product evaluation materially |
Feature page may deserve its own URL |
The goal is not to minimize URLs.
The goal is to avoid asking multiple URLs to perform the same job.
When Should One Page Become Several?
Split a page when its sections have evolved into separate tasks with different audiences, information requirements, proof, search patterns, or next actions.
A general commercial cleaning page might eventually need separate service pages for:
- Office Cleaning
- Medical Facility Cleaning
- Industrial Cleaning
- Day Porter Services
That does not mean every subsection automatically becomes a URL.
Before splitting, ask:
- Can the new child page become substantially more useful than the section it replaces?
- Does the topic require different proof?
- Does it have different pricing considerations?
- Do buyers describe the service separately?
- Does the company genuinely deliver it as a distinct offering?
- Does the child have a logical place in the architecture?
- Would the parent still have a clear job after the split?
If not, keep the information together.
The Multiplication Test
One of the most dangerous architecture decisions occurs when two page dimensions get multiplied.
Examples:
- Services × Cities
- Products × Applications
- Services × Industries
- Features × Industries
- Roles × Countries
- Problems × Locations
- Platforms × Services
Suppose a company has:
- 15 services
- 30 cities
- 12 industries
Creating every combination would produce:
- 450 service + city pages
- 180 service + industry pages
And potentially thousands more if dimensions get combined again.
Before authorizing a page matrix, test each combination independently.
Ask:
Does this combination have demand?
Does the combination change what users need to know?
Can we provide combination-specific proof?
Does the business actually support it?
Can we maintain it?
Does it have a distinct conversion path?
Could one broader page serve the task better?
Templates should help scale useful relationships.
They should not manufacture relationships that do not exist.
How Page Types Should Link to Each Other
Internal linking should reflect relationships between entities and tasks.
More links do not automatically create better architecture.
A strong internal link usually explains why two pages belong together.
Parent and Child Links
A hub should connect to the important pages it organizes.
Children should provide a useful path back to the parent when that parent helps users understand the broader category.
Example:
- Services → Fractional CFO Advisory
- Locations → Idaho → Coeur d'Alene
- Industries → Construction
Service and Capability Links
Link a capability to a service when the capability helps deliver that service.
Example:
- Managed IT Services → Cloud Migration
- Cloud Migration → Managed IT Services
These links describe an operating relationship.
Service and Application Links
Link services to industries, use cases, or markets where the service genuinely applies.
Example:
- Commercial Cleaning → Healthcare Facilities
- Commercial Cleaning → Industrial Facilities
The destination should explain the application rather than repeat the parent service.
Evidence Links
Commercial pages should link to proof that validates the claim being made.
Example:
- Commercial Roofing → Warehouse Roof Replacement Case Study
- Revenue Recognition Advisory → Manufacturing Close-Process Case Study
Evidence links reduce the distance between a claim and the proof supporting it.
Decision-Support Links
Commercial pages should connect to resources that answer common buying questions.
Examples:
- Managed IT Services → Managed IT Pricing
- Managed IT Services → How to Choose an IT Support Provider
- Fractional CFO Services → Financial Planning Roadmap
- Roof Replacement → Roof Replacement Cost
Informational-to-Commercial Links
Guides should connect toward commercial pages when the relationship genuinely helps the reader.
The anchor should make sense within the information being discussed.
Do not force every blog post to link to every service.
Sibling Links
Sibling pages can link when the relationship helps users continue the same task.
Good:
- Roof Repair → Roof Replacement
- Fractional CFO Services → Cash Flow Forecasting when the discussion involves planning and liquidity
- Spokane → Coeur d'Alene when both represent genuinely related operating markets
Weak:
- Every city page linking to every other city page
- Every industry page linking to every other industry
- Every service page linking to the full service catalog
A website should not become a complete mesh.
Relationships should have meaning.
Visual Structure Should Match Page Function
Page type is not only about text.
The order and presentation of information should reflect what the page is supposed to help the visitor accomplish.
A service page might prioritize:
- Service definition
- Fit
- Scope
- Problems addressed
- Process
- Proof
- Pricing context
- FAQs
- Conversion
A comparison page might prioritize:
- Quick answer
- Comparison table
- Decision criteria
- Differences
- Advantages and limitations
- Cost
- Best fit by situation
- Recommendation
A case study might prioritize:
- Result
- Customer context
- Problem
- Constraints
- Approach
- Execution
- Evidence
- Takeaways
A guide might prioritize:
- Direct answer
- Important context
- Detailed explanation
- Examples
- Steps or framework
- Evidence
- Related decisions
- Next resource
Using the same layout for every page may simplify design work.
It can also make different page types behave as if they serve the same task.
Consistency should support comprehension.
It should not erase meaning.
How to Decide Whether a Page Should Be Indexed
Not every valid website URL belongs in search results.
Before allowing a page to remain indexable, ask:
- Does this page perform a useful standalone task?
- Does it contain information searchers could reasonably benefit from?
- Does another URL serve the same task better?
- Is the page intended for public discovery?
- Is there enough unique value to justify keeping it in the searchable inventory?
Possible decisions include:
| Situation |
Possible action |
| Valuable distinct page |
Keep indexable |
| Two pages serve the same task |
Merge and redirect where appropriate |
| Page is useful for users but poor as a search result |
Consider noindex |
| URL exists only because of filtering or CMS mechanics |
Evaluate canonical, crawl, or index controls |
| Old page has a strong replacement |
Redirect |
| Page has no value and no replacement |
Remove with appropriate HTTP handling |
| Thin page can become useful |
Improve before expanding the family |
| Large template family has uncertain value |
Validate a smaller set before scaling |
Noindex is not a substitute for architecture.
Neither is canonicalization.
Start by deciding whether the URL deserves to exist.
Faceted and Filter Pages Need Their Own Rules
Ecommerce, directories, marketplaces, and large databases can generate enormous numbers of filtered URLs.
Examples include combinations of:
- Brand
- Color
- Size
- Price
- Material
- Location
- Category
- Availability
- Specification
Some filtered states may represent meaningful search tasks.
Most combinations do not need to become independent indexable pages.
Before indexing a filter state, evaluate:
- Search demand
- Stable inventory
- Distinct intent
- Useful content or product selection
- Internal linking
- Canonical behavior
- Crawl impact
- Duplication risk
- Long-term maintainability
Do not allow the technical ability to create a URL to become the editorial reason to index it.
Page Types and Structured Data
Page type and structured-data type are related concepts, but they are not interchangeable.
A service page does not need a special rich result to be a valid service page.
A profile page can describe a person regardless of whether a particular search feature appears.
An FAQ section should exist because the questions help users, not because the site expects an FAQ rich result.
Use structured data when it accurately describes information already visible or legitimately represented on the page.
Do not choose your architecture based on which schema types appear to promise rich results.
The page's task comes first.
How Page Types Work Together: Local Business Example
Consider a roofing company.
Its architecture might look like this:
- Home
- Services
- Roof Repair
- Roof Replacement
- Roof Inspection
- Metal Roofing
- Service Areas
- Spokane
- Coeur d'Alene
- Post Falls
- Projects
- Spokane Metal Roof Replacement
- Coeur d'Alene Storm Repair
- Decision Resources
- Roof Replacement Cost
- Metal Roofing vs Asphalt Shingles
- How to Choose a Roofing Contractor
- Guides
- When Should a Roof Be Replaced?
- Signs of Roof Damage
- How to Prepare for a Roof Replacement
- Request an Estimate
Each family answers a different question.
Services: What can you hire us to do?
Service areas: Where do we work?
Projects: Have we done this before?
Decision resources: How should you evaluate the purchase?
Guides: What do you need to understand?
Estimate: How do you start?
That is a semantic network built around the business.
How Page Types Work Together: B2B Example
Consider an accounting and finance firm.
- Home
- Services
- Fractional CFO
- Outsourced Accounting
- Audit Readiness
- Industries
- Manufacturing
- Construction
- Professional Services
- Capabilities
- Revenue Recognition
- Financial Reporting
- Cash Flow Forecasting
- Case Studies
- Manufacturing Finance Transformation
- Construction Close Process Improvement
- Decision Resources
- Fractional CFO vs In-House CFO
- Fractional CFO Cost
- How to Choose an Outsourced Accounting Firm
- Resources
- Audit Readiness Checklist
- Month-End Close Guide
- Cash Flow Forecasting Template
- Schedule a Consultation
Again, each family answers something different.
Services: What can we buy?
Industries: Do you understand a company like ours?
Capabilities: Can you handle the technical work involved?
Case studies: Can you prove it?
Decision pages: How should we evaluate our options?
Resources: Can you help us understand the problem?
Consultation: What happens when we are ready?
That is what good B2B architecture should accomplish.
How Page Types Work Together: Product or Software Example
A product-led site may use another structure:
- Product
- Features
- Reporting
- Automation
- Permissions
- Solutions
- Revenue Operations
- Customer Success
- Industries
- Professional Services
- Manufacturing
- Integrations
- Salesforce
- QuickBooks
- Slack
- Comparisons
- Product A vs Product B
- Competitor Alternatives
- Pricing
- Documentation
- Resources
- Demo or Signup
The page roles change because the buying model changes.
Your architecture should represent how your business actually works.
What Every Indexable SEO Page Should Have
Regardless of page type, a page intended to earn organic visibility should normally have:
- A clear primary task
- A specific subject or entity
- A descriptive title
- A clear main heading
- Enough information to complete the intended task
- A logical position within the website
- Useful contextual internal links
- A reason for the visitor to continue, decide, or act
- Accurate business information
- Appropriate proof where claims require it
- A canonical URL strategy
- Crawlable internal links
- Content worth finding independently
The exact content depends on the page's role.
A pricing page does not need the same structure as an industry page.
A case study does not need the same structure as a service page.
A physical location page does not need the same structure as a guide.
A calculator does not need the same word count as an article.
Good architecture standardizes relationships.
It does not force every document into the same content template.
Common SEO Page Architecture Mistakes
| Mistake |
Why it creates problems |
| Building one URL for every keyword variation |
Creates overlap without new task coverage |
| Creating several pages for synonymous services |
Splits relevance and confuses users |
| Using one broad service page for every offering |
Prevents deeper commercial tasks from being answered |
| Creating industry pages by swapping industry names |
Adds little industry-specific value |
| Building city pages without real local differentiation |
Creates thin geographic inventory |
| Treating service areas as physical locations |
Misrepresents business operations |
| Multiplying every service by every city |
Creates uncontrolled URL growth |
| Treating services and capabilities as interchangeable |
Makes the commercial hierarchy harder to understand |
| Publishing articles for queries that need commercial pages |
Matches the topic but not the buying task |
| Publishing commercial pages for purely informational queries |
Forces a sales experience onto a research task |
| Creating proof pages without connecting them to the claims they validate |
Leaves evidence isolated |
| Publishing dozens of thin glossary terms |
Creates definition inventory without useful depth |
| Creating FAQ pages for every question |
Fragments topics that could live naturally on stronger pages |
| Indexing every CMS taxonomy |
Lets platform mechanics define SEO architecture |
| Indexing every filter combination |
Creates crawl and duplication problems |
| Building comparison pages that always declare your product the winner |
Reduces usefulness and trust |
| Building calculators that do not calculate |
Fails the promised task |
| Hiding important pages deep in the site |
Weakens discovery and user navigation |
| Linking every page to every remotely related page |
Removes meaning from the internal-link graph |
| Scaling templates before validating them |
Multiplies weak assumptions |
A Better Way to Plan SEO Pages
Start with the business.
Document:
- What the company sells
- Who buys it
- Which problems create demand
- Which capabilities matter
- Which industries change the buying process
- Where the company genuinely operates
- Which products or technologies affect selection
- Which questions appear before purchase
- Which alternatives buyers compare
- Which proof exists
- Which costs buyers need to understand
- Which actions represent conversion
Then map search behavior onto those relationships.
Do not begin with 5,000 keywords and ask how many URLs you can produce.
Begin with the business model and ask which search tasks reveal or evaluate its real entities.
Search volume can help prioritize those pages.
It should not define the entire architecture.
The SEO Page Planning Framework
Before approving a new URL, complete this short specification.
| Field |
Question |
| Page type |
What job will this page perform? |
| Primary entity |
What service, product, person, market, problem, or concept does it represent? |
| Primary task |
What should the visitor accomplish here? |
| Audience |
Who needs this page? |
| Trigger |
What situation causes someone to search for it? |
| Existing overlap |
Which current page comes closest to answering the task? |
| Unique information |
What can this page contain that the existing page cannot? |
| Proof |
What evidence supports this page? |
| Parent |
Where does it belong in the architecture? |
| Child pages |
Does it organize narrower entities? |
| Related pages |
Which pages have genuine semantic relationships with it? |
| Conversion |
What should the visitor do next? |
| Maintenance |
Can the information remain accurate? |
| Indexation |
Should this document appear independently in search? |
| Success metric |
How will you know whether the page is useful? |
If you cannot answer several of these questions, the idea may not be ready for its own URL.
Before Creating a New Page, Choose One of Five Actions
Every keyword or content idea does not need a new URL.
Usually, you have five choices.
1. Create
Create a new page because the task, entity, and information requirements are meaningfully different.
2. Expand
Add the topic to an existing page because it strengthens the page's current job.
3. Merge
Combine overlapping pages because they compete to answer essentially the same task.
4. Reposition
Keep the page but change its role.
A weak article might become a comparison page.
A generic city page might become a legitimate service-area page.
A thin service page might become a capability section under a stronger parent.
5. Remove
Remove a page when it serves no useful task, has no reason to remain public, and no stronger architecture requires it.
The skill is not publishing.
The skill is choosing correctly among these five options.
Frequently Asked Questions About SEO Page Types
How many pages should a website have for SEO?
There is no ideal page count.
A website should have enough pages to represent its real offerings, markets, expertise, proof, and customer tasks without creating unnecessary overlap.
A specialized local company may need dozens of pages.
A national B2B company may need hundreds.
A large ecommerce or marketplace site may legitimately need millions.
Page count is the result of the business and information architecture, not the goal.
Does every keyword need a separate page?
No.
Several keywords can express the same task and belong on one strong page.
Create another URL when the search task, entity, required information, or evaluation criteria differ enough to justify it.
How do I know whether two keywords should target the same page?
Ask whether the same visitor would expect essentially the same answer.
Also compare the entity being searched, modifiers, evaluation criteria, expected page format, and likely next action.
If those remain substantially the same, one page is usually enough.
Should every service have its own page?
Not automatically.
A service deserves a page when it is genuinely offered and has enough distinct scope, demand, proof, or decision information to justify a standalone destination.
Minor variations can live under a broader service.
Should every city have its own page?
No.
Create geographic pages for legitimate markets where the company actually operates or serves customers and where the page can offer useful geographic information.
Do not create city pages simply because the city name can be attached to a keyword.
Are location pages and service-area pages the same?
No.
A location page represents a real physical business location.
A service-area page represents a market the company serves without implying a physical office.
Should I create service + city pages?
Only when the combination deserves one.
The service should have meaningful demand in that market, and the page should offer information beyond what the general service and market pages already provide.
Do not automatically multiply every service by every city.
Are industry pages useful for B2B SEO?
Yes, when industries change buyer problems, terminology, requirements, regulations, workflows, proof, or delivery.
An industry page with only the industry name swapped into generic service copy provides little value.
What is the difference between a service page and a capability page?
A service represents something the customer hires the business to provide.
A capability represents something the business knows how to do.
A capability may support several services.
Should pricing and cost be separate pages?
It depends.
Your pricing page explains how your company charges.
A cost guide explains what buyers can expect to spend and which variables affect cost.
Combine them when the answers substantially overlap.
Separate them when the tasks require different information.
Should FAQs have their own pages?
Usually only when the questions together create a useful standalone resource.
Questions directly related to a service, location, price, comparison, or process usually belong on those pages.
Is a blog post a page type?
Not really.
"Blog post" describes a publishing format.
The actual page might function as a guide, comparison, report, case study, checklist, opinion piece, or news article.
Is a landing page a page type?
Not by itself.
A landing page is any page a visitor lands on.
For SEO architecture, define whether the page is a service, industry, location, comparison, guide, or another functional type.
Is programmatic SEO a page type?
No.
Programmatic SEO is a method for producing pages at scale.
The generated pages still need a valid functional type and enough value to justify their URLs.
Should every glossary term get its own URL?
No.
Use individual glossary pages when a concept supports meaningful explanation, examples, related entities, and independent demand.
Use a consolidated glossary when definitions are short.
Does every page need a lot of text to rank?
No.
The amount of content should match the task.
A calculator may provide enormous value with little prose.
A complicated buyer guide may need thousands of words.
A location page may depend heavily on business information, imagery, staff, directions, and local proof.
Do not set word counts before understanding the task.
Do more pages create more topical authority?
Not automatically.
More pages create more inventory.
Useful topical coverage comes from answering meaningful tasks and relationships with sufficient depth while connecting those pages logically.
Ten purposeful pages can represent a subject better than 100 overlapping ones.
The Rule to Remember
Do not ask:
"What keyword can we create a page for?"
Ask:
"What job does this page need to perform that another page cannot perform as well?"
That question changes how you plan services.
It changes how you plan locations.
It changes how you use keyword research.
It changes how you handle content consolidation.
It changes how you scale programmatic SEO.
And it changes a website from a collection of keyword-targeted documents into a system where services, markets, expertise, proof, questions, and buyer decisions connect logically.
That is the point of SEO architecture.
Know the Page Type, but Not Which Ones Your Industry Needs?
The right architecture changes by business model.
A plumber may need service pages, problem pages, service-area pages, projects, cost guides, and booking paths.
A law firm may need practice-area pages, attorney profiles, office pages, case results, legal resources, and consultation pages.
A manufacturer may need product families, capabilities, materials, applications, industries, technical documentation, case studies, and RFQ pages.
A B2B consulting company may need services, industries, use cases, expert profiles, methodology, case studies, pricing resources, and buyer guides.
A software company may need product, feature, solution, integration, documentation, comparison, pricing, and use-case pages.
The correct sitemap is not a standard list.
It is a model of the business and the decisions customers make around it.
Explore Website Pages by Industry →Need Help Mapping Your Website Architecture?
The goal is not to publish every page type in this library.
The goal is to identify the smallest useful set of pages that can accurately represent:
- What you sell
- Who you serve
- Where you operate
- What problems you solve
- What you know how to do
- What buyers need to evaluate
- What proof you can provide
- What questions appear before a decision
- What deserves its own URL
Diakachimba maps search demand to services, markets, buyer tasks, capabilities, evidence, and business value before deciding what should become a page.
That creates an SEO system where every important URL has a job and every new page has a reason to exist.
