Please note that the Unrolling Tweet Threads extension of the Twitter block is no longer available due to the discontinuation of our Twitter API access. Learn more about this.
Use the Twitter block to embed tweets into your posts and pages.
Note: You don’t need a Twitter account to use the Twitter block. Only public tweets can be embedded.
Requirements
The Twitter block is available on all Jetpack-connected sites. It is a part of the Jetpack Blocks suite and is activated by default. It does not require a paid upgrade to use. See our Jetpack Blocks article to learn about the available blocks and how to activate them.
Jetpack Blocks require the Block Editor (also referred to as the Gutenberg editor). If you’ve installed the Classic Editor plugin, you have a few options:
- Deactivate the Classic Editor: Go to Plugins → Installed Plugins in your WP Admin and deactivate the Classic Editor plugin.
- Enable both editors: If you prefer flexibility, navigate to Settings → Writing in your WP Admin (not the menu under Jetpack settings). Set Allow users to switch editors to Yes. You will only see these options if you have the Classic Editor plugin installed and active.
Some custom themes or plugins may prevent you from using the Block Editor. In that case, please contact the support team for the plugin or theme for further assistance.
For more details, see Using Blocks and the Classic Editor.
How to add the Twitter block
To add the Twitter block, click on the + Block Inserter icon and search for “Twitter.” Click it to add the block to the post or page.
You can also type /Twitter on a new line, and press enter to quickly add a new Twitter block.
For more, visit our detailed instructions on adding blocks.
Single Tweet
To embed a tweet means that you can display an individual tweet on your site that includes:
- The tweet’s text, images, and links.
- Action buttons for Twitter users to retweet and favorite tweets without leaving your site.
- Links to hashtag pages, usernames, and a follow button.
The quickest way to embed a tweet is to paste the URL of the tweet on an empty line in the editor.
To find the URL, locate the tweet you want to post. Then click the timestamp to open a new page for that individual tweet. Copy the URL from the address bar and paste it onto your Twitter block.
You can also click the down arrow at the top right of the tweet on Twitter to find the Copy Link to Tweet option.

Twitter also has an ‘Embed Tweet’ option with a code. This method is not supported, so make sure to use the link instead.
Here’s how a single tweet looks when embedded:
Twitter feed
You can also use the Twitter block to embed a feed. You can paste the profile URL inside the box and click Embed:

Here is an example of an embedded Twitter feed:
Still need help?
Please contact support. We’re happy to advise.
Jetpack Comments
Integrate social media login options into your comment form with Jetpack Comments.
When someone reads an article on your site and wants to comment, offer them the option of using an existing social networking account to post.
Since it replaces the default WordPress comment form, Jetpack Comments are deactivated by default. To activate them, visit Jetpack → Settings → Discussion on your Dashboard and toggle the Let readers use WordPress.com or Facebook accounts to comment setting.
Please read this article to learn how to turn off WordPress comments altogether.
When activated, Jetpack Comments takes the place of your theme’s comment form. It will look something like this:
Third-party cookies must be enabled for social login
WordPress.com and Facebook login options for Jetpack Comments require third-party cookies to work properly. If WordPress.com and Facebook login options are not available when you enable Jetpack Comments, you can take the following steps to troubleshoot:
Comment form settings
Update your Comment form settings:
Other Settings
Pingbacks and trackbacks
Pingbacks are very similar to trackbacks. Think of pingbacks as a form of remote comment. When you publish a post that contains a link to a post on another person’s pingback-enabled blog, the author of the other post receives a notification that you’ve linked to their post on their blog. The pingback is then displayed on the other post as a link to your post.
Pingbacks can be used as a means to place spam comments on your site. You can follow these steps to completely disable pingbacks on your site:
You can also enable or disable Pingbacks for individual posts via the “Discussion” settings available in the sidebar when creating or editing a post.
Leave a comment
To leave a comment, click in the box and start typing. Once you click in the box, the comment form will expand and there will be options to log in with WordPress.com and Facebook.
If you do not have a WordPress.com or Facebook account or do not want to connect, you can still leave a comment by submitting your email and name. Your email address will never be publicly displayed; only the blog owners and admins will see it.
You can add your website if you would like to, and check a box to indicate you would like to save your email address in your current browser for next time you leave a comment here.
You can also sign up to be notified by email of new comments to the post and of new posts to the blog.
Comment Options
Before you click Post Comment, you have a few checkboxes that you can check:
Once you’ve clicked any checkboxes that you’d like, you can click Post Comment and your comment will either be posted automatically or held for moderation. This is based on the site owners’ settings found under Settings → Discussion → Before a comment appears.
Still need help?
Please contact support. We’re happy to advise.
Privacy Information
Jetpack Comments are deactivated by default. You can activate them at any moment from your WP Admin. To do so:
This features the same data as the core WordPress commenting system: commenter’s name, email address, and site URL (if provided to the comment form), submission date/time, and IP address.
Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.
If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
For toggle activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
This features the same data as the core WordPress commenting system: commenter’s name, email address, and site URL (if provided to the comment form), submission date/time, and IP address.
Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content.
If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
We also track when, and by which user, the feature is activated and deactivated. We also track when, and which, configuration settings are modified.
The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
We sync all data and metadata associated with a user’s comment. We also sync options that identify whether or not the feature is activated and how its available settings are configured.
We sync all data and metadata associated with a user’s comment.