Posts tagged annual-review

Search.gov Annual Reviews

What people are trying to do on government websites, in their own words

Search.gov is pleased to present our annual reviews - high level reports that show, in their own words, what the public has been searching for across government websites.

From common needs for forms and process status checks, to the latest information on the news of the year, or vulnerable moments seeking help in times of need, Search.gov is there, connecting people with their government.

Changes in the data over time reflect which agencies use our service, and major news in a given year. The data represents only those websites that use Search.gov, and does not include data on searches run on commercial search engines.

If you have questions or comments, please feel free to reach out to our team.

2019 in Review

Top Topics in 2019 poster, small version. Following is a link to a larger PDF version. The poster shows a set of 16 pie charts, one for each top topic. The pie charts show the details of the top 25 queries run in 2019 for that topic. The chart labels are accessible, but unfortunately the pie charts are image-only. Text versions are available on request, reach out to the Search team for assistnce.
Open large version

295,916,305 queries

~2,000 gov websites

16 top topics

365 days of connecting people with what they need.


System Highlights

  • Added ranking factors to our search algorithm (popularity, freshness)
  • Released help documentation about site launches and the indexing process
  • Added a sitelimit feature to provide an alternative to Collection search scoping
  • Added indexing coverage for javascript pages and other metadata-only files.
  • Increased security on user accounts
    • automatic disabling after 90 days of inactivity
    • MFA login through Login.gov
  • Upgraded Ruby
  • Upgraded Rails
  • Upgraded Elasticsearch
  • Upgraded jQuery
  • Increased server capacity and processing power
  • Added query caching on our primary index to improve response time
  • Expanded our Elasticsearch system twice