name (Organization Name)

name · Essential · Required

What is it?

The name field is your organization's primary public-facing name. This is the name people use when talking about your company, searching for you, or referring to you in conversation. It appears in Google's Knowledge Panel header, in search result titles when your organization is referenced, and in voice assistant responses.

Use your brand name, not your legal name. Google uses "Stripe" not "Stripe, Inc." HubSpot uses "HubSpot" not "HubSpot, Inc." Subway uses "Subway" not "Doctor's Associates Inc." If your customers call you something different from what's on your incorporation papers, the schema name field should match what your customers say.

Why this matters for AEO

AI answer engines use the Organization name field as the primary identifier when matching your content to a known entity. When ChatGPT or Perplexity evaluates whether to cite your website as a source, the system checks if the publisher name in your schema resolves to a recognized entity in its knowledge base. Inconsistent naming across pages weakens this resolution. If your homepage schema says "Acme Inc." but your blog post publisher says "Acme Corporation" and your footer says "ACME," the AI engine sees three potential entities instead of one. Each inconsistency reduces the confidence score for citation.

The name field, combined with sameAs links to verified profiles, is what transforms your website from anonymous content into a known, citable source.

Who created/maintains this?

Schema.org defines name as a property inherited from the base Thing type. Every entity in the schema.org vocabulary has a name property. For Organization schema specifically, name is one of the fields Google explicitly documents in their structured data guidelines.

Google uses the name field for Knowledge Panel matching, entity disambiguation, and organization rich results. Their documentation states that name should be the organization's commonly used name.

How to find your value

Ask: "What do our customers call us?"

Choosing the right name

Scenario	Value to use
Brand name differs from legal name	Use brand name
Multiple brands under one parent	Use the brand name for the site's primary entity
Well-known abbreviation	Use full name in `name`, put abbreviation in `alternateName`
Recently rebranded	Use new name in `name`, put old name in `alternateName`
Local branch of global company	Use the branch name if distinctive, parent name if not

Real-world examples

Legal Name	Brand Name (use this in `name`)
Alphabet Inc.	Google
Meta Platforms, Inc.	Meta
Doctor's Associates Inc.	Subway
International Business Machines Corporation	IBM
Stripe, Inc.	Stripe
Block, Inc.	Block (formerly Square)

Consistency check

Before setting your name value, verify it matches across: your Google Business Profile, your LinkedIn company page name, your Wikipedia article title (if you have one), your Crunchbase profile, and the visible company name on your website homepage. If these differ, AI engines have conflicting signals. Align them all to the same string before implementing schema.

Format

Type: Text (string)

Pattern: Plain text, no HTML, no special characters unless part of the actual brand name

Length: Your actual brand name. No taglines, descriptions, or keywords appended.

Valid examples:

"Stripe"
"HubSpot"
"Ben & Jerry's"
"The New York Times"
"dYdX"
"Karpi Studio"

Invalid examples:

"Stripe, Inc."                          (legal suffix)
"HubSpot - Marketing Software"         (tagline appended)
"HUBSPOT"                               (wrong capitalization)
"Ben and Jerry's"                       (ampersand is part of the brand)

How to implement in Webflow

Static pages (homepage, about, contact)

Add JSON-LD in Page Settings > Custom Code > Inside <head> tag. The name value is hardcoded since your organization name does not change per page:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.yoursite.com/#organization",
  "name": "Your Brand Name",
  "url": "https://www.yoursite.com"
}

Place this on the homepage. Other pages reference the Organization entity through @id without redefining name.

CMS template pages (blog, case studies)

On CMS templates, the Organization name appears inside the publisher reference. If you use @id referencing (recommended), the publisher block is two lines:

"publisher": { "@id": "https://www.yoursite.com/#organization" }

The full Organization entity with name is defined once on the homepage. CMS pages point to it. No need to repeat the name on every page.

With Schema HQ

Schema HQ defines your Organization name once in the dashboard. It injects the correct value with proper @id referencing on every page of your Webflow site automatically. If you rebrand, update it in one place and every page reflects the change.

Learn more about Schema HQ →

JSON-LD Examples

Stripe (SaaS company)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://stripe.com/#organization",
  "name": "Stripe",
  "legalName": "Stripe, Inc.",
  "url": "https://stripe.com",
  "sameAs": [
    "https://twitter.com/stripe",
    "https://www.linkedin.com/company/stripe",
    "https://en.wikipedia.org/wiki/Stripe_(company)"
  ]
}

Notice: name is "Stripe" (brand), legalName is "Stripe, Inc." (registered entity). These are separate fields with separate purposes.

