Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

SEO default Open Graph image usually means the fallback image a page declares with the og:image metadata property. When a page has no more specific social-preview image, this URL represents the page in Open Graph consumers. Add it in the document’s <head>, make the image relevant to the page, and provide supporting metadata such as its MIME type, dimensions, and alternative text when known. The tag can influence previews, including Google image previews, but it cannot force Google or another platform to display that exact image.

What is a default Open Graph image?

Open Graph treats a web page as an object that can be represented when it is shared or read by another service. Its basic properties are og:title, og:type, og:image, and og:url. The value of og:image is an image URL for that object, not an image file embedded in the page itself.

A site-wide default is a fallback: you use it when a page does not have a better page-specific image. For example, a documentation site might use a branded documentation illustration by default, while an article about a particular product uses an illustration made for that article. The default should still be representative; a generic company logo is usually a weaker choice than imagery that explains the page.

The Open Graph Protocol defines the metadata and its relationships. It does not define one universal image size, aspect ratio, file format, or file-size limit that every social platform must accept. Individual platforms may apply their own processing and selection rules.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Google documents og:image as one signal it may use for image previews. Google’s selection is automated and can draw from multiple sources, so the declaration is an input, not a guarantee or a direct ranking instruction. Open Graph Protocol documentation and Google’s Image SEO best practices describe these behaviors.

How to add a default image in HTML

Place the tags in the document head

Put Open Graph elements inside <head>. Use an absolute, publicly reachable HTTPS URL for the image so crawlers and sharing services can request it independently of your site’s URL structure.

<head>
  <meta property="og:title" content="Example article title">
  <meta property="og:type" content="article">
  <meta property="og:url" content="https://www.example.com/guides/example-article">
  <meta property="og:image" content="https://www.example.com/images/default-social.jpg">
  <meta property="og:image:secure_url" content="https://www.example.com/images/default-social.jpg">
  <meta property="og:image:type" content="image/jpeg">
  <meta property="og:image:width" content="1600">
  <meta property="og:image:height" content="900">
  <meta property="og:image:alt" content="Illustration representing the example article">
</head>

The required image property is og:image. The protocol also documents optional fields for a secure URL, MIME type, pixel width, pixel height, and alternative description. Keep those values associated with the image they describe. If you publish more than one image, place each image’s supporting properties directly after that image’s og:image declaration.

Use a page-specific image when one exists

A practical fallback hierarchy is:

  1. Choose an image made for the individual page when it is available.
  2. Otherwise use the site or section default declared in the shared template.
  3. Ensure the fallback still makes sense if a visitor sees it without the page title.

If multiple og:image values conflict, the protocol says the first tag from top to bottom is preferred. Do not leave an accidental, earlier image tag ahead of the image you intend to use.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Choosing an effective default image

Make it relevant and representative

Google recommends an image that represents the page’s subject. A generic logo rarely tells a user what an article, product, or guide is about. A default can include restrained branding, but its main visual should communicate the site’s content rather than merely identify the publisher.

Avoid text-heavy artwork

Google advises avoiding images containing text as the main visual. Text can be cropped, rendered at different sizes, or duplicated by a platform’s own title treatment. If words are unavoidable, keep them secondary to the image and verify that the artwork remains understandable when reduced.

Prefer high resolution without extreme shapes

Use a sufficiently large source so a service can resize it cleanly, and avoid an extremely wide or tall composition. The available official guidance does not establish one cross-platform pixel dimension or aspect-ratio rule, so select dimensions appropriate to your design system and check the services that matter to your audience.

Describe the image accurately

When you know the image’s dimensions and MIME type, publish them in the corresponding structured properties. Write og:image:alt as a concise description of what the image depicts, not as a list of keywords. This preserves the relationship between the image and its description for consumers that support the field.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Default versus page-specific images

Decision Default image Page-specific image
When to use No tailored artwork is available The page has a subject that can be represented directly
Relevance Broadly represents the site or section Represents the exact article, product, or resource
Risk May look generic beside a specific headline Requires an image-generation or editorial workflow
Maintenance One shared asset and template Each page needs a valid URL and metadata

Use the page-specific option when it materially improves relevance. Keep the default for pages that genuinely lack a suitable custom visual; do not replace a relevant page image with a generic brand mark merely to simplify templates.

How preview selection actually works

