Present a team and its skills on a website

Show responsibilities that matter to visitors

Start with practical questions: who prepares the project, makes decisions, does the work and responds after delivery? Introduce the people or teams responsible. A small organisation can explain that one person covers several functions; it need not imitate a large organisational chart.

Describe a skill through tasks and deliverables rather than a string of keywords. A profile may explain project types, methods and limits of involvement. Link these details to relevant services so readers can understand the work in context.

• Roles linked to actual tasks.
• Contact owner identifiable.
• Skills described through observable work.

Verify names, qualifications and evidence

Have the person approve their name, role, dates and evidence. Fictional example: a colleague coordinates projects but does not develop everything alone; describe her contribution without assigning all collective work to her. Distinguish attended training, earned certification and demonstrated practice. For an external partner, explain involvement without implying employment or permanent availability that does not reflect the organization.

Do not attribute all the company’s work to one person. For collaborative projects, name contributions without misassigning results. The case-study guide explains how to connect claims with evidence and scope.

Fictional exercise: a page presents one person and their validated role in the organisation. If ProfilePage markup is considered, mainEntity identifies that Person; page and person remain separate objects. Google limits this use to a page primarily focused on a single person or organisation affiliated with the site. A grid of several members therefore does not become one person’s profile by joining all their names in one field.

Also check the meaning of links and dates. sameAs identifies the same entity unambiguously: a client’s or partner’s page is not another profile of the person. For a profile’s dateModified, Google recommends reflecting human changes to the profile information. A new annual copyright or automatically added links do not justify presenting a biography as newly reviewed. These references certify neither competence nor ranking.

• Profile approved by its subject.
• Qualifications dated and checkable.
• Individual and collective work distinguished.

Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

Choose coherent portraits with permission

Use recent photographs made in reasonably consistent conditions. Prepare sharp versions for dense screens and crops suited to cards. A generic avatar should not suggest it depicts a real person.

Agree on portrait uses with the subject and photographer. Keep the information needed to correct or remove an image. Filename and alternative text should help explain the portrait without becoming a keyword list. The photography guide helps plan the session.

• Recent and consistent portraits.
• Image use clarified.
• Alternative text suited to its purpose.

Update profiles in every language

Assign an owner and backup for team changes. Fictional example: a project lead leaves their role but remains credited in an older case study; distinguish past contribution from the current contact. Check profiles, signatures, author cards and translations. Correcting a contact does not require rewriting project history; retaining a biography must not imply current membership.

If someone no longer wishes to appear, provide a useful editorial replacement rather than an empty card. Do not keep a profile artificially to look larger. The content operations guide helps plan reviews.

• Profile owner named.
• Republished copies and translations checked.
• Departures handled promptly.