About Us Page SEO: Trust, Entities and Rankings

An About page almost never ranks for a competitive commercial keyword, and that isn't really its job. Its job is to answer a question search engines and human readers both ask independently of any single query: who is actually behind this website? A vague, generic, or unverifiable answer can quietly limit how much a search engine is willing to trust the rest of the domain. A specific, checkable one turns the page into one of the clearest signals of who you are as an entity, not just what you claim about yourself.

This is not a question about author bios or E-E-A-T scoring in the abstract, and it isn't a page you optimize the way you'd optimize a landing page. It's a narrower, more mechanical question: what information, structured data, and links belong on this one page, and which parts of that actually move anything. The short answer is that the page supports trust and entity resolution more than it drives direct search traffic, and the way you build it decides whether search engines can use that support at all.

What an About Page Actually Does for Rankings

For most sites, an About page has a narrow direct-ranking ceiling. It can rank for branded queries like "[company] about" or "who owns [company]," and it occasionally surfaces for "[company] founder" or "[company] headquarters" if that information sits nowhere else. It is not built to compete for a commercial head term, and trying to make it compete — stuffing it with product keywords, service lists, or the target phrase repeated in every paragraph — usually backfires, because it displaces the one thing the page is actually good for: stating who you are in a way a crawler and a reader can both verify.

The indirect effect is where the page earns its place. Search engines build an understanding of the entity that owns a domain from signals scattered across the site: the footer, the legal pages, the contact information, structured data, and the About page itself. A domain that reads as an identifiable, real organization is treated differently in aggregate quality assessment than one that reads as anonymous — particularly in categories where trust carries weight, like finance, health, or anything transactional. The About page is one of the few places a site gets to state that identity in full sentences rather than as scattered metadata.

Organization Schema: What Belongs on the Page

Structured data is how you make the "who is behind this" answer machine-readable instead of leaving it for a crawler to infer from prose. The relevant type is schema.org's Organization (or a more specific subtype like Corporation or LocalBusiness when it fits), and it can be embedded as JSON-LD directly in the About page's markup, or sitewide in the footer template — either works, but the content on the page and the markup should describe the same entity consistently.

The properties worth filling in are the ones a person would ask about while vetting you: the legal or trading name, a logo, a physical or registered address, a way to make contact, the founding date where it matters, the names of founders where that's relevant to trust, and a plain-language description of what the organization does. Aim for accuracy over completeness — a shorter, correct set of properties beats a padded one with guessed values.

Do not let the markup say something the page's visible text doesn't. If the schema claims a founding year, employee count, or address that the page itself never mentions, or that contradicts other pages on the same domain, you've created an inconsistency that is more likely to be ignored or distrusted than to help. Structured data is a machine-readable restatement of facts you're prepared to stand behind on the page, not a separate channel for claims you didn't want to write in prose.

• name, legalName, and url — the entity's identity and canonical address
• logo — a stable, absolute image URL, since this feeds knowledge panel eligibility
• address — a real, verifiable postal address, not a virtual mailbox dressed up as a headquarters
• contactPoint — a genuine channel someone can use, not a form that goes nowhere
• foundingDate and founder — when they exist and are true
• sameAs — the array of profile URLs covered in the next section

sameAs Links: Connecting the Entity Across the Web

The sameAs property answers a specific disambiguation problem: many organizations share a name, and a system trying to build an entity profile needs a way to confirm that the "Acme" on your About page is the same "Acme" with a LinkedIn company page or a Crunchbase profile. Each sameAs URL is effectively a vote that this other profile and this website describe the same real-world entity.

Not every profile is worth including, and a long list of low-value links does less than a short list of strong ones. What generally earns a place:

• A LinkedIn company page, fully filled in and actively maintained, not created and abandoned
• Crunchbase, if the organization is the kind that would plausibly be listed there (funded startups, notable acquisitions)
• A Wikidata item, but only if the organization meets Wikidata's own notability bar — you cannot create one for a small business simply because you want the sameAs link; an unqualified entry gets deleted, and a deleted or redirected link is worse than no link
• Verified social profiles that are actually maintained, not dormant accounts kept only for the URL
• Relevant industry directories or registries where the organization has a genuine, claimed listing

