Website proof is the work, records, credentials, or genuine customer statements that support a specific service claim. Before asking a visitor to book, explain what you do and who it is for, then show relevant support in a readable order; a redesign should make those answers easier to judge, not merely change the colors.
Mike Mangione, founder of The Mangione Group, explains his team's diagnostic rule:
The finding determines the first fix. If important pages can’t be accessed or indexed, we investigate that first. If they’re accessible but leave buyers unclear about the service, we improve the explanation. If the claims lack support, we strengthen the evidence with relevant work, credentials, and specific examples.
This describes the team's practice, not a promise of indexing, rankings, inquiries, or future results.
This guide helps you decide what belongs on a service page, what evidence to collect, and how to give that evidence a readable place in the design. It does not promise that a particular layout will increase inquiries. Its purpose is to make the page more useful to someone deciding whether your business deserves a conversation.
Key Facts at a Glance
- Mike Mangione's rule separates access failures, unclear service explanations, and unsupported claims before choosing the first repair.
- An example of completed work supports a claim about that work, not every possible future customer outcome.
- A credential should identify the person or organization that holds it and the work to which it applies.
- A customer quotation should remain faithful to its source and include any material context needed to understand it.
- An attractive illustration is not evidence that the depicted meeting, customer, or result actually occurred.
- W3C's headings guidance explains that heading structure communicates organization and supports navigation.
- A page review should end with a specific correction and a way to check it, not a general instruction to make the site look more premium.
Mike Mangione brings 18 years of marketing expertise to the question of what a business should explain before asking for a response. His contribution here is a diagnostic rule for deciding which problem deserves attention first, rather than treating every weak page as a request for a new visual style.
What should you fix before changing the visual design?
Start with the first unresolved obstacle between the visitor and an informed decision. Check that the essential page is available, that it explains the service clearly, and that its important claims have support. The right first change depends on which check fails; a new color palette cannot supply missing service information or evidence.
Google states that following its guidance does not guarantee a site will be added to its index. Treat access and indexing checks as technical work with observable states, not as a benefit you can promise merely by redesigning a page. Google SEO Starter Guide
For this review, use an explicit stop rule: if a visitor cannot open the service page or complete its intended action, record that failure before judging the photography. If the page works, ask someone unfamiliar with the company to identify the service, intended customer, and next step. Any missing answer becomes a named content problem. If the answers are clear, match each material claim to evidence.
This is a working review sequence, not a universal scientific threshold. Several repairs can happen together. A broken form need not delay collecting an approved project example, and a technical review need not prevent a writer from clarifying a confusing sentence.
The practical point is to stop replacing the entire website when a narrower problem has been identified. Conversely, do not restrict a project to copy edits when the template cannot display ordinary text and evidence clearly. Write down what is failing and choose the smallest scope that can actually correct it.
What must the page explain about the service?
The page should explain the work you do, the customer or situation it suits, the important boundaries, and what happens after an inquiry. Use words a prospective customer would recognize without a sales presentation. A reader should not have to infer the service from a slogan, an industry photograph, or a broad promise of growth.
Suppose an imaginary accounting firm leads with “Financial clarity for ambitious businesses.” That may describe an aspiration, but it leaves the work open to interpretation. Does the firm handle bookkeeping, tax preparation, outsourced finance leadership, or investment advice? Which service is the page asking someone to discuss?
An illustrative rewrite might say, “Monthly bookkeeping and management reports for owner-led service businesses.” A following sentence can explain who supplies the records and what the monthly package includes. This is an invented writing example, not a client result or a claim that the second version converts better.
Use the same discipline for boundaries. If the service does not include payroll, do not force buyers to discover that after booking. If an assessment comes before a fixed proposal, explain the sequence. Clear limits can be presented calmly without turning the first screen into contract language.
Consider the questions salespeople repeatedly answer after an inquiry. Select those needed to decide whether to begin, then place more detailed implementation questions farther down. A headline can name the service; a short paragraph can define its scope; a comparison table can distinguish packages where real differences exist.
Do not mistake brevity for removing information the buyer needs. “We handle it” is short, but the reader still has to ask what “it” includes. The page is concise when it answers the question directly with little waste, even if that answer needs a sentence rather than a two-word label.
Our guide to lead generation website design addresses the broader path from service explanation to inquiry. The narrower job here is to make sure the evidence on that path supports a clear, specific offer.
Before commissioning new visuals, write the service in a plain sentence. Give it to the designer together with the actual scope. That sentence becomes a useful constraint: the design must not make the service harder to understand than it is in the brief.
How do you choose evidence that supports the claim?
Choose evidence by the question the claim creates. A statement about workmanship needs relevant work; a statement about qualifications needs a current credential; a numerical outcome needs records and context. Do not substitute a more impressive-looking item when it proves something different from the claim the visitor is being asked to believe.
Build a two-column list before designing the proof section. Put the proposed statement on the left and the strongest available support on the right. An empty right column is a content decision, not a request for an icon.
| Proposed claim | Potentially relevant support | What it still does not establish |
|---|---|---|
| We have completed this type of project | Approved example with scope and the firm's actual role | That every project will have the same result |
| A named specialist will handle the work | Current role, relevant credential, and agreed involvement | That an unrelated credential qualifies the entire company |
| The service follows a defined review process | Real checklist or process explanation with responsibilities | That a promised review has occurred on a specific future job |
| A campaign produced a stated outcome | Defined outcome, period, source records, and appropriate attribution | Guaranteed future performance |
| Clients find the team responsive | Authentic, contextual feedback about communication | Technical quality or financial return by itself |
This table is an editorial matching exercise. It is not a hierarchy in which every numerical case is stronger than every work sample. The right item depends on what the customer is assessing.
The FTC's advertising guidance requires claims to be truthful, nondeceptive, and supported by evidence. That is a reason to review the substance before presenting a statement in a large typeface; typography does not narrow an overly broad claim. FTC Advertising and Marketing Basics
A digital marketing agency might show a campaign sample to demonstrate how it writes. That sample is useful for judging the work itself. It becomes misleading if the surrounding layout implies that the sample independently proves sales growth that has not been documented.
If suitable evidence is unavailable, narrow the statement, gather support, or remove it. You can still explain a proposed method and show clearly labeled illustrative work. Be explicit about what the example is. Avoid quietly moving from “this is how the work could look” to “this is what happened for a customer.”

