VK Did Not Break Your Link Preview, Your WebP Image Did

When VK shows your link as a bare URL with no image and no headline, the VK link preview has failed for one of three reasons and you can test all three in about ten minutes. First, your preview image is probably a WebP file, because VK will not load WebP for link previews while the identical picture saved as a JPG works perfectly. Second, the image may be too small, since anything under 300 by 300 pixels does not load and 500 by 500 is the safe floor. Third, your server or your firewall may be blocking VK’s crawler, which means VK never read your og: tags at all. There is a fourth thing that is not a cause but wrecks your testing anyway. VK caches whatever it scraped the first time, so a link you already shared keeps showing the broken preview long after you fixed the page. Test in that order, then force a fresh scrape at the end.

Your og: Tags Are Usually Innocent

So the fix is to rewrite your Open Graph tags. Add og:image, add og:title, add og:description, add og:url, check the syntax twice, maybe throw in og:image:secure_url for luck. That is exactly what you were expecting to read here, and it is what most threads on this subject will tell you.

In the majority of these cases the tags were already correct on the very first attempt. Rewriting them changes nothing, because the failure happened either before VK reached the tags or after it read them. Confirm that before touching a single line of markup. Open your page, view the source, find a tag with og:image on it, then copy the URL inside that tag and paste it into a fresh browser tab. If the image loads on its own, your markup is fine. Move on to the real tests.

Test One: Look at the File Extension on Your Preview Image

This is the one that catches site owners who changed nothing. Take the URL out of your og:image tag and look at what it ends with.

If it ends in .webp, you have found your problem. VK will not render a WebP file as a link preview. Save the same picture as a JPG at identical pixel dimensions, point og:image at the JPG, and the preview comes back.

Now for the reason this happens to people who never touched a template. Image optimisation plugins and modern content delivery networks convert uploads to WebP automatically because it makes pages load faster, and plenty of them serve WebP straight from the original path without changing the URL you can see. Cloudflare’s Polish feature does this. WordPress image plugins do this. Your host may well have switched it on for you during a performance upgrade you approved with one click in an email. Nobody edited any markup and the preview broke regardless.

The fix is to exempt your Open Graph image from the conversion. Most plugins keep an exclusion list somewhere in their settings. If yours has none, upload a dedicated JPG purely for social previews, give it a filename or a folder the converter ignores, and hard-code that path into the og:image tag.

Test Two: Measure the Image, Because VK’s Floor Sits Higher Than Facebook’s

Right-click the image, check its pixel dimensions, and compare them with what VK accepts. Anything below 300 by 300 will not load. Aim for 500 by 500 or larger and you clear the floor with room to spare.

This trips people up because the numbers everybody copies come from Facebook’s documentation, and Facebook’s numbers are different. Facebook says the minimum allowed image dimension is 200 by 200 pixels, recommends at least 1200 by 630 for high resolution devices, suggests 600 by 315 as a practical minimum for the large link format, and caps the file at 8 MB. An image at 250 by 250 satisfies Facebook and fails VK outright. If you built your preview image from a Facebook guide years ago and never tested it anywhere else, that is a very ordinary path into this problem.

A target that keeps everything happy at once: a single JPG at 1200 by 630 pixels, well under 8 MB, with nothing else to remember.

Test Three: Find Out Whether VK’s Crawler Reached You At All

If your preview shows no image and also no title and no description, stop staring at the image. VK never got the page.

VK’s link scraper identifies itself with a user agent string containing vkShare. Open your server access log and search for it around the time you tried to share the link. Nothing there means something sitting in front of your site turned VK away before it ever reached your HTML.

The usual culprits:

  • A web application firewall running a default rule that blocks unrecognised bots, or requests from particular countries.
  • Bot fight or bot management settings at your content delivery network, which increasingly ship switched on by default.
  • An AI-crawler blocklist added to robots.txt or enforced at the edge, which sweeps up ordinary link scrapers alongside the ones it was aimed at.
  • Rate limiting that reads a scraper’s quick burst of requests as an attack.
  • Geo-blocking, which for obvious reasons is a common one in this particular case.

Being serious for a moment, because this is the step where people damage their own site. Do not solve this by switching the firewall off. Do not solve it by allowing every bot through either. Add one narrow rule that lets the VK user agent fetch the specific page and leave the rest of your protection exactly as it stands. If your host manages the firewall for you, send them the user agent string and ask them to allowlist it. The same class of failure is why Pinterest sometimes reports it cannot reach a page you can obviously see in your own browser, so fixing this often repairs two things at once.

Force VK to Look Again, or You Will Think Your Fix Failed

VK stores what it scraped. Share the same URL after fixing everything and you will very likely get the old broken preview handed back to you, which is what sends people into a second useless round of og: tag editing.

Two ways round it.

  • Change the URL. Add a harmless query string, so you share yoursite.com/page?v=2 rather than yoursite.com/page. VK treats it as a URL it has not seen before and fetches the page fresh. This works every time and costs you nothing, since the page loads identically for the visitor.
  • Clear the cached copy through the API. VK exposes a pages.clearCache method that drops its stored copy of a given page. That is the tidier route if you are comfortable making an API call with an access token.

Whichever you use, test the result inside the post composer before publishing anything. Paste the link, wait for the card to render, look at it, and only then write the post around it.

One more reason old advice misleads here. VK’s handling of these files has shifted over the years, so a forum answer written a while ago may describe behaviour that no longer matches what you get today. Test against your own live link rather than against somebody’s memory of 2019.

Here Is the Whole Sequence in One Table

Step What you see What it means and what to do
0 Anything at all View source, confirm an og:image tag exists, and confirm its URL opens in a browser tab
1 Title and description appear, image does not Check the file extension. WebP fails on VK, so serve a JPG at the same size
2 Title and description appear, image still missing Check the dimensions. Under 300 by 300 will not load, so go to 1200 by 630
3 Bare URL, no title, no description VK’s crawler was blocked. Search your access log for vkShare and allowlist it
4 Everything fixed, preview still broken It is cached. Share with a query string added, or clear it through the API

Work through it in that order and you will not lose an afternoon rewriting markup that was never wrong in the first place. The reason it is worth the effort is dull and financial. A post carrying a proper card with a picture and a headline gets read and passed along, while a naked URL sitting in a wall of text gets scrolled straight past by people who would happily have clicked. Every share of the broken version spreads the broken version further. So get the card rendering properly before you push the link anywhere, whether that push is your own audience, a paid placement or VKontakte shares. The order you do these in matters more than the money you spend.

Leave a Reply

Your email address will not be published. Required fields are marked *