Company and brand profile

A company profile is a neutral, sourced record of one organization’s identity, ownership, location, activities, leadership, official web presence, and material history. It helps a reader and a machine answer “Which organization is this?” without turning the record into advertising or a verdict.

Purpose: establish an organization as a distinct entity, make important facts easy to verify, and give consideration-stage readers a reliable route to deeper product, service, comparison, or evidence pages.

Reader question: “Is this the company I mean, what does it do, who owns it, where does it operate, and which facts can I trust?”

The core asset is a claim ledger: fact → value → source → verification date → owner → review trigger. Company facts decay silently: headquarters move, brands are acquired, leaders change, and social handles are abandoned while prose still sounds plausible.

Questions it answers

A complete profile resolves identity before it adds context:

• What are the current brand name, registered name, former names, and common aliases?
• Is the subject an independent company, parent, subsidiary, trading name, nonprofit, public body, or product brand?
• When and where was it founded, and which headquarters or registered office is current?
• What does it actually provide, to whom, and in which markets?
• Who owns or controls it, and which parent, subsidiary, or sibling relationships are material?
• Who leads it, and when was that role last verified?
• Which website, registry record, and social profiles identify the same organization?
• Which facts come from official records, first-party claims, or independent reporting?
• Which material events changed the organization, and when did they take effect?

Say when a fact is unknown, disputed, approximate, or only claimed by the organization. An explicit limitation is better than invented certainty.

When to use this post type

Use a profile when the organization itself is the search subject and readers need identification plus dependable context. It is especially useful when names collide, a brand differs from its legal entity, ownership has changed, or information is spread across registries, corporate pages, and reporting.

The reason to separate adjacent formats is editorial promise. A factual record can be maintained by verification; an evaluation needs criteria and evidence; a commercial page can advocate for its own offer.

An ownership table, criticism, or controversy does not automatically make a profile a review. The boundary is crossed when the editor translates facts into a recommendation, score, ranking, “best for” label, or unsourced reputation judgment. Either remove the verdict language or meet the stronger review standard.

Ready to Monitor Your AI Visibility?

Track how AI chatbots mention your brand across ChatGPT, Perplexity, and other platforms.

Get Started Contact

Best for these business types

The ranking reflects how often entity confusion occurs and how valuable a maintained factual record is to the audience.

1. Media publishers and affiliates . Directories and reference sites can consolidate identity and history, but independence requires visible sourcing and corrections.
2. Marketplaces . Provider profiles help users identify counterparties. Keep ratings separate from the identity record.
3. B2B services . Buyers vet legal identity, ownership, locations, leadership, credentials, and sector focus before an enquiry.
4. SaaS . Product names, corporate entities, acquisitions, and parent brands often diverge; the profile connects them without duplicating product detail.
5. Manufacturers and industrial businesses . Brand families, facilities, distributors, and acquired names need precise relationships. Never transfer a distributor’s facts to the manufacturer.
6. Agencies . Directories benefit from stable identity, offices, leadership, specialties, and ownership records; awards still need separate evidence.

Search intent

The dominant search intent is navigational plus commercial investigation. Query patterns include “[company],” “[company] profile,” “[company] owner,” “[company] headquarters,” “[company] founded,” “[company] parent company,” and “[brand] official website.” A broad name query may also carry support, employment, investment, product, or reputational intent, so one profile should orient rather than absorb every journey.

Inspect the current search engine results page before drafting. Record the knowledge panel, official domain, registry or filing results, profiles, recent news, and similarly named entities. Then inspect AI answers for identity conflation: wrong founders, old headquarters, a product treated as a corporation, or parent and subsidiary facts blended together.

Preserve a dated source for every volatile fact. Treat an unsourced knowledge-panel statement as a lead, not proof.

Stay Updated on AI Visibility Trends

Get the latest insights on AI mentions, brand monitoring, and optimization strategies.

Email address

Subscribe

Page structure

Word bands control scope rather than reward length. A simple private company may be complete at 1,600 words; a renamed group with several subsidiaries may need 3,000. Tables are often better than prose for exact identity fields.

Required elements

Each reusable element exists because profiles fail when exact facts dissolve into narrative.

Frontmatter and schema

Follow the shared frontmatter specification . For this playbook specification, use entity = "post-type-company-profile". For a published profile, the value must identify the organization, not the current headline: entity = "organization-northstar-analytics-ltd". Keep it stable through a rebrand; record former names separately.

