How to Use the Twitter / X Block in UniLink (Embed Your Posts and Feed on Your Page)
How to Use the Twitter / X Block in UniLink (Embed Your Posts and Feed on Your Page)
The Twitter / X block lets you embed your tweets, timeline, or a Twitter list directly on your UniLink page — no API key, no code, just a URL.
- Three embed modes: single tweet by URL, user timeline (latest posts from an account), or a Twitter list.
- No API key needed — UniLink uses Twitter's native oEmbed widget, so any public tweet or public profile URL works.
- Match the embed theme (light or dark) to your page design — a dark embed on a light page looks like a bug, not a feature.
- Timeline mode with retweets enabled will fill your page with other people's content — turn retweets off unless that is intentional.
If you post regularly on Twitter or X, your best content is already written — it just lives somewhere visitors to your bio page cannot see. Someone lands on your UniLink page, clicks your Twitter icon, maybe follows you, maybe does not. But what if the post that would convince them to follow was right there on the page, embedded and readable in ten seconds? That is what the Twitter / X block does. It closes the gap between the content you are already creating and the page where you send everyone. This guide covers every mode, every setting, and every mistake worth avoiding.
What the Twitter / X block does
The Twitter / X block embeds live Twitter content directly on your UniLink page using Twitter's official oEmbed API. There are three modes. Single tweet mode shows one specific tweet by URL — ideal for pinning a popular post, a product announcement, or a thread opener. Timeline mode pulls the latest tweets from any public account and displays them as a scrollable feed — best for creators who post frequently and want their recent activity visible without manual updates. Twitter list mode embeds a curated Twitter list, which is useful if you want to show a themed collection of posts rather than a single account's feed.
Because the block uses Twitter's native embed widget, no API key or developer account is required on your end. You supply the URL, UniLink handles the rest. The embed renders exactly as it would on Twitter — with avatars, engagement counts, media previews, and verified badges intact. In timeline mode you can control how many tweets to show, whether media appears inline, and whether retweets are included. In single tweet mode the tweet renders as a card with all its original formatting.
There are two constraints to understand upfront. First, the tweet or account must be public — protected accounts and locked-down tweets will not embed, and there is no workaround for that because Twitter's API simply does not expose private content. Second, the embed is third-party JavaScript loaded from Twitter's servers. It adds some page weight. UniLink lazy-loads the widget so it does not block the initial page render, but visitors on slow connections will see a brief loading state before the embed appears.
Before you start
- Confirm the account or tweet is public: Go to the tweet or profile URL in a private browser window without being logged in to Twitter. If you can see the content, the embed will work. If you see a "This account's posts are protected" message, the embed will fail regardless of settings.
- Decide which mode fits your goal: If you want to highlight a specific post (announcement, viral tweet, pinned thread), use Single tweet. If you want a live feed of your activity, use Timeline. If you curate a topical list of accounts, use Twitter list. Having a clear goal prevents you from defaulting to timeline mode when a single featured tweet would actually perform better.
- Copy the URL you plan to use: For single tweet mode, click the timestamp on any tweet to open it in its own URL, then copy that URL. For timeline mode, copy your profile URL (twitter.com/yourhandle or x.com/yourhandle). For list mode, open the list on Twitter and copy its URL.
- Check your page's color theme: Note whether your page uses a light background or a dark background. You will need to match the embed theme to your page design — light page gets light embed, dark page gets dark embed.
How to add the Twitter / X block to your page
- Open the page editor: Log in to your UniLink dashboard, select the page you want to edit, and click Edit.
- Add the Twitter / X block: Click the Add Block button (the + icon) to open the block picker. Find the Twitter / X block — it may be listed under Social or Embed. Click it to add it to your page. The block will appear at the bottom of your current block list.
- Select the embed mode: In the block settings panel on the right, choose Single Tweet, Timeline, or Twitter List from the Mode dropdown. The settings below the dropdown will change depending on which mode you select.
- Paste the URL: In the URL field, paste the tweet URL, profile URL, or list URL you copied earlier. The block will fetch a live preview shortly after you paste it — wait a moment for the embed preview to appear in the editor.
- Set the theme: Choose Light or Dark from the Theme dropdown. Match this to your page background. If your page uses a dark design, set the embed to Dark. If your page uses a white or light background, set it to Light.
- Configure timeline-specific settings (Timeline mode only): Set the number of tweets to show (1–10). Toggle Show Media on or off depending on whether you want images and videos to appear inline. Toggle Show Retweets on or off — for most creators, off is the right call unless your curated retweets are core to your brand.
- Set the height limit (optional): If the embed is growing too tall — especially in timeline mode with multiple tweets — use the height limit field to cap it at a fixed pixel value. A height of 500–600px is a reasonable starting point for a feed embed that does not dominate the page.
- Drag the block to the right position: Move the block to where you want it on the page. For most creators, placing it below the header and any primary CTA buttons, but above secondary link blocks, works well.
- Save and preview: Click Save, then check the mobile preview. Twitter embeds can be wider than expected on narrow screens — confirm the embed fits cleanly inside the page width before publishing.
Key settings explained
| Setting | What it controls | Best practice |
|---|---|---|
| Mode | Determines whether the block shows a single tweet, a user timeline feed, or a Twitter list | Single tweet for featured content; Timeline for active creators; List for curated topic feeds |
| URL | The source tweet URL, profile URL, or list URL that the embed pulls content from | Always copy from the browser address bar on the actual tweet or profile page — avoid shortened links |
| Theme | Sets the embed's color scheme to Light or Dark, independent of the page design | Always match to your page background — mismatched themes are visually jarring and look like errors |
| Number of tweets (Timeline) | Controls how many tweets appear in the feed, from 1 to 10 | 3–5 tweets is enough to show activity without overwhelming the page; more than 7 usually pushes other blocks too far down |
| Show media (Timeline) | Toggles whether images and videos in tweets render inline in the feed | On if your tweets include strong visual content; Off if your tweets are text-heavy and media previews add visual noise |
| Show retweets (Timeline) | Controls whether retweets from the account appear in the embedded feed | Off for almost all creators — visitors see your page to see your content, not content you have shared from others |
| Height limit | Caps the maximum pixel height of the embed, adding a scrollbar inside the widget if content exceeds the limit | Set to 500–600px for timeline mode to prevent the embed from taking over the page; leave uncapped for single tweet |
| Block title (optional) | Adds a label above the embed such as "My latest tweets" or "Follow me on X" | A short label helps visitors understand what they are looking at; skip it if the embed is self-evident |
Getting the most from the Twitter / X block
The Twitter / X block works best when it serves a specific purpose on the page rather than being added as a reflex. The most common mistake is setting up a timeline embed and leaving it on autopilot. That can work if you post consistently and the content is high quality — but for most creators, a curated single tweet or a tightly controlled timeline produces better results than a raw feed. Think about what a first-time visitor will see when they land on your page. If the most recent tweet in your timeline is a complaint about your internet provider or a throwaway hot take from three days ago, that is what your page now leads with.
For journalists, opinion writers, and finance or crypto creators who post frequently and whose tweets are the product, the timeline feed is the right call. These creators typically post multiple times per day, and the feed acts as a live content stream that gives visitors an immediate sense of their voice and posting cadence. If you are in this category, set tweets to show 5–7, enable media if you post charts or images, and consider placing the embed near the top of the page — right below the header block and any primary link buttons.
The dark mode setting deserves more attention than it usually gets. Twitter's native embed has a noticeably polished dark theme. If your UniLink page uses a dark color scheme, the dark embed blends in seamlessly and feels like an integrated part of the page design. On a light page, the same dark embed looks like a widget that was dropped in from a different website. This is a one-toggle change that has a disproportionate effect on how professional the page looks. Always match them.
Height matters more in timeline mode than most people realize. An uncapped timeline with 10 tweets can easily run 1,200–1,500 pixels tall on desktop, pushing every block below it completely off-screen on the first load. Unless the Twitter feed is the sole purpose of the page, cap it at 500–600px and let visitors scroll inside the widget. The other blocks on your page — your links, products, contact info — should not be buried because Twitter got too much vertical space.
Troubleshooting common issues
| Problem | Likely cause | Fix |
|---|---|---|
| Embed shows a blank space or loading spinner that never resolves | The Twitter account is protected, the tweet has been deleted, or the URL is incorrect | Open the URL in a private browser window without logging in — if the content is not visible there, it cannot be embedded |
| Timeline shows posts from other accounts, not yours | Show Retweets is enabled and the account retweets frequently | Toggle Show Retweets off in the block settings |
| Dark embed on a light page looks out of place | Theme is set to Dark but the page design uses a light background | Change the embed Theme to Light to match the page |
| Embed loads slowly and visitors see a blank block on first visit | Twitter's widget JavaScript loads from Twitter's servers and can be slow on first render | This is expected behavior — UniLink lazy-loads the widget to avoid blocking the rest of the page; no fix needed, but consider placing the embed lower on the page so content above it loads first |
| Embed is much wider than the page and causes horizontal scroll | Twitter's widget can overflow its container on some page layouts | Set a height limit, which also constrains width behavior, or move the block to a single-column layout section |
| Timeline shows an old tweet at the top instead of recent posts | Twitter's oEmbed API sometimes caches results for a short period | Wait 15–30 minutes and refresh; the feed updates from Twitter's servers and cache will clear |
| Block title says "Twitter" but you want "X" | Default label uses the legacy brand name | Edit the optional block title field manually and type whatever label you prefer |
Best fit for
- Creators who are active on X/Twitter and post multiple times per week — the timeline feed gives live social proof
- Journalists, opinion leaders, and finance or crypto creators whose tweets are the core of their content output
- Anyone with a high-engagement tweet they want to surface as featured content on their bio page
- Creators who run Twitter threads and want to embed the thread opener as a conversion element
- Pages targeting audiences who are active Twitter users and find the native embed format familiar and trustworthy
Not the right tool if
- Your Twitter account posts irregularly or has low engagement — a sparse feed with old, low-interaction tweets signals inactivity rather than authority
- Your page already has many blocks and is long — an uncapped timeline embed will bury everything below it
- Your audience is primarily on platforms where Twitter has little cultural relevance (some niches and regions) — a YouTube or Instagram block may drive more meaningful engagement
- The account you want to embed is protected — there is no way to embed content from private accounts
Frequently asked questions
Do I need a Twitter API key or developer account to use the Twitter / X block?
No. UniLink uses Twitter's native oEmbed endpoint, which is the same mechanism that powers tweet embeds across the web on news sites, blogs, and forums. You only need the public URL of the tweet, profile, or list you want to embed. There is no API key setup, no developer account, and no token to manage. If the content is publicly visible on Twitter, it can be embedded.
Can I embed tweets from someone else's account, not my own?
Yes. The URL field accepts any public tweet or public profile URL, not just your own. This can be useful for embedding a mention, a testimonial tweet, a press mention, or the feed of a Twitter list you manage. If you want to embed a tweet that mentions your product or business positively, single tweet mode with someone else's tweet URL works the same way as embedding your own.
Why does the embed show a "Tweet not found" or "This tweet is unavailable" message?
This happens when the tweet has been deleted by its author, the account has been suspended, the account has been switched to protected mode after the embed was set up, or the URL in the block settings points to an incorrect or incomplete link. Open the URL directly in a browser to verify the tweet still exists and is publicly visible. If the tweet has been deleted or the account has gone private, you will need to update the block with a different URL.
Will the timeline embed automatically update when I post new tweets?
Yes. The timeline embed pulls content live from Twitter's servers each time a visitor loads your page, so new tweets appear automatically without any action on your part. There can be a short caching delay — a tweet posted in the last few minutes may not appear immediately — but within 15–30 minutes your feed reflects your latest posts. You do not need to update or re-save the block after publishing new tweets.
Can I have both a single featured tweet and a timeline feed on the same page?
Yes. You can add multiple Twitter / X blocks to a single page. A common pattern is to place a single tweet block near the top of the page to feature a high-performing or relevant post, then add a timeline block lower on the page for visitors who want to explore more content. Each block is configured independently, so they can have different modes, different URLs, and different themes — though keeping the themes consistent is strongly recommended for visual cohesion.
- The Twitter / X block has three modes — single tweet, timeline, and Twitter list — and the right mode depends on whether you want to feature one post or show ongoing activity.
- No API key is needed: any public tweet, profile, or list URL works out of the box via Twitter's native oEmbed.
- Always match the embed theme (Light or Dark) to your page background — this one setting has an outsized effect on how polished the page looks.
- Turn off Show Retweets in timeline mode unless your curated shares are a deliberate part of your brand — otherwise your page fills with other people's content.
- Cap the timeline height at 500–600px to prevent the embed from pushing your other blocks off-screen for first-time visitors.
Active on Twitter / X? Build your UniLink page for free and put your best tweets front and center — no code, no API keys required.
Create Your Free Link-in-Bio Page
Join thousands of creators using UniLink. 40+ blocks, analytics, e-commerce, and AI tools — all free.
Get Started Free