How do you prioritize which owned properties to build first?
Prioritize by impact and dependency. Build the corporate site and executive LinkedIn profiles first, then Wikidata and a Wikipedia article where notability supports one (start Wikipedia early, since it is slow), then the Knowledge Panel, then second-tier platforms like Crunchbase and contributor profiles.
Prioritizing which owned properties to build first is a sequencing decision driven by impact and dependency: resources are finite, and some assets are foundations that others depend on. The principle is to build the foundation and highest-ranking assets first, and to start slow, conditional work like Wikipedia early rather than at the end.
The build order that works for most companies
- Corporate site and executive LinkedIn profiles. The corporate site is the entity home everything links back to, so it comes first. The executive LinkedIn profiles go alongside it: they rank consistently well on branded name searches, often in the top three, and are quick to strengthen.
- Wikidata and a Wikipedia article (where eligible). Add a Wikidata entry and, where the company genuinely meets notability, a Wikipedia article. We treat these as major entity-recognition sources, and Wikipedia in particular is slow to establish, so it should start early even though it pays off later.
- Knowledge Panel. The Google Knowledge Panel tends to follow once the underlying signals are strong, rather than being something you build in isolation.
- Second-tier properties. Crunchbase, contributor profiles, niche directories and similar assets round out the portfolio once the foundation is in place.
The logic is that the foundation and highest-ranking assets do the most to hold the branded result set, so they earn the early effort, while slow, conditional work is started early rather than deferred. We sequence this as a roadmap and track progress against the branded result set with IMPACT™.
Last reviewed: 20/05/2026