Use schema markup only for visible, sourced facts. Organization or a valid subtype is the primary entity; Article describes the editorial profile. Organization schema needs a stable @id, canonical url, current name, supported alternateName, representative logo, and governed sameAs. Add organization relationships only when their direction is verified, and FAQPage only when it exactly matches the visible FAQ.

sameAs means “this URL identifies the same entity,” not “this page mentions the entity.” Include official registry records, verified social profiles, a canonical knowledge-base record, or another controlled public profile when the match is unambiguous. Exclude reviews, press coverage, directory category pages, distributor pages, employee accounts, old handles, campaign landing pages, and profiles of the parent unless the parent is the subject. This strictness improves entity disambiguation by preventing two organizations from being merged through loose associations.

Full example

Bracketed text is an implementation instruction and must be replaced or removed before publication.

+++
title = "[Current Brand]: Company Profile, Ownership and Facts"
seoTitle = "[Current Brand] Company Profile — Verified Facts"
entity = "organization-[stable-legal-entity-slug]"
url = "/companies/[canonical-brand-slug]/"
keywords = [ "[brand]", "[brand] company profile", "[brand] owner", "[brand] headquarters", "[brand] founded", "[brand] official website" ]
description = "[150–160 characters identifying the company, activity, ownership or location context, and the date its principal facts were verified.]"
type = "academy"
date = "[publication date and time]"
lastVerified = "[YYYY-MM-DD]"
factOwner = "[team or named editor]"
schemaTypes = [ "Organization", "Article", "FAQPage" ]

[[sameAs]]
type = "official-registry"
url = "[canonical registry record]"
verified = "[YYYY-MM-DD]"

[[sameAs]]
type = "verified-social"
url = "[canonical profile URL]"
verified = "[YYYY-MM-DD]"

[[faq]]
question = "Who owns [Current Brand]?"
answer = "[Exact visible answer with effective date and source context.]"
+++

# [Current Brand] company profile

**[Current Brand] is [organization type] based in [place] that [plain factual activity]. It is [independent/owned by parent] as of [verification date].**

Last verified: [date] · Profile owner: [name or team] · Corrections: [route]

## Company facts

| Field | Value | Source status | Verified |
|---|---|---|---|
| Current brand | [value] | Official company property | [date] |
| Registered entity | [value and identifier] | Official registry | [date] |
| Former names | [value with effective dates] | Registry or filing | [date] |
| Organization type | [public/private/nonprofit/etc.] | Registry or filing | [date] |
| Founded | [date and place, if supported] | [source class] | [date] |
| Headquarters | [operating headquarters, not assumed registered office] | [source class] | [date] |
| Parent organization | [value or independent] | Filing or transaction record | [date] |
| Official website | [canonical URL] | Direct verification | [date] |

## What [Current Brand] does
[Describe activities, customers, markets, and explicit exclusions. Attribute company claims as claims.]

## Ownership and related organizations
[State parent, subsidiary, division, and brand relationships with direction and effective dates.]

## History
- **[YYYY-MM-DD]:** [Material identity event and source.]
- **[YYYY-MM-DD]:** [Material identity event and source.]

## Official profiles
[List only governed sameAs destinations, with platform and verification date.]

## Sources and methodology
[Group registry, filing, first-party, and independent sources. Explain conflict resolution and correction handling.]

## Frequently asked questions
### Who owns [Current Brand]?
[Exact answer from frontmatter.]

[One neutral next action: inspect sources, compare an offer, or view the official site.]

If a source does not support a field, omit it or mark it “not publicly verified.” Never infer headquarters from a contact address, ownership from a logo, or founding date from a domain record.

Design gallery

The visual system should make verification easier without making the company look endorsed.

Reference-directory profile

A compact identity card, sourced fact table, name history, related entities, and correction route.

Brand and parent relationship

A mobile layout with a readable ownership chain, effective dates, official profiles, and a non-promotional activity summary.

Public or regulated organization

A filing-led layout that prioritizes identifiers, status, governance, dated leadership, and an update log.

Quality checklist

A profile passes when an editor unfamiliar with the company can trace every material identity claim.

