A useful service page helps a prospective client decide whether to approach the firm. It explains the problem the firm addresses, the work a client would receive, the conditions that affect the engagement, and the next step. Those details also give an AI assistant concrete information to use when discussing the firm.
Chapter 10 addressed whether systems can access the website. This chapter addresses what they find there. The task is to turn the firm’s approved service facts and expertise into pages that answer the questions clients ask before they are ready for a proposal.
Google’s current guidance for its generative Search features supports useful content and clear organization. It specifies neither an ideal page length nor a special writing formula for AI. The practices in this chapter are editorial recommendations for clarity and responsible marketing; their effect on visibility should be measured through the monitoring program.
11.1 Map Priority Client Questions to Useful Service Pages, Guides, and Explanations
Begin with the priority questions developed in Chapter 3 and the gaps identified through monitoring. Add recurring questions from qualified inquiries, proposal discussions, and the people who deliver the work. Use approved summaries of those conversations, with confidential and identifying details removed.
For each question, identify the decision behind it. Someone asking about an operational diagnostic may be deciding whether outside help is warranted, whether the firm understands the problem, or whether the budget covers the necessary work. These decisions need different answers even when they concern the same service.
Client decision | Suitable content | Information the page must provide |
|---|---|---|
Is this service relevant? | Core service page | Problems addressed, client circumstances, actual scope, exclusions, and responsible practice. |
What would engaging the firm involve? | Service page or engagement guide | Steps, deliverables, client responsibilities, cost drivers, timing, and acceptance process. |
Which approach should we choose? | Buying or comparison guide | Meaningful alternatives, common selection criteria, evidence, and tradeoffs. |
How should we prepare? | Readiness checklist or intake explanation | What to establish internally, what to share initially, and how further information is requested. |
Group related questions on a coherent page. A diagnostic’s purpose, deliverables, typical inputs, and implementation boundary usually belong together. Create a separate guide when a subject needs substantial explanation or addresses a materially different decision. Different wording of the same question rarely justifies another page.
Apply the same judgment to sector and location variants. A distinct regulatory context, delivery model, or client problem may warrant a separate explanation. Changing a city or industry name in otherwise identical copy contributes little to a client’s decision.
Google’s helpful-content guidance asks whether readers can accomplish their purpose, whether information adds substantive value, and whether relevant expertise is evident. Use those questions to challenge a proposed page before committing production time.
Choose the next page by the importance of the gap
Correct material inaccuracies first. Then address missing information on a priority service, followed by recurring questions that prevent suitable prospects from assessing it. A missing explanation of exclusions may deserve attention before another broad article about an industry trend.
Record why each item matters: a repeated misunderstanding in inquiries, a material omission in monitored answers, or an unresolved buying question. Distinguish those observations from assumptions about demand. A frequently tested prompt in a monitoring tool is not, by itself, evidence that clients frequently ask it.
Prefer improving an existing relevant page when it can carry the answer well. Link a supporting guide from that page and give the guide a clear route back to the service. Keep the essential explanation available without requiring a download or a sales conversation.
11.2 Explain the Problem, Scope, Approach, Deliverables, Team, and Limitations of an Engagement
Draft the engagement explanation with someone who actually scopes and delivers the work. Ask them to describe what happens after a prospect becomes a client, including the points at which work is delayed, expanded, or found unsuitable. That conversation supplies information a generic marketing description will miss.
Use the following sequence as a starting structure. Adapt it to the service rather than forcing every page into identical headings.
- Problem and fit. Identify the situation the service addresses and the circumstances in which it is appropriate. Explain material reasons the service might not fit.
- Scope and approach. Describe the work included, the stages, and the methods a client needs to understand. Define the boundaries of broad terms such as assessment, implementation, or ongoing support.
- Deliverables. Name what the client receives and what it enables them to decide or do. Examples include a findings report, an agreed financial report, or a documented assessment of options.
- Team and client responsibilities. Explain who leads and performs the work, what oversight is involved, and what access, information, approvals, or staff time the client must provide.
- Exclusions and limitations. State what requires separate work and what the engagement cannot establish or guarantee.
Distinguish the deliverable from the hoped-for outcome. A consultancy can describe a roadmap it will produce under an agreed scope. A reduction in operating costs depends on additional facts and actions. A law firm can explain the questions an assessment will examine without promising a favorable resolution.
Replace adjectives with observable details. Instead of describing an engagement as comprehensive, specify the entities, processes, reporting periods, locations, or issues it covers. Replace partner-led with an explanation of the partner’s actual role. Link to the relevant practice and professional profiles established in Chapters 8 and 9.
Accounting example
An accounting guide should distinguish services that provide different levels of assurance. The AICPA explains that a compilation provides no assurance, a review provides limited assurance, and an audit provides high but not absolute assurance. Reviews and audits require the CPA to be independent; a compilation report must disclose a lack of independence where applicable.
A guide for a business seeking financial statements for a lender should therefore begin by establishing the recipient’s requirements. Explain the proposed engagement and reporting framework, the records needed, management’s responsibilities, the report to be issued, and the firm’s acceptance assessment. Help the reader establish whether a proposed service meets the actual requirement.
Place material qualifications beside the statement they qualify for. If implementation is excluded from a diagnostic, say so in the scope explanation. If a report addresses one entity or period, keep that boundary with the report description. This improves the meaning of passages read on their own, although it cannot guarantee how an assistant will summarize them.
Supply approved evidence through relevant links and concise explanations. Detailed case-study permissions and outcome substantiation belong in Chapter 12; the service page still needs a factual owner for every material claim it makes.
11.3 Address Fees, Cost Drivers, Timing, Selection Criteria, Alternatives, and Tradeoffs
A prospect should be able to understand how the engagement is priced even when the firm cannot quote a universal fee. Explain the charging basis, the variables that change the work, and how the firm develops and agrees an estimate.
If the firm publishes a price or range, define the unit: an initial assessment, one entity, one reporting period, one site, or a specified stage of a matter. State the currency, relevant date, included work, foreseeable additional charges, and treatment of taxes and expenses. Explain whether the number is a fixed offer, a budget illustration, or an estimate subject to scoping.
Use figures the firm can substantiate. A range derived from prior engagements needs a relevant comparison group and enough context to explain exceptions. A low starting price is unhelpful when foreseeable necessary work will usually increase the total materially.
An illustrative fee explanation
“For the defined single-site diagnostic, the professional fee is USD 18,000. It covers review of the agreed operating data, six stakeholder interviews, a findings report, and a remote workshop. Implementation and additional sites require separate scopes. Any applicable taxes and approved travel expenses are additional. The proposal confirms the work, assumptions, and fee before the engagement begins.”
This invented example demonstrates the relationship between price and scope. A real page would also state the offer’s effective date and explain how additional work is authorized. Where disclosure requirements permit, a firm unable to substantiate a numeric range can explain its cost drivers and estimate process. Where price information is required, the responsible professional must establish a supportable disclosure.
For consulting, relevant drivers might include sites, process complexity, data condition, and implementation involvement. For accounting, they might include entities, reporting requirements, transaction complexity, and historical cleanup. For legal work, identify the factors relevant to the specific service and stage, such as document volume or procedural complexity. Have the responsible professional confirm which factors actually apply.
Some professional regimes require particular public disclosures. For specified services within its scope, the Solicitors Regulation Authority’s Transparency Rules require prominent website information on costs, charging basis, relevant inclusions and exclusions, stages, and likely timescales. This is an England and Wales regulatory example, not a universal rule for all legal services.
Explain what controls the timetable
Separate the earliest available start, the expected elapsed duration, and dependencies outside the firm’s control. A four-week assignment beginning after receipt of usable records is different from a promise to finish four weeks after an inquiry.
Describe the principal stages and what the client must supply for each. Explain whether estimates depend on access to decision makers, records, inspections, third parties, or court schedules. Publish response and delivery commitments only when the responsible team can support them.
Help clients compare proposals on the same basis. Suggest questions about scope, team involvement, client effort, deliverables, acceptance conditions, and additional work. A lower fee may cover less work; a broader engagement may be unnecessary for the decision the client needs to make. Explain the circumstances in which a narrower engagement, an internal team, or another specialist could be appropriate.
11.4 Develop Clear FAQs, Checklists, Buying Guides, and Evidence-Based Comparisons
Choose the format according to the reader’s task. A short recurring question may need an FAQ. A readiness task may need a checklist. A choice involving several credible options may need a guide or comparison. Avoid producing several formats that repeat the same promotional claims.
FAQs that resolve real uncertainty
Use questions that the practice actually receives: Does the diagnostic include implementation? What happens if our records need cleanup? Is the initial conversation charged? Who will carry out the work? What happens if the firm cannot accept the engagement?
Answer the question directly, then explain the conditions and relevant next step. Replace “It depends; contact us” with the factors that determine the answer. Put the FAQ alongside the service it explains, and make its statements consistent with the main scope and fee sections.
FAQs should earn their place through usefulness. Google discontinued FAQ rich results from 7 May 2026 and subsequently removed the feature’s documentation. A firm’s FAQ text can still serve readers; publishing it should not be presented as a way to obtain that discontinued search display.
Checklists and buying guides
A readiness checklist should help someone establish what they know and what remains unresolved. An accounting checklist might ask the reader to identify the intended recipient, reporting period, required service, state of the records, and decision deadline. Distinguish information to assemble internally from information appropriate to submit to the firm.
A buying guide should explain how to judge the options. Include questions a client can ask every candidate, what a useful answer would contain, and tradeoffs that could change the decision. Define technical terms at the point they affect the choice.
For a consulting diagnostic, an illustrative comparison might look like this. The actual merits depend on the organization’s capabilities and the work proposed.
Option | Potential fit | Tradeoff to examine |
|---|---|---|
Internal assessment | The team has the relevant expertise, capacity, and access. | Internal knowledge is valuable; test whether the team has time and authority to challenge existing assumptions. |
External diagnostic | The organization needs an outside assessment before deciding on changes. | Adds external expertise and cost; confirm what happens after recommendations are delivered. |
Implementation engagement | The problem and required changes are sufficiently defined. | Provides execution capacity; confirm whether diagnosis, design, and ongoing support are actually included. |
Make comparisons defensible
If a guide compares named firms, disclose who publishes it and the publisher’s commercial interest. Use consistent criteria, dated primary sources, and equivalent scopes. Mark information that is not publicly stated as unknown. Give a competitor appropriate credit where the evidence supports it, and correct the table when the facts change.
Avoid unsupported rankings and claims about competitors’ competence or fees. The ABA Model Rules provide an illustration: the commentary to Rule 7.1 addresses misleading omissions, unjustified expectations, and unsubstantiated comparisons. The Model Rules are models for jurisdictional rules; a law firm must apply the requirements governing its lawyers and communications.
Review the implication of the whole page. A technically accurate row can still contribute to an unfair comparison if the categories were chosen solely to make the publisher appear superior. A useful guide should explain when an alternative would serve the client’s needs.
11.5 State Relevant Dates, Jurisdictions, Assumptions, and the Boundaries of General Information
Professional information often depends on facts that are easy to omit from a short answer. A rule may apply in one jurisdiction, a reporting requirement to one period, or an engineering recommendation to one set of site conditions. Include the context necessary to interpret the statement correctly.
For each substantive page, establish its intended audience, geographic or professional scope, relevant period, material assumptions, and reviewer. Put these details where they matter. A tax explanation needs the applicable tax period; a legal explanation needs the relevant jurisdiction; an engineering guide may need the code edition and the conditions under which the discussion applies.
Separate the date of the underlying rule or event from the page’s publication, substantive update, and professional review. Google’s byline-date guidance distinguishes publication and significant updates from the events discussed on a page and calls for consistent visible and structured date information.
A professional review can confirm that existing content remains accurate without implying it has been rewritten. Record that review honestly. Google’s helpful-content guidance specifically cautions against changing dates merely to make unchanged content appear fresh.
Keep general explanations within their stated scope
Explain what the page can help the reader understand and what requires an assessment of their circumstances. A legal guide can describe issues to discuss with counsel; it should not imply that reading a short checklist establishes the merits of a particular claim. An engineering explanation can describe an assessment process without declaring a reader’s structure safe.
Keep the qualification close to the claim. A broad footer disclaimer does not repair an inaccurate sentence or supply facts missing from a fee estimate. Avoid compressing a conditional statement into an unconditional headline merely to make it easier to quote.
Give the page a named owner and specific review triggers. Changes to scope, fee policy, personnel, regulation, reporting requirements, or intake procedures should prompt review of the affected passages and related pages. If material guidance can no longer be supported, correct it or withdraw it from active use while the responsible professional reviews it.
Apply the same controls to AI-assisted drafting. Provide approved facts and sources, require uncertainty to be flagged, and have the expert check the substantive answer. A fluent draft is not evidence that the service, rule, price, or professional qualification is accurate.
11.6 Explain Next Steps, Who to Contact, and What Information Is Appropriate to Share
The next step should match the decision the page helps the reader make. Someone exploring an unfamiliar service may need an engagement guide. Someone who understands the fit may be ready to request an initial conversation. Use a specific action label, such as “Discuss a diagnostic” or “Request an initial matter assessment.”
Explain who receives the inquiry, what happens next, whether the initial stage is charged, and what the firm needs to establish before proposing or accepting work. Keep the description consistent with the operating team’s actual process.
Request information in stages
Begin with the minimum information needed for the firm’s initial review. Depending on the service, this may include contact details, the broad problem, relevant location, intended timing, and other information approved for that stage. Tell the prospect when and how further documents will be requested.
A consulting prospect can describe an inventory problem before sending detailed operating data. An accounting prospect can identify entities and reporting needs before supplying financial records. A law firm should design its initial information request around its conflicts and suitability process, with instructions at the point of submission.
The ABA commentary to Model Rule 1.18 explains that duties relating to a prospective client’s information can arise even when representation does not follow. Whether a communication constitutes consultation depends on the circumstances, and initial consultation should be limited to information reasonably necessary to consider the matter. A signed engagement letter is therefore not a safe universal dividing line for all duties.
Have the responsible lawyer approve the actual form, warnings, handling of information, and follow-up process under applicable rules. Do not assume that a generic website disclaimer resolves these issues. A sensitive document upload, if needed, should use an approved channel with an appropriate request and access controls.
State how urgent situations should be handled. If the intake channel is not monitored for deadlines or emergencies, make that limitation clear where the prospect contacts the firm. Any response-time statement needs a responsible owner and a process for absences and delays.
Test the entire route before publication, including the form, confirmation, routing, and reply. Check that an assistant or a prospect following the page’s instructions reaches the intended team and receives a response consistent with the published description.
Practical Output: A Prioritized Content Plan and Detailed Page Briefs
Start with the pages most consequential to the firm’s priority services. The following sequence is a working default; adapt it to observed client needs, material risks, and the availability of approved information.
Priority | Work to commission | Evidence of completion |
|---|---|---|
1 | Correct material errors and complete the main service explanation. | Scope, fit, exclusions, commercial process, and next step have responsible approval. |
2 | Resolve recurring uncertainty through page improvements or a focused engagement guide. | The identified client questions have clear, supported answers. |
3 | Add a comparison, readiness checklist, or distinct specialist explanation. | The new material helps a decision not adequately served by existing pages. |
For every item, record the audience, decision, observed gap, intended URL, whether to create or revise, priority, subject expert, editor, approver, and due date. Add the source material, dependencies, review triggers, and acceptance criteria. Use the delivery ownership established in Chapter 7.
For the first production batch, select one to three important pages from your own firm’s services. Complete a plan entry and a detailed brief for each. Assign owners and due dates for factual approval and publication, and identify the changes that will trigger review.
Illustrative plan entry: A consultancy whose inquiries repeatedly confuse diagnosis with implementation could prioritize revising its diagnostic page. The practice lead would approve the scope and deliverables in week one; the editor would publish the revision in week two. Completion requires a reader to understand where the diagnostic ends and how any implementation work is scoped.
Each brief should contain a proposed core answer, the questions the page must resolve, the engagement details to verify, the commercial explanation, relevant context, supporting links, and the intended next step. The following three independent examples demonstrate how to make that brief concrete.
Consulting brief
Page: Operational diagnostic for distribution businesses. Reader and decision: An operations leader deciding whether to commission an assessment before committing to an implementation program.
Core answer to develop: “The diagnostic examines the agreed order-to-delivery processes, identifies likely causes of delay, and produces a prioritized improvement roadmap. Systems implementation and ongoing change management require separate scopes.”
Required content: Define the sites and processes considered, interview and data requirements, stages, findings report, workshop, and client responsibilities. Explain who performs the analysis and how recommendations are prioritized. Address what the work can establish when records are incomplete and what further investigation may be needed.
Commercial explanation and next step: Describe how sites, complexity, data condition, travel, and stakeholder access affect fees and timing. Request a high-level description of the operating problem and desired decision date through the designated inquiry route.
Inputs and acceptance: The practice lead supplies the actual methodology, approved scope, fee policy, and relevant evidence links. The page passes when a reader can distinguish the diagnostic from implementation and identify the inputs needed to scope it.
Accounting brief
Page: Choosing a financial-statement engagement for a lender’s requirements. Reader and decision: A business owner or finance leader establishing which service to discuss with a CPA firm.
Core answer to develop: “Start by establishing the intended recipient’s reporting requirements. This guide explains the services the firm offers, the work involved, and the information needed to assess an engagement.”
Required content: Explain compilation, review, and audit at an appropriate level, consistent with Section 11.2. Identify intended users, reporting periods and frameworks, relevant independence considerations, management’s responsibilities, and the report associated with each service. Explain the firm’s actual acceptance process. Avoid implying that any service automatically satisfies every lender.
Commercial explanation and next step: Describe how entities, record quality, reporting needs, and deadlines affect scoping. Distinguish preparatory cleanup from the proposed engagement. Request a high-level description of the requirement, with supporting records provided through the approved process.
Inputs and acceptance: The responsible accounting professional verifies the service descriptions against applicable standards and the firm’s capabilities. The page passes when a reader understands that the services provide different assurance and knows what requirements to establish before proceeding.
Law firm brief
Page: Requesting an initial assessment of a commercial contract dispute. Reader and decision: A business representative considering whether to approach the firm about a matter within its actual practice and jurisdiction.
Core answer to develop: “The first step is to establish whether the firm can consider the matter. The intake team will explain the information required for that review and the process for requesting any further assessment.”
Required content: Identify matters considered, jurisdictional scope, preliminary screening, and what an assessment would cover if undertaken. Explain the distinction between initial contact, any paid assessment, and further representation. State how the firm handles requests involving deadlines and when additional documents should be supplied.
Commercial explanation and next step: Clarify whether initial contact is charged and how a later assessment’s scope and fee are agreed. Route the inquiry to the approved intake team, requesting only the information authorized for that stage.
Inputs and acceptance: The practice and intake leads approve service facts and workflow; the responsible lawyer reviews professional obligations and wording. The page passes when a reader understands the next step without assuming the firm has accepted representation or promised a result.
Review the pages before expanding the plan
Give each completed page to a colleague unfamiliar with the service. Ask them to explain the intended client, work included, main exclusions, cost and timing dependencies, and next step. Revise where their account differs materially from the firm’s approved description.
An AI summary can provide another diagnostic. Supply the page text through an approved tool and ask it to use only that material to explain fit, scope, exclusions, cost and timing dependencies, and the next step. Ask it to mark missing information as “not stated” and identify supporting passages. Check every material statement yourself. A successful summary in that test does not establish wider visibility. After publication, use the existing monitoring program to track factual accuracy and relevant consideration, and review inquiry quality with the receiving team.
Complete the first pages, resolve misunderstandings, and assign ongoing ownership before expanding production. The content plan should leave the firm with useful, maintained explanations of work it can actually perform.