Coach Website Architecture Guide: Pages and Routes

This coach website architecture guide starts with what visitors need to do: understand the practice, assess a relevant service, make an appropriate enquiry or return to existing coaching. Architecture is the arrangement of pages, content and links that supports those tasks. It is not a rule that every coach needs six pages, a blog or the same booking button everywhere.

A small practice may combine several functions on one page. A practice serving individuals and organizations may need separate routes because those buyers ask different questions. The worked example below develops a complete page map, navigation, three visitor journeys and a fictional usability review, including changes that did not work initially.

Start with visitor tasks rather than a page count

A visitor's task is more concrete than “learn about my brand.” An individual may need to know whether a service includes live sessions and what it costs before making contact. An HR buyer may need to understand contracting and sponsor reporting. A current client may simply need their assigned preparation.

The GOV.UK Service Manual's user-needs guidance begins with people and what they are trying to accomplish. It was written for public services, not as a coaching sales formula. The transferable planning question is useful: what information and route does this person need to complete their task?

Write each priority task as a short sentence. Include the starting point, such as a search result, a referral or an existing invitation. Then define a satisfactory destination. “Reached the contact page” is insufficient if the visitor still does not know what they are asking about.

Keep the number of routes manageable. You do not need a separate page for every job title, every objection or every phrase someone might search. Separate pages earn their place when the audience, service or decision information materially differs. Similar pages with different headlines create maintenance work and can leave visitors unsure which one is current.

Give six functions a home, without forcing six pages

Contact details, privacy, terms and relevant accessibility information support these functions. They should be findable where they matter. The footer can provide a dependable route, while a form may need a nearby explanation of how submitted information will be used.

An evidence function does not require an empty page titled Results. An article function does not require starting a publishing operation you cannot maintain. A current-client route is a doorway into the actual service, not a reason to publish client information on the public site.

Make the homepage an orientation point

The opening should explain who you work with, the situation the service addresses and the kind of work offered. A visitor should not have to infer those facts from a slogan or scroll through a long autobiography. The coach homepage template develops the content of that opening; architecture decides where it sends people.

Offer a prominent next step suited to the visitor's stage. “Explore individual coaching” can fit someone still comparing services. A direct purchase can fit a clearly described standardized product. A scoped organizational engagement may require an enquiry rather than a generic booking.

Keep secondary routes visible. One primary action can simplify a page without making it the only possible action. Current clients should not be sent through prospect qualification, and an organizational buyer should not have to purchase an individual package to ask about a team engagement.

The homepage can summarize each service without duplicating every detail. A short overview and a descriptive link allow the service page to hold the authoritative scope. That makes later changes easier to keep consistent.

Put service information where the decision happens

A service page should answer the buyer's concrete questions: audience, purpose, format, session allowance, duration, support, price or quotation process, and the next step. State relevant limits. A polished button cannot compensate for uncertainty about whether the buyer receives a call, a course or ongoing messaging.

Separate services when the buying questions differ. Self-funded individual coaching and employer-sponsored coaching may need different explanations about agreements and information exchange. Two packages that differ only in a decorative name may be better presented as one service with clear options.

Keep one maintained source for each commercial fact. If a saved Offer is the price source, a manually typed amount elsewhere can become stale. If a service requires a quote, explain what determines the scope and how the buyer starts that conversation. Do not hide an invented fixed price behind an enquiry button.

At the transition to booking or checkout, identify what happens next. Is the visitor booking an introductory conversation, applying for a place or buying the service? The label, destination and confirmation should describe the same action.

Use about, evidence and articles to answer different questions

The About page explains relevant experience, current qualifications, approach and working boundaries. It should help a visitor understand the person delivering the work. The about-page writing guide develops that distinct writing task. A biography is not a substitute for service scope.

Evidence needs context and permission. A real client account should accurately distinguish what happened, what the client reported and what can be attributed to coaching. An altered name may not conceal a recognizable organization. If suitable permission is unavailable, a clearly fictional example can explain the process, but it cannot be presented as a customer result.

Place evidence near the question it helps answer. A description of how an engagement works may be useful beside the service explanation. A distant wall of praise can force readers to connect claims and services themselves. Do not add unapproved employer logos or imply that the coach's former employer is a coaching client.

An article hub should organize useful answers under plain topics. Give articles descriptive titles and relevant links to related explanations or services. Avoid making every article lead to the same unrelated product. If you cannot maintain the material, a few accurate resources may serve visitors better than a large outdated archive.

Keep navigation labels and destinations predictable

Use language visitors can interpret before learning your proprietary terms. “Individual coaching” and “For organizations” communicate more than “Ascend” and “Impact Circle” on their own. A service name can appear on the destination page once its purpose is clear.

