How to Add Twitter/X Feed Widget to Any Website (2026 Guide)

Twitter became X, the API changed twice, embed features disappeared and reappeared, and URLs switched from twitter.com to x.com — yet embedding a real-time X feed on your website remains one of the most effective ways to showcase social proof, demonstrate active engagement, and keep your site feeling current.

The challenge in 2026 isn't whether to embed X content — it's navigating the platform's ongoing changes while implementing a feed that actually works, looks professional, and serves a business purpose beyond just "we're on social media."

This guide covers the complete landscape: why X feeds work differently than Instagram or LinkedIn, how the Twitter-to-X rebrand affects embed implementation, the real differences between API v2 and deprecated v1.1 endpoints, strategic use cases for different feed types, and performance considerations for real-time content.

Why X (Twitter) Feeds Still Matter in 2026

Despite platform turbulence, name changes, and shifting API policies, X remains the real-time information network. When news breaks, industry conversations happen, and trending topics emerge, they happen first on X. For businesses, this creates unique opportunities that image-focused platforms like Instagram or professional networks like LinkedIn can't replicate.

Real-time credibility. An embedded X feed shows your brand is active, responsive, and engaged with current conversations. A feed displaying posts from today — or this hour — signals that real people are managing your social presence right now, not that you set something up six months ago and forgot about it.

Thought leadership and industry positioning. X is where industry commentary, analysis, and expertise get shared in real time. When you embed your X feed on your website, you're showcasing your company's voice, insights, and positioning within your industry. For B2B companies, professional services, and thought leaders, this builds authority in ways product photos never will.

Live event coverage. Conferences, product launches, webinars, breaking news responses — X excels at real-time event coverage. An embedded X feed showing live tweets from your company event creates FOMO, demonstrates scale, and gives remote audiences a way to participate. This works especially well for event social walls.

Customer support transparency. Some brands embed their X customer support timeline on help pages to demonstrate response speed and public accountability. When potential customers see your support team responding to questions publicly and quickly, it builds confidence before they even reach out.

The Twitter-to-X Rebrand: What Changed for Embeds

When Twitter rebranded to X in 2023, it wasn't just a logo change — URLs, API endpoints, and embed functionality all evolved. Understanding these changes prevents broken implementations and wasted time troubleshooting.

URL Changes: twitter.com vs x.com

The most visible change: URLs shifted from twitter.com to x.com. For embedded timelines, this created a caching problem. According to developer troubleshooting guides, embeds pointing to old twitter.com URLs can fail when cached data becomes stale. The fix: re-generate embed codes using current x.com URLs.

For most users, this means updating bookmarks, saved embed codes, and documentation. For developers working with the API, it means ensuring your application handles both URL formats gracefully during the transition period.

API Evolution: v1.1 Deprecation and v2 Adoption

X has been migrating from Twitter API v1.1 to X API v2 since 2020, but the transition accelerated post-rebrand. The official migration guide outlines key differences that affect timeline embeds:

Default fields changed. API v1.1 returned many fields by default (tweet text, user info, timestamps, engagement metrics). API v2 returns only tweet ID and text by default — you must explicitly request additional fields using fields and expansions parameters. This means third-party widgets built for v1.1 may show less information until updated for v2.

Authentication requirements tightened. V2 endpoints require credentials from a developer App associated with a Project. V1.1 allowed standalone Apps. For most users relying on third-party widgets, this doesn't matter — but if you're building custom integrations, you'll need to set up Projects in the developer portal.

Rate limits and quotas adjusted. V2 introduced tiered access (Free, Basic, Pro, Enterprise) with different rate limits per tier. Free tier access is extremely limited; most businesses need at least Basic tier for reliable timeline embeds.

Embed Feature Changes

X deprecated the grid-style embedded collections layout in 2023, focusing on timeline embeds instead. This means if your website used grid-based X embeds, they likely broke and need to be replaced with timeline-style widgets.

Some customization options also vanished. The data-border-color and data-link-color parameters no longer work in native X embeds, reducing branding flexibility. Third-party widgets fill this gap by offering full color and style customization.

Feed Types: User Timeline vs Hashtag vs List vs Search

X offers multiple feed types, each serving different strategic purposes. Choosing the right type determines whether your embedded feed drives value or just clutters your website.

User Timeline (Profile Feed)

Displays all public posts from a specific X account in chronological order. This is the most common implementation — your company's X timeline embedded on your website.

Best for: Showcasing your brand voice, thought leadership content, company updates, and regular social activity. Works well on homepages, about pages, and blog sidebars.

Limitation: You only see content from one account. If you want to aggregate content from employees, partners, or customers, you need a different feed type.

