WordPress

Not a single vendor; GPL open-source project stewarded by the WordPress Foundation, founded by Matt Mullenweg in 2010.

First released May 27, 2003 (version 0.70) by Matt Mullenweg and Mike Little, as a fork of b2/cafelog.

Self-hosted WordPress.org software, scope of this listing (distinct from hosted WordPress.com).

Released under GPLv2 (or later); themes and plugins are derivative works and inherit the GPL for their PHP code.

GNU General Public License version 2, or any later version, from the Free Software Foundation.

Broadest fit of any CMS given plugin ecosystem; requires more hands-on management than hosted builders.

The software itself has no pricing page since it is free; cost is driven by third-party hosting, themes, and plugins.

WordPress.org software is free to download and use; "free" here means the software has no license cost, not that hosting is included.

Unlike hosted builders, there is no platform-imposed free tier with feature gating; cost/limits are entirely a function of hosting choice.

No universal vendor trial exists since there is no single vendor.

Market-typical figure, not a WordPress.org price (software is free). Cheapest widely-used managed-WordPress entry plan with a custom domain: Bluehost Starter at $3.99/mo intro (renews $9.99/mo) or SiteGround StartUp at $2.99/mo intro (renews $17.99/mo). Used Bluehost as representative; actual cost varies enormously by host.

Market-typical figure, not a WordPress.org price. Used WP Engine Startup plan ($30/mo, annual billing) as a representative "popular" managed-WordPress tier aimed at serious small-business sites; other hosts price this tier anywhere from $10-$50/mo.

Market-typical figure. WooCommerce plugin itself is free; used Bluehost's WooCommerce/eCommerce Essentials hosting plan ($14.99/mo intro, renews $21.99/mo) as a representative entry ecommerce-ready hosting cost. Payment processing fees are separate (see ecommerce.platform_transaction_fee).

Self-hosted WordPress never injects vendor branding into the front end; some hosts add a small admin-bar badge that is trivially removable.

Not applicable to the free software itself, but true of virtually every managed-hosting vendor: e.g., SiteGround StartUp renews at $17.99/mo after a $2.99/mo intro rate (501% increase); Bluehost Starter renews at $9.99/mo after $3.99/mo.

Market-typical figure from representative host (Bluehost: 30-day money-back guarantee on hosting, excludes domains/add-ons). Not a WordPress.org policy; varies by host.

This variability is WordPress's defining pricing characteristic versus all-inclusive hosted builders.

The Block Editor (Gutenberg) is the default editor since WordPress 5.0 (Dec 2018); Full Site Editing extends block-based editing to themes/templates on block themes.

Blocks can be reordered via drag-and-drop in the editor; media can be drag-and-dropped into the uploader.

Click-to-edit text directly within blocks in the WYSIWYG block editor.

In-editor undo/redo plus full post/page revision history (native post type since WordPress 2.6).

WordPress autosaves drafts periodically in the block editor (shown as "Saved"/draft state in the toolbar).

Official WordPress mobile apps (iOS/Android) support post/page editing, block editing, and media upload.

Switching themes can break custom layouts, widget placements, and page-builder-authored content; block-theme-to-block-theme switches are safer but not guaranteed content-preserving, especially with classic themes or third-party page builders.

Editorial judgment: publishing posts/pages via the block editor is approachable, but full-site editing, theme customization, plugin management, and hosting/maintenance responsibilities add real complexity versus a hosted builder; steeper than Wix/Squarespace, gentler than a fully code-first stack.

Free themes currently listed in the official WordPress.org theme directory; excludes third-party marketplaces (ThemeForest etc.) and premium themes, which add many thousands more.

Native Font Library (WordPress 6.5+, block themes) supports uploading custom font files (TTF/WOFF/WOFF2/OTF) directly in the Site Editor; also configurable via theme.json.

Full CSS/theme control means responsive breakpoints and behavior are entirely customizable by theme/developer; block themes expose some breakpoint editing in the Site Editor, but full control requires CSS/code.

Native "Additional CSS" panel in the Customizer, plus unrestricted theme/child-theme CSS editing for administrators.

Full custom JavaScript is possible via theme files, plugins, or (for administrators, if unfiltered_html capability is enabled) code blocks/widgets; no platform-level restriction on self-hosted installs.

No native visual animation/interaction builder in core; achieved via theme features, plugins (e.g., animation blocks), or custom CSS/JS. Source is the official plugin directory tag showing animation is plugin territory.

theme.json-powered Global Styles (colors, typography, spacing) on block themes, editable via the Site Editor's Styles panel.

Editorial judgment: full source-code and template access, combined with the largest theme/plugin ecosystem of any CMS, makes design flexibility effectively unconstrained; at the cost of needing developer skill or an existing theme's limits.