W3C's explanation of consistent navigation describes keeping repeated navigation mechanisms in the same relative order. That supports predictable use, including for people with disabilities. It does not prescribe a universal maximum number of menu items.

W3C's headings and labels guidance also distinguishes descriptive wording from other accessibility requirements. Calling a heading Services does not establish that it is correctly marked up, and a descriptive label alone does not complete a form's accessibility.

Use the same label for the same destination across the site unless context needs a more specific explanation. Different links called Learn more should have enough surrounding context to identify their purpose. Keep contact, client help and legal information easy to find without making each compete equally with the main service choice.

Worked case: Mira's two-audience coaching practice

This practice, its pages, services, tests and results are fictional. Mira provides self-funded individual coaching and separately scoped work for organizations. Her current homepage mixes the two under Work with me. Its main button opens an enquiry form before visitors can see the individual service details. Client login is buried in the last paragraph of her biography.

Her individual service is three forty-five-minute sessions over six weeks for EUR 540, with no between-session messaging service included. Organizational work is quoted after a scope conversation and includes a separately agreed sponsor-information arrangement. Those are illustrative case facts, not recommended market terms.

Mira's first architecture decision is to separate the two service routes while keeping a shared About page. She has no client stories cleared for public use. She therefore uses explicitly fictional process illustrations within the service pages, creates no Results page and makes no claim that those examples are evidence of customer outcomes.

She already has four useful articles. She retains them and their existing addresses rather than creating a new article for every service phrase. The task is to make their next links relevant and organize their hub, not increase page count for its own sake.

Complete the page map and assign each page a job

The paths below are a fictional planning map, shown as text rather than links to a real practice. They are not Coachful's required URL scheme. Mira keeps her existing homepage address and existing article addresses.

This produces nine public entry or information destinations in the map, including the existing article hub, plus the separate client login. It does not mean nine pages must be newly built: existing articles and legal information remain where accurate, and the logged-in workspace already exists.

Mira owns the service facts and content approval. Her assistant, Niko, checks links and flags inconsistencies but does not invent qualifications or edit legal terms independently. A short maintenance register records the saved destination, owner, last check and trigger for review, such as a changed price or booking type.

Write the actual navigation and three routes

The primary navigation becomes Individual coaching, For organizations, About, Articles and Client login, in that order wherever repeated. Contact, Privacy, Terms and Accessibility remain in the footer. The homepage contains separate descriptive links to the two services. A contact route is also available after each service explanation.

Individual prospect: A referral visitor chooses Individual coaching, reads the three-session scope and price, then selects Book an introductory conversation. The booking introduction explains that this is a free twenty-minute conversation about fit, not one of the purchased coaching sessions. Its confirmation describes that same conversation.

Organization buyer: An HR visitor chooses For organizations, reads the scoping and information-sharing explanation, then selects Send an organization enquiry. The Contact page asks for a work contact and a short description of the proposed engagement, without requesting employees' personal coaching histories. Mira receives the contact-form submission and replies by email within her stated two-working-day window.

Current client: A returning client chooses Client login and uses the account that holds their coaching access. They then open their assigned preparation in My Coaching. If an invitation or access is missing, the public Contact page explains how to request help using the account email. It does not tell them to buy the service again.

The public service pages remain readable without signing in. The login route is clearly for existing clients. This prevents the account doorway from becoming an accidental barrier to evaluating the service.

Test a task and record the first failure

GOV.UK's moderated usability guidance describes observing participants attempting specific tasks. For a coaching site, adapt the method to relevant visitor questions rather than asking whether people like the design. The guidance is a practical research reference, not a conversion guarantee.

In the fictional first round, Mira recruits six people unfamiliar with her old site: two try the individual-service task, two the organization task and two the returning-client route. They use fictional scenarios and no real client records. She asks each to think aloud and avoids naming the button they should choose.

One individual visitor finds enough information through an old article link; the other cannot establish what the package includes. Neither organization visitor finds a distinct scoping route. One returning-client participant finds login; the other interprets Work with me as the only route. Two of six complete their assigned task independently. These are observations from six attempts, not a representative success rate for all visitors.

Mira builds the proposed map and tests its draft. The organization page initially has a copied Book a call button pointing to the individual introductory booking. One participant reaches the wrong service context. Mira corrects the button to Send an organization enquiry and checks the contact destination, rather than merely renaming the button while leaving its link unchanged.

The client-help instruction also initially says “contact us” without identifying the route. Mira adds the Contact page instruction and the information needed to locate an invitation. Niko confirms that it asks for an account email and a short access description, not a password or private coaching notes.

Recheck the revised routes and describe what improved

The same six participants repeat their assigned tasks after the corrections, and all six complete them independently. Mira records that repeat exposure may have helped them. She then asks three new participants, one per route, to attempt the revised version. All three complete their respective tasks, though the organization participant requests a clearer explanation of who receives the initial enquiry.

