How this tool works
Maps the supplied page title, description, canonical URL, and image URL to common Open Graph properties.
How to use it
- Enter the actual page title and concise summary.
- Use absolute public URLs for the page and image.
- Add the tags to the page head and test with the destination platform.
Limits to keep in mind
The tool does not fetch or validate the image, test social platform caches, or guarantee how another service renders a preview.
Frequently asked questions
Do Open Graph tags directly improve Google rankings?
They describe sharing metadata; this generator does not measure ranking effects.
Does the image URL get checked?
No network request is made. Confirm access and dimensions separately.
What image size should I use for og:image?
A landscape image around 1200 by 630 pixels is a common choice and works on most platforms. Use a full https URL and test it where you plan to share the page.
Why does a shared link still show the old preview?
Social platforms cache previews. After changing tags or the image, use the platform’s own debugging or refresh tool, or wait for the cache to expire.
What Open Graph tags do
Open Graph tags provide information that a service can use when someone shares a page. They commonly describe a title, summary, canonical share URL, site name, content type, locale, and preview image. The generator turns the values you enter into copyable HTML for a page head. It can also add optional image description and dimensions, plus social card tags that reuse or override the share text. The form creates markup; it does not publish or verify it.
A share card should give a visitor an accurate idea of the destination. The title identifies the page, the description explains its content or benefit, and the image represents the page or brand. The URL should be the public address intended for sharing. These values may match search metadata, but they serve a separate presentation context. A social title can be shorter or more conversational while still describing the same page.
Open Graph metadata does not replace visible page content, the page title element, a canonical link, or structured data. Do not assume that adding a tag guarantees a specific search ranking or that every platform will display the same preview. Services can support different properties, cache old values, crop images, or choose how information is presented. The generated preview in this tool is a local check of your inputs, not a live platform simulation.
How to fill in the advanced fields
Start with the share title and description. Use wording that matches the live page and does not promise a result the page cannot deliver. Enter the absolute public page URL. The form checks that it is an HTTP or HTTPS URL but does not visit it, follow a redirect, or decide whether it is the preferred canonical. If your site redirects from one host or protocol to another, enter the final public version after confirming it.
Select a page type that fits the content, such as a general website page, article, product, or profile. Set a locale only when you know the correct value, and add an alternate locale when the page genuinely has another language or regional version. The generator checks a basic locale pattern but cannot verify that the language page exists or that alternate links are reciprocal.
Add an image URL if you have a relevant image that is publicly reachable. Image alt text should describe meaningful image content for users or systems that consume it. Enter width and height only when you know the actual file dimensions; the two fields must be supplied together. The tool can use separate social card title and description values or reuse the Open Graph text. Before generating, check that all required values describe the same page and offer.
Choosing a share image
A relevant image helps a person recognize a shared page. For an article, use an image that relates to its topic. For a service, use a clear brand or service visual. For a product, use an accurate representation of the actual product. Check that any text embedded in the image remains readable on a phone and that the crop still makes sense in the destination platform’s card layout.
The image URL must be absolute and publicly accessible. A temporary media-library preview, local file path, signed URL that expires, or image that requires a login may fail when another service fetches it. This generator does not request the image or check its HTTP response. After publishing, open the image URL in a private browser window or another environment to confirm it is available without your logged-in session.
Width and height properties describe the asset. They do not resize or crop it. Check the dimensions in your file or media library rather than guessing. If you replace the image, update the metadata and allow for the platform’s cache behavior. Image alt text should be concise and useful; do not turn it into a list of search phrases. If the image is purely decorative or the destination platform handles image descriptions differently, follow the requirements of the publishing workflow.
Previewing and generating the tag set
After you generate, inspect the card preview and checklist. Confirm that the site name, title, description, image, and URL fit together. The preview uses your entered image address in the browser; if the image fails to load, that can indicate a typo or access issue, but a successful local load still does not guarantee that external platforms can fetch it. Review the alternate card title and description if you supplied them.
The output may include `og:type`, `og:site_name`, `og:title`, `og:description`, `og:url`, `og:locale`, `og:image`, and optional image alt and dimensions. It also emits social card title, description, image, and a card format based on whether an image is present. The specific set should be checked against the destination platform and the tags your site already outputs.
Copy the tags into the system that manages the page head. In a CMS, this is often the social metadata panel in an SEO plugin, not a raw content block. If the theme already adds tags, update the existing fields rather than pasting a duplicate set. Inspect the final source of the published page, because the rendered output can differ from the code you copied.
Locales, page types, and consistency
Use a locale value only when you can identify the page’s language and regional variant. A value such as `en_US` describes English for the United States, while another value may represent another audience. The field validator checks the general shape; it does not prove the content is written for that locale. An alternate locale should point to a real version of the page, not merely a translated label with no corresponding destination.
Page type is descriptive metadata. Choose a type that accurately represents the page. A general landing page is not automatically an article or a product. A profile type should not be used simply because it sounds more detailed. Incorrect type information can confuse downstream consumers and make maintenance harder. The tool offers common options but cannot inspect the page to recommend one.
Keep the social URL consistent with your site’s preferred page URL. A share link can contain tracking parameters in a campaign context, but the stable page identity should remain clear. Avoid using a preview or staging URL in public tags. Check the title and description against the page’s visible H1 and main content so users do not feel misled after opening the card.
Troubleshooting sharing cards
If a card does not show, check the live page source first. Confirm that the tags are in the document head, that the page is publicly fetchable, and that no robots or access restriction blocks the crawler. Open the image URL directly and confirm it returns the expected image. Verify that the social URL points to the right host and protocol. Then check the platform’s own card preview or debugging tool, if available.
A stale preview may come from a cache. Changing the HTML does not necessarily refresh a card immediately across every service. Use the platform’s refresh mechanism when available and allow time for the cached data to update. If the preview omits a description or image, confirm that the respective metadata is present and accessible in the live source. Check whether the platform supports the chosen content type and card fields.
Duplicate tags can cause confusing results. A theme, SEO plugin, social plugin, and manually pasted snippet may all output different titles or images. Search the final HTML for repeated `og:title`, `og:image`, and `og:url` properties. Keep one clear source of truth for each page. This tool can create a tag set, but debugging requires checking the actual page and destination service.
Examples, privacy, and limits
For a freelance contract guide, a useful card could name the guide, explain the contract details it covers, and use a relevant document or project image. For a consulting service, the title should name the service, while the description says who it serves or what the page explains. For an online utility, the card should describe the real input and result. Avoid claims such as guaranteed leads or perfect legal compliance unless those outcomes are genuinely supported.
The form analyzes values locally in your browser. It does not upload page copy, submit images to a platform, fetch the destination URL, validate image dimensions, clear caches, measure engagement, or guarantee that a card appears. It cannot confirm image rights or the accuracy of your text. Follow your organization’s data practices when working with private campaign details or unreleased pages.
Can this guarantee a social preview? No. The destination service controls fetching and display. Can one image work everywhere? Sometimes, but platforms may crop differently; inspect the actual card layout. Should social and search titles be identical? They can be different, but must describe the same page honestly. Does this directly improve Google rankings? The generator makes no ranking prediction. Use it to publish consistent sharing information and validate the live implementation.
More SEO Tools · Browse the tools catalogue