Traffic from external search engines - summary

A key metric in understanding the role external search engines play in Wikipedia's readership and content discovery processes is a very direct one - how many pageviews we get from them. This can be discovered very simply by looking at our request logs.

This dashboard simply looks at, very broadly, where our requests are coming from - search engines or something else? It is split up into “all”, “desktop” and “mobile web” platforms - but not apps, since the apps do not log referers.

Internal is traffic referred by Wikimedia sites, specifically: mediawiki.org, wikibooks.org, wikidata.org, wikinews.org, wikimedia.org, wikimediafoundation.org, wikipedia.org, wikiquote.org, wikisource.org, wikiversity.org, wikivoyage.org, and wiktionary.org (See Webrequest source for more information.)

Outages and notes

  • A: We switched to a finalized version of the UDF that extracts internal traffic (see T130083)
  • B: On 25 August 2016 we patched the UDF to also look for Duck Duck Go when it processes referer data. That referreral data was deleted and backfilled from 26 June 2016. See T143287 for more details.

Questions, bug reports, and feature suggestions

For technical, non-bug questions, email Mikhail. If you experience a bug or notice something wrong or have a suggestion, open a ticket in Phabricator in the Discovery board or email Deb.


Link to this dashboard: http://discovery.wmflabs.org/external/#traffic_summary

Traffic from external search engines, broken down

A key metric in understanding the role external search engines play in Wikipedia's readership and content discovery processes is a very direct one - how many pageviews we get from them. This can be discovered very simply by looking at our request logs.

This dashboard simply breaks down the summary data to investigate how much traffic is coming from each search engine, individually. As you can see, Google dominates, which is why we've included the option of log-scaling the traffic.

General trends

Outages and notes

  • A: On 25 August 2016 we patched the UDF to also look for Duck Duck Go when it processes referer data. That referreral data was deleted and backfilled from 26 June 2016. See T143287 for more details.

Questions, bug reports, and feature suggestions

For technical, non-bug questions, email Mikhail. If you experience a bug or notice something wrong or have a suggestion, open a ticket in Phabricator in the Discovery board or email Deb.


Link to this dashboard: http://discovery.wmflabs.org/external/#traffic_by_engine