The Social-Card Layer of Our Own 56 Pages: One Preview Image, 56 Titles, and 10 Pairs That Share a Description

I work on OnePassApps, the team behind app.onepassapps.com. This post is about the social-card metadata our own pages carry: the Open Graph and Twitter card tags that decide what a link to us looks like when it is pasted somewhere. Everything here was measured on 10 November 2026, from outside the browser, signed out, with no cookies and no JavaScript. The 56 URLs are the ones our own sitemap lists.

The same ten tags on every page

All 56 answered 200, and all 56 carry the same ten social-card tags: og:type, og:site_name, og:title, og:url, og:image, og:description, twitter:card, twitter:title, twitter:image and twitter:description. Nothing is missing on any page.

Four of them are one fixed value everywhere:

• og:type is website on all 56.
• og:site_name is OnePassApps on all 56.
• og:image is https://app.onepassapps.com/og-image.png on all 56 - one preview file for the whole site - and twitter:image points at the same file.
• twitter:card is summary_large_image on all 56.

So a link to any page of ours previews as the same picture, at the same size, with the same label under it. This one is about the fleet as it stands now: 56 pages, not 16.

The title is the page's own title

og:title is present on all 56 and takes 56 distinct values - one per page. On every one of the 56 it is character-for-character the page's <title> element, and twitter:title is character-for-character the same string again. The tab, the link preview and the card read the same words, on every page, with no exceptions.

The URL is the page's own URL

og:url is present on all 56 and on all 56 it is the page's own address, matching its canonical link exactly: 56 of 56, no rewrites and no trailing-slash differences.

The description is where the pages differ

A meta description is present on all 56, and it is also the og:description and the twitter:description on all 56 - the same string in all three places, on every page.

• 56 pages, 46 distinct description strings.
• Lengths run from 57 to 152 characters, with 30 distinct lengths.
• 20 of the 56 pages share their description with exactly one other page, in 10 pairs, and each pair is one app page together with that tool's guide page.
• The other 36 pages each carry a description of their own.

The pairs are the part worth naming. An app page and the guide page for the same tool say the same thing in the same words, so a link to either one produces the same preview text - which is sensible, because the guide is the app explained. The pages that have no partner - the studios, the vote board, the plans page and the rest - each say something of their own.

What this does not cover

One build, one day, one region, one request per URL, no cookies, no JavaScript, no session and no sign-in. I read the tags the server sends; I did not paste a link into a chat app and look at the card that got drawn, so nothing here is a claim about how any platform renders them. I did not check whether any crawler treats the tags differently from a browser, and I did not measure the image file itself - the earlier post on that file has the bytes.

Try it yourself

The File Studio is one of the seven browser studios, and it works on a file in the tab rather than uploading it: the File Studio

Every app and studio has a plain-language guide with its limits and its tool list: the OnePassApps guides