What belongs in a readable project example?
A readable project example identifies the situation, the work performed, and the supported outcome without requiring the visitor to decode a dense story. Put the most relevant conclusion first, then give enough context to judge it. Keep the firm's role, timeframe, source, and important limits visible near any prominent result.
Begin with the buyer question. Someone choosing a commercial photographer may need to see how a product looks under difficult lighting. A buyer choosing an intake service may need to understand how completed files are checked. A before-and-after website image can show a layout change, but it cannot on its own establish what caused a change in revenue.
An effective project panel can use a direct heading, one approved image, and three short blocks: the problem, what the team did, and what the records show. A deeper case page can carry the full method, supporting documentation, and limitations. The summary must remain accurate without requiring a click to discover a qualification that changes its meaning.
Distinguish a completed deliverable from a business outcome. “Rebuilt the appointment form” is a deliverable. “Received more qualified inquiries” is an outcome requiring a definition and evidence. “The new form caused the increase” is a stronger causal claim requiring more than a before-and-after comparison.
Do not crop a chart so tightly that its scale, measurement period, or source disappears. W3C's guidance for complex images calls for text equivalents that convey essential information, and recommends making fuller descriptions available where needed. Keep the interpretation and source readable as ordinary page content. W3C complex images tutorial
When you have several examples, choose different reasons to believe rather than repeating the same type of project in different colors. One might show the scope of work, another a relevant constraint, and another a carefully documented outcome. State those differences in the headings so the visitor can select the example that matters.
Permission belongs in the production process. Confirm what may be shown, redact unrelated private details, and save the approved version. An attractive mockup does not create permission to publish the underlying customer material. If only an anonymous version is approved, preserve enough context to make it useful without making the person or business identifiable through incidental details.
How should credentials and testimonials be presented?
Present credentials as evidence about the person, organization, or capability they actually cover. Present testimonials as a customer's account with its meaning and material context intact. Neither needs a wall of badges or quotations. A smaller number of relevant, readable items can answer a specific buyer question more directly than an undifferentiated collection.
A professional credential should be named correctly, assigned to its holder, and current where current status matters. An award should retain its category and year. A team's previous work should not become a claim that the present company performed every historical engagement. Clear attribution can be concise and still tell the reader what happened.
Ask what concern each item addresses. A certification may help establish specialist training. It may not tell a buyer whether the provider has handled a project of similar size. A quotation about friendly communication may answer a service concern while leaving technical capability unresolved.
Choose the quotation for relevance, then design around its actual length. Do not cut away a qualification because the card looks neater without it. If an excerpt is used, confirm that it preserves the original meaning and that any required disclosure remains noticeable.
The FTC explains that endorsements describing specific results can imply that others should expect those results; merely adding a general “results vary” disclaimer does not necessarily resolve that implication. Review the actual statement and presentation before treating an exceptional testimonial as a universal promise. FTC endorsement guidance
For a new business without a large testimonial library, the solution is not to fill the gap with invented praise. Show the people doing the work, accurate qualifications, permitted examples, and a concrete explanation of the process. Describe proposed work as proposed work.
A marketing company should be able to explain why an evidence item belongs on the page. “Competitors have this badge strip” is not a sufficient reason. Ask which claim the strip supports and whether a reader can verify the relationship without guessing.
Set a review owner and a review date for credentials and endorsements. When the team, permission, service, or supporting record changes, the page may need to change too. Keep source files and approval notes outside the public page so the design remains clean without losing accountability.
What should the photographs actually demonstrate?
Choose photographs that either show relevant real work or help the reader understand the service setting, and keep that distinction honest. A documentary image can support a statement about what it depicts. A staged or generated image can illustrate an idea, but it should not be presented as a customer, employee, completed project, or measured result.
An office photograph can establish atmosphere. It cannot demonstrate that a firm has a particular number of staff members, occupies that location, or has served the people in the image unless those facts are true. If the image is illustrative, the surrounding words and placement should not suggest a documentary claim.
When work is visual, choose an angle that shows the relevant quality. A contractor's wide room shot may show the finished space, while a separate close view shows the joinery the copy discusses. Each should have a job in the page, rather than appearing because there is an empty box in the layout.
For less visual services, consider a permitted sample deliverable, a clearly explained process diagram, or a real team photograph with accurate identity. Do not reveal customer data to make an image feel authentic. A simulated document must be labeled as illustrative if its contents could otherwise be mistaken for actual work or a result.
Keep important service explanations in real text rather than baking them into a photo. W3C distinguishes informative images, which need text alternatives conveying their essential content, from purely decorative images, which can use empty alternatives. The description should reflect the actual purpose and scene, not a list of keywords. W3C images tutorial
Review the crop where the image will appear. A face or useful detail may disappear when a wide desktop photo becomes a narrow phone panel. A good source image is not enough if the delivered crop removes what the text asks the reader to notice.
For this website, each photograph has one distinct visible placement. Responsive sizes of that same placement are delivery variants, not new photographs. That is our production rule, not a claim that search engines require unique photos in every component. The wider principle is simple: select and prepare the image for the meaning it must carry in that exact position.

