Property talk:P4264

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

LinkedIn company or organization ID
identifier for an official company, school, organisation page, or showcase page, on LinkedIn

Represents	LinkedIn company or organization profile (Q125207805)
Applicable "stated in" value	LinkedIn (Q213660)
Data type	External identifier
Domain	According to this template: companies and other organisations According to statements in the property: organization (Q43229), metropolitan area (Q1907114), website (Q35127), project (Q170584), service (Q7406919), real property (Q10494269), sports venue (Q1076486), brand (Q431289) or manufacturer (Q13235160) When possible, data should only be stored as statements
Allowed values	[a-z\d][a-z\d-]+[a-z\d]
Example	British Airways (Q8766) → british-airways LinkedIn (Q213660) → linkedin Brazilian Red Cross (Q47072433) → cruzvermelhabrasileira
Source	https://www.linkedin.com/
External links	Use in sister projects: [ar] • [az] • [bn] • [de] • [en] • [es] • [fa] • [fr] • [he] • [hi] • [it] • [ja] • [ka] • [kn] • [ko] • [ml] • [mr] • [nl] • [pl] • [pt] • [ro] • [ru] • [sv] • [te] • [tr] • [uk] • [ur] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Formatter URL	https://www.linkedin.com/company/$1/
Tracking: usage	Category:Pages using Wikidata property P4264 (Q43543158)
Related to country	United States (Q30) (See 835 others)
See also	LinkedIn personal profile ID (P6634), LinkedIn numeric company ID (P14756)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Items with deprecated claims Deprecated statements with this identifier as a source Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P4264 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 52,042 Main statement 50,333 96.7% of uses Qualifier 491 0.9% of uses Reference 1,218 2.3% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#single best value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#Unique value, SPARQL (every item), SPARQL (by value)

