I didn’t create that image, Obsidian (Publish?) did for me based on the contents of the note.
As soon as I add a permalink to the frontmatter of the note, the permalink correctly updates, however, the meta image no longer generates correctly. Instead, the generated meta image says “[permalink].md not found”—which makes sense, because [permalink].md isn’t a file that exists.
This is a similar issue as Obsidian Publish: use permalinks in sitemap if that helps. Both the meta image generator and the sitemap use [permalink].md to fetch the contents of the file, but [permalink].md doesn’t exist. Instead, they need to look at the note’s actual file which has a different name.
I have the same issue, permalink breaks the meta image and description, are this bug being worked on? This significantly reduce the usability of Obsidian Publish as a blogging solution.
I’m experiencing the same issue described in this report where setting a permalink
breaks the automatically generated OG preview meta image.
Current behavior
When I set a permalink in frontmatter (e.g., permalink: my-custom-url), bot crawlers (User-Agent: bot, facebookexternalhit, etc.) receive a 404 response with “File [filename].md does
not exist” instead of the actual content. This results in broken OG images showing “Not Found” messages.
Returns 404 with “File does not exist” message
curl -A bot https://minerva.mamansoft.net/2025-06-15-vscode-neovim-style-setup-2
Regular browser access works fine (JavaScript-rendered)
It appears that after some time (possibly 24 hours?), the OG image eventually becomes available for bot crawlers. However, this delay makes social sharing ineffective for new posts.
A 2-week-old article works fine
curl -A bot https://minerva.mamansoft.net/2025-06-02-vscode-neovim-style-setup
Regular browser access to a 2-week-old article works fine (JavaScript-rendered)
This significantly impacts the usability of Obsidian Publish as a blogging solution, especially for content that needs to be shared on social media promptly after publication.
You are right! I posted about the preview problem yesterday, but I didn’t know what was causing it. That’s why the preview never worked: all of my published notes have permalinks.
I just remove the permalink of one of them for a test and bingo! The preview worked. It’s definitely the permalink.
Good morning, @WhiteNoise. Did the team have a chance to check this? The problem is still there, and every time I test the “permalink” theory, pointed out by @mxstbr, it’s clear that that’s the culprit.
Even though I might still be doing something wrong, I’m more likely to think this is a bug now that I’ve tried all of the above variations on so many posts.
Setting a permalink does not break the social preview.
However, it may take longer for the social preview of permalinked pages to be correct.
One problem is that social preview are cached both by our CDN provider (cloudflare) and by the website you are using (twitter and co). If social preview is generated and says “page not found”, it’ll take a while before it is flushed and regenerated. We have no control over this.
This happens for regular non-permalinked pages as well. If you force the generation of a social preview for a page that hasn’t been published yet and then you publish it, it will take a while before social preview is correct.
Permalinks have an additional level of caching, done by us and lasts up to 4 hours, that aggravates the problem.
As a workaround, if you need to share a page immediately after you publish it (or add a permalink), you can share the non-permalinked url, which is likely correct from the get go.
@vladcampos the page you linked works now. If you share that url on bluesky, it should be picked up correctly.
Thank you for the detailed answer. Could you, please, explain the above in layman’s terms? Does it mean that it will take at least 4 hours to be able to paste a permalink that would show the correct image?
Another question. When I post with a permalink, is there a way to find/copy the non-permalink link?