Website profiles · Technology insights · Alternatives

siteorigin.com

Free, open-source WordPress page builder, themes, and widgets trusted by 400,000+ sites. No bloat, no lock-in. Start building for free.

Development Open Source
Paid content
Visit website
Profile views 8 Outbound visits 3 Normal
SiteOrigin Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
Paid contentObserved
Registered
2004
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is SiteOrigin?

SiteOrigin is a suite of free, open-source tools for building and styling WordPress sites without a heavy framework or vendor lock-in. Its core products are a drag-and-drop page builder that outputs clean code and works with any theme, a widgets bundle (sliders, forms, price tables and more), and a visual CSS editor for adjusting a theme's look in real time. The project has been actively developed since 2012 and reports 400,000+ active installs and a 4.8/5 rating on WordPress.org. Paid premium add-ons and expert support are offered alongside the free tools.

Who it suits

  • Small businesses and freelancers who want a capable builder without recurring licensing costs or code they can't take elsewhere.
  • Developers and agencies who value GPL licensing, clean output and compatibility with both the Classic and Block editors.
  • Site owners who mostly need styling tweaks rather than a full rebuild — the CSS editor is the low-risk entry point.

It is less compelling if you want an all-in-one ecosystem with a large library of prebuilt templates and integrated marketing tools; in that case, a broader commercial builder may save setup time.

A practical next step

Start with the free Page Builder on a staging copy of your site and rebuild one existing page. If the output is clean and the editor feels natural, add the Widgets Bundle; reach for the CSS editor only when you need visual refinements. Compare that experience with alternatives such as Elementor or WordPress.org plugin listings before committing your whole site.

Is SiteOrigin's page builder free to use, or do I need a paid subscription?

SiteOrigin's Page Builder is free to use. The core plugin is open source and GPL-licensed, and the site describes it as free with "no bloat, no lock-in" and reports 400,000+ active installs. You don't need a paid subscription to install it, drag rows and widgets into layouts, or use it with the Block Editor and any theme.

Paid options exist but are optional extras. SiteOrigin sells a Premium addons package for its themes and plugins, and offers expert support for WordPress projects. Treat those as add-ons for people who want more widgets, features or hands-on help, not as a gate on the builder itself. The free Widgets Bundle and the CSS editor are also listed as free downloads.

A practical way to decide: start with the free Page Builder and Widgets Bundle, build one real page, and see whether the free widget set covers your layout. If you later hit a specific missing feature or need direct support, evaluate Premium at that point rather than assuming you need it up front. For background on how the builder compares with the Layout Block and Widget Blocks, see SiteOrigin.

How does SiteOrigin Page Builder compare to other WordPress builders like Visual Composer in terms of page speed?

SiteOrigin Page Builder is generally lighter than Visual Composer on page speed, mainly because it outputs flatter, simpler markup and avoids the heavy frameworks and shortcode layers that older builders like Visual Composer carry. The page itself emphasizes "no bloat," "clean, efficient code," and compatibility with any theme, and one WordPress.org reviewer (drossmedia) specifically says they moved off Visual Composer because it "was slowing down page performance," finding SiteOrigin "really flat" and usable without instructions. That is a user's experience, not a benchmark—but it lines up with the design trade-off: fewer wrapper elements and less bundled CSS/JS usually means faster rendering.

What actually drives the speed difference

Factor SiteOrigin (as described) Typical older builders like Visual Composer
Markup output Clean, flat code; works with any theme Often nested wrappers and shortcode-heavy output
Editor integration Works with Block Editor, doesn't force its own lock-in Historically tied to its own editor/framework
Theme dependency Theme-agnostic Often paired with bundled themes/addons
Weight Positioned as "no bloat" Can load larger asset bundles

Practical decision criterion

If speed is your priority, the builder's code output and your theme/plugin stack matter more than the builder name alone. A concrete scenario: a small business site with a lightweight theme, a caching plugin, and optimized images will usually see SiteOrigin perform well, while a heavy theme plus many addons can erase the advantage regardless of builder. Test with a tool like PageSpeed Insights on a real page before committing.

For context on the alternatives, see Visual Composer and, if you want a mainstream comparison point, Elementor. A sensible next step is to build one representative page in each candidate builder on a staging copy and compare load times directly.

Can I use SiteOrigin widgets and themes with the WordPress Block Editor or only the Classic Editor?

Yes. SiteOrigin's widgets and themes work with both the WordPress Block Editor and the Classic Editor. The page builder integrates with the Block Editor, and the Widgets Bundle can be used with Page Builder or dropped into any widgetized area, so it isn't tied to one editing mode.

Where the difference actually matters