Format “[\p{Ll}0-9&_'.\-，]+”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#Format, SPARQL

Type “organization (Q43229), metropolitan area (Q1907114), website (Q35127), project (Q170584), service (Q7406919), real property (Q10494269), sports venue (Q1076486), brand (Q431289), manufacturer (Q13235160)”: item must contain property “instance of (P31)” with classes “organization (Q43229), metropolitan area (Q1907114), website (Q35127), project (Q170584), service (Q7406919), real property (Q10494269), sports venue (Q1076486), brand (Q431289), manufacturer (Q13235160)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Port of Baltimore (Q377595), Dulaney Valley Memorial Gardens (Q5313294), 2022 French Presidency of the Council of the European Union (Q110014438)
List of violations of this constraint: Database reports/Constraint violations/P4264#Type Q43229, Q1907114, Q35127, Q170584, Q7406919, Q10494269, Q1076486, Q431289, Q13235160, SPARQL

Format “[^\s/]+”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#Format, SPARQL

Scope is as main value (Q54828448), as reference (Q54828450), as qualifier (Q54828449): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P4264#Scope, hourly updated report, SPARQL

Conflicts with “website account on (P553): LinkedIn (Q213660)”: this property must not be used with the listed properties and values. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#Conflicts with P553, search, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#Entity types

Qualifiers “website username or ID (P554), language of work or name (P407), start time (P580), end time (P582), end cause (P1534), has characteristic (P1552), does not have characteristic (P6477), online access status (P6954), number of subscribers (P3744), point in time (P585), subject named as (P1810), statement is subject of (P805), archive URL (P1065), archive date (P2960), reason for deprecated rank (P2241), reason for preferred rank (P7452), retrieved (P813), applies to jurisdiction (P1001), LinkedIn numeric company ID (P14756)”: this property should be used only with the listed qualifiers. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P4264#allowed qualifiers, SPARQL

This property is being used by:

• he:תבנית:פרופילי אישים, he:תבנית:פרופילים ברשתות חברתיות
• n:ru:Шаблон:Оформление категории
• en:Template:LinkedIn page
• uk:Шаблон:У соціальних мережах
• b:ru:Шаблон:Оформление категории
• n:bg:Шаблон:Оформяне на категория
• ca:Plantilla:Xarxes, ca:Plantilla:Identificadors
• ja:Template:LinkedIn page
• el:Πρότυπο:Κουτί πληροφοριών Ομοσπονδίας Ποδοσφαίρου, el:Πρότυπο:Κουτί πληροφοριών εθνικής ποδοσφαιρικής ομάδας, el:Πρότυπο:Κουτί πληροφοριών περιοδικού, el:Πρότυπο:Κουτί πληροφοριών πετοσφαιρικής ομάδας, el:Πρότυπο:Κουτί πληροφοριών συλλόγου χειροσφαίρισης, el:Πρότυπο:Κουτί πληροφοριών συλλόγου καλαθοσφαίρισης, el:Πρότυπο:Τοπική ένωση καλαθοσφαίρισης, el:Πρότυπο:Κουτί πληροφοριών αθλητικού σωματείου, el:Πρότυπο:Πληροφορίες Ομοσπονδίας Ποδοσφαίρου, el:Πρότυπο:Πληροφορίες καλαθοσφαιριστή, el:Πρότυπο:Πληροφορίες Μουσικού Οργανισμού, el:Πρότυπο:Πληροφορίες πανεπιστημίου
• mai:आकृति:LinkedIn page
• fa:الگو:LinkedIn page
• vec:Modèl:Identifegadori, vec:Modeło:Identifegadori
• bn:টেমপ্লেট:লিংকডইন পাতা
• incubator:Template:Wn/tg/Ороиши гурӯҳ
• sl:Predloga:LinkedIn page
• zh:Template:LinkedIn页面
• ko:틀:링크드인 페이지
• zh-yue:Template:LinkedIn page
• th:แม่แบบ:LinkedIn page
• vi:Bản mẫu:LinkedIn page
• yue:Template:LinkedIn page
• n:eo:Ŝablono:Temkategorio 2, n:eo:Ŝablono:Temkategorio 2/DonSimon
• sr:Шаблон:LinkedIn
• ceb:Plantilya:LinkedIn page
• kaa:Úlgi:LinkedIn page
• tk:Şablon:LinkedIn page
• ckb:داڕێژە:LinkedIn page
• ar:قالب:صفحة لينكد إن
• ur:سانچہ:LinkedIn page

---

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

Link problem

I use this property for SMATRICS GmbH & Co KG (Q87212466). The correct link is this one. The only problem is that converts a & to a %26 and a ? to a %3F. If this wouldn't happen, the link would work. Any ideas for fixes? --D-Kuru (talk) 01:26, 7 March 2020 (UTC)

required qualifier constraint: online access status

A lot of LinkedIn accounts qualify for registration required. - Coagulans (talk) 11:10, 23 August 2021 (UTC)

If registration required or not to view content often depends on user agents and previous visits, I can often see an account on one device but not another one, or can bypass login by using another browser... Is there any company pages that always requires login? Abbe98 (talk) 19:55, 23 August 2021 (UTC)

Before adding this as a constraint, I would like to see at least one account that is universally not accessible. I'll revert until such proof is posted. Ainali (talk) 15:15, 24 August 2021 (UTC)

@Ainali, Abbe98: I see we've been discussing this in two places --Azertus (talk) 12:57, 25 August 2021 (UTC)

There does not seem to be consensus, nor is it actually clear if it's valid for LinkedIn accounts. I don't have LinkedIn and have yet to be unable to access an account. Feel free to point to an account which is universally inaccessible. Abbe98 (talk) 14:04, 25 August 2021 (UTC)

If you read the linked discussion, you'll see I share your arguments ;-) --Azertus (talk) 15:07, 25 August 2021 (UTC)

Sorry, I mistakenly addressed OP. Abbe98 (talk) 10:32, 27 August 2021 (UTC)

Regex validation too strict

Hello, it seems that the regex validation is incorrectly warning that some values are invalid, when they are indeed valid.

Take for example this link: https://www.linkedin.com/company/pomerleau-inc./ Because of the period in the company ID it doesn't match the provided regex Wolfy13399 (talk) 14:44, 30 April 2025 (UTC)

Seems like the regex is a bit over-restrictive and LinkedIn actually allows a lot of weird characters. IMO, it's useful to have a somewhat conservative format constraint to draw attention to possible mistakes, but if you know it's not a mistake, I think it's fine to expand the regex as needed. I just had to add fullwidth commas (， (Q87544556)) to the regex because Riitek (Q135956167)'s ID is shenzhen-riitek-co-，ltd. –IagoQnsi (talk) 17:00, 24 August 2025 (UTC)

There's a UTF-8 apostrope (') for Q20647765 that doesn't match the regex. It renders in the organisation URL as '%E2%80%8B (ie appended with a zero-width space). Gwirex (talk) 15:10, 29 December 2025 (UTC)