Mira adds that she and Niko can access submitted enquiries. Mira replies to new-service questions by email; Niko handles administrative access help under the practice's information-handling arrangements. The page asks people to omit private coaching histories. Its wording reflects the actual team audience rather than promising that only the coach can see a form response.

Her final record says: the copied booking destination was corrected; the three visitor routes were completed in this small fictional exercise; and a remaining enquiry-audience ambiguity was clarified. It does not say that the redesign increased sales, met every accessibility requirement or will work for every person.

Mira authorizes publication after those corrections. In the fictional final check, the public mobile menu opens with the stated labels, the individual and organization buttons reach their distinct destinations, and the authorized client view opens the assigned preparation. The keyboard route, headings and form labels are also reviewed, with no identified issue left open in that limited check. This is Mira's fictional record, not a claim that this article's author inspected a customer's website or performed a complete accessibility audit.

Implement the reviewed routes in Coachful

Coachful is our #1 recommendation for connecting a coach's public service information with the actual Offer and client-delivery environment. Use Simple Mode's Website or Advanced Mode's Create > Website & Pages. A public page, an Offer and a client's assigned coaching material serve different purposes; a page link does not grant every resource it describes.

1. Open the correct page. Identify the actual homepage and existing subpages. Avoid rebuilding a page simply because its label is unclear.
2. Set real destinations. Open a link or button's Link/Button dialog. Its Page tab lists enabled site pages; Funnel, Section and Custom serve different destinations. Use the appropriate saved destination.
3. Keep commercial facts connected. Where suitable, link a native Pricing card to the actual active Offer. Manually authored amounts still need their own maintenance check; a copied number is not automatically synchronized.
4. Review the right visitor state. Public information should work for a visitor without an account. Client preparation should be checked through the authorized client view and actual access rules.
5. Distinguish draft from publication. Saving changes the draft. Publish is a separate action. Publishing a subpage does not by itself replace the homepage; use the actual homepage control if that change is intended.
6. Verify after publication. Reopen the authorized public routes and check the saved links. A correct editor preview is not proof that a different public version is live.

The Your link demo earlier illustrates a compact public entry page and its editor, not the nine-page case site. It can serve as another entry route when its links lead to the appropriate service information. The My Coaching demo below illustrates the separate client preparation and next-action environment.

Maintain the map when the service changes

When Mira changes a service fact, she uses the register to find every place it appears: detail page, homepage summary, Offer, booking description and relevant article. She checks them together. An updated price on one page does not make a manually typed old amount elsewhere disappear.

Preserve useful existing addresses where possible. If an address genuinely must change, plan the old-link and redirect behavior supported by your actual setup. Do not delete an established page and assume search results, saved links or client instructions will repair themselves.

Review questions visitors actually send. Repeated confusion about whether the intro call is paid calls for clearer booking context. Repeated missing-resource messages call for an access investigation and better help instructions, not another sales button.

For a simple monthly check, choose one prospect route and the client-help route, then check service facts, broken links and the maintenance triggers. After a significant change, test every affected route. A calendar interval alone is insufficient if a service has already changed.

Troubleshoot architectural problems at their source

Every visitor reaches the same form. Check whether they need different information or service context first. Add a relevant service route, not merely another differently colored button to the same unexplained form.

Two pages compete to describe the same package. Identify one authoritative scope page and simplify or merge the overlap while preserving needed link behavior. Keep a second page only if it answers a meaningfully different question.

The mobile menu hides client access. Check the actual opened menu and destination on the intended device. A desktop link or screenshot does not establish a usable phone route.

The page promises private material. Verify the actual account and resource grant. An unlisted public URL is not an authorization system. Keep client records in the appropriate restricted environment and use a help process for access failures.

Explore Coachful's website and coaching features to match public information, saved purchases and delivery without making them interchangeable.

Frequently asked questions

How many pages does a coach need?

Enough to answer the important visitor questions and provide dependable routes. Several functions can share a page. Mira's larger map reflects two buying audiences and existing content, not a universal launch requirement.

Does every coaching website need a blog?

No. Publish useful answers if you can maintain them. Clear services, accurate information and functional contact and client routes remain valuable without a publishing schedule.

Should all buttons say Book a call?

No. Match the label and destination to the action: explore a service, enquire about an organizational engagement, book a defined conversation or purchase a specified product. Explain the commitment before the visitor acts.

Where should current clients log in?

Use a clearly labeled route to the actual workspace where their access exists. Keep access-help instructions available and avoid sending existing clients through a new purchase as a workaround.

Does a successful usability check prove the site converts?

No. Task completion identifies whether particular people could complete particular tasks in that exercise. Enquiries, purchases, accessibility and longer-term business effects require their own evidence and context.