OG history

Every Open Graph image a website has used, rebuilt from the Wayback Machine, with month-level dates.

When you share a link, the preview card shows the site’s Open Graph image (og:image). OG history keeps every image a website has used for its homepage, oldest to newest, so you can see how a brand’s share card changed over the years.

Open https://snaps.design/og to browse sites. Each site’s timeline is the Open Graph tab of its page: https://snaps.design/apps/linear?view=og for an app’s website, and a page of the same shape for a website with no app, such as https://snaps.design/apps/softgen?view=og. That page shows the site’s icon, name and a link to the website, with only the Open Graph tab. Old /og/<host> links redirect there.

What a timeline shows

Each version is one image the homepage pointed to, newest first. A version has:

The image itself, stored once and served from our image host.
A date range, such as “Mar 2024 – now”. “Now” means it is still the current image.
When the date it changed is not exact, the range it changed in, such as “changed between March and April 2026”.
Its pixel size and file type, and a link to the archived copy.

How dates work

Dates are month-level. We read archived copies of the homepage from the Wayback Machine: one every third month first, then the months in between wherever two neighbours show different images. A change is pinned to the month the new image first shows up, no closer.

about: the archive has a gap of more than 90 days around the change, so the date is a rough guess. Treat it as “around this time”.
seen once: the image appeared on only one archived page. It may have been a short test, a mistake that was fixed fast, or a bad capture.
not archived: the homepage pointed to this image, but the archive never saved the file. The dates are still real; there is just nothing to show.

What the archive cannot tell us

The timeline is only as good as the archive’s copies of the homepage:

Months the archive skipped are blind spots. A change that came and went between two captures is missed.
Sites that block the Wayback Machine, or are new, have little or no history. They start with their current image only.
We read the homepage only. Other pages may use other images.
Images hosted on another domain are taken from the archive, not fetched live, so the newest version of those can lag.

After the first pass, each site is checked again once a month. A new version is added only when the image file changes.

Add a site

Sign in and open https://snaps.design/og.
Paste a website, such as linear.app or a full URL, and choose Add. You can also type a domain in the search menu (⌘K).

The current image shows up within seconds. Past versions follow once the archive has been read, which usually takes a few minutes and can take longer when many sites are queued. Each account can add about 10 new sites per hour. Adding a site that is already tracked is free. Either way you land on the site’s page.

Only public websites are accepted: no IP addresses, local names or custom ports.

From an MCP client

The MCP server has four tools for OG history. See the tool reference for every field.

list_og_sites finds sites by name, host or category.
get_og_timeline returns one site’s versions, by host or by app slug.
get_og_image returns one version by id, such as the one in a copied link.
add_og_site starts history for a new site. It needs a key with the write scope.

{ "name": "list_og_sites", "arguments": { "query": "linear", "sort": "versions" } }

{ "name": "get_og_timeline", "arguments": { "host": "linear.app" } }

{ "name": "get_og_timeline", "arguments": { "app": "notion" } }

To hand an agent one image, open it on the site and choose Copy link. See Paste a Snaps link into your prompt.

Things to ask an agent:

“Show me how Linear’s share image changed since 2020.”
“Which sites in Productivity changed their OG image most often?”
“Add granola.ai and tell me when its timeline is ready.”