Two things matter more than the count of links. First, consistency: the name, logo, and description should match closely enough across these profiles that a system reconciling them doesn't have to guess whether they're the same entity. Second, upkeep: a sameAs link to a page that has moved, been deleted, or gone dormant sends a weaker signal than no link at all, because a broken cross-reference reads as neglect rather than as confirmation.

The Facts That Make the Page Verifiable

Strip out the structured data and the profile links, and what's left is the actual copy — and this is where most About pages fail, because they default to sentiment instead of fact. "We're passionate about helping businesses succeed" is not information; it's filler that could sit on any competitor's page unchanged. The version that supports trust and entity understanding states things a skeptical reader could go check.

The facts worth including, when they're genuinely true:

• The legal entity name and, where relevant to the audience, the jurisdiction it's registered in
• A real physical location — a city and country at minimum, a full address if the business has one worth publishing
• When the organization was founded, stated plainly rather than implied
• The names of actual leadership or founders, not "the Acme team," if those people are willing to be named — this is about who runs the company, distinct from bylines on individual articles
• What the organization actually does, described in the reader's terms rather than in internal jargon
• Any certifications, registrations, or memberships that are genuinely held and checkable, rather than badges nobody can verify

A useful test: could a reasonably diligent visitor cross-reference any single claim on this page against something outside your own site — a business registry, a LinkedIn profile, a filing, a real street address on a map? A page built entirely from claims that only exist on your own domain gives a search engine nothing external to anchor them against, which is exactly the position an anonymous or low-trust site is in.

Should the About Page Stand Alone, or Fold Into the Homepage?

For a small site — a solo consultant, a single-location local business, a very early-stage product — a dedicated About page can end up thinner than a short "who we are" block on the homepage itself, and a thin, orphaned page is worse than no separate page at all. If there genuinely isn't enough distinct, factual content to fill a page (founding story, team, facts, structured data) without padding it with restated marketing copy, folding the same information into a homepage section is a reasonable choice, and the Organization schema and sameAs links can live there instead.

The threshold for a standalone page is having enough real substance to earn one: a founding story with actual detail, more than one named person, or a facts section that goes beyond a sentence. Once a site has that, a dedicated page is easier to link to consistently and easier for a returning visitor or a journalist to find. The decision isn't about which choice search engines prefer in the abstract; it's about which one you can fill with real, specific content rather than restating the same sentence twice.

Linking the About Page Into the Rest of the Site

Every site should have a one-click path to the About page from the homepage — almost always through the primary navigation or the footer, since that's where a visitor or a crawler expects to find it. Beyond that baseline, a handful of additional internal links do more good than a long list of incidental ones.

Pages that carry any trust weight — pricing, checkout, a contact or support page, anything that touches payment or personal data — benefit from a link to the About page nearby, because a visitor evaluating whether to trust the transaction is asking exactly the "who is this" question the page answers. Press or media pages, and legal pages like a privacy policy or terms of service, are natural neighbors too: they're all part of the same "who is accountable here" cluster, and linking between them reinforces that they describe one coherent, identifiable organization rather than a set of disconnected templates.

Anchor text should stay ordinary — "about us," "learn more about [company]," "our team" — rather than working the target keyword into every instance. An About page doesn't need aggressive internal PageRank funneling to do its job; it needs to be reachable, consistently linked with sane anchor text, and not orphaned behind a single footer mention that a crawler might deprioritize.

Mistakes That Undercut the Page

A handful of recurring problems show up across otherwise reasonable sites, and each one weakens the exact signal the page is supposed to send.

None of these are exotic problems. They're the default outcome of writing the page once, quickly, early in a site's life, and never revisiting it as the organization becomes something with more facts worth stating.

• Stock photography paired with copy that names specific people — the mismatch is obvious to any human reader and undermines the "real organization" claim the page is trying to make
• A page built entirely from mission-statement language, with zero facts a visitor could independently verify
• No disclosed legal entity or location on a site operating in finance, health, legal, or another category where a buyer has real reason to ask who they're dealing with
• Structured data that states facts the visible page never mentions, or that contradicts what's stated elsewhere on the site
• sameAs links pointing at abandoned profiles, deleted accounts, or pages that now redirect somewhere unrelated
• Identical About page copy duplicated word-for-word across multiple country or language versions of a site, which flattens what should be locale-specific facts (address, entity name, registration) into a single templated block
• Treating the page as a place to work in the target keyword rather than a place to state who the organization actually is