How do you give the page a clear reading order?
Give each section one question to answer, a heading that states its purpose, and a visible relationship between the claim and its supporting material. The order should remain understandable when photographs, columns, and decorative effects are removed. Visual emphasis then helps the reader follow the argument instead of creating several competing starting points.
Sketch the page as a sequence of decisions: Is this the service I need? Does it suit my situation? Why should I consider this provider? What is involved? What happens if I inquire? The sequence can change with the offer, but each section should earn its position.
Give the answer a clear place before adding decorative labels. If the heading says only “Possibilities,” the visitor still has to read the paragraph to identify the topic. “What the monthly service includes” creates a more direct route to the information.
W3C explains that headings communicate page organization and can support in-page navigation through browsers and assistive technologies. Use actual heading elements, with a logical hierarchy, rather than making arbitrary text look like headings through size alone. W3C headings tutorial
Use space to group related material and separate different decisions. A case result and its qualification should remain close enough to read together. A new service section needs a clearer break. There is no universal padding value that makes every page readable; assess the relationships at the actual font size and screen width.
Multi-column layouts need a second check. W3C's meaningful-sequence guidance requires a programmatically determinable reading order where sequence affects meaning. A visual arrangement can look convincing while its underlying content order separates a claim from the explanation needed to understand it. W3C meaningful sequence
Give the main booking action a recognizable shape and enough space around it. Its prominence should not make the proof tiny or hide basic service information. If the page offers several actions, distinguish their purposes in plain language rather than giving every link identical emphasis.
Before approving the design, read only the headings in order. Then read only the opening sentence of each section. Both passes should describe a coherent service and decision. This is an editorial check, not evidence that every visitor will read that way.
What needs to change on a small screen?
The order and meaning should stay intact on a small screen, while columns, spacing, images, and controls adapt to the available width. Do not preserve a desktop composition by shrinking ordinary text until it is difficult to read. Check the full route from the first claim through the evidence and into the inquiry form.
Start with the actual published page, not only a design file. Long service names, real quotations, and genuine image crops expose problems that short placeholder text hides. Test more than one narrow width and enlarge text as part of the review.
W3C's reflow guidance addresses presenting content without loss of information or functionality and without unnecessary two-directional scrolling, with exceptions for content that genuinely needs a two-dimensional layout. A responsive screenshot alone does not establish that the full page meets that requirement. W3C reflow guidance
Keep the relationship between a claim and its evidence when columns stack. If a desktop row places the claim on the left and its project example on the right, the phone version should not insert unrelated material between them. Read the stacked sequence as a new composition.
Check text contrast on the actual backgrounds. WCAG's minimum text-contrast criterion specifies 4.5:1 for ordinary text, with a 3:1 threshold for qualifying large text and defined exceptions. These are accessibility criteria, not conversion targets or a complete accessibility audit. W3C contrast guidance
Forms deserve the same care as the hero. W3C's forms guidance describes associating labels with controls so people can identify each input's purpose. Make names, instructions, required fields, and errors understandable without relying only on visual position. W3C form-label guidance
If the design uses movement, give people control over nonessential interaction-triggered animation and respect reduced-motion preferences. W3C addresses that behavior in its animation-from-interactions guidance. A stylish reveal should not be necessary to access the only copy of the service explanation. W3C animation guidance
The accessible marketing website guide explores these implementation checks more broadly. Here the question is whether your evidence remains readable and usable when the visitor is not looking at the desktop view you approved.
How do you test whether people understand the page?
Ask likely users to complete realistic tasks and describe what they understand without coaching them toward the answer. Observe where they look, what they misinterpret, and whether they can explain the service and next step. Treat the findings as evidence about those sessions, not as a precise forecast of conversion or market demand.
A useful task is, “You are deciding whether this service fits your business. Find what is included and what you would do next.” A less useful task tells the participant to click the exact button you are trying to test. You learn whether instructions can be followed rather than whether the page supplies them.
The GOV.UK Service Manual recommends relevant, believable tasks that have a clear goal without giving away the answer, and recruiting actual or likely users. That provides a practical basis for a structured page review; it does not make a small review representative of every future visitor. GOV.UK moderated usability testing
Record observations in concrete terms. “Could not find whether installation was included” is more useful than “did not like the layout.” “Thought the photographed team worked for the company” may expose an inaccurate implication from illustrative photography. “Read the result but missed the timeframe” suggests a presentation problem that can be corrected and checked.
Separate taste from comprehension. A participant can dislike a color while correctly understanding the service. Another may love the visual design while misreading the offer. Both observations matter, but they answer different questions and should not be collapsed into a single approval score.
Use a simple record for each session:
- The participant's relevant situation, without unnecessary personal data.
- The task as asked, using the same neutral wording where comparison matters.
- What the person understood about the service and evidence.
- The first obstacle or misleading interpretation.
- The specific revision to test next.
Do not claim a percentage improvement from a handful of informal sessions. Report what happened, correct clear problems, and test the revised version. If you want to measure changes in qualified inquiries, define those outcomes separately and account for traffic, offer, follow-up, and other changes.
A digital marketing company should distinguish “people could find the scope after the change” from “the redesign will produce more customers.” The first can be observed in a usability task. The second requires commercial evidence and cannot be established by aesthetic approval.

