WordPress.com vs WordPress.org: which one for a blog that should rank?

WordPress.com's own support guide puts it in one line: both run on the same software, and "the main difference is hosting." The names cause the confusion. WordPress.org is the home of the open-source project, where the software, the plugin directory and the documentation live, so "WordPress.org" and "self-hosted WordPress" mean the same thing: the software installed on a server you rent, whether from a budget host, a managed WordPress host or your own machine.

What changed on WordPress.com in 2026

Older guides say WordPress.com allows plugins only from its Business plan up. That stopped being true on April 2, 2026, when WordPress.com announced that plugins are "now available on all paid WordPress.com plans, starting with Personal", together with global styles, font uploads and custom CSS. Its plan guide now lists plugin installation on Personal, Premium, Business and Commerce. The free plan still has none: "For free sites, upgrade your plan to install plugins."

That closes most of the old gap. What remains is server access, custom code, price, and who is responsible when something breaks.

WordPress.com vs WordPress.org compared

	WordPress.com	Self-hosted WordPress (WordPress.org)
Software	WordPress, updated for you	WordPress, a free download; you or your host keep it updated
Hosting	Included in every plan, including the free one	Bought separately from a host you choose
Price (October 2026)	Free plan; paid plans billed yearly from $4 a month (Personal), $8 (Premium), $25 (Business) and $45 (Commerce), excluding tax	Software free; you pay for hosting and a domain
Your own domain	From Personal up; annual plans include the first year's registration	Any domain you own
Ads	The free plan shows WordPress.com ads to visitors	None unless you add them
Plugins	Any paid plan; WordPress.com blocks plugins it considers risky	Any plugin, including your own
Custom code, SFTP/SSH, database access	Business and Commerce	Yes, plus control of the PHP environment
Built-in SEO tools and Google Analytics	Premium and up	Through the plugins you choose
Support	WordPress.com staff on paid plans	Community forums and your host
Moving away	Export and migrate at any time	The same

Both sides agree on ownership. WordPress.com's guide says you own your content "and are always free to move it", and that any WordPress site can be migrated to or from WordPress.com.

What the choice means for SEO

Search engines see pages, not the hosting contract behind them. A post on a well-run WordPress.com site and the same post on a self-hosted install can rank equally well. The differences are in what you are allowed to change.

The free plan is the real handicap. It has no custom domain, shows ads you do not control, and cannot run an SEO plugin. A business blog that builds its reputation on a WordPress.com address has to move later, and a move means redirecting every URL. For a site that should rank, start on a paid plan or self-hosted.

On any paid plan, the usual SEO plugins are available. That covers titles, meta descriptions, sitemaps, schema and redirects through the same tools a self-hosted site uses. Most sites need fewer of them than they think; our guide to the best plugins for WordPress SEO covers which ones earn their place.

Technical work needs the higher tiers or your own server. Custom code, SFTP and SSH, database access and staging sites start at the Business plan. On a self-hosted install they are always there, and WordPress.com's guide adds that self-hosting lets you change "the PHP environment", which matters mostly to developers fixing performance or server-level issues. Speed on WordPress.com comes with its managed hosting and CDN; self-hosted speed, in the guide's words, "depends on your host and hosting package."

Headless setups lean toward self-hosted. WordPress ships a REST API that the developer handbook says lets you "bring your WordPress content into completely separate applications", which is how headless WordPress works: WordPress stores the posts and a separate front end renders them. You want full control over the install that front end reads from.

Where the blog lives matters more than which WordPress runs it. If your main site is on another platform, a WordPress blog sits either on a subdomain or, behind a proxy, in a folder of the main domain; the subdomain vs subfolder page covers what Google says about each. After that, rankings come from the same things on both versions: posts that match what searchers want, and internal linking that connects related posts. The blog SEO page covers those layers.

Which one should you pick?

Pick WordPress.com if you want hosting, updates, backups and security handled for you, and a paid plan's plugins cover what the site needs. Personal or Premium suits a blog or a small business site; Business is the tier for developer access, staging and priority support. An agency can run client sites on it too: the higher tiers include SFTP, SSH, WP-CLI and GitHub deployments.

Pick self-hosted WordPress if you need code-level control, a specific host or server setup, WordPress as a headless backend, or one toolset across many sites. Managed WordPress hosting is the middle ground: the self-hosted software, on a host that takes over updates and backups.

Avoid the free WordPress.com plan for anything that should earn search traffic. It is a fine place to try WordPress, not to build a domain's reputation.

How Structura handles this

Structura publishes to WordPress through a plugin, so it needs a WordPress that can install plugins. On a self-hosted install that is always the case. On WordPress.com it rules out the free plan. WordPress.com now lists plugin installation on every paid plan from Personal up; Structura's install guide was written when plugins needed the Business plan and still names Business and Commerce as the plans it has been tested on, so treat Personal and Premium as untested rather than unsupported until the guide catches up.

Once installed, the plugin works the same on both. It writes each post into your WordPress as native Gutenberg blocks, with the title, slug, meta description and keyphrase set, images in the media library and categories and tags assigned. If you run Yoast SEO, Rank Math, SEOPress or All in One SEO, Structura leaves the article-level structured data to that plugin. You choose per campaign whether posts wait for your approval or publish on schedule. If WordPress is only a backend, the plugin's headless mode points the links in new posts at your public site.

If you would rather not run WordPress at all, a headless space keeps the posts in Structura and serves them to any front end through the Content API. The features overview shows what runs on each post.

FAQ