Web page metadata

[rviscomi]

Ensure all pages have metadata like <meta> descriptions, images, etc. Also consider open graph or structured data tags.

Ideally, when sharing a link to a report, a relevant image would be used as opposed to the HTTP Archive logo. For example, if deep linking to a particular metric in a report, the image used would be a screenshot of the metric's timeseries/histogram. At the very least, we could dynamically populate the page's metadata with info specific to the metric.

[jeannieh]

Alos, consider how your data transfers (or doesn't) in Google Analytics. It another reason why it is good to migrate is because HTTPs to HTTP referral data is blocked in Google Analytics. One example, let's say your website is on HTTP still and you went viral on Business2Community and Medium. Both of these websites are running over HTTPS. The referrer metadata is completely lost and the traffic from both of those sites could end up under direct traffic which is not very helpful. If someone is going from HTTPS to HTTPS the referrer is still passed. Lots of reasons to protect your metadata during migrations to HTTPS.

[rviscomi]

Thanks @jeannieh, great points to keep in mind! We're fully HTTPS compatible so thankfully we don't need to worry about that class of problems, right?