Property talk:P10768

Documentation

• Start a query
• Current uses
• Statistics by class
• Units
• Scale of values
• List of qualifiers
• Count

Similarweb ranking
the website's Similarweb global ranking

Represents	Similarweb ranking (Q112108975)
Applicable "stated in" value	Similarweb (Q17538813)
Data type	Quantity
Domain	website (Q35127)
Allowed units	not applicable
Example	southparkstudios.com (Q111952101) → 12,183 brainly.com (Q111952103) → 1,433
Source	https://www.similarweb.com
See also	Alexa rank (P1661)
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 statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Minimum and maximum Items with highest numeric value Items with lowest numeric value Database reports/Constraint violations/P10768 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 96 Main statement 93 96.9% of uses Qualifier 3 3.1% of uses

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

Scope is as main value (Q54828448): the property must be used by specified way only (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/P10768#Scope, 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/P10768#Entity types

Required qualifier “point in time (P585)”: this property should be used with the listed qualifier. (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/P10768#mandatory qualifier, SPARQL

Integer: values should be integers (ie. they shouldn't have a fractional part) (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/P10768#integer, SPARQL

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/P10768#single best value, SPARQL

Units: “novalue”: value unit must be one of listed. (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/P10768#Units

Type “website (Q35127)”: item must contain property “instance of (P31)” with classes “website (Q35127)” 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).
List of violations of this constraint: Database reports/Constraint violations/P10768#Type Q35127, SPARQL

This property is being used by: es:Plantilla:Ficha de sitio web, es:Badoo sv:Mall:Publikation, sv:Aftonbladet Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

Does someone want to update these rankings by means of a botjob? I think that when they are updated, the Alexa-ranking shown in many Wikipedia templates can be replaced by similarweb rankings.

I am not affiliated with Similarweb.com, but I suggested the Similarweb ranking (P10768) property in March 2022 because the Alexa ranking service was about to be closed. Tinker Bell created the property in May 2022. Jklamo, imported a large number of rankings around august 2022. user:Danielyepezgarces started some experiments with the WikiRankBot in 2023 to update rankings from Similarweb.com to web sites. -sasha- added it to templates in the Spanish Wikipedia.

I suggest that the property should allow more than one ranking values: the global ranking (without a country qualifier) and several country rankings, each with different country qualifier.

A very small number of non-webpage objects, for example persons, have P10768 as qualifier for their homepage, which is against the current instructions. If some template can accept it, perhaps it should be allowed. Alternatively, why not allow it as property in any object - at least one that has a webpage property? For example a journal, a person with homepage, a company, etc.

Using Similarweb rankings in templates is also discussed at enwiki:

• en:Infobox website/Archive 3#Proposal: Add SimilarWeb
• en:Talk:Similarweb#Should Similarweb be cited to report web traffic rankings on Wikipedia? (Some skepticism expressed)

Tomastvivlaren (talk) 04:45, 18 February 2024 (UTC)

I understand your position, currently Similarweb in its public API only allows the ranking of 5,000 domains to be published, the majority of which have no relevance in Wikipedia or are not in Wikidata. Also, the rankings are updated once a month so if you make a bot that updates periodically on a specific day of each month

Likewise, I will be willing to receive proposals and reactivate WikiRankBot, Danielyepezgarces (talk) 08:42, 18 February 2024 (UTC)

_:Good idea in principle, but some issues need discussion.

• what to link - at the moment we have about 10,000 "pure" instance of (P31) website (Q35127) items. These are indeed suitable for botjob (if they are notable enough). But there are another 5,000+ items that have multiple values with instance of (P31) website (Q35127). These are the stats for the other values. Some of them are suitable (web portal (Q186165) etc.), some of them are not because they are an inappropriate combination of several concepts in one item (business (Q4830453), organization (Q43229), magazine (Q41298) etc.), and most of them are borderline (organization (Q43229), mobile app (Q620615), social networking service (Q3220391) etc.). It is not too surprising that I am not a fan of using it on non-webpage objects objects or for webpage property.
• how often to update - this is a complex question, as wikidata is unforunately not designed to handle really large items. See Elo rating (P1087) related items or COVID-19 pandemic in the United States (Q83873577) like items (note tabular case data (P8204) and similar properties). At the same time, the historical numbers are also interesting and valuable as well. That's why I'm more in favor of less frequent updates, say once a quarter.
• multiple values (country rankings) - see previous consideration. Again, this is interesting data, but the limitations of wikidata are relentless. That's why I'm more in favor of limiting these as much as possible, perhaps to just one or two values.

Jklamo (talk) 14:40, 18 February 2024 (UTC)

@Danielyepezgarces, Jklamo: Thank you both for good answers. The Alexa rank Alexa rank (P1661) is used in 4,267 objects (but only 5 qualifiers). This property is used in 83 objects (and 4 qualifiers). Do you guys think it is possible to reach a similar level by developing a similar bot and applying similar procedures? The Alexa rank was updated by Alexabot until January 2018, and then by others.Tomastvivlaren (talk) 16:45, 18 February 2024 (UTC)