Browser Search Volume as a Congestion Metric in Mapping?

Looking for an efficient live-data tie-in for the purpose of adding a “current web traffic” metric into the mapping/airport control functions. If there is not already a way to incorporate accurate, relatively up-to-date web traffic (i.e. google searches for: Chicago O’Hare Delta Terminal, traffic leaving the Midway airport via “___” method of transportation, etc.) into the workflow, I’d love to hear best practices.

If not, I think this could be a very useful enhancement for transparency/efficiency’s sake.