Profile architecture

Choose a page structure for a multi-service practice

Choose shared and separate service pages by how much their audiences, prerequisites and handovers differ.

Reading-list saves stay in this browser. No account required.

Contents of this guide
THE SHORT ANSWER

Give services separate pages when their tasks, evidence or engagement conditions need distinct explanations. Use an overview to help visitors choose, and share background information where it genuinely applies. Keep each offer understandable on its own so direct arrivals do not need to decode the whole practice first.

Compare the offers before drawing the pages

Write a compact description of every current service, including its starting situation, client inputs, work and handover. Compare those descriptions side by side. Similar professional skills do not necessarily mean the services belong on one page. A one-time review and an ongoing advisory relationship may use the same expertise but ask the client to make different commitments. Identify where the decision questions diverge before choosing a page count or menu arrangement.

Consider audience overlap and likely reading depth. If visitors commonly compare the offers, an overview should explain the differences using consistent categories. If each service serves a substantially different task, an individual page can prevent one audience from reading through unrelated detail. Avoid splitting pages simply to make the practice look larger. A thin page that repeats the same broad promise under a different label creates maintenance work without giving the reader a clearer decision.

Separate common context from service conditions

Keep shared professional background in a stable place, such as a concise introduction or About page. Repeat a short relevant explanation when needed for a service to stand alone, but avoid copying long paragraphs across every page. Conditions specific to an offer belong with that offer: required material, review stages, availability and completion criteria. A general footer should not carry a limitation that changes what a visitor thinks a particular service includes.

Give the overview enough detail to support an initial choice. Brief descriptions can name the task and handover, then link to the full explanation. Use similar patterns for each offer so differences are easier to compare. Keep current status visible if an option is paused. Where a reader cannot identify a fit, provide a proportionate way to discuss the situation without implying that every enquiry will lead to a custom service or a guaranteed available engagement.

Check direct entry and future maintenance

Open each service page as though it were the first page a visitor sees. It should identify the practice, explain the offer and provide relevant evidence and a next step. Include an understandable route to other services without making a reader return through an animated homepage. When two pages refer to the same artifact, link to its primary explanation rather than maintaining independent descriptions that may drift apart. Check that the contact route carries useful context without requiring excessive information.

Keep a simple map of which pages advertise each offer. When scope changes, update the overview, individual page, comparison and project links together. If two services converge into the same work, consider combining their pages with a clear route from older links. If one becomes more distinct, split it only when you have enough useful content to explain that distinction. Page architecture should follow the actual practice, including the responsibilities required to maintain it over time.

ILLUSTRATIVE WORKED EXAMPLE

Fictional example: two services with different commitments

A fictional documentation specialist, Rafi, offers a report review and ongoing editorial advice. He first puts both in a single paragraph under “Support.” In the revised invented structure, a service overview contrasts a defined review handover with a recurring advisory cycle. Each has its own page because the required inputs, access pattern and completion boundaries differ.

Rafi keeps his professional biography on an About page and links to relevant examples from both offers. An independent sample is labelled consistently wherever it appears. A visitor entering directly on the advisory page can still understand its limits and find the review alternative. The example illustrates a structural choice without implying that multiple pages automatically improve visibility or that every small practice needs this arrangement.

A checklist for your next step

  • Compare tasks and handovers.
  • Identify where audiences diverge.
  • Keep offer-specific conditions nearby.
  • Test each page as an entry point.
  • Map updates across shared references.

Common questions

Can a multi-service practice use one page?

Yes, when the offers are compact and clearly distinguishable. Add pages when important explanations become difficult to scan or link to.

Should shared biography text appear on every service page?

Use a short relevant introduction where needed, with a link to fuller background. Avoid maintaining repeated long biographies.

Further reading

These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.

AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.

MOVE FROM READING TO A CLEAR NEXT STEP

Give your expertise a useful next step.

Create a private draft in this browser, review your own facts, then copy or download it. The workbench does not publish a profile, verify credentials or run an AI service.

Open the profile workbench