How to embed X (Twitter) timeline on your website
X (Twitter) timeline is your X timeline or a specific post embedded on your site, used by commentators, consultants, journalists and businesses active on X. Here's how to put it on your own website, which embed option to pick, and what goes wrong.
Quick answer
Get the code from X's publish tools for timelines, or the share menu on an individual post for a single-post embed. For most people the right choice is the timeline embed — a scrolling widget of your recent posts. Paste it into a code or embed block on your site — not a plain text field — then place it beside your main call to action and test the whole flow on a phone before relying on it.
X (Twitter) timeline: which option to use
| Option | What it does |
|---|---|
| Timeline embed | A scrolling widget of your recent posts. |
| Single post embed | One post, which is usually the better choice. |
| Follow button | A minimal button with no feed. |
Step-by-step
- 1
Find the code or link in your account
X (Twitter) timeline keeps this in X's publish tools for timelines, or the share menu on an individual post for a single-post embed. Copy what you need before touching your website — most of the time people lose is spent hunting for the snippet, not installing it.
- 2
Pick the right option for the job
The table above is the decision. Timeline embed: A scrolling widget of your recent posts. Single post embed: One post, which is usually the better choice. Choosing before you paste saves rebuilding the section later.
- 3
Paste it into a code or embed block
This needs an HTML, code or embed block — not a plain text field, where the code will simply appear as text on your page. On Adviita, ask the AI editor to add an embed section and drop the code in. On WordPress use a Custom HTML block, on Squarespace a Code block (Business plan or above), and on Wix an Embed HTML element.
- 4
Put it where the decision happens
Embedded social content is decoration unless it earns its place — it costs page speed, so make it count. A widget three scrolls down does a fraction of the work of the same widget beside your main call to action. Decide what the page is for, then place it at the point the visitor is deciding.
- 5
Check it on an actual phone
Most visitors to a small business website arrive on a phone, and embeds are where mobile layouts break. Open your live site on your own phone and confirm it loads, fits the screen without sideways scrolling, and does not push your contact button out of view. Third-party embeds are also the most common cause of a slow page, so if it noticeably delays loading, consider a plain link instead.
- 6
Test it end to end before you rely on it
Run through the whole flow yourself as a customer would — confirm it renders and links correctly — and confirm what should happen actually happens. Broken embeds fail silently, and the first person to notice is usually a customer who has already given up.
Tips & best practices
- ▸X's embed and API behaviour has changed repeatedly and without notice. Timeline embeds have broken more than once — do not build a critical page section on one.
- ▸A single post embed is far more robust than a timeline and usually more useful anyway.
- ▸The embed script sets cookies and is a consent consideration.
- ▸Re-test the embed after any change to your site, your plan, or the connected account — third-party widgets break quietly and nothing tells you.
Common questions
How do I embed a post from X on my website?
+−
Open the post, use its share menu and choose the embed option, then copy the generated code and paste it into a code block on your site. Single posts are considerably more reliable than timeline embeds, which have broken repeatedly as X has changed its platform.
Are X timeline embeds reliable?
+−
Less than they used to be. Access rules have changed several times, and timeline widgets have broken without warning more than once. If the content matters, quote the post as text with a link, or screenshot it — both survive platform changes that break embeds.
Do I need a developer to add X (Twitter) timeline to my site?
+−
No. Every option here is copy and paste into a code or embed block, which every mainstream website builder provides. The only genuine blocker is a builder or plan that does not allow custom code at all — Squarespace, for instance, requires a Business plan or above for code blocks.
Will adding X (Twitter) timeline slow down my website?
+−
Any third-party embed has some cost, because it loads code from another company's servers. One is usually unnoticeable; four or five on the same page is where small business sites become visibly slow. If page speed matters to you, prefer a plain link over a script wherever the option exists, and keep embeds to the pages that genuinely need them.