Entity SEO for ecommerce: the Wikipedia-shaped opportunity

Google does not really rank keywords anymore. It ranks entities and their relationships, and it happens to present the results to users in response to keyword queries. That shift started with the 2012 Knowledge Graph launch and completed around 2018-2020 when semantic search became the default. By 2026, entity SEO is not a niche discipline. It is the discipline.

For DTC ecommerce brands, entity SEO is a specific kind of work: making sure your brand is recognized as an entity in Google's knowledge graph, that the entity has the correct attributes, and that the graph of relationships around your entity reflects reality. This is the pattern library for how I do that work on DTC engagements.

What entity SEO actually means

An entity, in Google's usage, is a person, place, thing, or concept that exists independently of any particular web page. A brand is an entity. A product category is an entity. A founder is an entity. The Knowledge Graph is Google's internal representation of these entities and the relationships between them.

When a user searches for a query, Google tries to understand which entities the query is about and returns results that match those entities. A query like "sheets under $300" is about the Product entity type "sheets," filtered by price. Google knows which sites sell sheets as entities, not which sites have "sheets" in their metadata.

The implication for SEO is that a brand recognized as an entity with specific attributes (product category, price range, sustainability profile, geographic focus) shows up for queries matching those attributes even without explicit keyword targeting on the page. The brand is the target of the query, not the page.

The entity graph

Google builds its knowledge graph from multiple sources. For a DTC brand, five sources carry most of the signal.

Wikipedia. The entity-graph gold standard. A brand with a Wikipedia page gets treated as an established entity. The barrier to getting a Wikipedia page is high and deliberate: notability criteria, independent sources, neutral point of view.

Wikidata. The structured-data sibling to Wikipedia. Every Wikipedia page has a corresponding Wikidata entry with structured attributes. Wikidata entries without Wikipedia pages are possible and useful. Easier to set up than Wikipedia.

Google Business Profile. Formerly Google My Business. The brand's profile in Google's merchant and local listings. Required for any brand that wants to show up in the Knowledge Panel sidebar.

LinkedIn Company Page. A structured data source Google pulls from. Consistency between the LinkedIn page and other entity sources matters.

Schema.org Organization or Brand markup on the homepage. The brand's self-description in structured form. This is the one the brand controls directly.

The entity is defined by the agreement across these sources. When the attributes disagree (different founding year on LinkedIn vs. Wikipedia, different product categories on GBP vs. schema), Google weighs the sources and picks an interpretation. When they agree, the entity is stable.

Pattern 1: Organization schema on the homepage

The first move is shipping Organization schema on your homepage. This is the schema block that tells Google who the brand is in structured form.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Brand",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "description": "Example Brand makes linen bedding from Belgian flax.",
  "foundingDate": "2019",
  "sameAs": [
    "https://www.linkedin.com/company/example-brand",
    "https://www.wikidata.org/entity/Q12345",
    "https://twitter.com/examplebrand"
  ]
}

The sameAs array is load-bearing. It tells Google which external entity references refer to the same brand. If you have a Wikidata entry, link it here. If you have a Wikipedia page, link that. The array should include every authoritative external profile.

Pattern 2: a Wikidata entry

Wikidata entries are easier to set up than Wikipedia pages. The notability bar is lower, the structure is machine-readable, and once the entry exists, it feeds directly into Google's Knowledge Graph.

Creating a Wikidata entry manually is possible but slow. For most DTC brands I recommend the following approach: ensure your brand has enough external coverage (press mentions, independent references) that a Wikidata entry is supportable, then either submit the entry yourself or hire a Wikidata editor to do it.

The entry should include:

• Official name and known aliases
• Founding year
• Country of origin
• Industry classification
• Official website
• Social media handles
• Founder (linked to founder's Wikidata entry if they have one)
• Parent company (if any)

Each of these properties is a structured claim that Google can use to disambiguate the entity.

Pattern 3: Google Business Profile consistency

A brand's Google Business Profile (GBP) is what populates the Knowledge Panel in the SERP. The fields that matter most for a DTC brand:

• Name exactly matching the legal name used elsewhere
• Category chosen precisely from Google's taxonomy
• Primary website URL matching the homepage exactly (with or without www, consistent)
• Description matching the Organization schema description
• Logo and branded images matching the homepage

Inconsistency across these fields creates entity disambiguation noise. Google does not always pick the worst version; sometimes it picks a random version, which leaves the Knowledge Panel showing something unflattering or outdated.

Pattern 4: founder as a linked entity

For founder-led DTC brands, the founder is a separate entity that is related to the brand entity. Google's graph can model this relationship explicitly.

The founder should have:

• Their own Person schema on an About page or author page
• A LinkedIn profile consistent with the brand's LinkedIn page
• Optionally a Wikidata entry for the founder
• Reciprocal sameAs references between the founder's entity and the brand's entity

This is especially important for brands where the founder is publicly associated with the brand. Google's rankings for brand queries often surface both the brand entity and the founder entity, and consistent graph data across the two improves both.

Pattern 5: product category entity anchoring

Beyond the brand entity, DTC brands benefit from anchoring their product categories as entities. A bedding brand that wants to rank for "linen sheets" should make sure its catalog is machine-readable as an instance of the "linen bedding" category, not just a collection of pages with that keyword in the title.

Shopify's structured data for product categorization, combined with clean collection hierarchy, handles most of this. For more specific entity anchoring, you can add additionalType fields in Product schema pointing to specific Schema.org or Wikidata entity references.

What Wikipedia gets you that nothing else does

A Wikipedia page is the strongest entity-SEO asset a brand can have, and it is also the hardest to get.

The notability bar is specific. Wikipedia requires multiple independent reliable sources that cover the brand substantially. Press releases do not count. A single product review does not count. Substantial coverage from established media outlets over time counts.

For DTC brands, getting to Wikipedia-worthy notability usually requires either reaching significant revenue scale (typically $50M+), winning major industry awards, or developing a product or founder story that gets genuine long-form editorial coverage. It is not something you can shortcut with PR spend.

If you are not yet at that bar, do not fake it. A promotional Wikipedia page that violates notability guidelines gets deleted and can damage the brand's entity graph. The right sequence is: build the underlying notability, then accept the Wikipedia page when it happens naturally (or work with an editor who follows the rules).

The audit I run

Four steps.

1. Check the current Knowledge Panel. Search the brand name in an incognito window. Note what Google currently shows. Flag any attributes that are wrong.
2. Audit the Organization schema on the homepage. Fix missing fields, especially sameAs.
3. Audit external profiles (LinkedIn, GBP, Wikidata if any). Check that name, description, founding year, and website match across all sources.
4. Identify the entity gaps. If no Wikidata entry exists, evaluate whether the brand is notable enough. If GBP is missing, set it up. If the founder is publicly associated but has no Person schema or LinkedIn, fix.

The goal is a consistent, complete entity graph across all the sources Google reads.

Where this fits

Entity SEO underpins the rest of the programmatic SEO work. The cluster hub frames the full program. Schema markup for DTC product pages covers the Product-level schema that complements the brand-level Organization schema. E-E-A-T signals small brands can control covers the trust signals that feed the entity graph.

If you want an entity audit as part of a broader technical SEO review, the DTC stack audit includes it. Full product ladder is at /products.

Sources and further reading

• Schema.org Organization and Brand vocabularies
• Wikidata notability criteria and data model
• Google Knowledge Graph API documentation