IDENTITY
Who is speaking?
Name, role, organisation, expertise and verifiable references should make the party behind the website recognisable.
Guides
What a business website should contain for people, Google and AI
An effective business website is not a collection of mandatory pages. It is an information system that explains who is speaking, what they offer, who it is for, what evidence they provide and how to take the next step.
The short answer
It should make identity, offer, audience, process, conditions, evidence, answers, contact details and relevant legal information visible. This content needs clear pathways, consistency with structured data and ongoing maintenance. There is no universal number of pages, words, images or articles.
Gian Luca Partengo
Web developer since 1995 · Updated
What should a business website explain immediately?
Four questions come before page counts and keywords. If the website cannot answer them, the rest of its architecture starts from weak foundations.
OFFER
What is being offered?
Services and products need results, scope, process and conditions—not slogans alone.
AUDIENCE
Who is it useful for?
Visitors should recognise the problem, context or need that the offer addresses.
NEXT STEP
What can someone do now?
Contact, purchase, booking or further reading need a clear priority and realistic expectations.
How should content architecture be organised?
Architecture turns people’s questions into pathways. It does not depend on a fixed three-click rule, but on clear relationships between information.
Initial orientation
The homepage introduces identity, value and main pathways without trying to hold every detail.
An offer worth exploring
Each service or product area leads to enough information to understand its purpose, limits and next step.
Verifiable identity
About, company, team or professional pages show who takes responsibility for the claims made.
Evidence in context
Work, case studies, testimonials and data connect to the claims they support instead of acting as decorative numbers.
Answers and insights
FAQs, guides and information pages resolve real questions and support decisions that need more context.
Contacts and conditions
Channels, availability, service area, timings and legal information reduce ambiguity before contact.
Menus, internal links, breadcrumbs and hub pages make these relationships navigable. The number of levels follows the content, not a universal formula.
What should the homepage say?
The homepage does not need to tell the whole story. It should establish the right context and direct people to the information that completes their decision.
CONTEXT
A recognisable business and audience
The headline, opening copy and visual signals should explain what the business does and for whom, avoiding interchangeable claims.
VALUE
An understandable promise
The benefit should be concrete and consistent with what later pages can actually demonstrate.
PATHWAY
Well-ordered primary choices
Services, products, insights and contact options need readable hierarchy instead of competing at the same intensity.
EVIDENCE
A reason to continue
Method, work, expertise or distinctive elements give the promise substance and lead to complete evidence.
The practical rule
A homepage works when it provides orientation. If it replaces every internal page, it becomes overloaded; if it contains only a slogan, it makes visitors guess.
To distinguish information architecture from conversion, also read why a website is not generating leads.
What should service or product pages explain?
A credible commercial page lets people evaluate an offer before contacting the business. Hiding every detail does not automatically make a service more exclusive.
Expected outcome
The problem the offer addresses and the concrete change it can reasonably produce.
Scope
What is included, what remains outside and which variables can change timing, work or price.
Process
Stages, responsibilities, required materials and decision points make the journey understandable.
Conditions
Prerequisites, availability, location, delivery, support and limitations prevent false expectations.
Selection criteria
Differences between options and situations where the service fits support an informed decision.
Next step
The request should explain what follows: response, assessment, quotation, appointment or purchase.
Why do identity and an About page matter?
People and systems need to connect claims, expertise and responsibility to a recognisable party.
ENTITY
Consistent business identity
Business name, location, references and relevant details should not conflict across the website, documents and official profiles.
PEOPLE
Roles and expertise
Authors, owners and professionals should be presented when that helps assess experience and reliability.
HISTORY
A journey without empty autobiography
Experience, specialisation and methodological choices matter when they explain why the offer is built that way.
PRESENCE
Verifiable references
Professional profiles, registers, locations and official channels reinforce identity when they are authentic and current.
Not every architecture needs a page literally called About. The information that serves this purpose must still be findable and consistent.
What evidence makes a business website credible?
Evidence is useful when it can be connected to a claim. Logos, stars and numbers without context can look like decoration rather than proof.
Completed work
Portfolios and results show the type of work, its context and the contribution actually delivered.
Documented cases
Problem, constraints, decisions and outcome distinguish a useful case study from a gallery item.
Attributable testimonials
Reviews and quotes are more credible when their source, date and relationship are understandable.
Scoped data
Numbers and percentages should state period, sample, method or conditions so they can be interpreted.
Observable method
Explaining how the work is done makes expertise, responsibility and differences from a generic offer verifiable.
Declared limits
Saying what is not guaranteed or included strengthens trust more than an absolute promise.
Evidence before persuasion
Commercial content can persuade, but it should not distort evidence. One outcome does not become a universal guarantee.
Do you need FAQs, guides or a blog?
You need answers to questions that influence understanding and choice. The format depends on depth, update frequency and intent.
QUESTIONS
Recurring doubts
Short FAQs work when each answer is self-contained, direct and does not hide essential conditions.
OBJECTIONS
Risks and concerns
Timing, cost, compatibility and responsibility deserve explicit content rather than vague reassurance.
COMPARISON
Alternatives and criteria
A guide can explain differences and trade-offs without turning every alternative into a target.
SUPPORT
Information after the decision
Instructions, assistance and documentation reduce repeated questions and make the service clearer over time.
What should the contact area contain?
Contact is more than a form. It should explain the channel, context, timing and consequences of submitting a request.
CHANNELS
Available methods
Email, telephone, form, appointment and location should appear only when they are genuinely monitored.
SCOPE
Area and availability
Location, languages, hours and accepted request types prevent contacts that do not fit the service.
TIMING
Response expectations
Realistic timing is more useful than an instant promise the organisation cannot sustain.
OUTCOME
What happens next
Confirmation, assessment, required documents and subsequent steps should be clear before submission.
For security, accessibility and request delivery, also read how a website contact form should work.
What legal and privacy information is required?
It depends on the business, audience, processing, contracts and applicable law. An editorial checklist cannot replace legal assessment.
IDENTITY
Business details
Information required from a professional or business should be accurate, findable and consistent with the activity described.
DATA
Relevant privacy information
Purposes, grounds, recipients, retention and rights should reflect the website’s real processing and connected workflows.
TERMS
Conditions where necessary
Sales, bookings, subscriptions and services may need specific conditions rather than a copied standard text.
CONTEXT
Obligations proportionate to the case
Industry, country, users and functions change the scope: no single page is universally valid for every website.
Words and behaviour must agree
Policies and terms should describe what the website and organisation actually do. A footer link does not correct a tool configured differently.
Cookies and consent depend on the tools actually loaded: read the guide to a cookieless website and cookie banners.
How do you make content understandable to Google and AI systems?
You do not need to write for machines instead of people. You need to make entities, relationships, answers and sources explicit in an accessible, consistent document.
Visible text
Essential information should exist in HTML and remain readable without depending on images or fragile interactions.
Recognisable entities
Consistent names, roles, organisations, services and places help establish who and what the page is about.
Author and responsibility
Where relevant, attribution and profiles explain who produced the content and what experience supports it.
Sources in context
Primary links and verifiable references support technical, legal and numerical claims.
Consistent structured data
Schema describes visible content; it should not invent reviews, authors, services or information absent from the page.
Meaningful dates and updates
A date matters when it reflects a substantive review. Changing it without updating the content does not create quality.
Explore citability in the guide to appearing on ChatGPT and AI searchand keep it separate from the technical problems covered by why a website does not appear on Google.
How should website content be maintained?
Editorial quality is also a process. Prices, people, services and laws change: every critical item needs an owner and a reason to be reviewed.
OWNER
A person or role
Someone must be able to approve, correct or remove every critical area of the website.
EVENT
Update when reality changes
New services, people, locations, terms, tools or laws should trigger a focused review.
CHECK
Scheduled reviews
Contacts, links, prices, dates, case studies and policies deserve checks proportionate to how often they change.
CLEAN-UP
Correct or archive
Outdated content should not remain simply because it exists. It can be updated, consolidated, redirected or removed deliberately.
Who provides, organises and approves the content?
A professional project assigns responsibilities before launch. Content design does not automatically include writing every piece of copy.
THE GLP METHOD
Verifiable content, explicit responsibilities
I organise structure, hierarchy, requirements and connections so that information appears in the most useful place and format. I check consistency, completeness and compatibility with the technical architecture.
The client remains the responsible source for data, promises, prices, qualifications, terms and materials about their business. Complete editorial production, where needed, is defined and quoted as a separate service.
- The content scope is agreed before development.
- Sources and sensitive claims must be identifiable.
- Materials and approvals have defined owners and deadlines.
- Visible text, metadata and structured data must remain consistent.
- Post-launch changes follow a verifiable process.
- No ranking, citation or commercial result is guaranteed.
Checklist: the essential business website inventory
This is not a list of mandatory pages. It checks whether the chosen architecture makes essential information findable and understandable.
-
01
Identity
Who the party is, where they operate, who speaks and how to verify them.
-
02
Audience and need
Who the offer is for and which problem it addresses.
-
03
Offer and scope
Outcomes, inclusions, exclusions, conditions and selection criteria.
-
04
Process
Stages, materials, responsibilities, timing and decision points.
-
05
Evidence
Work, cases, testimonials, data and limitations connected to claims.
-
06
Answers
FAQs and insights built around real questions, not publishing volume.
-
07
Contact
Monitored channels, availability, timing and what follows submission.
-
08
Legal information
Identity, privacy and terms consistent with the real business and tools.
-
09
Authors and sources
Attribution, expertise and references for claims that require support.
-
10
Technical consistency
Copy, titles, descriptions, links and structured data describe the same reality.
-
11
Responsibility
Who provides, approves, publishes and updates every critical item.
-
12
Review
Events and schedules for correcting, consolidating or archiving content.
Verified primary sources
Official documentation used to distinguish technical requirements, editorial practices and general legal principles.
-
Google Search Central — Creating helpful, reliable contentOpen source
People-first principles, questions about who, how and why content was produced, and no universal preferred word count.
-
Google Search Central — SEO Starter GuideOpen source
Logical organisation, readable copy, unique content and information kept up to date.
-
Google Search Central — Developer guideOpen source
Visible text, semantic HTML and descriptive metadata that make pages understandable to Search.
-
Google Search Central — Structured data guidelinesOpen source
Structured data should represent visible content and remain truthful, relevant and current.
-
Google Search Central — Organization structured dataOpen source
Properties that describe an organisation’s identity, contact details and references where they appear on the page.
-
W3C WAI — Writing for Web AccessibilityOpen source
Informative headings, clear language, understandable instructions and content organised for accessible reading.
-
W3C WAI — Page structure and headingsOpen source
Heading hierarchies that organise sections and relationships without losing the page’s meaning.
-
OpenAI — Publishers and developers FAQOpen source
Official information about discovery, citations, crawler controls and the relationship between public content and ChatGPT products.
Sources checked on 28 September 2026. Legal requirements, technical documentation and system behaviour can change and should be verified in the project’s real context.
Frequently asked questions about business website content
Direct answers that avoid rigid checklists and distinguish completeness, quantity and responsibility.
Which pages are mandatory on a business website?
There is no universal list for every business. Information about identity, offer, contact and relevant obligations is needed; whether it appears across a homepage, services, About, contact, policies or other pages depends on the project and applicable law.
Is an About page always necessary?
Its function matters when identity, expertise and responsibility influence trust. It can be a standalone page or part of other pages, provided the information is findable, verifiable and consistent.
Does a business website need a blog?
No. A blog is useful when there are questions worth exploring, expertise to document and resources to maintain it. Generic or abandoned content does not automatically improve SEO, authority or conversion.
How long should website copy be?
Long enough to answer the page’s intent clearly. Google says it has no preferred word count. Cutting essential detail or adding words to hit a threshold produces worse content.
Does every page need images and video?
No. They help when they explain, demonstrate or orient. Heavy or irrelevant decoration can instead slow the page and distract from its main content.
Can structured data replace visible text?
No. It should describe real information consistent with the page. Adding services, reviews, authors or facts to schema when they are absent from visible content creates a misleading representation.
How do you write a website that is also useful to AI?
Make entities, relationships, answers, sources and dates explicit in readable HTML. There is no need to fill the copy with AI-oriented formulas: clarity, attribution and verifiability help people and systems.
Who should write the website content?
The client is the responsible source for information about their business. A professional can design structure, requirements and organisation; complete copywriting, when requested, should be defined as a service with clear ownership and approvals.
How often should website content be updated?
Whenever the reality described changes and according to checks proportionate to volatility. Contact details and terms may need frequent checks; history and method less often. Dates should not change without a substantive review.
Does a content checklist guarantee visibility or leads?
No. It creates a clearer, more verifiable foundation, but organic and commercial outcomes also depend on demand, competition, reputation, distribution, user experience and the quality of the whole project.
Next step
Do you want to turn scattered information into a clear business website?
On the websites I build, content, hierarchy, navigation, metadata and structured data are designed as parts of one system. Editorial scope and responsibilities are defined before development begins.