HubSpot (with alternateName)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.hubspot.com/#organization",
  "name": "HubSpot",
  "legalName": "HubSpot, Inc.",
  "alternateName": ["Hubspot", "Hub Spot"],
  "url": "https://www.hubspot.com"
}

alternateName captures common misspellings and alternate capitalizations that people might search for. This helps AI engines match searches for "Hubspot" (lowercase s) to the correct entity.

Karpi Studio (with @id referencing and full graph)

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "ProfessionalService",
      "@id": "https://www.karpi.studio/#organization",
      "name": "Karpi Studio",
      "legalName": "Karpis Design Studio LLC",
      "url": "https://www.karpi.studio",
      "sameAs": [
        "https://www.linkedin.com/company/76125840",
        "https://webflow.com/@karpi-studio",
        "https://clutch.co/profile/karpi-studio"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.karpi.studio/#website",
      "name": "Karpi Studio",
      "url": "https://www.karpi.studio",
      "publisher": { "@id": "https://www.karpi.studio/#organization" }
    }
  ]
}

The name field appears in both the Organization and WebSite entities. They should match. The WebSite publisher uses @id referencing to connect back to the Organization without redefining it.

Common Mistakes

❌ Including the legal suffix:

"name": "Acme Corporation, Inc."

✅ Using the brand name only:

"name": "Acme"

The legal name goes in the separate legalName field.

❌ Appending taglines or descriptions:

"name": "Acme - Leading Provider of Quality Widgets"

✅ Name only, no marketing copy:

"name": "Acme"

Taglines and descriptions have their own fields (slogan and description).

❌ Using ALL CAPS when your brand uses mixed case:

"name": "ACME CORPORATION"

✅ Matching your actual brand capitalization:

"name": "Acme Corporation"

If your brand is actually styled in all caps (like IBM or BMW), then all caps is correct. Match the real brand.

❌ Inconsistent naming across pages:

Homepage: "name": "Acme Inc."
Blog publisher: "name": "Acme"
About page: "name": "ACME Corporation"

✅ Same exact string everywhere:

Homepage: "name": "Acme"
Blog publisher: { "@id": "https://acme.com/#organization" }
About page: { "@id": "https://acme.com/#organization" }

Define once on the homepage. Reference via @id everywhere else. This guarantees consistency.

❌ Using the domain name instead of the brand:

"name": "acme.com"

✅ Using the actual brand name:

"name": "Acme"

Related Fields

legalName — The official registered name of the organization (e.g., "Stripe, Inc."). Use this alongside name when your brand name differs from your incorporation papers.
alternateName — Abbreviations, former names, common misspellings, or alternate capitalizations. IBM would have alternateName: ["International Business Machines"].
sameAs — Links to social profiles, Wikipedia, Crunchbase, and other authoritative pages that verify your entity. The name field identifies you; sameAs proves you are who you claim to be.
url — Your organization's homepage URL. Together, name and url form the minimum viable Organization entity.
disambiguatingDescription — A short phrase that distinguishes your organization from others with similar names.

Schema HQ

Schema HQ manages your name field across your entire Webflow site. Define the Organization name once in the dashboard, and Schema HQ injects the correct value with @id referencing on every page. No risk of the homepage saying "Acme" while the blog says "Acme Inc." When you rebrand, one update propagates everywhere.

Learn more about Schema HQ →

FAQ

What if my brand name contains special characters like & or accented letters?

Use the actual characters. "Ben & Jerry's" is correct, not "Ben and Jerry's." JSON-LD handles Unicode natively. Ampersands, accents, apostrophes, and non-Latin characters all work in the name field without escaping, as long as the JSON is valid UTF-8.

Should the WebSite name match the Organization name?

In most cases, yes. Google's documentation for WebSite schema recommends using your site's commonly known name, which is usually the same as your organization name. The exception is if your website has a distinct brand from the parent organization (like a product site under a holding company). In that case, the WebSite name matches the product brand.

How does Google use name for Knowledge Panel matching?

Google matches your schema name against its Knowledge Graph database to build or update your Knowledge Panel. If the name in your schema matches an existing Knowledge Graph entity (verified through sameAs links, consistent web mentions, and Wikipedia entries), Google associates your site with that entity. If no match exists, the schema name becomes a candidate for a new entity. Consistent naming across your schema, Google Business Profile, and third-party profiles accelerates this matching.

References

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

‍

"address": {  "@type": "PostalAddress",  "streetAddress": "1600 Amphitheatre Parkway",  "addressLocality": "Mountain View",  "addressRegion": "CA",  "postalCode": "94043",  "addressCountry": "US"}

Block quote

Ordered list

Item 1
Item 2
Item 3

Unordered list

Item A
Item B
Item C

Text link

Bold text

Emphasis

^Superscript

_Subscript