How do you turn the review into a useful design brief?
Turn each finding into a named problem, a proposed correction, an owner, and a completion check. Preserve the parts of the page that already work. The brief should explain which customer question the change answers and what evidence belongs beside it, so the designer is solving an identified problem rather than guessing what “better” means.
Use the worksheet below to choose the first review priority. It follows Mike's sequence of access, explanation, and support, with an additional usability check for delivering those answers. It is a planning aid created for this article. It does not score the quality of your company or predict how many inquiries a redesign will produce.
| Check | Mark unresolved when | First action |
|---|---|---|
| Access and action | An essential page or intended inquiry route fails | Record the failure and have the responsible person investigate |
| Service explanation | A new reader cannot identify the work, fit, or next step | Rewrite the specific missing answer |
| Claim support | A material claim has no relevant, approved evidence | Gather support, narrow the claim, or remove it |
| Presentation | Required information exists but is hard to read or operate | Correct hierarchy, crop, spacing, contrast, or control behavior |
Choose unresolved checks and the worksheet returns the first priority in that order. It also keeps the other unresolved items visible. It does not tell you to ignore them. If none is selected, it says to verify the page with likely users rather than announcing that the website is perfect.
For example, suppose the page opens and the form works, but buyers cannot tell whether a service includes ongoing support. The worksheet returns service explanation even if you also dislike the hero image. An initial correction could add the actual support scope and place it near the relevant package. A later task can improve the photo once its purpose is clear.
A useful brief might read: “Visitors cannot tell whether monthly review meetings are included. The service includes one meeting each month. Add that fact to the package section, show the actual meeting agenda if approved, and check whether a new reader can find it without assistance.” Those are illustrative service terms, not a description of a TMG package.
Include evidence ownership in the handoff. Name who approves the project description, who can confirm a credential, who supplies the image, and who verifies the final page. Avoid asking the designer to infer commercial claims from a folder of unexplained assets.
Our design services and website services connect the message, visual presentation, and functional page. A strong brief lets those disciplines work on the same buyer question instead of producing separate pieces that look polished but do not add up.
Frequently asked questions
Choose page changes by the question the buyer cannot yet answer, then use evidence you are permitted to show. A relevant work sample, current credential, or carefully scoped example may be enough for that question. More badges, a full redesign, and longer testimonials are not automatic substitutes for clear service information.
Do we need a complete redesign if the website is not generating inquiries?
Not necessarily. First check whether people can reach the right page, understand the service, find relevant support, and complete the inquiry route. A specific failure may call for a focused repair. A broader redesign is justified when the existing structure or implementation prevents the required corrections, not simply because inquiries are disappointing.
Look at the source and quality of visits and the follow-up process as well. A page is one part of the buying path. Do not assume a visual change will solve an offer, audience, availability, or sales-response problem.
Can we use a customer logo instead of writing a project example?
A permitted customer logo can identify a relationship, but it does not explain what work you performed or what happened. Add enough context for the reader to understand the relationship accurately. If a specific capability or result is the claim, use support that addresses that claim rather than expecting the logo to prove it.
Confirm permission and avoid implying endorsement beyond what was approved. A short scope statement may be more useful than making the logo larger. Where a relationship is confidential, choose another relevant evidence item.
What if we cannot publish our clients' names or results?
Use only the detail you are authorized to share, and do not describe an anonymous case so specifically that the client becomes identifiable anyway. You may be able to show a permitted work sample, explain a genuine process, or present accurate qualifications. Clearly distinguish illustrative examples from actual customer work and supported outcomes.
Anonymity is not permission to invent missing records. If the outcome cannot be substantiated, leave it out. Explain the service directly and show what can be shared honestly.
Should every page have a testimonial and a case study?
No fixed combination fits every service page. Select evidence according to the question the reader is deciding and the claim you are making. A relevant work sample may answer one concern better than a testimonial, while an accurate credential may answer another. Repeating unrelated proof creates volume without necessarily improving the explanation.
The test is whether the item adds support the visitor can understand. If two sections do the same job, consider keeping the stronger one and giving it a clearer presentation.
How do we make a page feel premium without making it hard to read?
Use disciplined typography, deliberate spacing, high-quality relevant images, and a restrained hierarchy that makes the important information easy to find. Keep ordinary copy readable and make the main action unmistakable. A premium impression should come from the care of the presentation, not from hiding useful detail behind tiny text or unexplained labels.
Review the actual page on small screens and with enlarged text. Preserve the message when animation is reduced. The visual style succeeds only if the visitor can still understand and use the service page.
When is a marketing review the right next step?
A marketing review is useful when you know the page is not making the business clear but cannot yet separate a message problem from an evidence or design problem. Bring the real service, the current page, and the support you are allowed to show. The first decision should be what needs fixing, not which template to buy.
The Mangione Group can review the page's explanation, the claims it asks people to believe, and the way the design presents both. We can identify missing information, recommend relevant evidence, and connect the copy and visual work to a clear inquiry route.
If your current page needs a focused repair, that should be considered before a broader rebuild. If the service itself is still changing, or nobody can verify the proposed claims, those issues need attention before the design can present them confidently.
We cannot manufacture a customer result, guarantee that a redesign will produce a particular number of inquiries, or make an unsupported claim true by giving it more visual emphasis. We can help you decide what to say, what supports it, and how to make it easier to understand.
Book My Marketing Review to discuss the page, the evidence available, and the most useful next change.
References and sources
- SEO Starter Guide, Google Search Central. Live documentation; checked October 20, 2026.
- Advertising and Marketing Basics, Federal Trade Commission. Live guidance; checked October 20, 2026.
- FTC's Endorsement Guides: What People Are Asking, Federal Trade Commission. June 2023; checked October 20, 2026.
- Headings, W3C Web Accessibility Initiative. May 4, 2017; checked October 20, 2026.
- Understanding Meaningful Sequence, W3C Web Accessibility Initiative. September 16, 2025; checked October 20, 2026.
- Images Tutorial, W3C Web Accessibility Initiative. April 8, 2026; checked October 20, 2026.
- Complex Images, W3C Web Accessibility Initiative. Live tutorial; checked October 20, 2026.
- Understanding Reflow, W3C Web Accessibility Initiative. Live guidance; checked October 20, 2026.
- Understanding Contrast (Minimum), W3C Web Accessibility Initiative. Live guidance; checked October 20, 2026.
- Labeling Controls, W3C Web Accessibility Initiative. Live tutorial; checked October 20, 2026.
- Understanding Animation from Interactions, W3C Web Accessibility Initiative. Live guidance; checked October 20, 2026.
- Using moderated usability testing, GOV.UK Service Manual. Live guidance; checked October 20, 2026.

