Open Graph and Twitter Card Audit

Social tags influence how shared links can appear on compatible platforms. Screpy provides Missing OG Tags, Incomplete OG Tags, Missing Twitter Card, and Incomplete Twitter Card filters.

These tags are presentation metadata. Treat them as a sharing and brand-quality feature, not a guaranteed Google ranking factor.

Understand complete metadata

Open Graph commonly uses a title, description, canonical URL, image, and content type. Twitter Cards commonly use a card type, title, description, and image. Platform behavior and caching can vary.

<meta property="og:title" content="Technical SEO Audit Guide" />
<meta property="og:description" content="Learn a repeatable page-audit workflow." />
<meta property="og:url" content="https://example.com/guide" />
<meta property="og:image" content="https://example.com/guide-cover.jpg" />
<meta name="twitter:card" content="summary_large_image" />

Analyze social-tag findings

1. Prioritize pages people are likely to share.
2. Inspect all required values in rendered HTML.
3. Confirm titles and descriptions represent the specific page.
4. Open image URLs and verify dimensions, format, accessibility, and branding.
5. Compare og:url with the preferred canonical URL.
6. Group missing values by template and optional content fields.

A private application screen may not need a share preview. A public article, product, landing page, or report usually benefits from one. Repeated homepage metadata across all pages creates misleading previews even when every field is technically present.

Fix the template safely

Generate values from accurate page-specific fields, define a deliberate fallback image, use absolute public URLs, and escape dynamic text. Keep preview copy concise without mechanically duplicating SEO metadata when a platform-specific message is more useful.

Example decision

All articles have OG tags, but og:image is empty whenever no custom cover exists. Add a branded fallback in the article template and preserve custom images where available. Do not add social metadata to authenticated settings pages solely to reduce the issue count.

Verify the result

Inspect rendered tags, open every asset URL, use platform preview validators where available, and recrawl. Cached previews may need to be refreshed after deployment. Confirm the result across several content states rather than testing only one ideal page.

Design social previews as a content contract

Open Graph and Twitter Card metadata control how a page may be represented when shared. They are not direct ranking guarantees, but accurate previews can improve clarity, trust, and click behavior in social and messaging platforms.

Prioritize public pages that people are likely to share: articles, products, tools, research, event pages, and major landing pages. Account, legal utility, and internal search pages may not need custom previews.

Review the complete preview

Check title, description, image, canonical URL, card type, and site identity together. Images should be public, stable, correctly sized, and representative. Avoid using a generic logo for every page when a meaningful page-specific visual exists.

Template variables must handle missing images, long titles, unavailable products, and localized content. A fallback is useful only when it remains accurate.

Interpreting filter movement

When tags are added, Missing Open Graph or Missing Twitter Card should fall. A zero missing count does not prove quality; generic or broken values can still produce poor previews. If counts rise after a frontend migration, inspect whether metadata moved into client-only rendering.

Platform caches may continue showing an old image after the page is fixed. Use platform preview debuggers to request a refresh, and verify the image response without authentication.

The Open Graph protocol defines core properties. Treat Screpy as an inventory and consistency check, then validate real shared previews on the platforms that matter to your audience.

Frequently asked questions

Are Twitter Cards still useful?

The metadata remains widely understood by sharing platforms and fallback systems. Maintain it when social previews matter, but verify the platforms that actually send traffic to your site.

Can the social image differ from the page's main image?

Yes. A dedicated preview image can use a share-friendly crop and text treatment, provided it represents the page accurately and remains publicly crawlable.

Related guidance

Return to the Pages overview to compare social metadata with the rest of the rendered page. MDN's meta element reference explains the HTML mechanism used for property-based social metadata.