WordPress.org software is not itself hosted; you must provide your own hosting (shared, VPS, managed-WordPress, or self-managed server).

Self-hosting is the entire premise of WordPress.org (as opposed to WordPress.com).

Self-hosted WordPress requires the site owner (or their host) to manage core, theme, and plugin updates and the underlying server stack; core offers optional auto-update toggles for itself and plugins, but hosting, security, and PHP/server maintenance remain the operator's responsibility.

Not included with core software; depends entirely on hosting provider (many managed-WordPress hosts bundle a CDN, e.g., WP Engine's "edge content delivery").

Not a core software feature; depends on host. Most modern hosts (Bluehost, SiteGround, WP Engine) include free Let's Encrypt SSL, so this is typical in practice even though not guaranteed by WordPress itself.

There is no WordPress.org uptime commitment since it is not a hosting service.

No platform-wide limit exists since WordPress runs on infrastructure you choose.

Not native, but well-supported via plugins (e.g., Simply Static, WP2Static) or WP-CLI-driven static site generation workflows; not a one-click core feature. Source is the official directory listing for the leading static-export plugin.

May 2026 CrUX data via HTTP Archive CWV Technology Report API: 50.7% of 4,646,103 origins with good CWV (desktop 53.0%, mobile 49.3%). Report technology name: 'WordPress'.

Core generates multiple responsive image sizes automatically but does not convert to modern formats (WebP/AVIF) or compress aggressively out of the box. WordPress 6.7 added automatic HEIC-to-JPEG conversion only; WebP output remains opt-in via the image_editor_output_format filter or a plugin, so optimization is developer/plugin-driven, not automatic by default.

Core has automatically generated srcset/sizes attributes on uploaded images since WordPress 4.4 (2015), with no plugin or configuration required; this covers responsive image markup, distinct from modern-format conversion (see performance.image_optimization) or LQIP/blur-up placeholders, which core does not provide.

Native lazy-loading (loading="lazy" attribute) for images has been default in WordPress core since version 5.5 (2020).

Site owners have full server/application-level caching control (object cache, page cache via plugins like WP Super Cache, or host-level caching); not built into core but fully within the owner's control given self-hosting, per the official optimization handbook.

Core ships no analytics or stats dashboard of any kind; site owners add Jetpack Stats, Google Analytics, or a plugin like WP Statistics for any visit/traffic data.

Not applicable to core, which has no built-in analytics to be privacy-first or not. The common near-universal add-on, Jetpack Stats, is itself a plugin rather than a core feature, consistent with analytics.builtin being none.

No core or official Automattic session-replay feature exists; tools like Microsoft Clarity or Hotjar are unaffiliated third-party scripts/plugins, not an official WordPress or Jetpack capability.

No core or official Automattic heatmap feature exists; heatmap tools are added entirely through unaffiliated third-party plugins or scripts.

Editable via SEO plugins (Yoast, Rank Math, All in One SEO) since core has no dedicated meta title/description UI; near-universal in practice. Source is the official directory listing for the leading SEO plugin.

Native permalink/slug editing for every post, page, and custom post type.

Among the most flexible URL control of the platforms compared; the category/tag base is the only notable forced element.

No native redirect manager in core; requires a plugin (e.g., Redirection) or server-level .htaccess/web-server config.

Core outputs a self-referencing canonical tag on singular pages via the rel_canonical() core function; SEO plugins allow overriding it per-post.

Core generates a virtual robots.txt that is editable via the Settings > Reading "discourage search engines" toggle and the robots_txt filter hook for developers/plugins; a physical robots.txt file in the site root overrides it entirely.

Native XML sitemaps at /wp-sitemap.xml, on by default since WordPress 5.5 (2020), covering posts, pages, custom post types, taxonomies, and authors; SEO plugins commonly replace it with their own at /sitemap.xml.

No native schema.org/JSON-LD output in core; requires an SEO plugin (Yoast, Rank Math) or manual implementation. Source is the official directory listing for the leading SEO plugin, which ships schema.org output.

No native hreflang support; requires a multilingual plugin (WPML or Polylang), both of which generate hreflang tags automatically once installed.

Not in bare core, but universally available via SEO plugins (Yoast, Rank Math) that ship Open Graph/Twitter Card control as standard. Source is the official directory listing for the leading SEO plugin.

Native site-wide "discourage search engines" toggle exists in core (Settings > Reading); true per-page noindex requires an SEO plugin, which is near-universal on production WordPress sites.

Native alt text field in the Media Library and block editor's image block; core also nudges users to fill it in.

Blogging (Posts) is WordPress's original core content type; categories, tags, and RSS are all native.

register_post_type() is a core WordPress API; no plugin required to define custom post types and taxonomies, though plugins like Advanced Custom Fields make it easier.

Categories and tags are native taxonomies; custom taxonomies are natively supported via register_taxonomy().

Native "Publish" date/time scheduling for posts and pages has existed since early WordPress versions.

Revisions are a native post type; every save creates a restorable revision, viewable via a native diff/compare UI.

Native roles (Administrator, Editor, Author, Contributor, Subscriber) support multi-author workflows out of the box.

Native RSS 2.0, RSS 0.92, and Atom feeds auto-generated for posts, categories, tags, and comments; no plugin required.

Native WordPress REST API supports querying, creating, and modifying content as JSON; read access is open by default for public content, write access requires authentication.

Core has no native form builder. Forms are built entirely through the plugin ecosystem (WPForms, Gravity Forms, Contact Form 7, WS Form), which is a marketplace/ecosystem add-on rather than a core capability.

Core has no native membership or paywall system; gated/paid content is achieved entirely via self-hosted plugins (MemberPress, Restrict Content Pro, Paid Memberships Pro) installed directly into the WordPress codebase.

Ecommerce is not part of WordPress core; requires the free WooCommerce plugin (by far the dominant choice) or an alternative like Easy Digital Downloads.

Unlike hosted platforms, there is no plan-based product cap.

No WooCommerce/WordPress-imposed transaction cut, unlike some hosted ecommerce platforms.

Widest gateway choice among platforms compared, since it is a plugin ecosystem rather than a closed system.

WooCommerce natively supports downloadable/virtual products; Easy Digital Downloads is a dedicated alternative plugin for digital-only stores.

Requires the paid WooCommerce Subscriptions extension (or a third-party plugin); not included in free WooCommerce core.

Not native to WooCommerce core; requires a currency-switcher plugin (CURCY, YayCurrency, FOX, Aelia) or WooPayments' built-in multi-currency feature.

Via the official Square for WooCommerce plugin (Woo's preferred POS partner), syncing inventory/payments between online store and in-person Square POS/Terminal; available in US, Canada, Australia, Japan, Ireland, France, Spain, and the UK.

Not tracked by WooCommerce core by default; requires a third-party plugin (free options include Cart Abandonment Recovery, Abandoned Cart Lite) or the paid official WooCommerce Abandoned Cart Recovery extension.

Baseline tools are native; advanced automation is plugin-gated.

Native WordPress Exporter (Tools > Export) and WP-CLI `wp export` produce a complete WXR (WordPress eXtended RSS) file of all posts, pages, comments, custom fields, and terms.

WXR does not include site configuration/options or attachment binary files, only content references.

Because you own the entire codebase (theme files, plugin files, database) on your own hosting, the whole site; design included; can be copied/migrated wholesale to any other host running PHP/MySQL.

Self-hosted WordPress imposes no domain lock-in; you register and point your own domain wherever you choose, and the official migration handbook documents changing domains/hosts without reinstalling.

Definitionally portable; WordPress.org software can run on any host supporting PHP and MySQL/MariaDB; this is the core distinction from WordPress.com.

The native REST API exposes full read/write content access (with authentication for private/write operations); WP-CLI and direct database access provide additional full-fidelity access paths.

Editorial judgment: self-hosted, GPL-licensed, standard PHP/MySQL stack with full database/file access and no vendor-controlled hosting makes this the lowest lock-in risk of any platform category; the main risk vector is accumulated plugin/theme dependencies rather than the platform itself.

Count is a third-party tracking estimate (WP Monitor), since WordPress.org itself does not publish a running total on-page; still by far the largest plugin ecosystem of any CMS/website platform.

Native REST API, ships in core since WordPress 4.7 (2016).

Native to WooCommerce (order/product webhooks) and available in core content workflows via plugins; core WordPress itself has action/filter hooks but outbound webhooks specifically are most commonly used via WooCommerce or a webhook plugin.

Unrestricted custom code embedding via theme files, plugins, code blocks (with unfiltered_html capability), or header/footer injection plugins; no platform-level gating on self-hosted installs.

One of the most widely known and documented stacks in web development, which underpins its large developer/plugin ecosystem.

WP-CLI is the official command-line tool, shipping continuously since 2011, covering nearly everything doable in wp-admin (users, content, plugins, multisite, search-replace) from the terminal.

Via plugin, not core: Zapier publishes an official "Zapier for WordPress" plugin in the WordPress.org directory, Make connects via the REST API, and WooCommerce has dedicated Zapier support for order/customer events.

WordPress's extensibility model is plugin-based rather than a curated native-integrations list. Source is the official directory listing for Jetpack, the flagship first-party integration plugin.

Not native to WordPress core as of version 7.0 (May 2026); AI Client and Abilities API (introduced WP 6.9/7.0) provide infrastructure for AI features, and a separate official AI plugin (launched Feb 2026, built on this infrastructure) adds content/image generation, but full AI site generation is not a core capability; closer to hosted-builder AI site builders like Wix ADI.

The official WordPress AI plugin (built on the new AI Client/Abilities API infrastructure) provides drafting, rewriting for tone/clarity, and title generation; not bundled in core by default, added as a plugin.

The official AI plugin adds AI image generation directly in the Media Library; not part of default core install.

The official AI plugin includes alt-text generation and content classification; broader AI SEO assistance is more commonly delivered via SEO plugins (Yoast, Rank Math) that have added AI features.

Editorial judgment: self-hosted WordPress renders full server-side HTML with no JS-dependent hydration required for content, and the SEO plugin ecosystem (Yoast, Rank Math) gives complete control over schema.org/JSON-LD, meta, canonical tags, and llms.txt, all directly parseable by AI crawlers and answer engines; full server access also means no platform-level crawler restrictions.

No core WordPress feature generates llms.txt. It is exclusively a plugin-ecosystem capability: Yoast SEO (since June 2025) and Rank Math both ship llms.txt generators as plugin add-ons, not core functionality.

Core exposes a filterable robots_txt hook allowing full custom robots.txt content, including per-bot rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and CCBot; SEO plugins (Yoast, Rank Math) add a dedicated robots.txt editor UI on top. No single one-click AI-bot toggle ships in core, but full custom-rule editing meets the granular bar.

The WordPress project (under its AI Building Blocks for WordPress initiative) ships an official MCP Adapter bridging the core Abilities API (WordPress 6.9+) to the Model Context Protocol, letting AI agents call site abilities. It ships as a separate official WordPress/Automattic package rather than being merged into WordPress core itself.

This is architecturally different from hosted builders that bundle one first-party AI assistant.

Native capability-based system with 6 default roles (Super Admin, Administrator, Editor, Author, Contributor, Subscriber) and dozens of individually assignable capabilities (add_cap/remove_cap), plus support for fully custom roles.

Core ships a native Multisite (network) feature letting one install run many sites sharing core files and users, with no core-imposed cap on the number of sites in a network; real-world networks scale to thousands of sites, limited only by server resources.

Core has native post-locking (wp_check_post_lock() prevents two users editing the same post simultaneously, shows "someone else is editing" notice) rather than true simultaneous co-editing; real-time concurrent editing (like Google Docs) requires a plugin.

Core has a basic "Pending Review" post status usable by Contributors, but structured multi-step editorial approval workflows require a plugin (e.g., PublishPress, Edit Flow).

Core provides native Preview (draft preview before publishing, documented officially); a true staging environment (clone of production for testing) is not a core feature and requires a hosting-provider tool (Kinsta, Pressable, WP Engine one-click staging) or a plugin (WP Staging).

No native in-editor commenting/annotation on drafts (distinct from public post comments, which are native); editorial commenting requires a plugin. It is planned work under Gutenberg Phase 3 (Collaboration) on the official roadmap, not yet shipped in core.

No native audit/activity log of admin actions in core; requires a plugin (e.g., WP Activity Log, Simple History) or host-level logging. Source is the official directory listing for a leading audit-log plugin.

Support model differs fundamentally from single-vendor platforms; no central paid support tier for WordPress itself.

No official 24/7 support exists for WordPress core itself (community forums only); many managed-WordPress hosts offer 24/7 support for their hosting/infrastructure layer, but that is a host feature, not a WordPress.org one.

Editorial judgment: wordpress.org/documentation and developer.wordpress.org provide extensive, actively maintained official documentation (user docs, developer handbooks, REST API reference, WP-CLI reference, theme/plugin handbooks), backed by one of the largest volunteer communities and third-party knowledge bases of any web platform.

Community size claim (~43% of the web) is a widely repeated W3Techs statistic; treat as approximate and time-sensitive rather than an official WordPress.org figure.

This is a structural difference from hosted platforms, which can certify their own infrastructure; self-hosted WordPress's security posture depends on the chosen host and the site owner's own practices.

No automatic backups in core; requires a plugin (UpdraftPlus, BlogVault) or a host-provided backup feature (most managed-WordPress hosts include automated backups, but that is a hosting feature, not core software).

Core provides a foundation, not a complete accessibility solution.

WordPress core ships translated in 70+ languages (the admin/software UI), but multi-language content on a single site (multiple language versions of the same page) is not native; requires a plugin, dominantly WPML (1.5M+ sites) or Polylang (800,000+ active installs).

Not native to core, but standard once a multilingual plugin (WPML, Polylang) is installed; both provide structured translation-management workflows.

Not native to core; both WPML and Polylang automatically generate hreflang tags and per-locale URL structures once installed, and integrate with major SEO plugins.

Native RTL (right-to-left) language support built into WordPress core and the block editor for languages like Arabic and Hebrew; theme-level RTL stylesheet support (rtl.css / style-rtl.css) is a documented core convention.