About page that ranks for your name: how to build it
An about page that ranks for your name answers one question: who is this? Sections, evidence, consistency checks and an update routine.
An about page that ranks for your name is a page on a site you own that states, in plain sentences, who you are, what you do and which facts about you can be checked, and that agrees with every other page that describes you. It ranks when it is the clearest answer to the question behind a name search, and assistants quote it for the same reason: it holds short, specific statements that need no interpretation.
Most about pages fail because they are written for no one in particular. They open with a mission or a story, and the facts a stranger needs (the full name, the field, the place, the dates, the proof) are missing or buried. The visitor who typed your name wants to know whether this is the right person and whether that person is credible. The page has a glance to say so.
This guide covers the About page itself: what it must settle, the sections that do the work, the evidence behind each claim, how it stays consistent with your other profiles and how to keep it current. Everything said about Google comes from its own documentation as read for this guide.
- Open with a two-sentence identity statement: full name, role or field, place, and one checkable fact. Everything below supports it.
- Back every claim with something a stranger can verify: a dated role, a named organization, a link to a page you do not control. Cut claims you cannot back.
- Keep one master copy of the facts and make the page, your profiles and your press mentions match it on name, role, dates and links.
- Review the page on a fixed schedule. A stale About page contradicts everything newer.
What an About page has to settle for a person, a search engine and an assistant
The page has one job: to remove doubt about who you are. A person wants reassurance that they have the right name and a reason to trust it. A search engine wants a page whose subject is unmistakable. An AI assistant wants sentences it can repeat without distorting them. A plain factual page serves all three.
Related readWikipedia notability guidelines for a personNeighboring jobs are easy to confuse with this one. Choosing which page acts as the reference for your identity sits above the About page, which is often the candidate. A professional bio is the portable text you paste into other people's pages. Markup that names your profiles is a technical layer over the visible page. An author page lists work published under your byline. Each is separate work; this guide keeps to the page that tells a stranger who you are.
What Google's own guidance says about About pages, and what it leaves unsaid
Google does not publish a template for an About page. It publishes questions about content and authorship, and the About page is the natural place to answer them.
In its guidance on creating helpful, reliable, people-first content, Google frames a self-assessment as Who, How and Why. On Who, it asks whether pages carry a byline where one might be expected and whether bylines lead to further information about the author. Among its expertise questions it mentions linking to an author page or a site's About page. It advises adding accurate authorship information and warns against deceptive authorship information.
The same page calls Why perhaps the most important question: content should be created primarily to help people. It says that trust is the most important of the quality aspects it describes, and that E-E-A-T is not itself a specific ranking factor.
Three readings follow. The About page is evidence a reader can follow from a byline or a result, so link it from every page. It should not be written to chase a score. And deception is the failure that is named: invented credentials, borrowed titles and ghost founders are what the guidance warns about. It does not say an About page raises rankings, has a required length or needs particular sections. Every structural recommendation below is practitioner judgment built to serve the reader.
Related readAuthor bio page and Person schema: what to buildThe seven blocks of a page that answers "who is this"
The reader's questions arrive in a predictable order, so a page that works follows it. Each block has a test that tells you whether it is doing its job.
| Block | What it holds | Test | Common failure |
|---|---|---|---|
| 1. Identity statement | Full name, role or field, place, one checkable fact | Quote it alone: does it still make sense? | Opens with a slogan |
| 2. Work and audience | One paragraph naming the work and for whom | Could a stranger repeat it in one breath? | Abstract nouns with no object |
| 3. Dated facts | Roles, employers, education, with years | Can each item be found on another page? | Undated claims, rounded-up titles |
| 4. Proof | Links to publications, talks, press, registers | Does each link open a page you do not control? | Links only to your own pages |
| 5. Other profiles | The profiles you run, named and linked | Same name and role on each? | Dead profiles, old titles |
| 6. Contact route | One way to reach you, chosen on purpose | Will you still answer it? | A private number or address |
| 7. Last reviewed | A visible review date | Does it match your routine? | No date, or one that never moves |
Write the identity statement first, as a reference entry and not as an introduction. "Maya Alder is a structural engineer based in Leeds who designs foot and cycle bridges for local authorities" is a statement. "Maya is passionate about building a better tomorrow" is a mood. The first can be matched against other pages, quoted by an assistant and understood in a snippet. Use your full name once, near the start.
The work paragraph needs an object: the kind of client, patient, reader or project. "Advises small manufacturers on supplier contracts" has one. "Provides strategic solutions" does not.
Dates make the page checkable and links make it verifiable. A role with a year and an employer can be confirmed on the employer's page. A talk with a conference name and a year can be confirmed on the conference's page. A claim with neither is an assertion. State the review date: it tells a visitor how far to trust the dates, and it keeps you honest about your own routine.
Evidence: which claims earn a place on the page
Every statement falls into one of three classes. A confirmed fact has a source you do not control. A claimed fact has a source only you control. An unverifiable claim has none. Keep the first in full, the second with care and the third not at all, because one mismatch makes a reader doubt the rest.
Related readVerification Badges: Do They Help Your Reputation?- List every claimCopy each sentence that states a fact: titles, dates, numbers, places, awards, affiliations, clients.
- Find the independent pageFor each claim, search for the page a stranger would find first. Note its address beside the claim.
- Compare word for wordCheck name form, title, employer and dates against that page. Where they differ, decide which is right and fix the other.
- Sort into three classesKeep confirmed claims, soften or source claimed ones, delete unverifiable ones.
- Link the proofWhere a stable confirming page exists, link to it from the claim. A link is stronger than an adjective.
Some claims are common and weak: "award-winning" with no award named, "featured in" with no publication, "trusted by thousands" with no basis, "expert" with no field. Name the thing or remove the line. Never invent a credential, a client or a quotation. Google names deceptive authorship information as a problem, and an invented line becomes a liability the day someone checks it. If a number matters, say in the sentence where it came from and which year.
Person or business: the same page with a different set of facts
The structure holds for both, but the reader's doubts differ. People ask whether you are the right person. Buyers ask whether a business is real, who stands behind it and where it is.
| Question | Person | Business | Shared rule |
|---|---|---|---|
| Who is it? | Full name, field, place | Legal and trading name, what it sells, where | One name form everywhere |
| Who stands behind it? | Dated roles and education | Named people, roles, registered entity | Only people who agree to be named |
| Is it real? | Third-party pages that mention you | Registration details, service area, customers who allow a mention | Link to pages you do not control |
| How to reach it? | One professional route | A named route for each need | A route that is monitored |
| What changes often? | Role, employer, location | Team, offer, address | Review on a fixed date |
A business page that talks only about values gives a reader nobody to check. Where a founder is comfortable being named, a role and a start date is the most useful line on the page. Where nobody wants to be named, give the registered entity rather than invent a persona. A person with a common name needs the identity statement to carry more: add the field, the place and distinctive facts such as an employer or a publication, so a reader and an assistant can tell you from your namesakes.
Keep the page consistent with everything else that describes you
An About page is only as believable as the pages that agree with it. When your professional profile, speaker listing and company page give three different titles, a reader sees three people and an assistant uses whichever it finds first. Consistency is the cheapest improvement available and it is in your hands.
Related readCrunchbase profile for a founder: claim, fix, limitsMake a master record before you edit anything: a private document with the exact name form, current role and employer with the start month and year, a one-line field description, the location you choose to share, and the profiles you vouch for. The page is cut from it, and so is every profile.
| Field | Pages that must copy the master | Typical drift |
|---|---|---|
| Name form | About page, profiles, bylines, talks | Middle initial added or dropped |
| Role and employer | About page, professional profile, company page | Old title on one profile |
| Start and end dates | About page, professional profile | Year differs by one |
| Field description | About page, directory listings | A newer phrase on one page only |
| Linked profiles | About page, each profile | Links to closed accounts |
Run the comparison at launch and at every review: open the page beside three or four main profiles, read the same field in each and fix every difference at its source. If the profile belongs to someone else, send the exact line you want and keep a record that you asked. If an outside page is wrong about you, the remedy is a correction request to its owner. Do not change the About page to match an error.
The title, heading, address and markup that frame the page
The visible text is the evidence and the framing is the hint. Give the page a plain, stable address such as an "about" path. Put your name in the title and the main heading, once each, with the field or role after it in the title. A title that reads "About" alone tells a result nothing.
Structured data is optional and secondary. Google documents ProfilePage markup as designed for sites where creators, people or organizations, share first-hand perspectives. The required property is mainEntity, the person or organization the profile is about. Recommended properties include name, alternateName, description, image, sameAs, dateCreated and dateModified. The documentation does not say the markup affects ranking, and Google does not guarantee that features built on structured data will show up in results. It also requires the page's primary focus to be a single person or organization affiliated with the site; its examples are forum profiles, news author pages and employee pages. If your About page is mainly about you as the site's owner it is a plausible fit; check the documentation before adding it.
Related readIMDb Profile Reputation: What Actors Can FixGoogle's general structured data guidelines set the limit that matters here. Markup must be a true representation of the page content, content that is not visible to readers must not be marked up, and structured data must not be used to deceive or mislead. A structured data manual action means the page loses eligibility for appearance as a rich result; Google says it does not affect how the page ranks in web search. Overreaching markup therefore does not help you and can cost you a feature.
An update routine that keeps the page true
An About page does not fail on day one. It fails in month fourteen, when you have changed roles, moved or closed an account and the page still says otherwise. The cure is a routine small enough to survive.
Use two kinds of review. A trigger review follows a real change: a new role, a published piece, a move, a closed profile. Update the master record, then the page, then each profile, within the same week. A calendar review happens on a fixed date whether or not anything changed: run the consistency comparison, check every outbound link and refresh the review date. Quarterly suits a career that moves; twice a year suits a stable one. The durations below are experience, not measurements.
| When | What you do | What usually happens |
|---|---|---|
| Day 1 to 3 | Build the master record, draft the page | You find two or three facts you cannot back |
| Week 1 | Audit claims, fix your profiles, publish | The page is live and matches your profiles |
| Weeks 2 to 4 | Request corrections on pages others control | Some are fixed; some are ignored |
| Weeks 4 to 12 | Search your name and watch the results | The page often gains ground as it is recrawled and other pages agree |
| Each quarter | Calendar review and link check | Small fixes; the review date moves |
Nothing here is certain: an accurate page is a better candidate to rank, but it competes with other pages for your name.
Six ways an About page backfires
- A story with no facts. An origin narrative with no dates, names or links is pleasant and unusable. Put the story after the facts.
- Claims that cannot be checked. One inflated line does more harm than ten honest ones.
- Private details. A home address, routine, family names or personal phone number do not belong on a public page.
- Copy-pasted text. A bio pasted from another site gives a search engine two pages saying the same thing and no reason to prefer yours.
- Profiles that disagree. The page is right and three profiles are not. Fix them, or the page looks wrong by comparison.
- A hidden page. An About page missing from the navigation and footer is hard to find for visitors and crawlers alike.
A worked scenario: a consultant with a scattered footprint (invented)
This is an invented scenario with generic details. A freelance supply-chain consultant has a one-paragraph "hello" page, a professional profile with one job title, a conference listing with another, and a directory entry that adds a middle initial. A search for the name shows the directory entry first.
Related readKnowledge panel for athletes: sources, claims, limitsThe consultant builds a master record: the name without the initial, the current title with its start year, and a one-line field description. Writing the identity statement exposes the problem, because "consultant" is too vague, so the statement now names the field and the kind of client. The claim audit removes an undated "award-winning" line, since no award can be named, and keeps three publications, each linked to the publisher's page.
The profile and the directory entry are the consultant's to edit and are fixed the same day. The conference listing belongs to the organizer, so the consultant sends the exact corrected line and keeps a copy. The About page goes live with a review date. Over the following weeks the consultant checks the name search, expecting movement but not a fixed position. The assumptions: one person, a small site, three profiles and no damaging page contending for the name. If one ranked, the About page would still help but would not be enough alone.
What to do next: one hour with your own page
Open your current About page and a blank document. Write your name form, your current role with its start date, and one sentence of field and audience. Then read the page against that sentence. If the first paragraph does not say the same thing, rewrite it. That single change fixes most of the problem.
If results for your name show the wrong page, an old title or a namesake, start with the master record and the identity statement, then build the owned page around them. Reputation Partners can review your page and the pages that describe you in a private audit and set out a sequence. See building an owned page.
Questions people ask
Should the About page be my home page?
It can be, and on a small personal site it often is. Keep a separate About page when the home page serves another purpose, such as selling a service or presenting a portfolio. What matters is that one page states who you are in plain sentences and that the main navigation links to it.
Should I write it in the first or third person?
Either works; choose one and keep it. First person reads warmer and suits an individual's site. Third person reads more formal and suits a company. Do not mix the two on one page. If you plan to reuse sentences in other bios, third person travels better, because the sentences still make sense when copied.
How long should the page be?
Long enough to carry the seven blocks and no longer. For most people that is a few hundred words plus a list of links. A short page of confirmed facts is stronger than a long page of claims, and a longer story can sit below the facts for readers who want it.
Do I need a photo?
A photo helps a reader recognize the right person, and it is not required. Use a recent, plain image with alternative text that includes your name, and the same photo across the profiles you control. The page works without one.
What if a profile ranks above my About page?
That is not a conflict. Several pages that agree reinforce one another. Make sure they agree, then let the About page serve as the longer account and the profiles as the short ones. You can still improve the page, but a profile ranking higher is no threat to it.