Open Graph metadata describes your preferred representation, but the receiving service controls whether and how it uses that data. Google explicitly says image-preview selection is automated and may use multiple sources. Therefore:

  • og:image can influence Google’s choice, but it does not guarantee display.
  • The tag is not a promise that every social network will use the same crop, format, or image.
  • There is no evidence for describing og:image as a direct ranking guarantee.

When diagnosing a mismatch, first confirm that the fetched HTML contains the intended tag and that the URL resolves to the intended image. Then account for the receiving service’s own cache and selection process rather than assuming the metadata alone determines the result.

Implementation checklist

  • Declare og:title, og:type, og:url, and og:image in the page head.
  • Use an absolute HTTPS image URL that does not require a logged-in session.
  • Make the fallback relevant to the page type, not just a generic logo.
  • Add og:image:secure_url, og:image:type, og:image:width, og:image:height, and og:image:alt when those values are known.
  • Keep each image’s optional properties grouped with its image declaration.
  • Put the preferred image first when more than one image is declared.
  • Use a high-resolution, non-extreme composition and avoid making text the main visual.
  • Render the final server response and inspect the source, not only a client-side preview.

Common failures and fixes

The preview shows a logo instead of the article image

Cause: A shared default appears before the article’s custom og:image, or the custom tag is missing from the server-rendered head.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Fix: Remove the unintended earlier tag or place the desired image first, then verify the raw HTML returned for that URL.

The image URL returns an error

Cause: The URL is relative, mistyped, blocked, requires authentication, or does not serve an image to crawlers.

Fix: Request the exact absolute HTTPS URL independently, confirm a successful response and the expected content type, and make the asset publicly fetchable.

Google does not use the declared image

Cause: Google’s image selection is automated and can use multiple sources.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Fix: Ensure the image is relevant, representative, high resolution, and not an extreme aspect ratio. Treat the metadata as a preference signal, not a guaranteed instruction.

The wrong image is selected when several are present

Cause: Open Graph’s first-image preference means an earlier declaration wins when values conflict.

Fix: Reorder the tags and keep the intended image’s optional fields adjacent to it.

The image looks cropped or unreadable

Cause: Receiving services resize or crop previews differently, and text-heavy artwork loses context at small sizes.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Fix: Use a balanced composition, avoid extreme proportions, and make the visual understandable without relying on embedded text.

Inspecting a page before publishing

You can inspect the final HTML with browser developer tools: open the page, choose View page source (or the equivalent source command), and search for og:image. Confirm that the URL, order, and optional fields match the page you intend to publish. Repeat this for a representative page that uses the default and another that overrides it.

For automated checks, fetch the rendered response in your build pipeline and assert that exactly the intended image appears first. Also verify that the image URL is stable and publicly retrievable. These checks catch template regressions before a crawler or sharing service sees them.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Or skip the browser setup

If you need a visual capture of the finished page to inspect its actual rendered layout, ScreenshotNeo is a website screenshot API and MCP server for developers. It can capture a URL as PNG, JPEG, WebP, or PDF, including full pages and selected elements. Before capture it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. See the ScreenshotNeo documentation for parameters.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo supports full-page captures with lazy images loaded, CSS-selector element captures, dark mode, device presets and custom viewports, retina scale, custom CSS and JavaScript, click-before-capture actions, waits, request blocking, headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, selectable cache TTLs, signed links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.

The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Learn about ScreenshotNeo, then create a free account to try it.

FAQ

Is an Open Graph image the same as a favicon?

No. A favicon identifies a site or page in browser interfaces, while og:image is the image URL intended to represent the page object in sharing and graph contexts.

Should every page use the same default image?

Only pages without a more representative image should use the fallback. A page-specific image is preferable when it accurately depicts that page’s subject.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Does adding og:image guarantee a Google image preview?

No. Google may use the tag as one input, but its preview selection remains automated.

Frequently Asked Questions

Can I claim one official Open Graph image size works everywhere?

No. The Open Graph Protocol does not establish a universal pixel, aspect-ratio, format, or file-size standard across platforms. Choose a high-resolution, balanced image and check the services important to your audience.

What should I do if my custom image conflicts with the default?

Inspect the server-rendered head and remove or reorder duplicate declarations. Open Graph prefers the first image tag when multiple values conflict.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.