The choice is less about compatibility and more about how you want to build:

  • Block Editor users: Use the Layout Block and Widgets Bundle blocks alongside native blocks. SiteOrigin's own guide compares Page Builder, the Layout Block and Widget Blocks specifically for sites on either editor, which suggests the layout block is the intended path for block-based editing.
  • Classic Editor users: Page Builder's drag-and-drop rows and widgets are the familiar route, and themes work the same way.
  • Mixed sites: Widgets placed in widgetized areas (sidebars, footers) appear regardless of editor, so shared widget content is a practical bridge.

A concrete scenario

If you maintain a site built with the Classic Editor but want to migrate pages gradually, keep existing Page Builder layouts and rebuild new pages with the Layout Block. Widgets Bundle items such as sliders, forms and price tables can stay in widget areas throughout, so they don't need rebuilding during the transition.

How to decide

Pick the Layout Block or native blocks for new block-based pages; keep Page Builder for complex row layouts you already maintain. Either way, confirm your chosen theme renders both editors' output as expected before committing to a full migration. For broader WordPress comparisons, see WordPress.org.

How do I fix contact form emails from SiteOrigin not arriving?

Start by treating it as a delivery problem, not a plugin problem. SiteOrigin's own tutorials cover this exact issue ("Contact Form Emails Not Arriving?"), and the usual cause is that WordPress's built-in mail function sends from your web server, which inbox providers often reject or filter as spam. Work through the checks below in order, since each one explains why the previous step failed.

Check these in order

  1. Look in the spam and junk folders of the recipient, and search the mail account for the sender address. A surprising share of "missing" messages are delivered but misfiled.
  2. Confirm the form itself submits. Submit a test entry and check whether the message appears in the SiteOrigin widgets bundle's stored entries or contact log (SiteOrigin offers a Contact Log addon for this). If the entry is saved but no email arrives, the form works and only delivery is failing.
  3. Send a test to a different provider. Send to a Gmail address and a work address. If Gmail receives it but the business inbox doesn't, the problem is on that inbox's filtering or server side, not in WordPress.
  4. Fix the sender address. Set the "From" address on your domain (for example, [email protected]) rather than a generic default. Mismatched senders are a common spam signal.
  5. Route mail through an SMTP or transactional email service. This is the reliable fix: an SMTP plugin or an email API service sends on your behalf with proper authentication. Providers such as Brevo or Postmark are built for this; check their current sending requirements before choosing.
  6. Set up SPF, DKIM and DMARC records for your domain with your host or DNS provider. Without them, even well-formed mail is more likely to be filtered.

Choosing between fixes

Situation Likely cause Practical fix
Test entry saved, no email anywhere Server mail blocked or unauthenticated SMTP or transactional email service
Email arrives for Gmail, not for the client's inbox Recipient-side filtering Sender domain records, ask recipient to allowlist
Nothing saved when submitting Form or widget misconfiguration Recheck the widget settings and re-add the form

If you use SiteOrigin's widgets bundle, confirm which contact form widget you have and whether entries are being stored. That single check tells you whether to debug the form or the mail path, and saves time otherwise spent changing settings at random.

What do the SiteOrigin Premium addons include, and is upgrading worth it?

SiteOrigin Premium is a set of paid addons that extend the free Page Builder, Widgets Bundle and themes rather than replacing them. The free core is open-source and GPL-licensed; Premium adds extras on top. From the page's own framing, Premium is aimed at people already building with SiteOrigin who want more widget and layout options and access to expert support.

What the addons are for

  • Extra widgets and addons for the Page Builder and Widgets Bundle, such as the Custom Body Class addon mentioned in the tutorials (targeting any page with a body class) and the Contact Log addon (keeping a record of contact form messages).
  • Support for your WordPress projects, which the page lists as a Premium benefit.
  • Theme and plugin extensions that build on the free themes and plugins.

The page does not enumerate every addon or its limits, so check the Premium page's own list before assuming a specific feature is included.

Is it worth it?

That depends on whether the extras map to work you'd otherwise pay for:

Your situation Reasonable call
You use the free builder and need the specific Premium addons (e.g. contact logging, body classes) Premium is the direct route
You want paid support for client sites Support alone can justify it for agencies
You only need drag-and-drop layouts, widgets and CSS tweaks The free tools likely cover you

A practical next step: list the Premium addons you'd actually use, then compare that against the cost of a separate plugin for each. If two or more are must-haves, or you need support, upgrading makes sense; if none are, stay on the free core.

For broader context, the free Page Builder is on WordPress.org, and alternatives include Elementor and WordPress.org for plugin listings and reviews.

Related questions

More questions →
What Are Open-Source UI Element Libraries and How Do They Differ From UI Frameworks?

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

  • Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
  • UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
  • Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

