10 hours ago
To add a Twitter feed to Wix, generate a timeline embed through X Publish or a compatible feed tool, then paste the code into an Embed HTML element in Wix. Resize the element, check the mobile version and test the published page on a phone. The mobile check matters because the feed sits inside an iframe—a separate window within your page—and its content may not fit simply because the surrounding Wix layout does.
For a straightforward public profile feed, start with X’s own embed. You do not need to build an API integration for this method. The main work is choosing the correct timeline, giving it enough space and confirming that visitors can actually view and scroll through it.
Generate the feed’s embed code
Open X Publish and enter the URL of the public profile you want to display. Choose Embedded Timeline when offered, adjust the available appearance settings and copy the complete code. Use the profile URL for a feed; a URL pointing to one specific post creates a different type of embed.
X’s documentation lists two supported timeline types: profiles and public lists. Protected posts are excluded, so an account’s visibility is worth checking before troubleshooting the website.
Choose a height that suits the feed’s role on the page. A compact updates section should not dominate the entire mobile experience, while a dedicated news page can give the timeline more room. Treat the initial height as a starting point: you will need to judge it alongside your headings, page spacing and neighbouring content.
If you need to review posts before displaying them or customise the feed’s layout, Taggbox Twitter Feed widget is another option. You can collect content, moderate the selection, customise its appearance and generate an embed code. Check the available sources, refresh frequency and plan limits against your requirements before choosing this route. You will still need to test the finished widget inside Wix’s container.
Add the feed to your Wix page
In the standard Wix Editor, open the page where the feed belongs and follow these steps:
Choose the HTML option for generated embed code; the Embed a site option is intended for an external website address. Pasting an ordinary X profile URL into that field is not a substitute for installing the timeline snippet.
Keep the supplied script and markup together. Copying only the profile link can leave you with a clickable text link rather than a rendered feed. Also, avoid placing the snippet in a normal text box: it needs the HTML embed element to run as intended.
In Wix Studio, add an Embed code element from the Add Elements panel and enter the snippet there. After inserting it, inspect its sizing at your desktop, tablet and mobile breakpoints rather than following the standard Editor’s mobile-only workflow.
Fit the feed and its container separately
There are two sizes to consider: the space Wix allocates to the embed and the dimensions of the content inside it. Making the outer box wider does not necessarily remove a fixed width in the embedded content. Similarly, increasing the timeline’s height without enlarging its Wix container can leave part of the feed clipped.
Wix confirms that oversized content can be cut off or show scrollbars inside an HTML iframe. Start by checking whether the outer element is too narrow or too short, then review the settings used to generate the feed. Changing both at once makes it harder to identify which adjustment solved the problem.
For embed snippets that contain an explicit inner iframe, Wix suggests percentage dimensions where fixed pixel values cause cropping. However, setting height="100%" means filling the existing container; it does not make that container automatically grow to the full length of a feed. Do not add iframe attributes to unrelated parts of X’s generated snippet.
A useful distinction is between deliberate timeline scrolling and accidental overflow. A feed with its own vertical scroll area can be perfectly usable. A second scrollbar around that feed, clipped controls or sideways scrolling usually means the inner content and outer frame need better alignment. Try scrolling with a thumb: visitors should be able to move through the feed and continue down the page without repeatedly getting stuck inside it.
Check the mobile layout on the published page
Switch to the mobile view in Wix Editor and locate the embed. Confirm that it is visible, positioned beneath the correct heading and contained within the page width. Adjust its dimensions and the surrounding spacing, then publish your changes. The editor preview is useful for arranging the page, but the live version is where you should assess loading, links and touch behaviour.
Use a real phone where possible, and supplement it with browser device emulation. For example, checking widths of 360, 390 and 430 CSS pixels can expose problems that one preview size misses. These are practical test widths, not required Wix settings. Pay particular attention to longer posts, images and quoted content because they can make sizing problems easier to spot.
Work through the following checks on the live page:
The signed-out check deserves its own test. A feed working in your usual browser does not establish that every visitor sees the same thing. If the timeline displays an error or login prompt, changing its width will not resolve that access problem. Keep a clearly labelled link to your X profile outside the embed so visitors have an alternative route.
If the desktop embed cannot be made usable on mobile, Wix recommends hiding it on mobile and adding a mobile-friendly alternative. In the standard Editor, elements added through the mobile editor are mobile-only, and the code inside a desktop HTML element cannot be edited directly from that mobile editor. Make code changes in the desktop editor, or create a separate mobile embed when genuinely necessary.
Diagnose a blank or broken feed before rebuilding it
If the feed is blank, first check that the source account is public and that you copied the entire current snippet from X Publish or your feed provider. Compare the published page with the editor preview, then test in another browser. If it works only in one environment, browser extensions, privacy settings or consent controls may be affecting the external script; treat those as diagnostic clues rather than assuming the Wix layout is responsible.
If the feed loads but looks wrong, focus on dimensions instead. Clipped content calls for checking the frame size, while excess space calls for inspecting both the embed height and the surrounding section. When posts appear but seem outdated or incomplete, verify the source and any provider settings before altering the page design. Layout adjustments cannot correct the content delivered by an external service.
Finally, reload the published page on a mobile connection and watch what happens before the feed appears. Keep essential information—such as opening hours, event details or important announcements—in ordinary Wix content as well. The timeline can support those updates, while the page remains useful if the external feed is delayed or unavailable.
For a straightforward public profile feed, start with X’s own embed. You do not need to build an API integration for this method. The main work is choosing the correct timeline, giving it enough space and confirming that visitors can actually view and scroll through it.
Generate the feed’s embed code
Open X Publish and enter the URL of the public profile you want to display. Choose Embedded Timeline when offered, adjust the available appearance settings and copy the complete code. Use the profile URL for a feed; a URL pointing to one specific post creates a different type of embed.
X’s documentation lists two supported timeline types: profiles and public lists. Protected posts are excluded, so an account’s visibility is worth checking before troubleshooting the website.
Choose a height that suits the feed’s role on the page. A compact updates section should not dominate the entire mobile experience, while a dedicated news page can give the timeline more room. Treat the initial height as a starting point: you will need to judge it alongside your headings, page spacing and neighbouring content.
If you need to review posts before displaying them or customise the feed’s layout, Taggbox Twitter Feed widget is another option. You can collect content, moderate the selection, customise its appearance and generate an embed code. Check the available sources, refresh frequency and plan limits against your requirements before choosing this route. You will still need to test the finished widget inside Wix’s container.
Add the feed to your Wix page
In the standard Wix Editor, open the page where the feed belongs and follow these steps:
- Select Add Elements → Embed Code → Popular Embeds.
- Choose Embed HTML.
- Select the new element and click Enter Code.
- Paste the complete timeline snippet and click Apply.
- Position and resize the element, then preview the page.
Choose the HTML option for generated embed code; the Embed a site option is intended for an external website address. Pasting an ordinary X profile URL into that field is not a substitute for installing the timeline snippet.
Keep the supplied script and markup together. Copying only the profile link can leave you with a clickable text link rather than a rendered feed. Also, avoid placing the snippet in a normal text box: it needs the HTML embed element to run as intended.
In Wix Studio, add an Embed code element from the Add Elements panel and enter the snippet there. After inserting it, inspect its sizing at your desktop, tablet and mobile breakpoints rather than following the standard Editor’s mobile-only workflow.
Fit the feed and its container separately
There are two sizes to consider: the space Wix allocates to the embed and the dimensions of the content inside it. Making the outer box wider does not necessarily remove a fixed width in the embedded content. Similarly, increasing the timeline’s height without enlarging its Wix container can leave part of the feed clipped.
Wix confirms that oversized content can be cut off or show scrollbars inside an HTML iframe. Start by checking whether the outer element is too narrow or too short, then review the settings used to generate the feed. Changing both at once makes it harder to identify which adjustment solved the problem.
For embed snippets that contain an explicit inner iframe, Wix suggests percentage dimensions where fixed pixel values cause cropping. However, setting height="100%" means filling the existing container; it does not make that container automatically grow to the full length of a feed. Do not add iframe attributes to unrelated parts of X’s generated snippet.
A useful distinction is between deliberate timeline scrolling and accidental overflow. A feed with its own vertical scroll area can be perfectly usable. A second scrollbar around that feed, clipped controls or sideways scrolling usually means the inner content and outer frame need better alignment. Try scrolling with a thumb: visitors should be able to move through the feed and continue down the page without repeatedly getting stuck inside it.
Check the mobile layout on the published page
Switch to the mobile view in Wix Editor and locate the embed. Confirm that it is visible, positioned beneath the correct heading and contained within the page width. Adjust its dimensions and the surrounding spacing, then publish your changes. The editor preview is useful for arranging the page, but the live version is where you should assess loading, links and touch behaviour.
Use a real phone where possible, and supplement it with browser device emulation. For example, checking widths of 360, 390 and 430 CSS pixels can expose problems that one preview size misses. These are practical test widths, not required Wix settings. Pay particular attention to longer posts, images and quoted content because they can make sizing problems easier to spot.
Work through the following checks on the live page:
- Width: Text and media fit without making the page scroll sideways.
- Height: The feed’s controls remain accessible, with no clipped bottom edge or oversized empty area.
- Touch scrolling: You can browse the timeline and then continue to the next page section.
- Links: Profile and post links respond when tapped.
- Loading: The feed does not cover nearby content or leave an unexplained blank section.
- Visitor access: The timeline is usable in a browser session that is not signed into X.
The signed-out check deserves its own test. A feed working in your usual browser does not establish that every visitor sees the same thing. If the timeline displays an error or login prompt, changing its width will not resolve that access problem. Keep a clearly labelled link to your X profile outside the embed so visitors have an alternative route.
If the desktop embed cannot be made usable on mobile, Wix recommends hiding it on mobile and adding a mobile-friendly alternative. In the standard Editor, elements added through the mobile editor are mobile-only, and the code inside a desktop HTML element cannot be edited directly from that mobile editor. Make code changes in the desktop editor, or create a separate mobile embed when genuinely necessary.
Diagnose a blank or broken feed before rebuilding it
If the feed is blank, first check that the source account is public and that you copied the entire current snippet from X Publish or your feed provider. Compare the published page with the editor preview, then test in another browser. If it works only in one environment, browser extensions, privacy settings or consent controls may be affecting the external script; treat those as diagnostic clues rather than assuming the Wix layout is responsible.
If the feed loads but looks wrong, focus on dimensions instead. Clipped content calls for checking the frame size, while excess space calls for inspecting both the embed height and the surrounding section. When posts appear but seem outdated or incomplete, verify the source and any provider settings before altering the page design. Layout adjustments cannot correct the content delivered by an external service.
Finally, reload the published page on a mobile connection and watch what happens before the feed appears. Keep essential information—such as opening hours, event details or important announcements—in ordinary Wix content as well. The timeline can support those updates, while the page remains useful if the external feed is delayed or unavailable.