Search result vs social card
A page’s title and description show up in two different places with different rules. Google reads the <title> tag and meta name="description" for the blue link and gray snippet in search results. Facebook, LinkedIn, and Slack read og:title and og:description instead, and Twitter reads its own twitter:title and twitter:description before falling back to the Open Graph values. Filling in all three keeps the wording consistent across both surfaces.
og:image aspect ratio
Open Graph images render at roughly 1.91:1. A square photo or a tall portrait gets cropped from the center, which can cut faces or headlines placed near the top or bottom. Export a 1200x630px image when the source photo does not already match that ratio.
Canonical URL and duplicate pages
Set the canonical URL to the version of the page you want indexed and shared, without query strings like ?utm_source= or ?ref=. Sharing a link with tracking parameters attached still points crawlers back to the canonical address, so social previews and search listings stay tied to one URL.
Twitter Card type
summary_large_image renders a full-width image above the title and description, which is the layout most publishers use for articles and product pages. summary renders a small square thumbnail beside the text instead, which reads better for profile pages or short updates where the image is secondary to the copy.
Locale format
og:locale expects an underscore-separated language and region code, such as en_US or pt_BR, not a hyphenated BCP 47 tag like en-US. Platforms that read Open Graph locale fall back to en_US when the value does not match that format.