Hashtag Feed

Aggregates posts from anyone using a specific hashtag. Perfect for campaigns, events, and user-generated content.

Best for: Live events (conference social walls, product launches), branded campaigns (#YourBrandChallenge), and community engagement.

Limitation: Public hashtags attract spam, off-topic posts, and occasionally inappropriate content. You MUST implement moderation. Manual approval or keyword filtering is non-negotiable for public hashtag feeds. According to best practices guides, unmoderated hashtag feeds on business websites inevitably display something you don't want.

List Feed

Displays posts from members of an X List you've created. This lets you curate a feed from multiple accounts — employees, industry leaders, partners, customers.

Best for: Employee advocacy feeds (all team members' posts in one place), industry news aggregation (thought leaders you follow), or partner showcase feeds.

Limitation: Requires manual list curation. As you add or remove people from the List, the embedded feed updates automatically, but you need to actively maintain the List itself.

Search Results Feed

Displays posts matching a search query — keywords, mentions, or combinations.

Best for: Brand mention monitoring (showing when others talk about you), industry conversation tracking, or topic-specific aggregation.

Limitation: Search results can be noisy and require aggressive moderation. Like hashtag feeds, you risk displaying off-brand or negative content unless you filter carefully.

Implementation Methods: Native vs Plugin vs Widget vs API

There are four primary ways to embed an X feed on your website, each with different tradeoffs in complexity, cost, control, and functionality. According to implementation best practices, most businesses choose based on technical skill and customization needs.

Method 1: Native X Embed (Simplest)

X provides a free official embed tool at publish.x.com. Enter your X profile URL, customize basic settings (dark mode, tweet limit, etc.), and copy the generated code snippet.

Pros: Free, official, instant setup, no third-party dependencies, automatically updated by X.

Cons: Minimal customization (limited color options, no layout control), displays "X" branding prominently, only supports basic timeline embeds (no advanced filtering or moderation), limited to 20 most recent posts.

Best for: Quick implementations, personal websites, or situations where budget is zero and basic functionality is enough.

Method 2: CMS Plugin (WordPress, etc.)

If your website runs on WordPress, Shopify, Wix, or Squarespace, plugins/extensions exist specifically for X feed embedding. These typically wrap the native X embed with additional customization options and easier installation.

Pros: No-code installation, platform-specific optimization, often include caching to improve performance.

Cons: Still limited by native X embed constraints, plugin quality varies widely, some charge subscription fees for premium features, may conflict with other plugins.

Best for: Non-technical users on popular CMS platforms who need slightly more control than native embeds provide.

Method 3: Third-Party Widget (Most Common)

Social media aggregation tools like Tagembed, Curator, EmbedSocial, and CollectSocials (coming soon) offer X feed widgets with extensive customization, moderation tools, and multi-platform support.

Pros: Full design control (colors, fonts, layouts, spacing), moderation workflows (approve/reject posts, keyword filters), multi-platform feeds (combine X with Instagram, LinkedIn, etc.), analytics and engagement tracking, responsive design handled automatically, Shadow DOM isolation prevents CSS conflicts.

Cons: Subscription cost (typically $19-99/month depending on features and volume), requires trusting third-party with your social data (though they only access public posts).

Best for: Businesses that need professional presentation, brand control, content moderation, and are willing to pay for quality tools. According to Curator's implementation guide, this is the approach most agencies and established brands choose.

Method 4: Custom API Integration (Most Complex)

Build your own X feed implementation using the X API v2. Fetch tweets programmatically, store them in your own database, and render them however you want on your website.

Pros: Complete control over functionality, data storage, presentation, and integration with other systems. No monthly widget fees (just API access costs). Can build custom features impossible with pre-built widgets.

Cons: Requires developer resources, ongoing maintenance (API changes, authentication refreshes, rate limit management), responsible for security and compliance, time-intensive to build and maintain. X API access costs money at scale (Free tier is extremely limited; most businesses need Basic tier minimum at $100/month).

Best for: Large enterprises with development resources, products that deeply integrate X data, or situations where widget solutions can't meet specific requirements.

Step-by-Step: Embedding an X Feed (Third-Party Widget Method)

The most practical approach for most businesses is using a third-party widget tool. Here's the complete implementation process using this method.

Step 1: Choose Your Widget Provider

Select a social media aggregation tool that supports X feeds. Options include Taggbox, Tagembed, EmbedSocial, Curator, and CollectSocials (coming soon for X). Most offer free trials — test before committing.

Step 2: Connect Your X Account

Authenticate your X account via OAuth within the widget platform. This grants the tool read-only access to your public posts (and any other public posts you want to aggregate, like hashtags or mentions).

You'll need to log in with X credentials and authorize the application. The tool receives an access token it uses to fetch your timeline data via the X API. No passwords are stored; you can revoke access anytime through X's app permissions page.

Step 3: Configure Your Feed Source

Select what content to display:

• Your own X timeline (user feed)
• A specific hashtag (#YourBrand)
• An X List you've created
• Search results for keywords or mentions

For hashtag, list, or search feeds, set up initial moderation rules: keyword blacklists, manual approval workflows, minimum engagement thresholds (only show posts with 5+ likes).

Step 4: Design Your Widget

This is where third-party tools shine. Customize:

• Layout: Grid, carousel, list, masonry, waterfall — choose what fits your page design
• Theme: Colors, fonts, borders, shadows, spacing to match your brand
• Display options: Show/hide timestamps, engagement counts (likes, retweets, replies), profile images, post actions (like, reply, retweet buttons)
• Dark mode support: Toggle for sites with dark themes

Step 5: Set Refresh Frequency

Decide how often your feed updates. For real-time content (live events, breaking news), refresh every 1-5 minutes. For general brand presence, 15-60 minutes is usually sufficient. More frequent refreshes consume more API quota and can impact performance, so balance timeliness against resource usage.

Step 6: Generate Embed Code

Once your widget is designed and configured, generate the embed code — typically a single <script> tag. Copy this code and paste it into your website wherever you want the X feed to appear.

For WordPress: use a Custom HTML block. For Shopify: add to a Custom Liquid section. For Webflow: use an Embed element. For Wix: use an HTML iframe widget. The code works on any platform that allows custom HTML/JavaScript.

Strategic Placement: Where X Feeds Work Best

X feeds serve different purposes than Instagram or YouTube embeds. The content is text-heavy, often time-sensitive, and focused on conversation rather than visual appeal. This affects where they work best on your website.

Homepage (below the fold, sidebar): An X feed showing recent company posts works well near the bottom of a homepage or in a sidebar. It demonstrates social activity without competing with your primary conversion elements. Keep it compact — 3-5 recent posts maximum.

Blog and resources section (sidebar): A sidebar X feed on blog pages keeps content feeling current and can surface related commentary or discussions happening in real time. This works especially well for news sites, industry blogs, and thought leadership platforms.

About page (featured): Employee X feeds or company culture posts humanize your brand on About pages. A curated List feed showing posts from team members gives visitors a sense of who you are beyond corporate copy.

Events and conferences (prominent display): Live event hashtag feeds belong front and center on event pages or physical displays. Showing real-time posts from attendees creates FOMO, demonstrates event scale, and encourages participation. This is one of the strongest use cases for embedded X feeds. See our social media wall for events guide.

Support pages (transparency): Some brands embed their customer support X timeline on help pages to showcase response times and public accountability. When visitors see support questions answered publicly and quickly, it builds confidence before they reach out.

Landing pages (almost never): X feeds distract from singular conversion goals. If your landing page is designed to drive one specific action — sign up, purchase, download — adding an X feed gives visitors somewhere else to look and often hurts conversion rate.

X Feed Moderation: What You Can't Ignore

Unlike Instagram where most embedded content is visual and relatively safe, X content is text-based, conversational, and sometimes controversial. Moderation isn't optional — it's essential for maintaining brand safety.

Why Moderation Matters More for X

Reply culture: X posts often include replies that can be negative, off-topic, or inappropriate. Embedding a timeline means potentially displaying those replies unless you filter them out.

Hashtag hijacking: Hashtag feeds are especially vulnerable. Public hashtags get used by spammers, trolls, and unrelated conversations. An unmoderated hashtag feed on a business website will eventually display something you don't want.

Political and controversial content: X is where political discussions, controversial opinions, and heated debates happen. Even if your brand stays neutral, a search feed or hashtag feed can surface politically charged content unless you actively filter it.

Moderation Strategies

Keyword blacklists: Automatically hide posts containing specific words or phrases. Most widget tools provide this feature. Build a comprehensive blacklist of profanity, competitor names, and off-brand terms.

Manual approval: For hashtag or search feeds, enable manual approval so every post requires review before appearing on your website. This is labor-intensive but provides maximum control.

Engagement thresholds: Only show posts with minimum engagement (5+ likes, 2+ retweets). This filters out spam and low-quality content automatically.

Hide replies and retweets: Configure your feed to show only original posts, not replies or retweets. This reduces clutter and minimizes risk of displaying inappropriate responses.

Review regularly: Even with automated filters, schedule weekly reviews of your embedded X feed to catch anything that slipped through and refine your moderation rules.

Combining X with LinkedIn for B2B Presence

For B2B companies, professional services, and thought leaders, combining X feeds with LinkedIn feeds creates a powerful multi-platform presence.

X excels at real-time commentary, industry news reactions, quick insights, and conversational engagement. LinkedIn excels at long-form thought leadership, professional credibility, and formal business updates.

A unified social media wall combining both platforms shows different dimensions of your expertise: X demonstrates you're actively engaged with current conversations; LinkedIn demonstrates deep expertise and professional standing.

Implementation: Use a multi-platform aggregation tool that supports both X and LinkedIn. Create separate feeds or combine them into one unified wall. Display prominently on About pages, resource sections, or blog sidebars.

Performance Considerations

X feeds are text-heavy rather than media-heavy, which means they're generally lighter than Instagram or YouTube embeds. However, real-time updates and frequent refreshes can still impact performance if not implemented carefully.

Caching: Widget tools typically cache X content for a few minutes before refreshing. This reduces API calls and improves load times. According to performance optimization guides, caching intervals of 5-15 minutes balance freshness with performance.

Lazy loading: Load the X feed widget only when it's about to enter the viewport, not immediately on page load. This prevents the feed from blocking more critical above-the-fold content. Good widget tools handle this automatically via Intersection Observer.

Limiting post count: Don't display 100+ posts in your embedded feed. Show 10-20 recent posts with a "Load More" option if visitors want additional content. Loading too many posts at once increases page weight and slows rendering.

Measuring What Matters

An embedded X feed generates multiple types of engagement data, but not all of it matters for business decisions. Focus on metrics that connect to your goals.

Click-through rate to X profile: What percentage of visitors who see your X feed click through to your X profile? This indicates whether the content is compelling enough to drive further engagement. High CTR to X can be positive (brand awareness) or negative (visitors leaving your site prematurely) depending on page goals.

Time on page impact: Do visitors who engage with your X feed spend more time on your website overall? Segment users in Google Analytics by whether they interacted with the feed. If engagement correlates with longer sessions, the feed is working.

Post performance: Which types of X posts get the most engagement when embedded on your website? Use this data to inform your X content strategy — double down on what resonates.

Conversion impact: The ultimate test: do visitors who interact with your X feed convert at higher or lower rates? Track this by setting up custom events in GA4 for X feed interactions and comparing conversion rates between segments.

For more on social feed analytics, see our guide on measuring what actually matters.

Common Mistakes and How to Avoid Them

After analyzing hundreds of embedded X feeds, several failure patterns emerge consistently.

Mistake 1: No moderation on hashtag feeds. Public hashtags attract spam and off-topic content. Always moderate. Set up keyword filters and manual approval for hashtag-based feeds.

Mistake 2: Using old twitter.com URLs. After the rebrand, embeds with cached twitter.com URLs can break. Use current x.com URLs when generating embed codes.

Mistake 3: Embedding too many feeds. Multiple X feeds on one page create visual clutter and confuse visitors. One well-placed feed is better than three competing feeds.

Mistake 4: Ignoring dark mode. If your website offers dark mode, your X feed widget should too. Mismatched light/dark modes look unprofessional and hurt user experience.

Mistake 5: Set it and forget it. X content cycles fast. A feed showing posts from a campaign that ended two months ago signals inactivity. Review your feed monthly to ensure it still represents your current brand and messaging.

Final Thoughts

Embedding an X feed on your website isn't about jumping on a trend or checking a box — it's about showcasing real-time social proof, demonstrating active engagement with your industry, and keeping your website feeling current without constant manual updates.

The platform may have changed names, the API may have evolved, and embed features may have shifted, but the core value remains: X is where real-time conversations happen, and bringing those conversations to your website builds credibility and trust.

Done correctly, an embedded X feed becomes a genuine asset: fresh content that updates automatically, thought leadership that positions your brand, and social proof that builds confidence. Done poorly — without moderation, without strategic placement, without design coherence — it becomes noise that distracts from your core message.

The difference comes down to intention. Know why you're embedding X content, choose the right feed type for your goals, implement proper moderation, design it to match your brand, place it where it serves a purpose, and measure whether it actually contributes to business outcomes.

Sources

• Timelines standard v1.1 to v2 migration guide - X Developer Platform
• Working with timelines - X Developer Platform
• How to Embed a Twitter Feed in HTML - EmbedSocial
• How to Embed Your Twitter (X) Feed on Your Website - Curator
• How to Fix Twitter Embeds Not Working on Your Website - Smash Balloon
• How to Embed a Twitter Hashtag Feed on Your Website - Smash Balloon
• How To Embed Twitter Feed On Website in 2026 - Taggbox