WordPress.com Review
🔗 **Source:** [WordPress.com Review](https://www.pcmag.com/reviews/wordpresscom)
> [!note]+ Document Notes
> tags: [wordpress-com, website-builders, cms-review, hosting, blogging, woocommerce]
> author: [MISSING]
> source: PCMag
> reference: https://www.pcmag.com/reviews/wordpresscom
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> # 🏷️ Title: WordPress.com Review
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- [WordPress.com](https://wordpress.com)
- [WordPress.org](https://wordpress.org)
- [Automattic](https://automattic.com)
- [WooCommerce](https://woocommerce.com)
- [Jetpack](https://jetpack.com)
## 📝 Summary
- What happened: PCMag reviews WordPress.com as a hosted website builder, walking through plans and pricing, site building, web design, page management, images, blogging, commerce, mobile, AI assistance, stats, uptime, and support.
- Why it matters: It's a high-traffic mainstream review that shapes how non-developers pick between WordPress.com and pure builders like Wix, Squarespace, and Duda. It also tries to draw the WordPress.com vs WordPress.org line for newcomers.
- Key stakeholders: Automattic (the vendor), prospective site owners and bloggers, competing builders, and the broader WordPress open-source project whose name gets borrowed here.
- Risks and tradeoffs: The review repeatedly conflates "WordPress.com" (the hosted product) with "WordPress" (the open-source CMS), which can mislead readers about what they're actually buying and who builds it. It also judges a block/CMS editor against WYSIWYG-builder expectations.
- Bottom line: The reviewer calls WordPress.com a good, low-cost, blogging-first option with excellent uptime, but says it feels dated next to modern WYSIWYG builders and rewards people willing to get hands-on.
## 📖 Main Content
- Core argument: WordPress.com is a reasonably priced, blogging-strong hosted platform that now covers most general website needs (commerce, social, drag-and-drop, mobile), but it's less turnkey than WYSIWYG builders.
- The review opens with the key distinction: WordPress.com is a service from Automattic that runs on WordPress.org code, hides the server code, and handles hosting — so it "resembles website builders more than sites built using the open-source WordPress.org code."
- Pricing ladder (as reviewed): ad-supported Free (1GB), Personal $4/mo, Premium $8/mo (13GB, some monetization), Business $25/mo (unlimited storage, plug-ins, all branding removed, 24/7 priority support, one-on-one screen share), Commerce $45/mo (payments, marketing automation), and WordPress VIP for enterprise via sales.
- Editing: the reviewer frames the block editor as "more suitable for blogging than for general website creation" and "not at all WYSIWYG like Wix." Drag-and-drop exists but feels "oddly clunky" next to the block up/down arrows.
- Pages: no pre-built page types (Contact, About, Store) like Duda offers — you assemble pages from widgets/blocks manually. GDPR cookie notice via a widget. Navigation reorder lives on a separate Customizing > Menus page.
- Images: only crop and rotate, no integrated photo editor like the Aviary integrations in Duda/Squarespace/Wix; uploads save to a per-site reusable repository.
- Commerce: PayPal buttons on premium plans; full store via the WooCommerce plug-in (also an Automattic product), a five-step setup. Newsletters and email marketing supported.
- AI: the Jetpack AI Assistant, "derived from the OpenAI API," handles spelling/grammar, titles, translation, and lookups — free for a limited time, expected to become paid.
- Stats and SEO: robust stats (views, visitors, top search terms, visitor geo map, Insights), editable meta titles/descriptions, and a separate WP Admin page to submit the site to search engines.
- Portability: you can export contents as an XML file and move to another WordPress host (the review says this requires installing the Jetpack plug-in on that host).
- Uptime: a 14-day monitoring test (15-minute ping interval) found zero downtime.
- Support: community-only on Free; email and chat 24 hours Monday–Friday on paid; Business gets a 30-minute Concierge Zoom session; no regular phone support. Support reps are branded "Happiness Engineers."
- Contested/uncertain claims: the WordPress.com-vs-WordPress.org framing is muddied throughout (see Logical Validity). The "Jetpack required for XML import on another host" claim is questionable — WordPress core import/export doesn't require Jetpack. The "derived from the OpenAI API" detail and free-forever caveat are time-sensitive and likely stale.
### 🗒️ Notes
- The lede sells the value angle first: cheap, fast to launch, free tier exists.
- The single most important framing in the piece: "WordPress.com is not WordPress in the commonly understood sense" — a service from Automattic using WordPress.org code, hiding the server and handling hosting.
- Editor critique anchors the whole review: blogging-first, block-heavy, not WYSIWYG, drag-and-drop bolted on and clunky.
- Free themes get a genuine compliment — "some rival Squarespace's slick visual style" — with tablet/phone/desktop previews.
- Page management is deliberately manual: widgets/blocks instead of templated page types; the reviewer dings the split between Page Settings and Customizing > Menus as un-DIY-friendly.
- Blogging is the declared strong suit: "For blogging features, WordPress.com is hard to beat," with the Reader community (follow, Discover, recommendations) as a differentiator most builders lack.
- Commerce is plug-in-driven (WooCommerce), fast to bolt on, full-featured store once added.
- Mobile: no dedicated mobile-design tools or preview, but responsive templates; mobile apps can edit themes, menus, plug-ins, and stats but can't manage store products.
- AI Assistant demo (Seoul travel suggestions) reads as a light, anecdotal test rather than a rigorous one.
- Uptime is the most empirical section: a real 14-day, 15-minute-interval monitoring test, zero downtime.
- Verdict line: blogging-and-then-some; great inexpensive hosting/blogging if you don't mind manual customization, but Editors' Choice goes to Duda and Wix for faster prefab layouts.
- Byline note: Michael Muchmore "also contributed to this review," but no primary author is named in the supplied text.
## 📚 References
- [WordPress.com](https://wordpress.com)
- [WordPress.org](https://wordpress.org)
- [Automattic](https://automattic.com)
- [WooCommerce](https://woocommerce.com)
- [Jetpack](https://jetpack.com)
- [Jetpack AI Assistant](https://jetpack.com/ai/)
- [Squarespace](https://www.squarespace.com)
- [Wix](https://www.wix.com)
- [Duda](https://www.duda.co)
## 🗣️ Paraphrase
- WordPress.com bundles building, hosting, and blogging at low prices, including a free tier, and now covers commerce, social, and mobile beyond its blogging roots — a quick, cheap way to get online.
- Crucially, it's not the open-source WordPress; it's Automattic's hosted service built on WordPress.org code, closer in feel to a website builder than to self-hosted WordPress.
- Plans run from ad-supported Free up through Personal, Premium, Business, and Commerce, with WordPress VIP for enterprise, and the pricing lands as reasonable against Wix, Squarespace, and Duda.
- The editor is blogging-first and block-based, not WYSIWYG, with clunky drag-and-drop; pages are assembled manually from widgets rather than from templated page types.
- Strengths are blogging (including the Reader community), excellent uptime, robust stats, plug-in commerce via WooCommerce, and a (temporarily free) Jetpack AI Assistant; the main knock is a dated, hands-on interface versus modern builders.
## 📰 Newsletter
- Heads up, builders: PCMag's WordPress.com review is a useful reminder that "WordPress.com" and "WordPress.org" still confuse newcomers — and even the reviewers blur the line. If you do DevRel or support, this is the exact gap your docs should close.
- The good news for your blogging friends: the Reader community, solid stats, and rock-solid uptime still make WordPress.com a friendly on-ramp. The caveat: the editor reads as blogging-first, and the review judges blocks against WYSIWYG expectations.
- Commerce is a WooCommerce plug-in away, and the Jetpack AI Assistant is free for now (expect that to change). Want the clearest explainer to hand a client? Point them at [How to Get Started With WordPress](https://wordpress.org/support/article/new-to-wordpress-where-to-start/) and the WordPress.com vs .org distinction before they pick a plan.
## ✅ Action Items
#### DevRel
- Developer advocacy: publish a crisp "WordPress.com vs WordPress.org vs self-hosted" explainer that fixes the exact conflation this review makes.
- Education: build a short workshop on choosing block editor vs WYSIWYG mental models for non-developers.
- Developer experience: ship a one-page migration guide for XML export/import that clarifies Jetpack is not required for core import/export.
- Developer marketing: counter-message the "feels dated" critique with content showing modern Site Editor/blocks workflows.
- Community management: seed Reader/community onboarding tips for new bloggers.
- Internal/external/cross-project: align Automattic product messaging with .org project messaging on naming.
#### OSPO
- Policy & Governance: clarify trademark/naming guidance so press uses "WordPress.com" vs "WordPress" precisely.
- License Compliance: document that WordPress.org code is GPL and how WordPress.com consumes it.
- Security Management: note GDPR cookie-notice widget behavior in compliance docs.
- Software Inventory: track Jetpack/WooCommerce as Automattic-maintained dependencies referenced in reviews.
- Developer Support: prep FAQ answers for "is WordPress.com the real WordPress?"
- Community Engagement: coordinate with press relations on accurate product/project framing.
- Strategic Alignment: measure how naming confusion affects funnel and support load.
#### Community
- Maintainers: provide a canonical naming/positioning snippet maintainers can reuse.
- Contributors: invite contributions to the "get started" primer the review links to.
- Sponsors: surface that WooCommerce/Jetpack are commercial Automattic products in transparency notes.
- Ecosystem: coordinate messaging with hosts on portability and migration paths.
#### WordPress
- Core: note that block-vs-WYSIWYG perception is a recurring reviewer complaint worth addressing in onboarding.
- Core Performance: nothing actionable from this review beyond uptime (host-side).
- Core AI: track third-party framing of Jetpack AI ("derived from the OpenAI API") for accuracy.
- **Core Program Team:** flag naming-confusion as a cross-team narrative issue.
- Mobile: address the gap that mobile apps can't manage store products.
- Playground: build a Playground demo that shows the block editor isn't "blogging-only."
- Community: equip meetup organizers to answer .com vs .org questions.
- Training: add a Learn lesson on choosing hosted vs self-hosted.
- Marketing: rebut the "dated interface" framing with current Site Editor visuals.
- Support: prepare canned responses for migration and Jetpack-import myths.
- Design: gather the "clunky drag-and-drop" critique as UX research input.
- Documentation: tighten DevHub/HelpHub on export/import requirements.
- Photos: n/a.
- TV: n/a.
- Polyglots: note that AI translation is a selling point worth localized docs.
- Accessibility: review block editor against WCAG given "hands-on" framing.
- Meta: ensure .org "where to start" content ranks for these comparison queries.
- CLI: n/a.
- Hosting: standardize a host-agnostic migration checklist.
- Tide: n/a.
- Openverse: n/a.
- Themes: highlight free themes that "rival Squarespace" as showcase material.
- Plugins: document WooCommerce setup path referenced here.
#### The WPCC
- Programs: consider a "WordPress literacy" track aimed at non-developer site owners.
- Projects: a documentation sprint to fix .com/.org confusion in third-party-facing content.
- Funding experiments: n/a.
### FAIR
- Technical independence: this review underscores that hosted .com hides server code — a contrast point for FAIR's local-metadata/provenance arguments.
- Policies and covenants: naming/ownership transparency is the relevant covenant theme.
- Productized governance artifacts: a positioning scorecard distinguishing hosted product from open project.
## 🧪 Hypotheses
- Readers exposed to this review will conflate WordPress.com with WordPress.org at a measurably higher rate than readers given a corrected explainer.
- Users who choose WordPress.com primarily for blogging report higher satisfaction than those choosing it for general site building.
- The "feels dated / not WYSIWYG" perception drops significantly when users are shown the current Site Editor rather than the classic block flow described here.
- WordPress.com uptime over a longer window (90 days) remains effectively at or near 100%, consistent with the 14-day result.
- A material share of prospective buyers don't realize WooCommerce and Jetpack are Automattic products until told.
### 📊 Methodology
- Run an A/B comprehension study: show one group this review, another a corrected explainer, then test .com-vs-.org understanding.
- Survey WordPress.com users segmented by primary use case (blog vs general site vs store) on satisfaction and editor perception.
- Usability test classic block flow vs current Site Editor with non-developers; measure task success and "dated" ratings.
- Reproduce the uptime test at 15-minute intervals over 90 days with an independent monitor.
- Card-sort or survey to measure awareness of Automattic's ownership of WooCommerce/Jetpack.
### ❓ Questions
- How should press consistently disambiguate "WordPress" (project), "WordPress.org" (self-hosted), and "WordPress.com" (hosted)?
- Is the claim that XML import on another host "requires" Jetpack actually true, or a reviewer error?
- Is the Jetpack AI Assistant still "derived from the OpenAI API," and is it still free?
- Does the block editor still warrant a "blogging-first" label given Full Site Editing?
- What's the real conversion impact of naming confusion on the funnel?
### 🔮 Future Research
- A longitudinal study of how mainstream review framing shapes WordPress brand perception.
- Comparative editor-usability research across WordPress.com, Wix, Squarespace, and Duda with current builds.
- An accuracy audit of recurring claims in WordPress.com reviews (Jetpack-required import, AI provider, free-tier limits).
- Measuring whether the Reader community meaningfully improves blogger retention versus pure builders.
### 💡 Implications
- Practice: DevRel and support teams should treat .com/.org disambiguation as a first-class onboarding asset.
- Policy: trademark and press-relations guidance can reduce repeated naming conflation in high-traffic reviews.
- Security: GDPR cookie-notice and hosted-server-hiding details belong in compliance and trust messaging.
- Education: choosing hosted vs self-hosted deserves a dedicated, evergreen Learn lesson.
- Funding models: the commercial nature of WooCommerce/Jetpack should be transparent to buyers and to the open project's positioning.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade roughly 9–11 (mixed sentence length, some compound product/pricing sentences); Flesch Reading Ease roughly 45–55 (fairly difficult). Estimated from sentence length and syllable density, not a tool run.
#### 👀 Visual learners
- Present: captioned product screenshots (desktop theme view, phone preview), all credited to WordPress.com.
- Improve: add a pricing-tier comparison table, a .com-vs-.org diagram, and before/after editor screenshots.
#### 🔊 Aural learners
- Present: none — text and images only.
- Improve: add a 2–5 minute audio summary or TTS narration of the verdict and pricing.
#### 🗣️ Verbal learners
- Present: plain-language definitions of the .com/.org distinction and comparisons to Wix/Squarespace/Duda.
- Improve: add a short glossary (block, widget, WYSIWYG, WooCommerce, Jetpack).
#### 🧩 Kinesthetic learners
- Present: implicit step-by-steps (site creation flow, five-step store setup).
- Improve: a reproducible "build your first page" checklist readers can follow.
#### 🧠 Logical learners
- Present: ordered pricing ladder and feature-by-feature section structure.
- Improve: a decision tree (blog vs store vs general site → recommended plan) and a feature matrix.
#### 🧑🤝🧑 Social learners
- Present: mentions the Reader community, follows, and Discover.
- Improve: link to forums or community Q&A for setup help.
#### 🧘♀️ Solitary learners
- Present: self-contained narrative readers can work through alone.
- Improve: a self-check "is WordPress.com right for me?" quiz.
#### 🌿 Naturalistic learners
- Present: none.
- Improve: note hosting sustainability/efficiency where relevant.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: clear section headings structure the review.
- Improve: ensure images (theme view, phone preview) carry descriptive alt text beyond "(Credit: WordPress.com)."
#### Keyboard navigation
- Present: not assessable from supplied text (publisher-page concern).
- Improve: verify the PCMag article page has visible focus and logical tab order.
#### Contrast and readability
- Present: not assessable from text.
- Improve: confirm 4.5:1 body-text contrast on the live article.
#### Text resizing and reflow
- Present: not assessable from text.
- Improve: confirm reflow at 200% zoom on the article page.
#### Media and captions
- Present: images are captioned with credits.
- Improve: add genuine alt descriptions; if any embedded media exists, provide transcripts.
#### Forms and interactions
- Present: n/a to the article content itself.
- Improve: n/a.
#### Standards reference
- Map gaps (image alt text, contrast, reflow) to WCAG 2.2 AA: 1.1.1 Non-text Content, 1.4.3 Contrast, 1.4.10 Reflow.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: the AI demo uses a Seoul, South Korea example, a small non-US touch.
- Improve: include non-US pricing/currency context and global hosting considerations.
#### Inclusive language
- Present: generally neutral, jargon mostly defined.
- Improve: define remaining terms (XML, metatitles) for first-time site owners.
#### Neurodiversity support
- Present: consistent section structure and chunked content.
- Improve: more frequent subheadings and an upfront summary box.
#### Representation
- Present: minimal — product-focused, few people referenced beyond a contributing reviewer.
- Improve: include varied user personas (blogger, small-shop owner, nonprofit).
#### Psychological safety
- Present: respectful, non-alarmist tone.
- Improve: n/a.
### ✅ Logical Validity
#### Strong reasoning
- Inductive (uptime): the 14-day, 15-minute-interval monitoring test supporting "remarkably stable" is the review's strongest empirical claim — a real measurement generalized cautiously. Clarify by reporting the exact uptime percentage and the longer-term window.
- Comparative/analogical (pricing): benchmarking against Squarespace ($19), Wix ($14), and Duda ($19) to conclude pricing "is quite reasonable" is a sound comparative move. Clarify by normalizing feature tiers, since the compared plans differ.
- Causal (editor → use case): "more suitable for blogging than for general website creation" is reasonably supported by the block/widget-assembly description.
#### Fallacies
- Equivocation / conflation (central, recurring): the review slides between "WordPress.com," "WordPress.org," and bare "WordPress." It states WordPress.com "is not WordPress in the commonly understood sense," yet later writes "WordPress as a whole started life as a blogging platform," "One advantage of WordPress is that your site is portable," and "WordPress is not as streamlined as WYSIWYG website builders" — using "WordPress" to mean the hosted product, the open-source CMS, and the broader project interchangeably. This is the key flaw: it blurs the open-source WordPress (WordPress.org CMS) with WordPress.com (Automattic's hosted service). Fix: use precise nouns throughout — "WordPress.com" for the product, "WordPress (the open-source CMS)" for the software, and avoid bare "WordPress" in evaluative claims.
- Questionable premise: "Doing so requires that you install the JetPack plug-in on your WordPress host server" overstates Jetpack's role — WordPress core export/import doesn't require Jetpack. Fix: verify and correct, or scope the claim to a specific migration method.
- Faulty comparison / category error: judging a CMS/block editor for "not at all WYSIWYG like Wix" applies a builder yardstick to a different tool class without flagging the tradeoff. Fix: state the tradeoff (flexibility/portability vs prefab speed) explicitly.
- Hasty generalization (AI): one Seoul travel-suggestions prompt supports "powerful tool" — a thin sample. Fix: test more varied tasks before the superlative.
#### Tone of voice
- Pragmatic, consumer-advisory, lightly informal ("start venting your mind to the world"), even-handed with clear verdicts. Examples: "It's a good, low-cost option," "the interface feels a bit dated," "For blogging features, WordPress.com is hard to beat."
### 🛡️ DARVO Analysis
- Not applicable to this source. This is a product review, not a defense against accusations — there is no accuser, denial, counter-attack, or victim/offender reversal to analyze. The closest rhetorical move is mild defense of the free themes ("Don't think that the free themes are worthless"), which is consumer guidance, not DARVO.
## 🎯 Conclusion
- Bottom line: WordPress.com is a low-cost, blogging-strong, reliably hosted platform that handles most site needs but trades modern WYSIWYG polish for manual, block-based customization — best for people willing to get hands-on.
- The review's most important contribution and its biggest weakness are the same topic: it names the WordPress.com vs WordPress.org distinction up front, then repeatedly blurs it. Read the pricing and uptime sections as the most reliable, and treat bare-"WordPress" claims (portability/Jetpack, "started as blogging") with care.
- Practical next steps for readers: decide blog-first vs store-first before picking a plan; if you want prefab speed, compare against Wix/Squarespace/Duda; verify current AI Assistant pricing and the Jetpack-import requirement before relying on either; and read the .com-vs-.org primer first.
## 🔄 Refactor Appendix — WordPress.com Review
> Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4).
> Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't
> articulate in one line why a claim matters, drop it.
### 📚 Literature Atoms (H3)
#### [H1] WordPress.com is a hosted Automattic service, not WordPress itself
> [!quote] ID:rw_1
> WordPress.com is not WordPress in the commonly understood sense. Rather, WordPress.com is a service from Automattic Inc. that uses code from WordPress.org
**Context & use**:
- Opening framing of the review (paragraph 3).
- The single most important distinction for newcomers; the review names it then blurs it later.
**Tags**: #xref #addendum
**Highlight**: [view highlight](readwise://)
<!-- atomicity: 1 idea ✓ -->
#### [H2] Hosted WordPress.com resembles a website builder by hiding server code
> [!quote] ID:rw_2
> WordPress.com hides the server code and handles hosting. In that sense, it resembles website builders more than sites built using the open-source WordPress.org code
**Context & use**:
- Paragraph 3, the .com-vs-.org explanation.
- Useful for FAIR/technical-independence contrasts and for positioning hosted vs self-hosted.
**Tags**: #xref
**Highlight**: [view highlight](readwise://)
<!-- atomicity: 1 idea ✓ -->
#### [H3] WordPress.com's editor is blogging-first, not WYSIWYG
> [!quote] ID:rw_3
> The WordPress.com editor is definitely more suitable for blogging than for general website creation. It feels outdated compared with modern web-based site builders
**Context & use**:
- "Web Design With WordPress.com" section.
- Captures the recurring reviewer critique DevRel should counter with current Site Editor content.
**Tags**: #xref #articleseed
**Highlight**: [view highlight](readwise://)
<!-- atomicity: 1 idea ✓ -->
#### [H4] WordPress.com showed zero downtime over a 14-day test
> [!quote] ID:rw_4
> it didn't go down once in the two-week testing period
**Context & use**:
- "Excellent Uptime Results" section; 15-minute ping interval.
- The review's strongest empirical claim; cite when discussing managed-hosting reliability.
**Tags**: #xref
**Highlight**: [view highlight](readwise://)
<!-- atomicity: 1 idea ✓ -->
### 🧠 Permanent Candidates (H4)
#### [P1] Mainstream reviews blur WordPress.com and the open-source WordPress CMS
**Claim** (one sentence, Courtney's voice): High-traffic product reviews routinely conflate the hosted WordPress.com service with the open-source WordPress CMS, creating buyer confusion DevRel must actively correct.
**Evidence pointer**: [[#H1]]
**Scope & conditions**: Holds for consumer-facing press that name the product and the project interchangeably; breaks when writers consistently say "WordPress.com" vs "WordPress (the open-source CMS)."
**Links**:
- [[WordPress.com vs WordPress.org]] — because extends
- [[Developer naming and positioning]] — because applies-in DevRel messaging
- [[Builder vs CMS editing models]] — because contrasts on tool class
<!-- atomicity: 1 idea ✓ -->
### ✏️ Fleeting Queue
- [F1] Verify whether XML import on another host actually requires Jetpack, or if this is a reviewer error — https://www.pcmag.com/reviews/wordpresscom #fleeting #inbox
- [F2] Check current Jetpack AI Assistant provider and pricing (review says "derived from the OpenAI API," free for a limited time) #fleeting #inbox
### → Things 3 (max 2 actions)
- [ ] Draft a crisp WordPress.com-vs-WordPress.org explainer for non-developers — DevRel #things
- [ ] Fact-check the "Jetpack required for XML import" claim and note correction — content #things
<!-- deep-read:sections end -->
📄 **Full text:** [[Full Document Contents/Articles/WordPress.com Review.md|WordPress.com Review by pcmag.com]]
## Highlights
- From the outset, it's important to make clear that WordPress.com is not WordPress in the commonly understood sense. Rather, WordPress.com is a service from Automattic Inc. that uses code from WordPress.org, the popular and free, open-source blogging and site-building platform. In fact, WordPress.com hides the server code and handles hosting. In that sense, it resembles [website builders](https://www.pcmag.com/picks/the-best-website-builders) more than sites built using the open-source WordPress.org code, which requires you to sign up for a [WordPress hosting service](https://www.pcmag.com/picks/the-best-wordpress-web-hosting-services). You can learn more about the WordPress.com and WordPress.org differences in our [How to Get Started With WordPress](https://www.pcmag.com/how-to/how-to-get-started-with-wordpress) primer. ([View Highlight](https://read.readwise.io/read/01kvwwfv28pwz0sa5qsk60m624))
- Note: Central distinction stated up front (then blurred later): WordPress.com (hosted Automattic service) resembles a website builder more than self-hosted WordPress.org.
- Tags: wordpress-com, atom/literature/h1, website-builders
- The WordPress.com editor is definitely more suitable for blogging than for general website creation. It feels outdated compared with modern web-based site builders, because it's not at all WYSIWYG like [Wix](https://www.pcmag.com/reviews/wix) and other modern website builders. WordPress.com introduced drag-and-drop functionality to modernize its editing tools, but it still heavily utilizes blocks. You add or remove content blocks for text, business hours, contact forms, carousels, comments, images (more on that in a bit), and other essential site items. Small arrows at the top of each block section let you move a block up or down. You can also use the drag-and-drop feature to move blocks around, but this feels oddly clunky compared to the conventional arrows. ([View Highlight](https://read.readwise.io/read/01kvwwfz6ea5v2zzwny4a6pd4w))
- Note: Recurring editor critique — blogging-first, block-heavy, not WYSIWYG. (Reviewer's frame, debatable for block-theme users.)
- Tags: atom/literature/h3, cms-review
- We used a website-monitoring tool to track our WordPress.com-hosted test site's uptime over a 14-day period. Every 15 minutes, the tool pings the website and sends us an email if it is unable to contact the site for at least one minute. The testing data reveals that WordPress.com is remarkably stable; in fact, it didn't go down once in the two-week testing period. You need not worry about your WordPress.com site going down for extended periods. ([View Highlight](https://read.readwise.io/read/01kvwwg2d315dyj7hhyjf8kz75))
- Note: Strongest empirical claim: zero downtime over a 14-day, 15-minute-interval monitoring test.
- Tags: atom/literature/h4, hosting