Revision 1
WordPress
@namkyu · Sep 3, 2026, 8:45 AM
Added WordPress.org vs WordPress.com, setup, practical workflows, plugins, business uses, maintenance, APIs, and alternatives.WordPress is an open-source content management system used to build websites, blogs, online stores, membership sites, directories, publications, and other web-based businesses.
The WordPress software itself is free, but a self-hosted WordPress website normally requires separate hosting and a domain. Its main advantage is flexibility: themes and plugins can turn the same core system into anything from a simple blog to an e-commerce store or custom web application.
Item | Details |
|---|---|
Main use | Building and managing websites |
Best for | Blogs, business websites, content sites, ecommerce, and custom websites |
Core software | Free and open source |
License | GPLv2 or later |
Hosting | Required separately for self-hosted WordPress |
Domain | Required separately for a custom site |
Website share | More than 43% of the web according to WordPress.org |
Free plugins | 71,000+ in the official directory |
Themes | Thousands of free and commercial options |
Ecommerce | Available through plugins such as WooCommerce |
API | Built-in REST API |
Coding required | No for basic sites; useful for advanced customization |
The WordPress software available from WordPress.org is free.
There is no WordPress.org subscription fee or per-transaction platform fee for using the core software commercially.
A realistic self-hosted WordPress site can still involve costs for:
Domain registration
Web hosting
Premium themes
Premium plugins
Backups
Email services
Development
Maintenance
The practical cost depends more on the website's hosting and plugin stack than on WordPress itself.
These are related but different services.
WordPress.org provides the open-source WordPress software that can be installed on your own hosting.
WordPress.com is a hosted service with its own free and paid plans.
A typical self-hosted setup is:
Domain → Hosting → Install WordPress → Choose theme → Add plugins → Publish site
A WordPress.com setup is:
Create WordPress.com account → Choose hosted plan → Build site
For businesses that want maximum control over hosting, plugins, data, and customization, self-hosted WordPress is usually the more relevant version.
WordPress provides the underlying system for managing:
Pages
Posts
Images and media
Users
Categories
Tags
Navigation
Themes
Plugins
A normal content workflow looks like:
Create article → Add images → Choose categories → Publish → Search engines crawl page → Update article later
Plugins can extend this into more specialized workflows.
For example:
WordPress → WooCommerce → Products → Checkout → Orders
or:
WordPress → Membership plugin → Paid member → Restricted content
or:
WordPress → Form plugin → Lead submission → CRM
This extensibility is one of the main reasons WordPress can support many different business models.
Choose a domain that the business controls independently.
Keeping the domain separate from the website software makes it easier to change hosting providers later.
A host needs to provide a server environment capable of running WordPress.
WordPress currently recommends:
PHP 8.3 or greater
MariaDB 10.11 or greater, or MySQL 8.0 or greater
HTTPS support
Apache or Nginx is recommended, although WordPress can run on other compatible web servers.
For a beginner, managed WordPress hosting can reduce setup and maintenance work.
Many hosting providers provide one-click installation.
After installation, the main administrative interface is commonly accessed through:
yourdomain.com/wp-admin/
From there, the site owner manages content, plugins, themes, users, and settings.
A theme controls the site's presentation.
It can determine:
Typography
Colors
Header
Footer
Page layouts
Blog layouts
Responsive behavior
Start with a lightweight theme that already supports the required layout.
Do not choose a theme simply because its demo contains many visual effects.
Plugins extend WordPress functionality.
Examples include:
SEO
Forms
Ecommerce
Security
Caching
Backups
Memberships
Analytics
Install plugins because the site needs a specific capability, not because a plugin appears useful.
A business website commonly begins with pages such as:
Home
About
Services or Products
Contact
Privacy Policy
Content-driven websites can then add articles through WordPress Posts.
WordPress separates more permanent content from chronological content.
Pages are typically used for:
About
Services
Contact
Landing pages
Posts are normally used for:
Articles
News
Tutorials
Blog content
For a Blogging business, Posts usually make up most of the content library.
Modern WordPress uses a block-based editor.
Content can be assembled using blocks such as:
Paragraph
Heading
Image
List
Table
Columns
Buttons
Embed
The same block system can also be used by block themes to customize larger parts of the website.
A simple distinction is:
Theme = appearance
Plugin = functionality
For example:
Changing the visual layout → Theme
Adding ecommerce → Plugin
Adding an SEO sitemap → Plugin
Adding a contact form → Plugin
Keeping those responsibilities separate usually makes a WordPress site easier to maintain.
Choose niche → Install WordPress → Publish useful articles → Optimize internal structure → Acquire search traffic → Monetize
Possible monetization methods include:
Advertising
Affiliate marketing
Digital products
Services
Sponsorships
WordPress is particularly well suited to long-form content because content remains under the site owner's control.
Service page → Visitor arrives → Reads case study → Completes form → Business follows up
A business can combine WordPress with:
SEO
Google Ads
Email marketing
CRM systems
The website becomes a lead-generation asset rather than simply an online brochure.
Install WooCommerce → Add products → Configure payments → Configure shipping → Customer orders → Fulfill order
WordPress itself is not primarily an ecommerce system.
WooCommerce adds the ecommerce layer.
This combination gives merchants more infrastructure control than a fully hosted platform such as Shopify.
WordPress.org currently lists more than 71,000 free plugins.
That does not mean a site should install many of them.
Every plugin can potentially add:
Code
Database queries
Updates
Security exposure
Compatibility issues
Use the smallest plugin stack that solves the site's actual requirements.
Create a recoverable backup before:
WordPress updates
Major plugin updates
Theme changes
Server migrations
Significant code changes
WordPress documentation specifically recommends backing up before updating.
A backup is useful only if it can actually be restored.
Outdated components can create:
Security vulnerabilities
Compatibility problems
Bugs
WordPress can automatically install many minor and security updates.
Major changes should still be tested when the site is commercially important.
For important websites, test significant changes in a staging environment before applying them to the live site.
This is especially useful for:
WooCommerce stores
Membership sites
Custom plugins
Major theme changes
For example, running several caching plugins or multiple SEO systems can create conflicts and unnecessary complexity.
Choose one primary solution for each major function.
A simple blog and a busy ecommerce store do not need the same hosting.
As traffic increases, important resources can include:
CPU
Memory
Database performance
Caching
CDN
Backup capacity
Cheap hosting is not necessarily cheaper if performance problems begin affecting sales or traffic.
A major advantage of self-hosted WordPress is portability.
Maintain control of:
Domain account
Website files
Database backups
This reduces dependence on one developer or hosting company.
WordPress began as a publishing system and remains particularly strong for content-heavy websites.
Businesses can combine content with:
SEO
Affiliate marketing
Advertising
Newsletter acquisition
Digital products
Service businesses can use WordPress for:
Landing pages
Portfolio pages
Case studies
Lead generation
Booking
This can support businesses ranging from local services to agencies and professional consulting.
WooCommerce can turn WordPress into an online store.
This can support:
Physical products
Digital products
Subscriptions
Memberships
The additional flexibility also creates more maintenance responsibility than a fully hosted ecommerce system.
WordPress itself can also be used as the basis of a service business.
Freelancers can sell:
Website creation
Theme customization
WooCommerce setup
Site migration
Maintenance
Performance optimization
This fits naturally with Freelancing and Web Design.
WordPress has a large plugin ecosystem for connecting external services.
Common integration categories include:
Analytics
Email marketing
CRM
Payments
Ecommerce
SEO
Forms
Automation
Social media
For standard business requirements, a maintained plugin is usually easier than building a custom integration.
When no appropriate plugin exists, WordPress also provides APIs for custom development.
WordPress includes a REST API that allows external applications to interact with site data using JSON.
Standard endpoints can expose resources such as:
Posts
Pages
Categories
Tags
Media
Users
For example, an external application can retrieve WordPress posts through the API and display them in a separate frontend.
A custom architecture might look like:
WordPress CMS → REST API → Custom frontend
This allows WordPress to operate as a headless content-management backend.
Most ordinary business websites do not need this architecture.
Use standard WordPress rendering unless a custom frontend provides a meaningful benefit.
Developers can create their own:
Themes
Plugins
Custom post types
Taxonomies
API integrations
WordPress can therefore be extended beyond conventional websites.
The tradeoff is maintenance.
Custom code must continue working as WordPress, PHP, themes, and plugins evolve.
The core software costs nothing, but hosting, domains, premium plugins, development, and maintenance can create meaningful expenses.
A self-hosted WordPress website requires ongoing attention to:
Updates
Security
Backups
Hosting
Plugin compatibility
A managed platform handles more of this automatically.
Plugins and themes are developed by many different organizations and developers.
Two individually functional plugins can still conflict when installed together.
Test important updates.
Installing optimization plugins cannot completely compensate for severely inadequate hosting.
Infrastructure still matters.
Custom code can solve unusual business requirements but can also make future upgrades harder.
Prefer standard WordPress capabilities and maintained plugins when they solve the problem adequately.
WordPress security is not determined only by WordPress core.
The full environment includes:
Hosting
Plugins
Themes
Administrator accounts
Passwords
Server configuration
Unused plugins and themes should not remain installed indefinitely.
Platform | Best Fit | Main Difference |
|---|---|---|
WordPress | Content-heavy and highly customizable websites | Open source and self-hosted |
Webflow | Visual website building with managed hosting | More integrated visual design workflow |
Shopify | Dedicated ecommerce stores | Commerce infrastructure included |
Custom development | Unique applications and workflows | Maximum flexibility with much higher development burden |
Choose WordPress when:
Content publishing matters
You want control over hosting
You need a large plugin ecosystem
Customization is important
You want to avoid dependence on one hosted website builder
Choose Webflow when visual site building and managed infrastructure are more important than WordPress's plugin ecosystem.
Choose Shopify when ecommerce is the primary requirement and you prefer a more managed commerce platform.
Choose custom development when the product behaves more like a software application than a conventional content website.
Yes.
The open-source WordPress software available from WordPress.org is free and licensed under the GPL.
Hosting, domains, premium plugins, and other services can still cost money.
WordPress.org provides the open-source WordPress software for self-hosting.
WordPress.com is a hosted service built around WordPress with its own pricing plans and infrastructure.
For self-hosted WordPress.org, yes.
You need a server or hosting provider capable of running WordPress.
No for many standard websites.
Themes, blocks, and plugins allow users to build substantial websites without writing code.
Coding becomes useful for advanced customization and custom integrations.
Yes.
WooCommerce is a widely used WordPress ecommerce plugin that adds products, checkout, orders, payments, and other store functionality.
Yes, particularly when the business values content publishing, extensibility, ownership, and control.
The tradeoff is greater maintenance responsibility compared with a fully managed website builder.
Canonical Markdown
WordPress is an open-source content management system used to build websites, blogs, online stores, membership sites, directories, publications, and other web-based businesses. The WordPress software itself is free, but a self-hosted WordPress website normally requires separate hosting and a domain. Its main advantage is flexibility: themes and plugins can turn the same core system into anything from a simple blog to an e-commerce store or custom web application. # Quick Facts | Item | Details || --------------- | ----------------------------------------------------------------------- || Main use | Building and managing websites || Best for | Blogs, business websites, content sites, ecommerce, and custom websites || Core software | Free and open source || License | GPLv2 or later || Hosting | Required separately for self-hosted WordPress || Domain | Required separately for a custom site || Website share | More than 43% of the web according to WordPress.org || Free plugins | 71,000+ in the official directory || Themes | Thousands of free and commercial options || Ecommerce | Available through plugins such as WooCommerce || API | Built-in REST API || Coding required | No for basic sites; useful for advanced customization | # Pricing The WordPress software available from WordPress.org is free. There is no WordPress.org subscription fee or per-transaction platform fee for using the core software commercially. A realistic self-hosted WordPress site can still involve costs for: - Domain registration- Web hosting- Premium themes- Premium plugins- Backups- Email services- Development- Maintenance The practical cost depends more on the website's hosting and plugin stack than on WordPress itself. ## WordPress.org vs WordPress.com These are related but different services. **WordPress.org** provides the open-source WordPress software that can be installed on your own hosting. **WordPress.com** is a hosted service with its own free and paid plans. A typical self-hosted setup is: Domain → Hosting → Install WordPress → Choose theme → Add plugins → Publish site A WordPress.com setup is: Create WordPress.com account → Choose hosted plan → Build site For businesses that want maximum control over hosting, plugins, data, and customization, self-hosted WordPress is usually the more relevant version. # What It Does WordPress provides the underlying system for managing: - Pages- Posts- Images and media- Users- Categories- Tags- Navigation- Themes- Plugins A normal content workflow looks like: Create article → Add images → Choose categories → Publish → Search engines crawl page → Update article later Plugins can extend this into more specialized workflows. For example: WordPress → WooCommerce → Products → Checkout → Orders or: WordPress → Membership plugin → Paid member → Restricted content or: WordPress → Form plugin → Lead submission → CRM This extensibility is one of the main reasons WordPress can support many different business models. # Getting Started ## 1. Buy a Domain Choose a domain that the business controls independently. Keeping the domain separate from the website software makes it easier to change hosting providers later. ## 2. Choose WordPress Hosting A host needs to provide a server environment capable of running WordPress. WordPress currently recommends: - PHP 8.3 or greater- MariaDB 10.11 or greater, or MySQL 8.0 or greater- HTTPS support Apache or Nginx is recommended, although WordPress can run on other compatible web servers. For a beginner, managed WordPress hosting can reduce setup and maintenance work. ## 3. Install WordPress Many hosting providers provide one-click installation. After installation, the main administrative interface is commonly accessed through: `yourdomain.com/wp-admin/` From there, the site owner manages content, plugins, themes, users, and settings. ## 4. Choose a Theme A theme controls the site's presentation. It can determine: - Typography- Colors- Header- Footer- Page layouts- Blog layouts- Responsive behavior Start with a lightweight theme that already supports the required layout. Do not choose a theme simply because its demo contains many visual effects. ## 5. Install Only Essential Plugins Plugins extend WordPress functionality. Examples include: - SEO- Forms- Ecommerce- Security- Caching- Backups- Memberships- Analytics Install plugins because the site needs a specific capability, not because a plugin appears useful. ## 6. Create Core Pages A business website commonly begins with pages such as: - Home- About- Services or Products- Contact- Privacy Policy Content-driven websites can then add articles through WordPress Posts. # How to Use ## Pages vs Posts WordPress separates more permanent content from chronological content. **Pages** are typically used for: - About- Services- Contact- Landing pages **Posts** are normally used for: - Articles- News- Tutorials- Blog content For a [Blogging](https://incomewiki.com/wiki/blogging) business, Posts usually make up most of the content library. ## Block Editor Modern WordPress uses a block-based editor. Content can be assembled using blocks such as: - Paragraph- Heading- Image- List- Table- Columns- Buttons- Embed The same block system can also be used by block themes to customize larger parts of the website. ## Themes and Plugins A simple distinction is: **Theme = appearance** **Plugin = functionality** For example: Changing the visual layout → Theme Adding ecommerce → Plugin Adding an SEO sitemap → Plugin Adding a contact form → Plugin Keeping those responsibilities separate usually makes a WordPress site easier to maintain. # Practical Workflows ## Content Website Choose niche → Install WordPress → Publish useful articles → Optimize internal structure → Acquire search traffic → Monetize Possible monetization methods include: - Advertising- Affiliate marketing- Digital products- Services- Sponsorships WordPress is particularly well suited to long-form content because content remains under the site owner's control. ## Business Lead Generation Service page → Visitor arrives → Reads case study → Completes form → Business follows up A business can combine WordPress with: - SEO- Google Ads- Email marketing- CRM systems The website becomes a lead-generation asset rather than simply an online brochure. ## Ecommerce Install [WooCommerce](https://incomewiki.com/wiki/woocommerce) → Add products → Configure payments → Configure shipping → Customer orders → Fulfill order WordPress itself is not primarily an ecommerce system. WooCommerce adds the ecommerce layer. This combination gives merchants more infrastructure control than a fully hosted platform such as [Shopify](https://incomewiki.com/wiki/shopify). # Tips & Best Practices ## Keep the Plugin Stack Small WordPress.org currently lists more than 71,000 free plugins. That does not mean a site should install many of them. Every plugin can potentially add: - Code- Database queries- Updates- Security exposure- Compatibility issues Use the smallest plugin stack that solves the site's actual requirements. ## Back Up Before Major Changes Create a recoverable backup before: - WordPress updates- Major plugin updates- Theme changes- Server migrations- Significant code changes WordPress documentation specifically recommends backing up before updating. A backup is useful only if it can actually be restored. ## Keep WordPress, Plugins, and Themes Updated Outdated components can create: - Security vulnerabilities- Compatibility problems- Bugs WordPress can automatically install many minor and security updates. Major changes should still be tested when the site is commercially important. ## Avoid Editing Production Sites Blindly For important websites, test significant changes in a staging environment before applying them to the live site. This is especially useful for: - WooCommerce stores- Membership sites- Custom plugins- Major theme changes ## Do Not Install Multiple Plugins for the Same Job For example, running several caching plugins or multiple SEO systems can create conflicts and unnecessary complexity. Choose one primary solution for each major function. ## Choose Hosting Based on Workload A simple blog and a busy ecommerce store do not need the same hosting. As traffic increases, important resources can include: - CPU- Memory- Database performance- Caching- CDN- Backup capacity Cheap hosting is not necessarily cheaper if performance problems begin affecting sales or traffic. ## Control the Domain and Backups A major advantage of self-hosted WordPress is portability. Maintain control of: - Domain account- Website files- Database backups This reduces dependence on one developer or hosting company. # Business Uses ## Blogging and Publishing WordPress began as a publishing system and remains particularly strong for content-heavy websites. Businesses can combine content with: - SEO- Affiliate marketing- Advertising- Newsletter acquisition- Digital products ## Business Websites Service businesses can use WordPress for: - Landing pages- Portfolio pages- Case studies- Lead generation- Booking This can support businesses ranging from local services to agencies and professional consulting. ## Ecommerce WooCommerce can turn WordPress into an online store. This can support: - Physical products- Digital products- Subscriptions- Memberships The additional flexibility also creates more maintenance responsibility than a fully hosted ecommerce system. ## Freelance Web Development WordPress itself can also be used as the basis of a service business. Freelancers can sell: - Website creation- Theme customization- WooCommerce setup- Site migration- Maintenance- Performance optimization This fits naturally with [Freelancing](https://incomewiki.com/wiki/freelancing) and [Web Design](https://incomewiki.com/wiki/web-design). # Integrations WordPress has a large plugin ecosystem for connecting external services. Common integration categories include: - Analytics- Email marketing- CRM- Payments- Ecommerce- SEO- Forms- Automation- Social media For standard business requirements, a maintained plugin is usually easier than building a custom integration. When no appropriate plugin exists, WordPress also provides APIs for custom development. # Advanced Use ## REST API WordPress includes a REST API that allows external applications to interact with site data using JSON. Standard endpoints can expose resources such as: - Posts- Pages- Categories- Tags- Media- Users For example, an external application can retrieve WordPress posts through the API and display them in a separate frontend. A custom architecture might look like: WordPress CMS → REST API → Custom frontend This allows WordPress to operate as a headless content-management backend. Most ordinary business websites do not need this architecture. Use standard WordPress rendering unless a custom frontend provides a meaningful benefit. ## Custom Themes and Plugins Developers can create their own: - Themes- Plugins- Custom post types- Taxonomies- API integrations WordPress can therefore be extended beyond conventional websites. The tradeoff is maintenance. Custom code must continue working as WordPress, PHP, themes, and plugins evolve. # Limitations & Common Mistakes ## Free Software Does Not Mean Free Website The core software costs nothing, but hosting, domains, premium plugins, development, and maintenance can create meaningful expenses. ## Maintenance Is the Owner's Responsibility A self-hosted WordPress website requires ongoing attention to: - Updates- Security- Backups- Hosting- Plugin compatibility A managed platform handles more of this automatically. ## Plugin Conflicts Can Occur Plugins and themes are developed by many different organizations and developers. Two individually functional plugins can still conflict when installed together. Test important updates. ## Poor Hosting Can Hurt Performance Installing optimization plugins cannot completely compensate for severely inadequate hosting. Infrastructure still matters. ## Excessive Customization Creates Technical Debt Custom code can solve unusual business requirements but can also make future upgrades harder. Prefer standard WordPress capabilities and maintained plugins when they solve the problem adequately. ## Security Depends on the Entire Stack WordPress security is not determined only by WordPress core. The full environment includes: - Hosting- Plugins- Themes- Administrator accounts- Passwords- Server configuration Unused plugins and themes should not remain installed indefinitely. # Alternatives | Platform | Best Fit | Main Difference || ------------------ | ---------------------------------------------- | ------------------------------------------------------- || WordPress | Content-heavy and highly customizable websites | Open source and self-hosted || Webflow | Visual website building with managed hosting | More integrated visual design workflow || Shopify | Dedicated ecommerce stores | Commerce infrastructure included || Custom development | Unique applications and workflows | Maximum flexibility with much higher development burden | Choose WordPress when: - Content publishing matters- You want control over hosting- You need a large plugin ecosystem- Customization is important- You want to avoid dependence on one hosted website builder Choose Webflow when visual site building and managed infrastructure are more important than WordPress's plugin ecosystem. Choose [Shopify](https://incomewiki.com/wiki/shopify) when ecommerce is the primary requirement and you prefer a more managed commerce platform. Choose custom development when the product behaves more like a software application than a conventional content website. # FAQ ## Is WordPress free? Yes. The open-source WordPress software available from WordPress.org is free and licensed under the GPL. Hosting, domains, premium plugins, and other services can still cost money. ## What is the difference between WordPress.org and WordPress.com? WordPress.org provides the open-source WordPress software for self-hosting. WordPress.com is a hosted service built around WordPress with its own pricing plans and infrastructure. ## Do I need hosting for WordPress? For self-hosted WordPress.org, yes. You need a server or hosting provider capable of running WordPress. ## Do I need coding skills? No for many standard websites. Themes, blocks, and plugins allow users to build substantial websites without writing code. Coding becomes useful for advanced customization and custom integrations. ## Can WordPress run an online store? Yes. WooCommerce is a widely used WordPress ecommerce plugin that adds products, checkout, orders, payments, and other store functionality. ## Is WordPress good for business websites? Yes, particularly when the business values content publishing, extensibility, ownership, and control. The tradeoff is greater maintenance responsibility compared with a fully managed website builder. # Sources - [WordPress.org — About WordPress](https://wordpress.org/about/)- [WordPress.org — Features](https://wordpress.org/about/features/)- [WordPress.org — Download WordPress](https://wordpress.org/download/)- [WordPress.org — Requirements](https://wordpress.org/about/requirements/)- [WordPress.org — Plugins](https://wordpress.org/plugins/)- [WordPress.org — Themes](https://wordpress.org/themes/)- [WordPress.org Documentation — Introduction to Plugins](https://wordpress.org/documentation/article/introduction-to-plugins/)- [WordPress.org Documentation — Updating WordPress](https://wordpress.org/documentation/article/updating-wordpress/)- [WordPress Developer Resources — REST API Handbook](https://developer.wordpress.org/rest-api/)- [WordPress Developer Resources — REST API Reference](https://developer.wordpress.org/rest-api/reference/)- [WordPress Developer Resources — What Is a Theme?](https://developer.wordpress.org/themes/getting-started/what-is-a-theme/)- [WordPress.com — Pricing](https://wordpress.com/pricing/)