UniLink supports the oEmbed standard — paste your UniLink URL into any compatible platform and it auto-embeds as a rich media card without copying any embed code.
- oEmbed lets platforms like WordPress, Notion, and Ghost auto-embed UniLink pages by detecting the URL pattern.
- Paste your UniLink URL in a supported platform's editor and it renders as a rich preview card automatically.
- No API key or manual HTML required — oEmbed works entirely on the platform side via URL detection.
oEmbed is an open standard that lets websites automatically create rich embeds when a supported URL is pasted into a content editor. Instead of copying iframe code or hunting for an embed widget, you paste the URL and the platform handles discovery, fetching the embed data, and rendering a preview — all invisibly. UniLink supports the oEmbed standard, which means anywhere that has registered or will detect the UniLink URL pattern, your page appears as a rich card rather than a plain text link. It is the most frictionless embed method available, and it requires nothing from you beyond your page URL.
What oEmbed Support Does
oEmbed works through a discovery and endpoint mechanism. When a supported platform like WordPress detects a URL that matches a known oEmbed provider's pattern, it queries the provider's oEmbed endpoint with the URL as a parameter. UniLink's oEmbed endpoint is at https://unilink.us/api/v1/oembed?url={encoded_url}. The endpoint returns a JSON response describing how to embed the content — including the embed type (in UniLink's case, a "rich" embed), the HTML to render, the title, the thumbnail image URL, and the page dimensions. The platform then renders this HTML in place of the raw URL, showing visitors a rich interactive card.
What the rendered embed looks like depends on the platform doing the rendering. In WordPress, oEmbed returns a styled preview card with your page's profile image, name, and a selection of your top links — essentially a compact snapshot of your UniLink page that visitors can interact with. In Notion, the oEmbed renders as an inline block that shows your page content. In Ghost, it renders as a bookmark card with your page title, description, and thumbnail. Each platform styles the oEmbed output according to its own design system, so the visual result varies — but the underlying data comes from UniLink's endpoint in every case.
UniLink pages are registered as an oEmbed provider with the major platforms that maintain provider registries. For platforms that do not use a registry and instead rely on auto-discovery via HTML link tags, UniLink pages include the necessary <link rel="alternate" type="application/json+oembed"> tag in their HTML head. This means even platforms that are not pre-registered with UniLink can discover the oEmbed endpoint automatically by parsing the page's head tags — expanding oEmbed support to virtually any platform that follows the oEmbed discovery specification.
How to Get Started
- Copy your UniLink page URL — either
https://unil.ink/usernameor your custom domain URL if you have one connected and published. - Open a WordPress post or page editor, paste the URL on its own line in the block editor, and press Enter. WordPress automatically converts registered oEmbed URLs into rich embed blocks.
- In Notion, type
/embedin a page, paste your UniLink URL into the embed dialog, and click "Embed link." Notion fetches the oEmbed data and renders an inline block. - In Ghost editor, paste the UniLink URL on its own line. Ghost's editor auto-converts oEmbed-compatible URLs to bookmark cards showing your page's title, description, and thumbnail.
- To query the oEmbed endpoint directly for testing:
curl "https://unilink.us/api/v1/oembed?url=https%3A%2F%2Funil.ink%2Fusername". The JSON response shows exactly what embed data the platform receives.
How to Use oEmbed
- WordPress block editor: Paste your UniLink URL on its own line in a paragraph block and press Enter. If WordPress recognizes the URL as oEmbed-compatible, it automatically converts the paragraph to an Embed block showing your page preview.
- WordPress classic editor: In the text editor (not visual), paste the URL on its own line with a blank line above and below. WordPress's oEmbed processing applies during page render and displays the embed in the published post.
- Notion: Use
/embedor/linkcommands and paste the URL. Notion renders supported URLs as interactive embed blocks that visitors can interact with inline. - Ghost: Paste the URL on a new line in the editor. Ghost converts it to a bookmark card; use the card options to switch between bookmark and embed display modes if available.
- Direct API query: Call
GET https://unilink.us/api/v1/oembed?url={encoded_url}&maxwidth=600&maxheight=800to fetch embed data programmatically — useful for building your own platform with oEmbed support for UniLink pages.
Key Settings
| Setting | What It Does | Recommended |
|---|---|---|
url parameter | The URL-encoded UniLink page address passed to the oEmbed endpoint | Always URL-encode the full page URL — spaces and special characters must be encoded |
maxwidth | Suggested maximum width for the embed in pixels | Pass 420 to match UniLink's mobile-first page width; platforms may override this |
maxheight | Suggested maximum height for the embed | Pass 700–900 for typical page lengths; the actual rendered height may differ per platform |
Response type | oEmbed response type: rich, photo, video, or link | UniLink returns "rich" — platforms render this as an interactive HTML embed block, not just a link |
| Page publish status | oEmbed only returns data for published, publicly accessible pages | Ensure the page is published and publicly accessible before sharing the URL for oEmbed use |
Get the Most Out Of oEmbed Support
Use oEmbed embeds in blog posts to turn static content into interactive touchpoints. A blog post about your latest product launch, with your UniLink page embedded midway through, lets readers click through to buy or learn more without leaving the article. Because the embed is live, any updates you make to your UniLink page — new links, updated prices, new products — appear automatically in the embed without touching the blog post.
For newsletters that support HTML content (like Substack, Ghost newsletters, or Beehiiv), test whether the platform renders your UniLink URL as a rich embed in the web version of the post. Even if the email version shows a plain link, the web archive version often renders oEmbed content, which can drive meaningful click-through from readers who browse your newsletter archive.
If you are building a platform or developer tool that should support UniLink oEmbed, your implementation needs two things: URL pattern matching (detect URLs matching https://unil.ink/* and optionally your user's custom domains) and an HTTP fetch to https://unilink.us/api/v1/oembed?url={encoded_url}. Parse the JSON response, extract the html field from a "rich" type response, and render it in your editor. The entire implementation requires no API key — it is a public endpoint.
Not all platforms that claim oEmbed support behave identically. Some platforms cache the oEmbed response aggressively — if you change your UniLink page name, profile photo, or content significantly and want embeds on other platforms to reflect the changes, you may need to prompt a refresh. In WordPress, you can force a refresh by deactivating and reactivating the embed. In Notion, deleting the embed block and re-pasting the URL creates a fresh fetch. For mission-critical embeds, test them after any major page changes.
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| URL pasted in WordPress shows as a plain link, not an embed | The UniLink URL is not on its own line, or WordPress oEmbed cache has not discovered the provider yet | Ensure the URL is on its own paragraph line with no other text; save and preview the post — WordPress fetches oEmbed data during the first render |
| oEmbed endpoint returns 404 | The UniLink page does not exist or is set to draft/private | Confirm the page is published and accessible by visiting the URL in a browser while logged out |
| Embed shows stale content after updating your UniLink page | The embedding platform cached the original oEmbed response | Force a cache refresh on the embedding platform — in WordPress, use the "Refresh" option on the embed block; in Notion, delete and re-embed the URL |
| Custom domain URL does not trigger oEmbed auto-detection | Custom domains may not be registered in all platform provider lists | Use the default unil.ink/username URL for maximum oEmbed compatibility; custom domains work via HTML auto-discovery but may not trigger in all editors |
- Zero configuration — paste a URL and the embed appears automatically without any HTML or API key
- Supported natively in WordPress, Notion, Ghost, and other major platforms without plugins or extensions
- Auto-discovery via HTML link tags extends support to any oEmbed-compliant platform, even unregistered ones
- Live embeds reflect your current UniLink page content without updating the host document
- Embed appearance varies by platform — UniLink cannot control how each platform styles the oEmbed output
- oEmbed only works for public, published pages — password-protected or draft pages return errors
- Platform caching may delay content updates from appearing in existing embeds
What is the oEmbed endpoint URL for UniLink?
The UniLink oEmbed endpoint is https://unilink.us/api/v1/oembed. Pass the target page URL as the url query parameter, URL-encoded: ?url=https%3A%2F%2Funil.ink%2Fusername. No API key is required — the endpoint is publicly accessible.
Does oEmbed work with subdomain UniLink URLs (username.unil.ink)?
Yes — subdomain URLs are supported by the oEmbed endpoint. Platforms that use HTML auto-discovery will find the oEmbed link tag in the page head. For platforms using a registered provider list, the unil.ink pattern matches both path-based and subdomain URLs.
Can I disable oEmbed for my UniLink page?
oEmbed is enabled for all public UniLink pages automatically and cannot be disabled per-page. If you do not want your page embeddable on other sites, set the page to private or password-protected — the oEmbed endpoint will return an error for non-public pages, preventing embedding.
Does oEmbed count as a page view in UniLink analytics?
Fetches to the oEmbed API endpoint are not counted as page views. Views are only counted when a visitor's browser renders the actual page — whether as an iframe embed or a direct visit. oEmbed meta-fetches by platform servers are not visitor sessions.
Which platforms support UniLink oEmbed?
Confirmed platforms include WordPress (self-hosted with oEmbed support), Notion (via the /embed command), Ghost, and any platform that follows the oEmbed auto-discovery specification by parsing HTML link tags. Platforms including Webflow, Coda, and GitBook also support oEmbed auto-discovery.
- oEmbed lets platforms auto-embed your UniLink page by detecting the URL — no HTML code or API key needed.
- The oEmbed endpoint is
https://unilink.us/api/v1/oembed?url={encoded_url}— publicly accessible, no authentication required. - In WordPress, paste your URL on its own line; in Notion, use
/embed; in Ghost, paste on a new line and the editor handles the rest. - Only published, public pages are embeddable — draft or password-protected pages return errors to the oEmbed endpoint.
- Cached embeds may show stale content after page updates — force a re-fetch by removing and re-pasting the URL in the host editor.
Share your UniLink page URL in any oEmbed-compatible platform and watch it auto-embed — get your URL at app.unilink.us and paste it into your next WordPress post or Notion page.