When WordPress.com fits
WordPress.com combines managed hosting with WordPress publishing and, on every paid plan, plugin installation. The decisive choice is not simply WordPress versus a no-code builder: it is which plan supplies the operational controls your business needs. Personal can suit a straightforward company site, while backups, staging, SFTP/SSH and database access push more demanding teams toward Business. Email, premium plugins, domain renewal and one plan per site must remain visible in the total cost.
Affiliate link: we may earn a commission if you continue through this link, at no extra cost to you. Compensation does not affect our assessment.
Strengths to evaluate
- Managed hosting, CDN, SSL, security and core updates reduce infrastructure work
- Every paid plan supports plugins and third-party themes, widening the integration path
- WordPress content export and full-site migration options provide a clearer portability path than many closed builders
- Business adds staging, automated backups and developer access for controlled change management
Limitations and trade-offs
- The permanent free plan is useful for evaluation but keeps the WordPress.com address and platform ads
- Business email is a separate service and domain renewal becomes a separate cost after an eligible first-year offer
- Plugin licences, plugin conflicts and specialist maintenance can add cost even though hosting is managed
- Each website needs its own paid plan, which materially changes agency or multi-site economics
Choose the operating model before choosing the WordPress.com plan
The cheapest plan is not the right baseline for every business. Match the subscription to the site's change risk, integration needs and recovery requirements, then add costs that sit outside the plan.
Choose WordPress.com when
- Content depth, structured publishing and the WordPress ecosystem matter
- The team wants hosting and core platform maintenance handled centrally
- A future move to another WordPress host is a credible exit path
Choose another route when
- Choose Squarespace when a tightly managed design workflow matters more than plugin breadth
- Choose Wix when visual page construction and its managed app workflow better fit the team
- Choose self-hosted WordPress when infrastructure freedom justifies owning hosting, security and update operations
Model the real cost
- Use the local checkout price and the intended billing term rather than the lowest three-year headline
- Add domain renewal, every mailbox, premium plugins and specialist implementation
- Use Business as the baseline when staging, automated restore or developer access is a real requirement
Prove before committing
- Build a representative page, navigation and form and test the mobile editing handoff
- Install the actual critical plugins and verify compatibility, performance and data access
- Run content/media export and, for Business, test staging plus backup restore before migration
A workflow to evaluate in WordPress.com
A service business needs a home page, an about page and a clear contact path. Use that compact site to judge editing effort before adding plugins or a larger plan.
These steps combine linked product documentation with our evaluation questions. They are not a record of our own completed product test. Retained test results are identified separately below.
Choose a design
WordPress.com's guide starts with a theme. Preview the design before activation, then use the Site Editor to work with page blocks.
Try your real headline and service description. A demo theme can look polished while your own content needs a different layout.
Build the small site
Create the home, about and contact pages with blocks. The guide distinguishes pages from the wider site's design and navigation.
Can a mobile reader understand the offer and reach the contact path? Check headings and links before spending time on decoration.
Launch deliberately
New sites begin in Coming Soon mode. Choose the address and move to Public when ready; domain connection is a separate decision from editing a page.
Open the public address while signed out. Keep domain renewal, email and any required plugins in the cost comparison.
Source material checked:
How we assess the product
We only show criteria with published evidence notes. Levels are editorial conclusions based on labelled evidence—never commission or user ratings.
Technical control
StrongProvides more flexibility but requires more decisions.
Vendor verifiedFirst-party source: WordPress.com Business developer tools · 2026-09-01 ↗Room to grow
Very strongFits content operations intended to grow over time.
Vendor verifiedFirst-party source: WordPress.com hosting and plan path · 2026-09-01 ↗Integrations
Very strongA large ecosystem provides many extension paths.
Vendor verifiedFirst-party source: WordPress.com plugin documentation · 2026-09-01 ↗What does WordPress.com cost?
A free tier plus localised website subscriptions. Total cost depends on billing term, plan, domain renewal, separate business email, premium plugins, commerce and whether advanced backups or developer access are required.
- Starting price
- 4 USD/month
- Free plan
- Yes, according to vendor pricing information
- Last checked
- 2026-09-01
Verified pricing facts
The free site uses a WordPress.com address, includes 1 GB storage and displays WordPress.com ads.
- Checked
- 2026-09-01
- Market
- US / USD
WordPress.com localises prices by country and currency; confirm checkout for the business market.
- Checked
- 2026-09-01
- Market
- US / USD
- Checked
- 2026-09-01
- Market
- US / USD
- Checked
- 2026-09-01
- Market
- US / USD
- Checked
- 2026-09-01
- Market
- US / USD
Premium plugin licences and services may still cost extra.
- Checked
- 2026-09-01
- Checked
- 2026-09-01
Renewal depends on the TLD and is separate after the first year.
- Checked
- 2026-09-01
A current plan may advertise a first-year mailbox offer, but ongoing mailbox pricing must be verified separately.
- Checked
- 2026-09-01
Free, Personal and Premium rely on content/media export rather than automated full-site backups.
- Checked
- 2026-09-01
- Checked
- 2026-09-01
Affiliate link. We may earn a commission at no extra cost to you.
Source: the provider’s current price list ↗Prices, promotions, taxes and plan limits can change. Market and currency are shown when the source is localised. Always confirm the final price with the vendor.
How we verified and tested
- Evidence status
- Vendor verified
- Test status
- Test planned
- Documentation checked
- 2026-09-01
- Hands-on test date
- Not performed
- Plan tested
- No plan tested
Workflow test log
- Build and publish a representative business page · Not performed
- Install, configure and remove a required plugin · Not performed
- Connect a domain and configure business email separately · Not performed
- Use staging and restore a backup on an eligible plan · Not performed
- Export content, media and a complete site migration package · Not performed
Observations
- The published assessment is based on first-party product documentation and editorial workflow analysis.
Limitations
- ToolSelect HQ has not yet completed an authenticated, hands-on product workflow.
- Interface behaviour, setup effort and support quality have therefore not been directly observed.
Screenshots
No screenshots are published until a documented product test has been completed.
What the evidence labels mean
- Hands-on tested
- Observed in a recorded product workflow by ToolSelect HQ.
- Vendor verified
- Checked against current first-party product documentation. It is not a hands-on finding.
- Third-party verified
- Corroborated by an identified independent source.
- Not tested
- Not yet verified through a product test or sufficient source evidence.
Check before buying
- Which exact plan supplies the required backup, staging and developer controls?
- Which plugins are essential, what do their licences cost and who maintains them?
- What will the domain, mailboxes and paid extensions cost after the first year?
- Does each additional site need its own paid plan in the intended operating model?
- Can content, media, theme configuration and plugin data be migrated in a usable form?