<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">ResProt</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Res Protoc</journal-id>
      <journal-title>JMIR Research Protocols</journal-title>
      <issn pub-type="epub">1929-0748</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v9i7e16543</article-id>
      <article-id pub-id-type="pmid">32442159</article-id>
      <article-id pub-id-type="doi">10.2196/16543</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Protocol</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Protocol</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Using Application Programming Interfaces to Access Google Data for Health Research: Protocol for a Methodological Framework</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Mavragani</surname>
            <given-names>Amaryllis</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Kardes</surname>
            <given-names>Sinan</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Zepecki</surname>
            <given-names>Anne</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>The Wallace Center for Maternal, Child, and Adolescent Health</institution>
            <institution>School of Public Health</institution>
            <institution>University of California, Berkeley</institution>
            <addr-line>2121 Berkeley Way #5302</addr-line>
            <addr-line>Berkeley, CA, 94720</addr-line>
            <country>United States</country>
            <phone>1 408 335 5009</phone>
            <email>annezepecki@berkeley.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8240-9541</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Guendelman</surname>
            <given-names>Sylvia</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9690-3121</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>DeNero</surname>
            <given-names>John</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-9152-3891</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Prata</surname>
            <given-names>Ndola</given-names>
          </name>
          <degrees>MD, MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5913-0737</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>The Wallace Center for Maternal, Child, and Adolescent Health</institution>
        <institution>School of Public Health</institution>
        <institution>University of California, Berkeley</institution>
        <addr-line>Berkeley, CA</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Electrical Engineering and Computer Sciences</institution>
        <institution>College of Engineering</institution>
        <institution>University of California, Berkeley</institution>
        <addr-line>Berkeley, CA</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Anne Zepecki <email>annezepecki@berkeley.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>7</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>6</day>
        <month>7</month>
        <year>2020</year>
      </pub-date>
      <volume>9</volume>
      <issue>7</issue>
      <elocation-id>e16543</elocation-id>
      <history>
        <date date-type="received">
          <day>8</day>
          <month>10</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>11</day>
          <month>11</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>4</day>
          <month>2</month>
          <year>2020</year>
        </date>
        <date date-type="accepted">
          <day>24</day>
          <month>3</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Anne Zepecki, Sylvia Guendelman, John DeNero, Ndola Prata. Originally published in JMIR Research Protocols (http://www.researchprotocols.org), 06.07.2020.</copyright-statement>
      <copyright-year>2020</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Research Protocols, is properly cited. The complete bibliographic information, a link to the original publication on http://www.researchprotocols.org, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.researchprotocols.org/2020/7/e16543" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Individuals are increasingly turning to search engines like Google to obtain health information and access resources. Analysis of Google search queries offers a novel approach, which is part of the methodological toolkit for infodemiology or infoveillance researchers, to understanding population health concerns and needs in real time or near-real time. While searches predominantly have been examined with the Google Trends website tool, newer application programming interfaces (APIs) are now available to academics to draw a richer landscape of searches. These APIs allow users to write code in languages like Python to retrieve sample data directly from Google servers.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>The purpose of this paper is to describe a novel protocol to determine the top queries, volume of queries, and the top sites reached by a population searching on the web for a specific health term.  The protocol retrieves Google search data obtained from three Google APIs: Google Trends, Google Health Trends (also referred to as Flu Trends), and Google Custom Search.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>Our protocol consisted of four steps: (1) developing a master list of top search queries for an initial search term using Google Trends, (2) gathering information on relative search volume using Google Health Trends, (3) determining the most popular sites using Google Custom Search, and (4) calculating estimated total search volume. We tested the protocol following key procedures at each step and verified its usefulness by examining search traffic on <italic>birth control</italic> in 2017 in the United States. Two separate programmers working independently achieved similar results with insignificant variation due to sample variability.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>We successfully tested the methodology on the initial search term <italic>birth control</italic>. We identified top search queries for <italic>birth control</italic>, of which <italic>birth control pill</italic> was the most popular and obtained the relative and estimated total search volume for the top queries: relative search volume was 0.54 for the pill, corresponding to an estimated 9.3-10.7 million searches. We used the estimates of the proportion of search activity for the top queries to arrive at a generated list of the most popular websites: for the pill, the Planned Parenthood website was the top site.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The proposed methodological framework demonstrates how to retrieve Google query data from multiple Google APIs and provides thorough documentation required to systematically identify search queries and websites, as well as estimate relative and total search volume of queries in real time or near-real time in specific locations and time periods. Although the protocol needs further testing, it allows researchers to replicate the steps and shows promise in advancing our understanding of population-level health concerns.</p>
        </sec>
        <sec sec-type="registered-report">
          <title>International Registered Report Identifier (IRRID)</title>
          <p>RR1-10.2196/16543</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>Google</kwd>
        <kwd>search data</kwd>
        <kwd>infodemiology</kwd>
        <kwd>infoveillance</kwd>
        <kwd>infodemic</kwd>
        <kwd>reproductive health</kwd>
        <kwd>abortion</kwd>
        <kwd>birth control</kwd>
        <kwd>Google Trends</kwd>
        <kwd>APIs</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Individuals in the United States seeking health information online turn to search engines first. According to a 2012 Pew Internet &#38; American Life survey, 83% of users identified Google as their main search engine [<xref ref-type="bibr" rid="ref1">1</xref>]. Health questions and concerns are frequently of a sensitive nature, so queries people type privately into a search engine can provide insight about their true health concerns, especially those that they may not be comfortable sharing with their clinician or a research survey. Stephens-Davidowitz has found that these types of searches often capture what people actually “do, think, or want” because people reveal “some very personal things” in constructing their Google queries [<xref ref-type="bibr" rid="ref2">2</xref>].</p>
      <p>The most popular tool for analyzing and aggregating patterns of search data is Google Trends, a public website that has provided real-time and archived data on Google queries by users since 2004 [<xref ref-type="bibr" rid="ref3">3</xref>]. It has been used to study online behavior on diverse health topics, such as early detection of influenza epidemics [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref6">6</xref>], pertussis outbreak monitoring [<xref ref-type="bibr" rid="ref7">7</xref>], asthma monitoring [<xref ref-type="bibr" rid="ref8">8</xref>], and cancer detection [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. The tool has also been used to study public interest in cancer [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], suicide assessment [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>], depression-related information seeking [<xref ref-type="bibr" rid="ref15">15</xref>], lifestyle-disease surveillance [<xref ref-type="bibr" rid="ref16">16</xref>], bariatric surgery [<xref ref-type="bibr" rid="ref17">17</xref>], herpes zoster vaccinations [<xref ref-type="bibr" rid="ref18">18</xref>], searches for walk-in clinics and emergency departments [<xref ref-type="bibr" rid="ref19">19</xref>], obesity-related behavior [<xref ref-type="bibr" rid="ref20">20</xref>], and reproductive health [<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. Research using this tool has increased over 20-fold between 2009 and 2018 [<xref ref-type="bibr" rid="ref27">27</xref>].</p>
      <p>From a methodological standpoint, Google Trends has been used to measure web-based interest and variations of this interest over time [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref28">28</xref>], assess correlations between search queries with other data sources to inform public health and policy [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref26">26</xref>], and to forecast disease occurrence and outbreaks [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]. These applications fall within the emerging field of infodemiology. As first described by Eysenbach, infodemiology is “the science of distribution and determinants of information in an electronic medium, specifically the internet, or in a population, with the ultimate aim to inform public health and public policy” [<xref ref-type="bibr" rid="ref32">32</xref>]. A related term, infoveillance, has been used where infodemiology methods are employed for surveillance.</p>
      <p>While infodemiology was first used to analyze the quality of information on websites (ie, supply side), the scope has expanded to include what people need and their health-seeking behavior (ie, demand side). According to Eysenbach, analyses of information supply and demand both require new methods to measure the epidemiology of information and to examine the relationships between information supply and/or demand and population health [<xref ref-type="bibr" rid="ref33">33</xref>].</p>
      <p>Although Google Trends is an easily accessible tool for analyzing large population search queries, there is no consensus on how to retrieve, organize, and code queries. Researchers have applied inconsistent methodologies when using this tool and interpreting search data, which sometimes has led to questionable or invalid findings and problems with replicability and comparability across studies [<xref ref-type="bibr" rid="ref34">34</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. In response to these shortcomings, Mavragani and Ochoa [<xref ref-type="bibr" rid="ref35">35</xref>] recently proposed a concise step-by-step methodological framework that describes how to select the appropriate keyword, region, time period, and category for analysis of search queries to ensure the validity of health assessments with the web-based Google Trends tool. This framework, if used appropriately by researchers, should prove useful to ascertain more uniformity and comparability across studies and further our insight into human behavior.</p>
      <p>Less noted is that Google data is also available through Google application programming interfaces (APIs). <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> compares the Google Trends website and the API and illustrates their similarities and differences through an example. The Google Trends API can be used as a first step to identify top queries or search terms, and the API can be used in combination with two other Google APIs—Google Health Trends API and the Custom Search API—to extend the researcher’s understanding of search behaviors. The reason to combine APIs is that although the Google Trends website gives insight into search query volume, the additional APIs are needed to relate search intent to individual websites. All three APIs allow users to write code in a programming language such as Python to retrieve sample data directly from Google servers. However, access to the Google Trends API and Health Trends API is restricted to researchers and requires an application to Google.</p>
      <p>This article aims at documenting and illustrating a novel protocol for the use of three Google APIs to determine search query volume and individual websites reached by a given population searching using a health-related search term. This protocol is not the only one enabled by these APIs but is appropriate for the stated aim. We draw on examples from our study, which seeks to examine insights obtained from aggregated search queries related to the prevention of pregnancy. Analyses of queries related to birth control are relevant for policy and programmatic efforts because public funding and access to birth control are increasingly under attack in the United States [<xref ref-type="bibr" rid="ref36">36</xref>]. As access becomes more restrictive, use of the web may become more important in decision making about family planning.</p>
      <p>Since there are no accepted methodological standards for the use of Google APIs in academic research, our paper contributes to the systematization of an approach to combining APIs. The proposed methodology allows for a fuller picture of the volume and content of searches we are exploring through the examination of top topics and queries, relative search volume (RSV), top websites visited when searching for these top queries, and estimated volume of searches. The use of multiple APIs also provides multiple methods to estimate key values, ensuring the data obtained are accurate and reliable.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>We obtain key pieces of Google search data by using three Google APIs. Google Trends provides the top search topics and top search queries given an initial search term for a specified time period and location. Google Health Trends generates the RSV for a list of top queries in a specific region and time period. Finally, Google Custom Search provides the list of top websites that people who search using a given initial search term are shown when using the Google search engine. Custom Search gives results at the time of accessing the API, and these results can be specified at the national level.</p>
        <p>The Google Health Trends API, previously known as Google Flu Trends, gives normalized RSV across a set of search queries, allowing for more in-depth analysis of the relationships between queries. This RSV refers to the proportion of searches for a specific query as compared to the sum total of searches for a set of queries, and thus differs from the relative search index given by Google Trends, which gives search interest relative to all searches during the specified period of time. Although this proprietary tool is not available via the Google Trends website, it offers benefits to the researcher by providing a clearly defined metric to understand and interpret RSV.</p>
        <p>We show that the RSV provided by Google Health Trends can be combined with another trusted data source to estimate total search volume. RSV can also inform estimates of proportions of searches to a given site. To gather information on the top websites displayed on the Google search engine for a specific search term or topic of interest, we can access data through the Custom Search API. Because Custom Search gives results at the time of API access, researchers should plan accordingly and prepare to take regular samples of top sites during the time period of interest. This list of top sites is for the entire country. Evidence shows that the selection, sorting, and ranking criteria of search engines influence online health-information seeking [<xref ref-type="bibr" rid="ref37">37</xref>]. Custom Search data allow for analysis of content and quality of information that people get online. Thus, while the Google Trends website can determine what information people search for, it cannot determine what information they find. Hence, working with the three APIs enables a more comprehensive analysis than could be completed by using only the Google Trends website.</p>
        <p>We developed a simulation protocol that consisted of four steps: identifying a list of search queries for the topics of interest, obtaining RSV, determining top sites for top search queries, and calculating estimated total search volume. We describe these fully in <xref ref-type="table" rid="table1">Tables 1</xref>-<xref ref-type="table" rid="table5">5</xref>. We tested the protocol to examine the top queries for <italic>birth control</italic> in the United States in 2017 and created visualizations for each step. We used Python, version 2.7.13 (Python Software Foundation), for all of the API calls. Examples of the Python commands used are shown in Figures MA2-1 to MA2-7 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> contains the documentation of the Python package Graphviz [<xref ref-type="bibr" rid="ref38">38</xref>] and the APIs used.</p>
      </sec>
      <sec>
        <title>Step 1: Developing a List of Search Queries</title>
        <p>In the first step, we used the <italic>getTopQueries</italic> function to get the queries most associated with the initial topic of interest during a researcher-specified time period in a researcher-specified geographic region. The <italic>getTopQueries</italic> function can also gather the queries most associated with the previously obtained top queries, referred to as follow-up queries. Top queries are displayed in a graph that illustrates the relationship between queries. More details of the step-by-step procedures carried out are shown in <xref ref-type="table" rid="table1">Table 1</xref>. <xref rid="figure1" ref-type="fig">Figures 1</xref> and <xref rid="figure2" ref-type="fig">2</xref> show intermediary Steps 1.3 and 1.5 of the protocol.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Developing a list of top search queries.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="70"/>
            <col width="930"/>
            <thead>
              <tr valign="top">
                <td>Step</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1.1</td>
                <td>Begin with a list of regions to explore and a single, broad, initial search term, such as <italic>birth control</italic>.</td>
              </tr>
              <tr valign="top">
                <td>1.2</td>
                <td>For each region, make a request to Google Trends’ <italic>getTopTopics</italic> function to obtain the most searched-for topics for a specific initial search term. The function will return a list of topics that term is most closely related to as well as a value from 0 to 100 that denotes how strongly linked the topic is to the initial term: 100 is the most closely associated and 0 is the least. This list of top topics serves only to validate the top queries by examining similarities between the top topics and top queries.</td>
              </tr>
              <tr valign="top">
                <td>1.3</td>
                <td>Next, make a call to Google Trends’ <italic>getTopQueries</italic> function to get a list of the search queries most related to the initial search term in Step 1.1 for a given region, such as the United States. Each response from the <italic>getTopQueries</italic> method contains a <italic>title</italic>, or query, and a <italic>value</italic> attribute, which is a number from 0 to 100 and represents how related the query is to the provided initial search term in the United States: 100 is the most associated and 0 is the least. The data are presented in the form of a JSON (JavaScript Object Notation)-encoded mapping (see Figure MA2-1 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>), which can easily be converted into a graph via Python or exported to a CSV (Comma-Separated Values) file. If there are other regions of interest (eg, US states), this step must be repeated for all other regions. Each region will have a <italic>final list</italic> variable that stores all the top queries for that region. Once all final lists are generated for all regions of interest, they will be combined to create a <italic>master list</italic> that includes the top queries for every region of interest (<xref rid="figure1" ref-type="fig">Figure 1</xref> shows an example). Figure MA2-2 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> shows a snippet of the Python code.</td>
              </tr>
              <tr valign="top">
                <td>1.4</td>
                <td>For every query generated in Step 1.3, send a request to <italic>getTopQueries</italic> to obtain <italic>follow-up terms</italic>. Only queries with a <italic>value</italic> attribute greater than or equal to 70, as this indicates a high level of correlation between the terms, is added to our <italic>follow-up queries</italic> list. Irrelevant searches relating to pop culture should be manually filtered from results. Step 1.4 should be recursively executed—the <italic>follow-up queries</italic> become the base set at each iteration—until no new queries can be added to the base set. During this step, how each query is related to each other (ie, how a query ended up in our set of queries) should be recorded. This step is terminated when requests to <italic>getTopQueries</italic> do not return unique queries that have not already been received in the simulation for this region.</td>
              </tr>
              <tr valign="top">
                <td>1.5</td>
                <td>Then, generate a graph using the Graphviz package for Python 2.7 [<xref ref-type="bibr" rid="ref38">38</xref>] that illustrates how the search queries in the <italic>final list</italic> and the <italic>follow-up queries</italic> list are related to one another. As shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>, every node in the graph is a search query, and those in the first level will be included in the final list of search queries for the simulation. If a node is encapsulated by a double circle, then this represents an overarching topic coded for internal organizational purposes within the Google application programming interface (API) and is not included in the <italic>final list</italic> or <italic>follow-up queries</italic>. Every direct edge (arrow) in the graph represents a relationship between two search queries (nodes) in the graph. Note that with the current cutoff value of 70 in Step 1.4, there may be other intermediate terms in the graph not captured. Figure MA2-3 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> shows the Python function used.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Creation of a master list as visualized in Python for <italic>birth control</italic> in the United States, Mississippi, and Louisiana in 2017.</p>
          </caption>
          <graphic xlink:href="resprot_v9i7e16543_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Top queries for <italic>birth control</italic> in the United States in 2017. Single circles in the graph represent search queries, whereas a double circle indicates an overarching topic coded for internal organizational purposes within the Google application programming interface (API) and is not included in the list of top queries. Numbers in parentheses indicate how relation of query to the provided initial search term. iud: intrauterine device.</p>
          </caption>
          <graphic xlink:href="resprot_v9i7e16543_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Step 2: Gathering Information on Search Volume</title>
        <p>In the second step, the <italic>getTimelinesForHealth</italic> function in the Google Health Trends API gives the RSV for the top search queries generated in the previous step. All values generated are relative: the API gives the relative frequency of a specific term as compared to the other terms in the <italic>master list</italic> for a specific region during a specified period of time. More step-by-step details are shown in <xref ref-type="table" rid="table2">Table 2</xref>. <xref rid="figure3" ref-type="fig">Figure 3</xref> illustrates the normalized RSV as described in the intermediary Step 2.3.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Gathering information on search volume.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="60"/>
            <col width="940"/>
            <thead>
              <tr valign="top">
                <td>Step</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>2.1</td>
                <td>For each region, for every term in the master list, send a request to the <italic>getTimelinesForHealth</italic> function from the Google Health Trends application programming interface (API) to obtain relative search volume. Figure MA2-4 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> shows an example of the API call in Python.</td>
              </tr>
              <tr valign="top">
                <td>2.2</td>
                <td>The process in Step 2.1 should be repeated 30 times to minimize error. We take the average of the 30 samples of relative search volumes, which represents the estimated search volume for a given term with the date and location restrictions provided. Figure MA2-5 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> shows a sample response of relative search volumes given by the <italic>getTimelinesForHealth</italic> function in the United States.</td>
              </tr>
              <tr valign="top">
                <td>2.3</td>
                <td>To compare across regions, normalize the values for each region by dividing each term’s value with the aggregate search volume for the region. Before normalization, the value returned is skewed and does not take into account parameters such as geographical size differences. The normalized value will range from 0 to 1. The total sum of all values of the set of queries is 1 after normalization. The value from 0 to 1 allows for understanding of the relative search frequency within search queries. These data can then be used to define search frequencies for each term (see <xref rid="figure3" ref-type="fig">Figure 3</xref>). The normalization function used in this study is found in Figure MA2-6 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Relative search volume for <italic>birth control</italic> in the United States in 2017. IUD: intrauterine device.</p>
          </caption>
          <graphic xlink:href="resprot_v9i7e16543_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Step 3: Determining the Most Popular Sites</title>
        <p>In the third step, we send a request to the Google Custom Search API for each query in the master list to obtain a list of ranked top websites as they appear on the Google search engine results (see <xref ref-type="table" rid="table3">Table 3</xref>). A study from Chitika [<xref ref-type="bibr" rid="ref39">39</xref>] demonstrated that the first 10 sites in the search results receive about 95% of the traffic or more, prompting us to only consider the first page of sites returned in the search results. According to the Chitika study, the probabilities of someone clicking on the first, second, and third sites are 0.35, 0.20, and 0.15, respectively; the probabilities of someone clicking on the fourth and fifth sites are 0.08 and 0.07, respectively. The probabilities keep decreasing, such that the probability of someone clicking on any site following the ninth site is 0.01. The Chitika frequencies for site rankings, the Custom Search API rankings, and the RSV for the query can be used to calculate the estimated proportion of site visits at the time of API access. The call to the Custom Search API is outlined in Figure MA2-7 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. An example of this step, involving the term <italic>birth control pills</italic> and the top five sites visited [<xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref44">44</xref>], is illustrated in <xref ref-type="table" rid="table4">Table 4</xref> in the Results section.</p>
        <table-wrap position="float" id="table3">
          <label>Table 3</label>
          <caption>
            <p>Determining the most popular sites.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="60"/>
            <col width="940"/>
            <thead>
              <tr valign="top">
                <td>Step</td>
                <td>Description</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>3.1</td>
                <td>Use the master list generated in <italic>Step 1: Developing a List of Search Queries</italic> and send a request to the Google Custom Search application programming interface (API) for every term in the master list. This API returns a list of ranked top websites as they appear on the Google search engine results.</td>
              </tr>
              <tr valign="top">
                <td>3.2</td>
                <td>Use the frequencies for site rankings, the Custom Search API rankings, and the relative search volume for the query to calculate the estimated proportion of site visits. For example, as shown in Table 4, the top site for the term <italic>birth control pills</italic> in the United States is the <italic>birth control pill</italic> webpage on the Planned Parenthood website [<xref ref-type="bibr" rid="ref40">40</xref>]. The relative search volume for <italic>birth control pills</italic> in the United States in 2017 is 0.54, and the probability of someone clicking on the first site returned on the Google search engine is 0.35. Thus, the estimated proportion of site visits to Planned Parenthood is 0.19.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap position="float" id="table4">
          <label>Table 4</label>
          <caption>
            <p>Top five sites visited for birth control pill searches in the United States in August 2018.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="160"/>
            <col width="370"/>
            <col width="470"/>
            <thead>
              <tr valign="top">
                <td>Site ranking</td>
                <td>Website</td>
                <td>Webpage</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Planned Parenthood [<xref ref-type="bibr" rid="ref40">40</xref>]</td>
                <td>Birth control pill</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>WebMD [<xref ref-type="bibr" rid="ref41">41</xref>]</td>
                <td>Birth control pills</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Wikipedia [<xref ref-type="bibr" rid="ref42">42</xref>]</td>
                <td>Combined oral contraceptive pill</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>BirthControl.com [<xref ref-type="bibr" rid="ref43">43</xref>]</td>
                <td>Birth control pills</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Healthline [<xref ref-type="bibr" rid="ref44">44</xref>]</td>
                <td>Birth control pills: Are they right for you?</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Step 4: Calculating Estimated Total Search Volume</title>
        <p>Google does not provide total search volumes. We overcome this limitation by using actual volume on searches to a concrete website as the baseline for calculating estimated total search volume corresponding to the RSV for the top search queries obtained from the Health Trends API. We worked with Planned Parenthood Federation of America (PPFA) to obtain the number of searches that led to their website, as this is the most popular website for reproductive health information that people access in the United States. PPFA works with Vector Media to collect analytics on the number of visitors to their site. A search is defined as a user typing in a query in a search engine and then being directed to the search engine’s results [<xref ref-type="bibr" rid="ref45">45</xref>]. All of the data on searches that we obtained are, thus, the result of a user entering in a query regarding a particular initial search term in the Google search engine, which then leads them to the Planned Parenthood website. Slightly different processes must be used when the search query that directly relates to the site that the search data comes from is not present in the list of top queries. Estimated total search volume should be presented as a range that includes an upper bound determined by the lowest association of the top queries obtained. This assumes that there may be queries with lower associations that are not returned by the API. We show an example in the Results section.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Step 1: Developing a List of Search Queries</title>
        <p>We follow Step 1 of our procedure to gain information on the top queries for <italic>birth control</italic> in the United States in 2017. As shown in <xref rid="figure2" ref-type="fig">Figure 2</xref>, the most popular query was for birth control pills, followed in order of popularity by the shot, often searched for by its medical term Depo Provera and its effects; the implant; male birth control; and the intrauterine device (IUD). Queries for the IUD were predominantly for the copper IUD.</p>
      </sec>
      <sec>
        <title>Step 2: Gathering Information on Search Volume</title>
        <p>We then use our findings in Step 1 to complete Step 2 of the protocol: determining the RSV of the top queries. <xref rid="figure3" ref-type="fig">Figure 3</xref> shows, for instance, that in the United States in 2017, the pill (RSV=0.54) was searched for 4.5 times more than the implant (RSV=0.12) and 5.4 times more than male birth control (RSV=0.04).</p>
      </sec>
      <sec>
        <title>Step 3: Determining the Most Popular Sites</title>
        <p>We follow Step 3 of the protocol to obtain information on top sites. We chose one top query, <italic>birth control pills</italic>, as an example to demonstrate; however, to gain a full picture of top sites viewed, it is important to carry out this step for all top queries (see <xref ref-type="table" rid="table4">Table 4</xref>).</p>
      </sec>
      <sec>
        <title>Step 4: Calculating the Estimated Total Search Volume</title>
        <p>We estimate that the total number of searches for birth control in 2017 fell within the following ranges for the United States: 17,171,784-19,747,552 searches. These values were calculated using the formula outlined in <xref ref-type="table" rid="table5">Table 5</xref>. <italic>Planned Parenthood</italic> is not a top search query for the term <italic>birth control</italic>, but as we found out, it is a top search query for <italic>abortion</italic>. By obtaining the RSV of <italic>birth control</italic> as compared to <italic>abortion</italic>, we were able to obtain the estimated total search volume for <italic>birth control</italic> and then applied the RSV weights to obtain estimated total search volume for the top queries. Because the top queries do not account for all queries searched for—evidenced by the association values presented in <xref rid="figure3" ref-type="fig">Figure 3</xref>—we calculated an upper bound of 15% that we include in our estimates. <xref rid="figure4" ref-type="fig">Figure 4</xref> shows the estimated total search volume for each of the top search queries for <italic>birth control</italic> in the United States in 2017 based on the RSV weights for the top birth control methods.</p>
        <table-wrap position="float" id="table5">
          <label>Table 5</label>
          <caption>
            <p>Calculations for estimated total search volume for birth control in the United States.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="780"/>
            <col width="220"/>
            <thead>
              <tr valign="top">
                <td>Search item measure</td>
                <td>Value</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Total number of searches for <italic>abortion</italic> from Planned Parenthood</td>
                <td>12,393,960</td>
              </tr>
              <tr valign="top">
                <td>RSV<sup>a</sup> for <italic>abortion</italic></td>
                <td>0.4192</td>
              </tr>
              <tr valign="top">
                <td>RSV for <italic>birth control</italic></td>
                <td>0.5808</td>
              </tr>
              <tr valign="top">
                <td>Estimated total number of searches overall</td>
                <td>29,565,744<sup>b</sup></td>
              </tr>
              <tr valign="top">
                <td>Estimated total number of searches for <italic>birth control</italic></td>
                <td>17,171,784<sup>c</sup></td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table5fn1">
              <p><sup>a</sup>RSV: relative search volume.</p>
            </fn>
            <fn id="table5fn2">
              <p><sup>b</sup>0.4192 (<italic>RSV for abortion</italic>)x = 12,393,960 (total number of searches for <italic>abortion</italic> from Planned Parenthood); x = 29,565,744.</p>
            </fn>
            <fn id="table5fn3">
              <p><sup>c</sup>0.5808 (RSV for <italic>birth control</italic>) × 29,565,744 (estimated total number of searches overall) = 17,171,784.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Estimated total search volume (range) and relative search volume (within parentheses) for <italic>birth control</italic> in the United States in 2017. IUD: intrauterine device.</p>
          </caption>
          <graphic xlink:href="resprot_v9i7e16543_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>Google Trends has become a popular tool for analyzing search traffic on health. It has been used by researchers to measure general web-based interest, examine policy-related issues, get insights into health behavior, and to monitor and predict health-related events [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. However, it has been used inconsistently due to a lack of consensus on how to document Google search engine queries in academic research. This leaves room for methodological development. In this article, we show that Google Trends data, when retrieved from the Google Trends API, offers more versatile analytic capabilities than the data from the Google Trends website and offers the benefit of incorporating other APIs to extend insight into search-traffic behavior.</p>
        <p>The proposed protocol—empirically tested with <italic>birth control</italic> as the key initial search term—is capable of addressing important questions about Google search traffic and search interest. By following four distinct steps using three Google APIs, we are able to identify top search queries and websites as well as estimate relative and total search volume of queries in real time or near-real time in specified locations and time periods. The use of multiple APIs also provides multiple methods to obtain key values, ensuring the data obtained are accurate and reliable.</p>
        <p>Our methodology is robust insofar as it is well documented and avoids inserting any personal bias into the process of determining top search queries, since all top queries are given by the API. In addition, we are able to provide a novel solution to the current limitation of Google data, which, for privacy concerns, does not provide the absolute volume of searches. Prior studies proposed an approach to calculating total estimated search volume [<xref ref-type="bibr" rid="ref25">25</xref>], but this approach is no longer replicable given the constant updates Google makes to its technologies.</p>
        <p>The thorough documentation provided to apply the proposed protocol will allow researchers to replicate the methods used to further the understanding of population interest in health issues. The protocol can be applied to compare state-level searches to those at the national level and to explore changes in search traffic over time. It can easily be applied to other initial search terms; in our own exploration, we found that in the United States, people who searched for <italic>family planning</italic> instead of <italic>birth control</italic> were searching for traditional or <italic>natural family planning</italic> methods based on fertility awareness. Additionally, our protocol can be utilized at the zip code–based Nielsen Demographic Marketing Area (DMA) level, which is the smallest geolocation level that Google reports on and is available for each state. However, to protect user privacy, Google does not report data below a certain unknown threshold, so data may be unavailable for some DMAs.</p>
        <p>Google data can provide essential context to administrators, health care professionals, and academics. Top queries show varying interest in health topics as well as products and services by location, thus allowing health care providers to tailor services and information available at clinics and local practices to the questions people are asking. RSV provides context on how search interest compares by location, thus allowing one to focus on what resources are most desired or sought out. Top websites are crucial information for researchers, as they give a direct picture of what searchers are finding when they seek information. This data can provide insight as to why misinformation may spread or what organizations are having the greatest influence in sharing their beliefs, products, and services with potential patients and/or consumers. Finally, estimated total search volume allows professionals to know the amount of the population that may be seeking access to resources or information on the resources in question. More broadly speaking, this data gives interested stakeholders understanding of the changing health care landscape and identifies key concerns of potential patients and clients. Trends in search data over time may reveal the impact of administrative revisions and/or decisions made at the state or national level.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The results that our protocol can achieve must be tempered by the limitations of the data and the data sources. Google Trends reports on the top related and rising queries, as well as the top related and rising topics, but does not provide a list of all queries searched for. Thus, although the list of top queries is a comprehensive list of the most popular queries that users search for, it does not include every single query searched for relating to a particular initial search term. Similarly, the RSV is only relative to the other queries in our final list and does not include other queries that were not a part of the list of top queries. Furthermore, we are not able to identify the number of unique users or their individual characteristics.</p>
        <p>For most popular sites, we were unable to identify the key websites at the state level or request a specified time period. To overcome this limitation, one could import another source of data, such as a Google Consumer Survey (GCS) run at the state level. GCS is a tool that allows for online, customized market research and can be used to survey internet users about their preferred websites that they seek for specific queries [<xref ref-type="bibr" rid="ref46">46</xref>]. The values obtained from these responses could additionally be used as anchor points for calculating total volume of searches.</p>
        <p>Clearly, we require more studies to assess the value and validity of the proposed methodology. Temporal changes in the interface and capabilities of Google data pose challenges to the research community because researchers cannot build on nonspecific, nonreplicable, and discontinued methodologies. Hence, the proposed methodology will necessarily evolve as Google continues to make changes. In June 2019, Google made additional changes to the Google Trends API that had an effect on the <italic>getTopQueries</italic> function, resulting in a broader list of top queries than when our study data were retrieved. Future studies may integrate Google searches and other sources of online big data with machine learning models to track health topics [<xref ref-type="bibr" rid="ref47">47</xref>].</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>The combination of Google APIs suggested in the proposed methodological framework offers a novel approach to analysis of Google health queries, expanding the tools available to gain insight into health assessments.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Google Trends website and Google Trends application programming interface (API) comparison.</p>
        <media xlink:href="resprot_v9i7e16543_app1.docx" xlink:title="DOCX File , 845 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Python code appendix.</p>
        <media xlink:href="resprot_v9i7e16543_app2.docx" xlink:title="DOCX File , 1764 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Details of packages used within code and documentation for application programming interfaces (APIs).</p>
        <media xlink:href="resprot_v9i7e16543_app3.docx" xlink:title="DOCX File , 13 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">API</term>
          <def>
            <p>application programming interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CSV</term>
          <def>
            <p>Comma-Separated Values</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">DMA</term>
          <def>
            <p>Demographic Marketing Area</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">GCS</term>
          <def>
            <p>Google Consumer Survey</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">IUD</term>
          <def>
            <p>intrauterine device</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">JSON</term>
          <def>
            <p>JavaScript Object Notation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">PPFA</term>
          <def>
            <p>Planned Parenthood Federation of America</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">RSV</term>
          <def>
            <p>relative search volume</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>We wish to thank Prem Ramaswami, former Google employee, for his guidance and validation of the simulation protocol and William Sumfest, who pioneered the initial simulation protocol. We also thank the William and Flora Packard Foundation for their financial support of the case study and other members of the Wallace Center that contributed to the development and testing of the protocol.</p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Purcell</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Brenner</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Rainie</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <source>Search Engine Use 2012</source>
          <year>2012</year>
          <month>03</month>
          <day>09</day>
          <access-date>2019-08-15</access-date>
          <publisher-loc>Washington, DC</publisher-loc>
          <publisher-name>Pew Internet &#38; American Life Project</publisher-name>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.pewinternet.org/wp-content/uploads/sites/9/media/Files/Reports/2012/PIP_Search_Engine_Use_2012.pdf">https://www.pewinternet.org/wp-content/uploads/sites/9/media/Files/Reports/2012/PIP_Search_Engine_Use_2012.pdf</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stephens-Davidowitz</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>Everybody Lies: Big Data, New Data, and What the Internet Can Tell Us About Who We Really Are</source>
          <year>2017</year>
          <publisher-loc>New York, NY</publisher-loc>
          <publisher-name>HarperCollins Publishers</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="web">
          <source>Google Trends</source>
          <access-date>2020-01-27</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://trends.google.com/trends/">https://trends.google.com/trends/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ginsberg</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mohebbi</surname>
              <given-names>MH</given-names>
            </name>
            <name name-style="western">
              <surname>Patel</surname>
              <given-names>RS</given-names>
            </name>
            <name name-style="western">
              <surname>Brammer</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Smolinski</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Brilliant</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Detecting influenza epidemics using search engine query data</article-title>
          <source>Nature</source>
          <year>2009</year>
          <month>02</month>
          <day>19</day>
          <volume>457</volume>
          <issue>7232</issue>
          <fpage>1012</fpage>
          <lpage>1014</lpage>
          <pub-id pub-id-type="doi">10.1038/nature07634</pub-id>
          <pub-id pub-id-type="medline">19020500</pub-id>
          <pub-id pub-id-type="pii">nature07634</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Klembczyk</surname>
              <given-names>JJ</given-names>
            </name>
            <name name-style="western">
              <surname>Jalalpour</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Levin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Washington</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Pines</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Rothman</surname>
              <given-names>RE</given-names>
            </name>
            <name name-style="western">
              <surname>Dugas</surname>
              <given-names>AF</given-names>
            </name>
          </person-group>
          <article-title>Google Flu Trends spatial variability validated against emergency department influenza-related visits</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>06</month>
          <day>28</day>
          <volume>18</volume>
          <issue>6</issue>
          <fpage>e175</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2016/6/e175/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.5585</pub-id>
          <pub-id pub-id-type="medline">27354313</pub-id>
          <pub-id pub-id-type="pii">v18i6e175</pub-id>
          <pub-id pub-id-type="pmcid">PMC4942685</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kandula</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hsu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Shaman</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Subregional nowcasts of seasonal influenza using search trends</article-title>
          <source>J Med Internet Res</source>
          <year>2017</year>
          <month>11</month>
          <day>06</day>
          <volume>19</volume>
          <issue>11</issue>
          <fpage>e370</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2017/11/e370/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.7486</pub-id>
          <pub-id pub-id-type="medline">29109069</pub-id>
          <pub-id pub-id-type="pii">v19i11e370</pub-id>
          <pub-id pub-id-type="pmcid">PMC5696582</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gianfredi</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Bragazzi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Mahamid</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bisharat</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Mahroum</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Amital</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Adawi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Monitoring public interest toward pertussis outbreaks: An extensive Google Trends-based analysis</article-title>
          <source>Public Health</source>
          <year>2018</year>
          <month>12</month>
          <volume>165</volume>
          <fpage>9</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1016/j.puhe.2018.09.001</pub-id>
          <pub-id pub-id-type="medline">30342281</pub-id>
          <pub-id pub-id-type="pii">S0033-3506(18)30282-8</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mavragani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sampri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sypsa</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Tsagarakis</surname>
              <given-names>KP</given-names>
            </name>
          </person-group>
          <article-title>Integrating smart health in the US health care system: Infodemiology study of asthma monitoring in the Google era</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2018</year>
          <month>03</month>
          <day>12</day>
          <volume>4</volume>
          <issue>1</issue>
          <fpage>e24</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2018/1/e24/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/publichealth.8726</pub-id>
          <pub-id pub-id-type="medline">29530839</pub-id>
          <pub-id pub-id-type="pii">v4i1e24</pub-id>
          <pub-id pub-id-type="pmcid">PMC5869181</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Phillips</surname>
              <given-names>CA</given-names>
            </name>
            <name name-style="western">
              <surname>Barz Leahy</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Schapira</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Bailey</surname>
              <given-names>LC</given-names>
            </name>
            <name name-style="western">
              <surname>Merchant</surname>
              <given-names>RM</given-names>
            </name>
          </person-group>
          <article-title>Relationship between state-level Google online search volume and cancer incidence in the United States: Retrospective study</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>01</month>
          <day>08</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>e6</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/1/e6/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.8870</pub-id>
          <pub-id pub-id-type="medline">29311051</pub-id>
          <pub-id pub-id-type="pii">v20i1e6</pub-id>
          <pub-id pub-id-type="pmcid">PMC5778251</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Hou</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Hou</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Association between cancer incidence and mortality in web-based data in China: Infodemiology study</article-title>
          <source>J Med Internet Res</source>
          <year>2019</year>
          <month>01</month>
          <day>29</day>
          <volume>21</volume>
          <issue>1</issue>
          <fpage>e10677</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2019/1/e10677/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10677</pub-id>
          <pub-id pub-id-type="medline">30694203</pub-id>
          <pub-id pub-id-type="pii">v21i1e10677</pub-id>
          <pub-id pub-id-type="pmcid">PMC6371071</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mukhija</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Venkatraman</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Nagpal</surname>
              <given-names>SJ</given-names>
            </name>
          </person-group>
          <article-title>Effectivity of awareness months in increasing internet search activity for top malignancies among women</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2017</year>
          <month>08</month>
          <day>21</day>
          <volume>3</volume>
          <issue>3</issue>
          <fpage>e55</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2017/3/e55/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/publichealth.7714</pub-id>
          <pub-id pub-id-type="medline">28827213</pub-id>
          <pub-id pub-id-type="pii">v3i3e55</pub-id>
          <pub-id pub-id-type="pmcid">PMC5583504</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Vasconcellos-Silva</surname>
              <given-names>PR</given-names>
            </name>
            <name name-style="western">
              <surname>Carvalho</surname>
              <given-names>DB</given-names>
            </name>
            <name name-style="western">
              <surname>Trajano</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>de La Rocque</surname>
              <given-names>LR</given-names>
            </name>
            <name name-style="western">
              <surname>Sawada</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Juvanhol</surname>
              <given-names>LL</given-names>
            </name>
          </person-group>
          <article-title>Using Google Trends data to study public interest in breast cancer screening in Brazil: Why not a pink February?</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2017</year>
          <month>04</month>
          <day>06</day>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>e17</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2017/2/e17/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/publichealth.7015</pub-id>
          <pub-id pub-id-type="medline">28385679</pub-id>
          <pub-id pub-id-type="pii">v3i2e17</pub-id>
          <pub-id pub-id-type="pmcid">PMC5399222</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Stuckler</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>McKee</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Tracking search engine queries for suicide in the United Kingdom, 2004-2013</article-title>
          <source>Public Health</source>
          <year>2016</year>
          <month>08</month>
          <volume>137</volume>
          <fpage>147</fpage>
          <lpage>153</lpage>
          <pub-id pub-id-type="doi">10.1016/j.puhe.2015.10.015</pub-id>
          <pub-id pub-id-type="medline">26976489</pub-id>
          <pub-id pub-id-type="pii">S0033-3506(15)00425-4</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Examining the relationship between past orientation and US suicide rates: An analysis using big data-driven Google search queries</article-title>
          <source>J Med Internet Res</source>
          <year>2016</year>
          <month>02</month>
          <day>11</day>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>e35</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2016/2/e35/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.4981</pub-id>
          <pub-id pub-id-type="medline">26868917</pub-id>
          <pub-id pub-id-type="pii">v18i2e35</pub-id>
          <pub-id pub-id-type="pmcid">PMC4768042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Tana</surname>
              <given-names>JC</given-names>
            </name>
            <name name-style="western">
              <surname>Kettunen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Eirola</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Paakkonen</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Diurnal variations of depression-related health information seeking: Case study in Finland using Google Trends data</article-title>
          <source>JMIR Ment Health</source>
          <year>2018</year>
          <month>05</month>
          <day>23</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e43</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mental.jmir.org/2018/2/e43/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/mental.9152</pub-id>
          <pub-id pub-id-type="medline">29792291</pub-id>
          <pub-id pub-id-type="pii">v5i2e43</pub-id>
          <pub-id pub-id-type="pmcid">PMC5990858</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Memon</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Razak</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Weber</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Lifestyle disease surveillance using population search behavior: Feasibility study</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <month>01</month>
          <day>27</day>
          <volume>22</volume>
          <issue>1</issue>
          <fpage>e13347</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/1/e13347/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13347</pub-id>
          <pub-id pub-id-type="medline">32012050</pub-id>
          <pub-id pub-id-type="pii">v22i1e13347</pub-id>
          <pub-id pub-id-type="pmcid">PMC7011125</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rahiri</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Barazanchi</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Furukawa</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>MacCormick</surname>
              <given-names>AD</given-names>
            </name>
            <name name-style="western">
              <surname>Harwood</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hill</surname>
              <given-names>AG</given-names>
            </name>
          </person-group>
          <article-title>Using Google Trends to explore the New Zealand public's interest in bariatric surgery</article-title>
          <source>ANZ J Surg</source>
          <year>2018</year>
          <month>12</month>
          <volume>88</volume>
          <issue>12</issue>
          <fpage>1274</fpage>
          <lpage>1278</lpage>
          <pub-id pub-id-type="doi">10.1111/ans.14772</pub-id>
          <pub-id pub-id-type="medline">30173419</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Berlinberg</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Deiner</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Porco</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Acharya</surname>
              <given-names>NR</given-names>
            </name>
          </person-group>
          <article-title>Monitoring interest in herpes zoster vaccination: Analysis of Google search data</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2018</year>
          <month>05</month>
          <day>02</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e10180</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2018/2/e10180/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/10180</pub-id>
          <pub-id pub-id-type="medline">29720364</pub-id>
          <pub-id pub-id-type="pii">v4i2e10180</pub-id>
          <pub-id pub-id-type="pmcid">PMC5956160</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ssendikaddiwa</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lavergne</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Access to primary care and internet searches for walk-in clinics and emergency departments in Canada: Observational study using Google Trends and population health survey data</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2019</year>
          <month>11</month>
          <day>18</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e13130</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2019/4/e13130/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13130</pub-id>
          <pub-id pub-id-type="medline">31738175</pub-id>
          <pub-id pub-id-type="pii">v5i4e13130</pub-id>
          <pub-id pub-id-type="pmcid">PMC6913775</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Economic recession and obesity-related internet search behavior in Taiwan: Analysis of Google Trends data</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2018</year>
          <month>04</month>
          <day>06</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e37</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2018/2/e37/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/publichealth.7314</pub-id>
          <pub-id pub-id-type="medline">29625958</pub-id>
          <pub-id pub-id-type="pii">v4i2e37</pub-id>
          <pub-id pub-id-type="pmcid">PMC5910536</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nobles</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Dredze</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ayers</surname>
              <given-names>JW</given-names>
            </name>
          </person-group>
          <article-title>"Repeal and replace": Increased demand for intrauterine devices following the 2016 presidential election</article-title>
          <source>Contraception</source>
          <year>2019</year>
          <month>05</month>
          <volume>99</volume>
          <issue>5</issue>
          <fpage>293</fpage>
          <lpage>295</lpage>
          <pub-id pub-id-type="doi">10.1016/j.contraception.2018.10.012</pub-id>
          <pub-id pub-id-type="medline">30878137</pub-id>
          <pub-id pub-id-type="pii">S0010-7824(18)30485-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wood</surname>
              <given-names>LN</given-names>
            </name>
            <name name-style="western">
              <surname>Jamnagerwalla</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Markowitz</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Thum</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>McCarty</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Medendorp</surname>
              <given-names>AR</given-names>
            </name>
            <name name-style="western">
              <surname>Raz</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Public awareness of uterine power morcellation through US Food and Drug Administration communications: Analysis of Google Trends search term patterns</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2018</year>
          <month>04</month>
          <day>26</day>
          <volume>4</volume>
          <issue>2</issue>
          <fpage>e47</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2018/2/e47/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/publichealth.9913</pub-id>
          <pub-id pub-id-type="medline">29699965</pub-id>
          <pub-id pub-id-type="pii">v4i2e47</pub-id>
          <pub-id pub-id-type="pmcid">PMC5945987</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cartwright</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Karunaratne</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Barr-Walker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Johns</surname>
              <given-names>NE</given-names>
            </name>
            <name name-style="western">
              <surname>Upadhyay</surname>
              <given-names>UD</given-names>
            </name>
          </person-group>
          <article-title>Identifying national availability of abortion care and distance from major US cities: Systematic online search</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>05</month>
          <day>14</day>
          <volume>20</volume>
          <issue>5</issue>
          <fpage>e186</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/5/e186/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9717</pub-id>
          <pub-id pub-id-type="medline">29759954</pub-id>
          <pub-id pub-id-type="pii">v20i5e186</pub-id>
          <pub-id pub-id-type="pmcid">PMC5972217</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reidpath</surname>
              <given-names>DD</given-names>
            </name>
            <name name-style="western">
              <surname>Allotey</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>Predicting US state teenage birth rate using search engine query data on pregnancy termination and prevention</article-title>
          <source>J Glob Health Rep</source>
          <year>2018</year>
          <month>03</month>
          <day>01</day>
          <volume>2</volume>
          <fpage>1</fpage>
          <lpage>4</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.joghr.org/article/11938-predicting-us-state-teenage-birth-rates-using-search-engine-query-data-on-pregnancy-termination-and-prevention"/>
          </comment>
          <pub-id pub-id-type="doi">10.29392//001c.11938</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stephens-Davidowitz</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <source>The New York Times</source>
          <year>2016</year>
          <month>03</month>
          <day>05</day>
          <access-date>2019-08-18</access-date>
          <comment>The return of the D.I.Y. abortion<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.nytimes.com/2016/03/06/opinion/sunday/the-return-of-the-diy-abortion.html">https://www.nytimes.com/2016/03/06/opinion/sunday/the-return-of-the-diy-abortion.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Reis</surname>
              <given-names>BY</given-names>
            </name>
            <name name-style="western">
              <surname>Brownstein</surname>
              <given-names>JS</given-names>
            </name>
          </person-group>
          <article-title>Measuring the impact of health policies using internet search patterns: The case of abortion</article-title>
          <source>BMC Public Health</source>
          <year>2010</year>
          <month>08</month>
          <day>25</day>
          <volume>10</volume>
          <fpage>514</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcpublichealth.biomedcentral.com/articles/10.1186/1471-2458-10-514"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2458-10-514</pub-id>
          <pub-id pub-id-type="medline">20738850</pub-id>
          <pub-id pub-id-type="pii">1471-2458-10-514</pub-id>
          <pub-id pub-id-type="pmcid">PMC2936430</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Arora</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>McKee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Stuckler</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Google Trends: Opportunities and limitations in health and health policy research</article-title>
          <source>Health Policy</source>
          <year>2019</year>
          <month>03</month>
          <volume>123</volume>
          <issue>3</issue>
          <fpage>338</fpage>
          <lpage>341</lpage>
          <pub-id pub-id-type="doi">10.1016/j.healthpol.2019.01.001</pub-id>
          <pub-id pub-id-type="medline">30660346</pub-id>
          <pub-id pub-id-type="pii">S0168-8510(19)30001-6</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Foroughi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Lam</surname>
              <given-names>AK</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Saremi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ahmadvand</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>"Googling" for Cancer: An infodemiological assessment of online search interests in Australia, Canada, New Zealand, the United Kingdom, and the United States</article-title>
          <source>JMIR Cancer</source>
          <year>2016</year>
          <month>05</month>
          <day>04</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e5</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://cancer.jmir.org/2016/1/e5/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/cancer.5212</pub-id>
          <pub-id pub-id-type="medline">28410185</pub-id>
          <pub-id pub-id-type="pii">v2i1e5</pub-id>
          <pub-id pub-id-type="pmcid">PMC5369660</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mavragani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ochoa</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Forecasting AIDS prevalence in the United States using online search traffic data</article-title>
          <source>J Big Data</source>
          <year>2018</year>
          <month>5</month>
          <day>19</day>
          <volume>5</volume>
          <issue>17</issue>
          <fpage>1</fpage>
          <lpage>21</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journalofbigdata.springeropen.com/track/pdf/10.1186/s40537-018-0126-7"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s40537-018-0126-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Parker</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cuthbertson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Loveridge</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Skidmore</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Dyar</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>Forecasting state-level premature deaths from alcohol, drugs, and suicides using Google Trends data</article-title>
          <source>J Affect Disord</source>
          <year>2017</year>
          <month>04</month>
          <day>15</day>
          <volume>213</volume>
          <fpage>9</fpage>
          <lpage>15</lpage>
          <pub-id pub-id-type="doi">10.1016/j.jad.2016.10.038</pub-id>
          <pub-id pub-id-type="medline">28171770</pub-id>
          <pub-id pub-id-type="pii">S0165-0327(16)31110-7</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Young</surname>
              <given-names>SD</given-names>
            </name>
            <name name-style="western">
              <surname>Torrone</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Urata</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Aral</surname>
              <given-names>SO</given-names>
            </name>
          </person-group>
          <article-title>Using search engine data as a tool to predict syphilis</article-title>
          <source>Epidemiology</source>
          <year>2018</year>
          <volume>29</volume>
          <issue>4</issue>
          <fpage>574</fpage>
          <lpage>578</lpage>
          <pub-id pub-id-type="doi">10.1097/ede.0000000000000836</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Eysenbach</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Infodemiology and infoveillance tracking online health information and cyberbehavior for public health</article-title>
          <source>Am J Prev Med</source>
          <year>2011</year>
          <month>05</month>
          <volume>40</volume>
          <issue>5 Suppl 2</issue>
          <fpage>S154</fpage>
          <lpage>S158</lpage>
          <pub-id pub-id-type="doi">10.1016/j.amepre.2011.02.006</pub-id>
          <pub-id pub-id-type="medline">21521589</pub-id>
          <pub-id pub-id-type="pii">S0749-3797(11)00088-2</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Eysenbach</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Infodemiology and infoveillance: Framework for an emerging set of public health informatics methods to analyze search, communication and publication behavior on the internet</article-title>
          <source>J Med Internet Res</source>
          <year>2009</year>
          <month>03</month>
          <day>27</day>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>e11</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2009/1/e11/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.1157</pub-id>
          <pub-id pub-id-type="medline">19329408</pub-id>
          <pub-id pub-id-type="pii">v11i1e11</pub-id>
          <pub-id pub-id-type="pmcid">PMC2762766</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nuti</surname>
              <given-names>SV</given-names>
            </name>
            <name name-style="western">
              <surname>Wayda</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Ranasinghe</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Dreyer</surname>
              <given-names>RP</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>SI</given-names>
            </name>
            <name name-style="western">
              <surname>Murugiah</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>The use of Google Trends in health care research: A systematic review</article-title>
          <source>PLoS One</source>
          <year>2014</year>
          <volume>9</volume>
          <issue>10</issue>
          <fpage>e109583</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.plos.org/10.1371/journal.pone.0109583"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0109583</pub-id>
          <pub-id pub-id-type="medline">25337815</pub-id>
          <pub-id pub-id-type="pii">PONE-D-14-22976</pub-id>
          <pub-id pub-id-type="pmcid">PMC4215636</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Mavragani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ochoa</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Google Trends in infodemiology and infoveillance: Methodology framework</article-title>
          <source>JMIR Public Health Surveill</source>
          <year>2019</year>
          <month>05</month>
          <day>29</day>
          <volume>5</volume>
          <issue>2</issue>
          <fpage>e13439</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://publichealth.jmir.org/2019/2/e13439/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/13439</pub-id>
          <pub-id pub-id-type="medline">31144671</pub-id>
          <pub-id pub-id-type="pii">v5i2e13439</pub-id>
          <pub-id pub-id-type="pmcid">PMC6660120</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>Public Policy Office, Guttmacher Institute</collab>
          </person-group>
          <source>Guttmacher Institute</source>
          <year>2020</year>
          <month>05</month>
          <day>01</day>
          <access-date>2019-08-17</access-date>
          <publisher-loc>Washington, DC</publisher-loc>
          <publisher-name>Guttmacher Institute</publisher-name>
          <comment>Insurance coverage of contraceptives<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.guttmacher.org/state-policy/explore/insurance-coverage-contraceptives">https://www.guttmacher.org/state-policy/explore/insurance-coverage-contraceptives</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Allam</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Schulz</surname>
              <given-names>PJ</given-names>
            </name>
            <name name-style="western">
              <surname>Nakamoto</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>The impact of search engine selection and sorting criteria on vaccination beliefs and attitudes: Two experiments manipulating Google output</article-title>
          <source>J Med Internet Res</source>
          <year>2014</year>
          <month>04</month>
          <day>02</day>
          <volume>16</volume>
          <issue>4</issue>
          <fpage>e100</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2014/4/e100/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.2642</pub-id>
          <pub-id pub-id-type="medline">24694866</pub-id>
          <pub-id pub-id-type="pii">v16i4e100</pub-id>
          <pub-id pub-id-type="pmcid">PMC4004139</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref38">
        <label>38</label>
        <nlm-citation citation-type="web">
          <source>Python Package Index (PyPI)</source>
          <access-date>2019-08-17</access-date>
          <comment>Simple Python interface for Graphviz: Project description<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pypi.org/project/graphviz/">https://pypi.org/project/graphviz/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref39">
        <label>39</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Donnini</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <source>Search Engine Journal</source>
          <year>2013</year>
          <month>07</month>
          <day>22</day>
          <access-date>2019-08-17</access-date>
          <comment>The value of Google result positioning<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.searchenginejournal.com/the-value-of-google-result-positioning/65176/">https://www.searchenginejournal.com/the-value-of-google-result-positioning/65176/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref40">
        <label>40</label>
        <nlm-citation citation-type="web">
          <source>Planned Parenthood</source>
          <access-date>2020-05-12</access-date>
          <comment>Birth control pill<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.plannedparenthood.org/learn/birth-control/birth-control-pill">https://www.plannedparenthood.org/learn/birth-control/birth-control-pill</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref41">
        <label>41</label>
        <nlm-citation citation-type="web">
          <source>WebMD</source>
          <access-date>2020-05-12</access-date>
          <comment>Birth control pills<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.webmd.com/sex/birth-control/birth-control-pills#1">https://www.webmd.com/sex/birth-control/birth-control-pills#1</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref42">
        <label>42</label>
        <nlm-citation citation-type="web">
          <source>Wikipedia</source>
          <access-date>2020-05-12</access-date>
          <comment>Combined oral contraceptive pill<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://en.wikipedia.org/wiki/Combined_oral_contraceptive_pill">https://en.wikipedia.org/wiki/Combined_oral_contraceptive_pill</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref43">
        <label>43</label>
        <nlm-citation citation-type="web">
          <source>BirthControl.com</source>
          <access-date>2020-05-12</access-date>
          <comment>Birth control pills<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://birthcontrol.com/options/birth-control-pills/">https://birthcontrol.com/options/birth-control-pills/</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref44">
        <label>44</label>
        <nlm-citation citation-type="web">
          <source>Healthline</source>
          <access-date>2020-05-12</access-date>
          <comment>Birth control pills: Are they right for you?<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.healthline.com/health/birth-control-pills">https://www.healthline.com/health/birth-control-pills</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref45">
        <label>45</label>
        <nlm-citation citation-type="web">
          <source>Google Analytics Help</source>
          <year>2019</year>
          <access-date>2019-08-17</access-date>
          <comment>How a web session is defined in Analytics<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://support.google.com/analytics/answer/2731565?hl=en">https://support.google.com/analytics/answer/2731565?hl=en</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref46">
        <label>46</label>
        <nlm-citation citation-type="web">
          <source>Google Surveys Help</source>
          <year>2019</year>
          <access-date>2019-08-17</access-date>
          <comment>How it works<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://support.google.com/surveys/topic/6194669?hl=en&#38;ref_topic=7156628">https://support.google.com/surveys/topic/6194669?hl=en&#38;ref_topic=7156628</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref47">
        <label>47</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sadilek</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Caty</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>DiPrete</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Mansour</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Schenk</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Bergtholdt</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jha</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Ramaswami</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gabrilovich</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Machine-learned epidemiology: Real-time detection of foodborne illness at scale</article-title>
          <source>NPJ Digit Med</source>
          <year>2018</year>
          <month>11</month>
          <volume>1</volume>
          <fpage>36</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31304318"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41746-018-0045-1</pub-id>
          <pub-id pub-id-type="medline">31304318</pub-id>
          <pub-id pub-id-type="pii">45</pub-id>
          <pub-id pub-id-type="pmcid">PMC6550174</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
