Skip to content

fix: use absolute URLs for OG/Twitter image meta tags - #105

Open
aledx18 wants to merge 1 commit into
HANCORE-linux:mainfrom
aledx18:fix/og-image-absolute-url
Open

fix: use absolute URLs for OG/Twitter image meta tags#105
aledx18 wants to merge 1 commit into
HANCORE-linux:mainfrom
aledx18:fix/og-image-absolute-url

Conversation

@aledx18

@aledx18 aledx18 commented Aug 12, 2026

Copy link
Copy Markdown

Problem

og:image used a relative path, which social crawlers (including X)
can't resolve. plugin.html also had no OG/Twitter meta tags at all,
so sharing a plugin page showed nothing either.

**
image
**

Fix

  • index.html: use absolute URL for og:image, add og:url and
    explicit twitter:title/description/image
  • plugin.html: add the same OG/Twitter meta tag block, reusing the
    existing marketplace preview image (no dedicated image was available)

Testing

  • npm test passes
  • Verified HTML renders correctly in browser

Future improvement

plugin.html currently reuses the marketplace preview image for all
plugins since pages are rendered client-side. Per-plugin OG images
would need server-side/prerendered pages — out of scope here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant