100% FREE  -  NO SIGN-UP  -  YOUR FILES NEVER LEAVE YOUR DEVICE

Open Graph Checker

Paste your page HTML and see every Open Graph property, the four required checks and six platform card previews. The checker reads tags only and never loads your image file.

100% free, no premium plan No sign-up Files never leave your device
Drop your text here
or click to choose a file from your device

Your files are processed in your browser, on your own device. Nothing is uploaded to a server.

    This open graph checker reads the Open Graph tags in HTML you paste and reports what each platform will work with. Paste a full page or just the head section. Nothing is fetched from a URL. You get every og property with its value, the four required checks first, then notes on truncation, image declarations and canonical matches.

    One blind spot, stated before anything else: this checker reads the tags you paste. It does not load the og:image file, so the image real size, file weight and reachability stay unverified. Only the declared tags get checked. Server tools that fetch a page can measure the image itself. This one will not pretend to.

    How this open graph checker works, step by step

    • Step 1: Open the page you want to test and view its source.
    • Step 2: Copy the whole page, or just the head section. The head holds every tag this checker reads.
    • Step 3: Paste it into the box above. The report builds at once, with no URL fetch and no waiting on a server.
    • Step 4: Start with the required four, then work through the notes in order.
    • Step 5: Download the report as a text file if you want a copy for a client, a team or your own records.

    What this open graph checker looks at, in order

    The required properties come first: og:title, og:type, og:image and og:url. A page missing any of the four is asking platforms to improvise, and some will improvise badly.

    Then come the quiet problems. A title past about 60 characters and a description past about 160 are flagged as truncation risks. An og:image written as a relative path, or served over http instead of https, gets flagged too. Declared image dimensions are checked against 1200 x 630, with 600 x 315 as the floor. Last, og:url is compared with the canonical tag from the same paste, and a mismatch is named, because the two should agree on which URL owns the page.

    The previews from this open graph checker are sketches

    Six cards are drawn from the values you pasted: Facebook, X, LinkedIn, Slack, Discord and WhatsApp. Treat them as sketches of shape and wording, labelled as approximations, not as screenshots of what each app shows tonight. Platforms crop, round and reflow cards on their own schedules.

    Twitter tags found in the same paste appear in a second table under the og results. If that table is empty, do not panic. X falls back to the og values when twitter tags are missing. The card then runs on og:title, og:description and og:image, which is a workable default rather than an error.

    What this open graph checker cannot see

    It reads a paste, and a paste is a snapshot. If your live page has changed since you copied the source, the report describes the copy, not the page. Tags added by a plugin after you copied, or swapped by a caching layer, stay invisible here.

    The image limit from the top of the page applies in full. Declared dimensions get checked. The file itself does not get loaded, measured or weighed, and a dead image URL with tidy tags passes. Server based tools that fetch the page can measure the image. This one trades that trick for working on any paste, including pages that are not live yet.

    When this open graph checker is the right tool

    Before a launch, when the page exists only on staging. After a theme or plugin change, when the head is the first thing that silently changes. During a handover, when a client swears the tags were added and you want the answer in one paste. Any time the page is not public yet, a fetch based tool has nothing to fetch, and this one already has the answer.

    FAQs

    Why does the checker ask for a paste instead of a URL?

    Because it runs in your browser and never fetches. A paste also works on staging pages, drafts and pages behind a login, where a fetch based tool gets a login screen instead of your tags.

    Which four properties does every page need?

    og:title, og:type, og:image and og:url. Everything else improves the result, but a card built without one of these four is partly guesswork on the platform side.

    My og:image passed, but the card shows no picture. Why?

    The checker verified the declared tags, not the file. Open the image URL on its own. If it returns an error, redirects oddly or sits behind a block, the platform crawler hits the same wall. Declared dimensions can also be wrong while looking tidy.

    What if og:url and the canonical disagree?

    Pick the one true URL for the page and set both to it. A mismatch tells search engines one owner and social platforms another, and shares then credit a URL the page itself disowns.

    Are the six previews exact?

    No, and they are labelled as approximations on the page. They show the title, description and image each platform receives. Cropping and layout belong to the platforms and change without notice.

    Is my pasted HTML uploaded or stored?

    No. The paste is read in your browser and the report is built there. Close the tab and nothing remains, which is why the downloaded text report exists if you need a copy.

    More SEO Tools

    Same rules as this one: free, in your browser, with nothing uploaded.

    Scroll to Top