The Two WordPresses, Explained Without the Jargon
If you run a small business site, freelance portfolio, or inherited a single WordPress install at work, you have probably typed “WordPress” into a search bar and landed on two different websites that look almost identical. One is WordPress.com. The other is WordPress.org. They share a name, a logo family, and a publishing heritage, but they are not the same product, and the difference decides who controls your site, who pays for what, and what you can fix yourself from wp-admin.
Here is the short version. WordPress.org distributes the free, open-source WordPress software you download and install on your own hosting. WordPress.com is a hosted service built on that same software, run by Automattic, with plans, limits, and a support team attached. If you own your domain, pay a hosting bill, and log into /wp-admin on your own URL, you are almost certainly on a self-managed WordPress.org site. That is the audience this article is written for.
This matters because most confusion, and most unnecessary panic, comes from following instructions written for the wrong platform. A tutorial that tells you to install a plugin from the WordPress.com dashboard will not match what you see. A support article about “upgrading your plan” has nothing to do with your hosting invoice. Knowing which side of the fence you are on is the first step in doing routine updates, content edits, access control, and first-response troubleshooting without a developer on retainer.
WordPress.org: The Software You Own
WordPress.org is the project home of the WordPress software itself. You download a zip file, upload it to a host, connect a database, and run the installer. After that, your site lives on infrastructure you rent, under a domain you control, with a database you can back up.
The practical consequences for a non-technical operator are these:
- You choose the host. Your site’s speed, uptime, and backup options come from your hosting company, not from WordPress.org.
- You install plugins and themes yourself. The full plugin directory is open to you, including free and paid options.
- You are responsible for updates. Core, plugins, and themes all need attention. Skipping them is the most common cause of the scary emails we will get to later.
- You control access. You decide who gets an Administrator, Editor, Author, or Contributor role, and you can remove anyone at any time.
- You own the exit. If you want to move hosts, you export your files and database and go. No platform approval required.
The tradeoff is real: nobody is going to fix your site for you at 2 a.m. unless you pay for managed hosting or a support plan. The upside is that nobody can shut your site down for violating a plan’s terms, and nobody can upsell you into a tier you do not need.
WordPress.com: The Hosted Service
WordPress.com runs the same core software, but wraps it in a managed environment. You sign up for an account, pick a plan, and publish. Automattic handles hosting, security patching, backups on paid tiers, and customer support.
What that means in practice:
- Free and low-cost tiers exist, but they come with ads, limited storage, and a WordPress.com subdomain unless you pay for a plan.
- Plugin and theme access depends on your plan. The free tier does not allow arbitrary plugin installation. Business and Commerce tiers do.
- You cannot edit theme files or add custom code on lower tiers. On higher tiers you can, within limits.
- Support is included on paid plans, which is genuinely useful if you never want to touch a database.
- Migration out is possible but involves exporting content and rebuilding on a new host. It is not a one-click move for a complex site.
WordPress.com is a reasonable choice for a simple blog, a personal site, or someone who genuinely wants zero maintenance. It is a poor fit if you need a specific plugin, custom post types, e-commerce with particular requirements, or full control over your database and files.
How to Tell Which One You Are On
Before you follow any tutorial, confirm your platform. This takes about thirty seconds.
- Look at your browser’s address bar when you are logged in. If the URL contains
wordpress.com, you are on WordPress.com. If it is your own domain followed by/wp-admin, you are on a self-hosted WordPress.org site. - Check your dashboard sidebar. WordPress.com sites show a Upgrades or Plans menu item. Self-hosted sites show Plugins and Appearance > Theme File Editor (unless your host has hidden them).
- Look at your billing. If you pay a hosting company like SiteGround, Bluehost, Kinsta, or a local provider, you are self-hosted. If you pay WordPress.com directly, you are on the hosted service.
- Check your plugins screen. If you can install any plugin from the directory, you are self-hosted or on a high-tier WordPress.com plan.
Write the answer down somewhere. It will save you from following the wrong instructions later.
Why the Difference Matters for Routine Maintenance
On a self-managed WordPress.org site, your maintenance rhythm looks like this:
- Weekly: Check for core, plugin, and theme updates. Apply them after a backup.
- Monthly: Review user accounts. Remove anyone who no longer needs access. Check your backup actually ran.
- Quarterly: Review plugins you are not using and delete them. Update your PHP version if your host recommends it.
- As needed: Respond to security alerts, broken layout reports, or “critical error” emails.
On WordPress.com, most of that is handled for you on paid tiers. You still manage content, users, and plan limits, but you are not applying core updates or restoring from a database backup yourself.
The reason this distinction matters is that the order of operations for fixing a problem is different on each platform. On a self-hosted site, the first move is usually to check whether a plugin update broke something. On WordPress.com, the first move is usually to check your plan’s feature limits or contact support. Applying the wrong playbook wastes time and can make things worse.
Common Symptoms and What They Usually Mean
These are the messages that make people email a developer at midnight. Almost none of them are as bad as they look.
“There has been a critical error on this website.”
This is WordPress telling you a PHP error occurred and it cannot render the page. On a self-hosted site, the usual causes are a plugin conflict, a theme conflict, or a PHP version mismatch after a host upgrade. The site is not gone. The database is almost certainly intact.
Order of operations: check your email for the WordPress recovery mode link, which lets you log into wp-admin and deactivate the offending plugin. If you cannot get in, use your host’s file manager to rename the plugin folder. Do not delete anything until you have a backup.
“Briefly unavailable for scheduled maintenance.”
This appears during a core or plugin update. It usually clears in under a minute. If it persists, WordPress left a .maintenance file in your root directory. Deleting that file via your host’s file manager resolves it. This is a cosmetic problem, not a data problem.
Rankings dropped after an update
This is rarely caused by the update itself. More often, a plugin update changed how your pages render, slowed the site down, or altered your permalinks. Check your sitemap, run a speed test, and compare a cached version of a key page. If the layout is intact and the site loads, the drop is usually temporary and recovers as search engines recrawl.
You cannot log in
On a self-hosted site, this is usually a password issue, a security plugin locking you out, or a corrupted session. Use the “Lost your password?” link first. If that fails, your host can reset it from the database. On WordPress.com, use the account recovery flow tied to your WordPress.com login, which is separate from your site’s admin users.
Access Control: Who Should Have What
WordPress ships with five default roles. For a small site, you rarely need more than three.
- Administrator: Full control, including plugins, themes, users, and settings. Give this to as few people as possible.
- Editor: Can publish and manage all posts and pages, including other people’s. Good for a content lead.
- Author: Can write and publish their own posts. Good for a regular contributor.
- Contributor: Can write but not publish. Good for guest writers or review workflows.
- Subscriber: Can only manage their own profile. Useful for membership sites.
On WordPress.com, roles work the same way, but the people you invite may need a WordPress.com account. On a self-hosted site, you create users directly in wp-admin and they log in at your domain.
Review this list every quarter. The most common security problem on small sites is not a sophisticated attack. It is a former contractor who still has Administrator access.
Plugins, Themes, and the Limits You Will Hit
On a self-hosted WordPress.org site, you can install any plugin or theme that is compatible with your PHP and WordPress versions. That freedom is the main reason people choose self-hosting. It is also the main source of maintenance work, because every plugin is a small piece of software that needs updating.
On WordPress.com, plugin access depends on your plan. The free tier does not allow it. The Business and Commerce tiers do, but with some restrictions on what can be installed. If a tutorial tells you to install a plugin and you cannot find the Plugins menu, you are likely on a WordPress.com plan that does not include it.
For a self-managed site, a sensible plugin stack for a small business looks like this: one backup plugin, one security plugin, one caching plugin, one SEO plugin, and one forms plugin. Everything else should earn its place. Fewer plugins means fewer updates and fewer conflicts.
Hosting, Backups, and the Things You Actually Own
On WordPress.org, you own your content and your database. Your host owns the server. Your backup plugin or your host’s backup service owns the copy. If you do not have a backup you can restore yourself, you do not have a backup. You have a hope.
On WordPress.com, Automattic owns the infrastructure and handles backups on paid plans. You can export your content, but restoring a full site to a different host takes more work than a self-hosted migration.
For a self-managed site, confirm three things this week:
- Your host takes automatic backups, and you know how to restore one.
- You have a copy of your site you can access without your host’s dashboard.
- You know your database name and where your
wp-config.phpfile lives, even if you never touch it.
You do not need to memorize these. You need to know where to find them when something breaks.
When WordPress.com Is the Better Choice
This article is written for self-managed site owners, but honesty matters. WordPress.com is a good fit if:
- You want a simple blog or brochure site and never want to think about updates.
- You do not need custom plugins or theme code.
- You would rather pay a subscription than manage a hosting account.
- You value included support over full control.
It is a poor fit if you need e-commerce with specific requirements, membership features, custom post types, or the ability to move hosts freely. Those needs point to WordPress.org.
What to Do Next on Your Self-Managed Site
If you have confirmed you are on WordPress.org, here is a calm, ordered checklist for this week.
- Log into wp-admin and check for updates. Take a backup first if your host offers one-click backups.
- Open the Users screen and remove anyone who should not be there.
- Open the Plugins screen and note anything you do not recognize. Do not delete it yet. Look it up first.
- Confirm your backup schedule and restore process.
- Write down your host’s support URL and your WordPress version number. You will need both if you ever have to ask for help.
None of this requires a developer. It requires knowing which WordPress you are on and following the right order of operations. That is the whole skill.
FAQ
Is WordPress.org free?
The software is free and open source. You still pay for hosting, a domain name, and any premium plugins or themes you choose. The cost is usually lower than a WordPress.com plan with comparable features, but you take on the maintenance work.
Can I move my WordPress.com site to a self-hosted WordPress.org site?
Yes. You export your content from WordPress.com, set up hosting, install WordPress, and import the content. Themes, plugins, and some settings do not transfer automatically, so expect to rebuild parts of the site. It is a project, not a click.
Why can’t I install plugins on my WordPress site?
If you are on WordPress.com, your plan may not include plugin installation. If you are self-hosted and still cannot see the Plugins menu, a security plugin or your host may have hidden it, or your user role may not be Administrator. Check your role first, then your host’s documentation.
Do I need to update WordPress myself?
On a self-hosted site, yes. Core, plugin, and theme updates are your responsibility. Many hosts offer automatic minor core updates, but plugins and themes usually need your attention. On WordPress.com, updates are handled for you.
What is the difference between WordPress.com and WordPress.org in one sentence?
WordPress.org is the free software you install and manage on your own hosting; WordPress.com is a hosted service that runs that software for you, with plan limits and support attached.
Where This Fits in Your Site’s Library
This article is the foundation piece for a small but useful cluster: platform basics, routine maintenance, access control, and first-response troubleshooting. A natural follow-up is a step-by-step walkthrough of restoring a backup from your host’s control panel, or a glossary of the wp-admin screens a non-technical owner actually uses. If you inherited a site and are not sure what you are looking at, start here, then work through the checklist above. The goal is not to become a developer. The goal is to know enough to keep the site running, fix the small things, and ask for help only when it is genuinely needed.