Portfolio Pages That Help Buyers Decide: What Proof Should a SME Show?

A portfolio is a decision page, not a gallery

Google Web Sifu's current portfolio index presents work with service and Malaysian location context. Its homepage also says different businesses need different content, with the goal of helping the right customer find, understand and contact the business.

Use that as a planning test for your own portfolio. A case should not depend on the visitor recognising a visual style. It should make the business situation legible: industry or application, buyer type, location, service scope and the reason the page is relevant. The page can still be beautiful, but beauty should support the decision rather than replace the explanation.

• Lead with the buyer problem or brief.
• Name the service and context in plain language.
• Give the visitor one logical route to inspect the official business or ask a question.

Show the brief before the beautiful image

The current Hup Yun case study on Google Web Sifu opens with “A transport website that makes the route easier to choose.” It explains that the structure follows routes published by the official website, including residential moves, business logistics, industrial cargo and Malaysia–Singapore transport.

The useful lesson is not to copy that transport vocabulary. It is to state the brief before showing the finish: what had to be made easier to choose, which audiences had different questions and what public source defined the service. For a hardware supplier, the brief may be product discovery; for a clinic, appointment confidence; for a professional service, the scope of a consultation. Use the client's actual published language and do not fill gaps with a flattering story.

• Brief: what decision was the page designed to support?
• Audience: which buyer or user is the page helping?
• Boundary: what does the source confirm, and what still requires an enquiry?

Make the proof inspectable

Proof can be a public service route, an accurate process explanation, a visible specification, a real location, a permitted photograph or a link to the official website. It should be possible for a careful reader to see where the statement came from. If a fact is not published, label it as an open question instead of presenting it as a project detail.

Google's structured-data guidance says markup should describe the visible content of the page and should not add information that is not visible to users. The same honesty standard belongs in a portfolio: do not let a badge, schema block or AI-generated summary imply a result that the case page does not show.

• Link to the official source or current business route.
• Separate delivered scope from a suggestion for future work.
• Keep outcome language qualified unless a primary source publishes a measured result.

Organise cases around buyer questions

Categories are useful when they help a visitor narrow the decision. Google Web Sifu's portfolio page currently exposes location groups such as Kuala Lumpur, Perak, Johor, Penang, Selangor, Negeri Sembilan, Others and Sarawak, alongside case titles that include industry or service context.

For your SME portfolio, choose groupings that match how buyers compare: service type, application, product family, business size, operating area or project constraint. Do not create a filter simply because it sounds like a keyword. Each group should lead to cases with a shared decision question, and each case should still explain its own facts rather than inheriting a generic paragraph.

• Use the category label a buyer would understand.
• Keep the case title specific enough to stand alone in a search result or shared link.
• Link related cases only when the comparison is genuinely useful.

End every case with a useful next action

A buyer who has read the proof should know what to do with it. The next action might be viewing the official business website, downloading a published document, asking for a recommendation or sending a brief. Make the destination specific and say what information will make the first conversation productive.

Google Web Sifu's public Contact Us page provides a real message form and WhatsApp enquiry route. That is a destination to verify, not a promise that every enquiry will produce a particular result. For your own portfolio, keep the CTA tied to the case: “Discuss a similar product catalogue” is more useful than a generic “Learn more”.

• Use one primary CTA and one supporting official link.
• Ask for the business problem, location, scope and timing needed to start the conversation.
• Test the link on mobile and make sure the contact route is still live.

Run a proof QA before publishing

Read the case as a cautious buyer. Can you identify the brief in the first screen? Are the service, location and audience supported by a public source? Does every image have a clear role and an honest description? Are claims separated into verified facts, editorial interpretation and questions for the client? Is the page title a helpful summary rather than a string of keywords?

Ask a second reviewer to check links, names, spelling, mobile layout and the CTA. Keep a source list with the page URL, retrieval date and excerpt used. If evidence is insufficient, block the case until the source is found. A smaller portfolio with inspectable proof is more useful than a larger portfolio built from assumptions.

Sources: Google Web Sifu's portfolio index, the Hup Yun case study, Google's people-first content guidance and Google's structured-data guidance.