Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
3,581 questions
Why does Teams prioritize Twitter meta data tags over OpenGraph/Schema definitions?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 45%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
dev4352
0
Reputation points
I have a website that has specific content for twitter cards & previews defined in meta tags
ie: <meta name='twitter:title' content='twitter:content /> along with both open graph and schema definitions.
It seems that Teams prioritizes the twitter specific meta tags rather than the more generic open graph or schema definitions when rendering link previews as well.
Is there any documentation around which meta tags the link previews will prioritize when multiple options are provided?
Microsoft Teams Development
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 65%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Meghana-MSFT 4,091 Reputation points Microsoft Vendor2025-02-21T08:15:31.08+00:00 Hi dev4352 - Could you please let us know if you are developing any Teams app? If yes, could you please share more details on the issue and repro steps, document followed.
-
dev4352 0 Reputation points
2025-02-21T20:17:33.3233333+00:00 Not a specific teams app but just trying to figure out how teams parse and previews a web site's meta data. I have an example page here: https://meta-tester.pages.dev/ the head is defined as:
<head> <meta charset="utf-8"> <link rel="icon" href="https://meta-tester.pages.dev/favicon.png"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta property="og:title" content="OG - Title"> <meta property="og:type" content="website"> <meta property="og:url" content="https://meta-tester.gregle.dev/"> <meta property="og:image" content="https://placehold.co/600x400"> <meta property="og:description" content="OG - Description"> <meta name="twitter:image" content="https://placehold.co/200x200"> <meta name="twitter:card" content="summary"> <meta name="twitter:title" content="Twitter - Title"> <meta name="twitter:description" content="Twitter - Description"> <script type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Article", "headline": "Schema - headline", "abstract": "Schema - abstract", "description": "Schema - description", "image": "https://placehold.co/300x300", "thumbnailUrl": "https://placehold.co/300x300" } </script> <meta name="description" content="Basic - Description"> <title>Basic - Title</title> </head>Which gets rendered in teams as:
Which is unexpected. For comparison, when I misspell the twitter tags to
twister:titleit uses the basic tags instead:Which is fine, but then why not the OG tags or the Schema def? So seeking clarification on why and if there's a workaround to prevent teams from picking that twitter meta data over the more generic options.
-
dev4352 0 Reputation points
2025-02-21T21:57:15.7366667+00:00 --double posted--
-
dev4352 0 Reputation points
2025-02-21T21:58:57.48+00:00 sorry for the double post, this things a little buggy on my end 🫠
Sign in to comment
Sign in to answer