Numeric ID

LinkedIn assigns every company a numeric internal ID. For example, Brussels Museums (Q15873578) has the numeric ID 10515361. This ID follows the same pattern as the current company URL (https://www.linkedin.com/company/$1). You can locate it in the page’s source code by searching for urn:li:fs_normalized_company:. Using this numeric ID might be a more stable alternative to the current scheme.

JhowieNitnek (talk) 11:45, 25 July 2026 (UTC)

@JhowieNitnek: I didn't know it was a thing, but I'm all for more stable IDs. That said, I think it might be better to propose a new property for this. Yirba (talk) 13:06, 25 July 2026 (UTC)

@Yirba I have a few property proposals open so I am not going to propose anything new at this moment but feel gree to propose one yourself! -- JhowieNitnek (talk) 13:08, 25 July 2026 (UTC)

Fair enough. I may well do so! Yirba (talk) 13:09, 25 July 2026 (UTC)

By the way, I don't see urn:li:fs_normalized_company: in the page source but I do see urn:li:organization:10515361. When signed in, anyway. When signed out, I just get taken to the login screen. Yirba (talk) 15:03, 25 July 2026 (UTC)

@Yirba Weird I don't have urn:li:organization: only urn:li:fs_normalized_company JhowieNitnek (talk) 15:07, 25 July 2026 (UTC)

Deletion of property restriction

I have removed the added restriction regarding the qualificator LinkedIn numeric company ID, because contrary to the claim of User JhowieNitnek the identifier cannot simply be found in the source code. As long as this is the case, I consider the restriction on properties to be incorrect. --Gymnicus (talk) 23:47, 15 August 2026 (UTC)

@Gymnicus Please see the discussion above, where we already discussed this. There are two possible parameters you can look for: urn:li:organization: or urn:li:fs_normalized_company.

You can find these in the source code of the LinkedIn page. Could you please give me an example of a page where you could not find either of them? -- JhowieNitnek (talk) 11:00, 16 August 2026 (UTC)

If you had read my comments properly, you would have noticed that I searched the source code specifically for those two terms. However, I cannot find either of these terms and consequently no ID in the source code for any of the examples listed under this property. As long as that remains the case, I am reverting the property restriction. --Gymnicus (talk) 15:42, 16 August 2026 (UTC)

@Gymnicus I have looked in a on different pages and I can find them every time, are you sure you are doing it properly? @Yirba want to give your 2 cents? -- JhowieNitnek (talk) 18:10, 16 August 2026 (UTC)

It's probably a bit unhelpful for me to say "it works on my machine", but I have no problem finding it, at least, although you do need to be signed in to LinkedIn. It does seem there are different versions of the HTML that are served (which is why there are the two parameters above). Perhaps there are actually more than two possible parameters. Unfortunately, I'm not sure what's happening in this case that means Gymnicus cannot find the ID. But the IDs certainly do exist, even if they may be difficult to find, so I think the constraint should still be present. Yirba (talk) 18:29, 16 August 2026 (UTC)

In my case, when I view the source code of a LinkedIn page as an unregistered user, I usually only see various script functions rather than any actual HTML source code; consequently, neither of the two parameters is displayed. As long as the ID isn't easily accessible to everyone, I consider it a mistake to introduce this restriction, especially by making it mandatory. Gymnicus (talk) 22:18, 17 August 2026 (UTC)