Dimension Open-source UI element library UI framework / design system
Unit of reuse A single snippet you copy A component you import or call
Installation None; paste into your code Package install, config, sometimes a provider
Consistency Depends on you; each element may look different Enforced by shared tokens and APIs
Theming Manual edits per element Central theme/config file
Updates You own the copy; no upstream updates Version bumps bring fixes and changes
Accessibility Varies per contributor; must be checked Usually tested and documented
Best for Prototypes, landing pages, small sites, one-off needs Multi-page apps, teams, long-lived products
Learning curve Low—read the CSS Higher—learn the API and conventions

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

  1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
  2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
  3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
  4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
  5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

  • Keyboard focus is visible and the element is reachable by Tab.
  • Color contrast meets WCAG AA (4.5:1 for normal text).
  • Interactive elements use semantic HTML (<button>, not a clickable <div>).
  • Form inputs have associated labels.
  • Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

  • Prototypes and demos: you need something clickable today, not a design system.
  • Landing pages and marketing sites: a handful of distinctive elements, each custom.
  • Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
  • Learning: reading well-made CSS is one of the fastest ways to improve.
  • Small projects: a personal site doesn't need a theming architecture.

Where they fall short

  • Consistency at scale: ten elements from ten contributors rarely look like one product.
  • Maintenance: you own every copy. When your design changes, you edit each one.
  • Accessibility debt: you inherit whatever the contributor did or didn't do.
  • No upstream fixes: a bug fixed in the original won't reach your copy.
  • Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2004, this domain has about 22 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is GoDaddy.com, LLC, a widely used domain service provider. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Google Workspace email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google. Such markers may also remain after a service stops being used.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: HSTS, CSP, Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

The public page identifies WordPress, jQuery, Google Analytics, Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 58 characters, within a common display range. A meta description is present, with 135 characters. The observed directives allow indexing and link following.

Hosting and Email
DNSCloudflare
HostingCloudflare
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.26.10.241

Registration details

RDAP / WHOIS

RegistrarGoDaddy.com, LLC
Registered2004-04-27
Expires2030-04-27
Domain statusclient delete prohibited、client renew prohibited、client transfer prohibited、client update prohibited
Nameserversnoah.ns.cloudflare.com、pam.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Asiteorigin.com104.26.10.241300—
Asiteorigin.com104.26.11.241300—
Asiteorigin.com172.67.69.97300—
AAAAsiteorigin.com2606:4700:20::681a:af1300—
AAAAsiteorigin.com2606:4700:20::681a:bf1300—
AAAAsiteorigin.com2606:4700:20::ac43:4561300—
MXsiteorigin.comaspmx.l.google.com3001
MXsiteorigin.comalt1.aspmx.l.google.com3005
MXsiteorigin.comalt2.aspmx.l.google.com3005
MXsiteorigin.comaspmx2.googlemail.com30010
MXsiteorigin.comaspmx3.googlemail.com30010
NSsiteorigin.comnoah.ns.cloudflare.com86400—
NSsiteorigin.compam.ns.cloudflare.com86400—
TXTsiteorigin.combrevo-code:7559062aecbeb25467e6d9873263ec62300—
TXTsiteorigin.comgoogle-site-verification=ACKdg-UQfELvaS1hhERS1K9yfwaYGxcjt077bb5nxmo300—
TXTsiteorigin.comgoogle-site-verification=ZEX3k1ET1MCluvmNcPNJAGT2L1--2USBVQQo7jtPyEU300—
TXTsiteorigin.comv=spf1 mx a ?all300—
DMARC_dmarc.siteorigin.comv=DMARC1; p=quarantine; sp=none; pct=100; rua=mailto:[email protected]; ri=86400; aspf=r; adkim=s; fo=1;300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectsiteorigin.com
IssuerGoogle Trust Services
Valid until2027-01-13T19:49 · Remaining when checked: 87 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlmax-age=432000
servercloudflare
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff

Identified technologies
WordPressjQueryGoogle AnalyticsCloudflare

Pages, Search and Sharing
Meta descriptionFree, open-source WordPress page builder, themes, and widgets trusted by 400,000+ sites. No bloat, no lock-in. Start building for free.
Canonical URLhttps://siteorigin.com/
LanguageEnglish (default)
Twitter Cardsummary_large_image

Social Sharing Preview

16 fields

robots.txt (opens in a new tab)

5 rules
All bots 0 allowed · 3 disallowed
  • Disallow/wp-json/
  • Disallow/wp-login.php
  • Disallow/wp-admin/
googlebot 1 allowed · 0 disallowed
  • Allow/thread/
bingbot 1 allowed · 0 disallowed
  • Allow/thread/

Sitemaps

1

User reviews (0)

  • No reviews yet.