• The H1, direct answer, canonical URL, entity ID, and schema identify the same organization.
• Current brand, legal entity, former names, aliases, and similarly named entities are distinguished.
• Every fact is labeled by source class and carries a verification date appropriate to its volatility.
• Legal identity comes from an authoritative registry or filing where available; first-party copy does not substitute for it.
• Headquarters, registered office, facilities, and markets served are not treated as interchangeable.
• Parent, subsidiary, division, and product-brand relationships have the correct direction and effective date.
• The activity summary uses plain factual language and attributes claims that cannot be independently verified.
• Leadership names and roles are current, sourced, and omitted when they add no reader value.
• Every sameAs URL represents the same organization, resolves correctly, and was manually checked.
• Criticism and material disputes are relevant, proportionate, sourced, dated, and attributed.
• The page contains no score, recommendation, ranking, or implied endorsement without review methodology.
• The freshness stamp names the last full check, owner, cadence, and event triggers.
• FAQ text exactly matches frontmatter; structured data matches visible content.
• The content refresh checklist is scheduled, and corrections have an accountable route.

Common mistakes

Rewriting the About page

An About page is self-presentation, not neutral evidence. Use it for the organization’s own description, remove slogans, and verify identity facts elsewhere.

Treating all sources as equal

A social bio cannot override a registry on legal status. Choose the source closest to each claim and document conflicts.

Blending a brand with its owner

State “Brand A is owned by Group B since [date]” rather than transferring the parent’s headquarters, leadership, revenue, or founding year to the brand.

Using sameAs as a link dump

Loose links can merge unrelated entities. Require corroborating identifiers and a live canonical URL; ordinary citations belong in sources.

Smuggling in a verdict

“Leading,” “trusted,” “innovative,” and “controversial” are conclusions unless attributed. If the job is to judge the company, use a review method.

Publishing precise but stale facts

Old facts look authoritative in tables. Precision increases the duty to show verification dates and trigger rechecks.

Hiding conflicts by overwriting

Preserve source conflicts in the research record, select supported public wording, and log material corrections.

Letting the subject control independent context

Verify proposed corrections and disclose sponsorship or approval rights. Do not remove a material, well-sourced fact because it is inconvenient.

Internal linking

The profile is an entity hub, not a site map. Every link should clarify identity or continue a reader’s specific task.

Link into the profile where readers need to identify the organization, understand a former name, or distinguish a parent from a product brand.

Link out to the official site, authoritative records, parent or subsidiary profiles, and pages that own evaluation or transaction intent. A review page owns a verdict. A product page owns capabilities and conversion. A comparison page owns a symmetric choice. The profile can summarize their relationship but should not reproduce their arguments.

Use a related content block only when two to five destinations have distinct jobs. Programmatic links must preserve relationship direction.

How to measure results

Measure whether the profile becomes a trusted identity source and routes readers accurately. Traffic alone can rise because of news, controversy, or name ambiguity.

Use prompt tracking for the organization name plus owner, headquarters, founder, official website, parent, former name, and “what does it do” variants. In source and citation intelligence , check whether AI answers cite the profile and whether extracted facts retain dates, qualifiers, and the correct entity boundary.

Apply the measurement methodology across four layers:

Open the AmICited Cockpit to compare visibility and cited pages around publication and updates. Annotate renames, acquisitions, leadership changes, migrations, schema changes, and corrections. Sample answers manually because a mention can still carry the wrong identity. Track event response time separately from routine reviews.

Frequently asked questions

What is the difference between a company profile and a review?

A company profile establishes what an organization is through sourced facts and neutral context. A review evaluates quality or fit from a stated method and reaches a verdict. If the page scores, recommends, criticizes, or ranks the company, it needs review evidence and disclosure.

Which sources should a company profile trust?

Use the source closest to each fact: an official registry for legal identity, the company’s controlled properties for current operations, regulators or filings for governed facts, and reputable independent reporting for disputed context. Never let one source stand in for every claim.

What should go in sameAs?

Include only canonical public URLs that identify the same organization, such as an official registry record or verified social profile. Do not include review pages, distributors, news articles, employee profiles, campaign pages, or similarly named organizations.

Which schema type should a company profile use?

Use Organization or the most specific valid subtype when the visible page supports it. Use Article for the editorial profile itself, BreadcrumbList when visible breadcrumbs are implemented, and FAQPage only when the marked-up questions and answers exactly match the page.

How often should a company profile be updated?

Set the cadence by volatility, not convenience. Check high-change companies quarterly and stable organizations at least annually, then trigger an immediate review after a rename, acquisition, leadership change, relocation, funding event, closure, major product shift, or broken identity URL.

Can a company edit or approve its profile?

It may submit corrections and verify first-party facts, but it should not control independent context or suppress sourced material facts. Record the request, verify the correction against the appropriate source, and disclose sponsorship or approval rights if they exist.