How SGEN is different
If you have built on WordPress, Wix, or Squarespace, four things change: (1) everything is built in — no plugins, no add-on marketplace; (2) no plugin layer at all — features are first-party and updated by the platform; (3) pages render server-side — speed is in the platform, not a caching plugin; (4) you rebuild, you don't import — there is no one-click importer, so plan the move page by page. Everything else — visual editing, pages, posts, menus, media — feels familiar.
All-in-one platform
Builder, hosting, forms, SEO, analytics, ecommerce, and team management are one product — not a core app plus add-ons you assemble.
No plugins
The features other platforms sell as plugins or apps are built in. There is no plugin marketplace to shop, install, update, or troubleshoot.
Rebuild, not import
You move to SGEN by rebuilding pages in SG-Builder — not by running a one-click importer. SGEN does not import a WordPress, Wix, or Squarespace site wholesale.
The short version
Four shifts coming from WordPress, Wix, or Squarespace — read each row as old model → SGEN model.
All-in-one platform
Builder, hosting, forms, SEO, analytics, ecommerce, and team management are one product — not a core app plus add-ons you assemble.
No plugins
The features other platforms sell as plugins or apps are built in. There is no plugin marketplace to shop, install, update, or troubleshoot.
Server-side rendering
Pages are built on SGEN's servers and delivered ready to view. The speed comes from how the platform is built, not from a caching plugin you bolt on.
Rebuild, not import
You move to SGEN by rebuilding pages in SG-Builder — not by running a one-click importer. SGEN does not import a WordPress, Wix, or Squarespace site wholesale.
1. SGEN is all-in-one
On most platforms, the builder is the starting point and everything else — forms, SEO controls, analytics, a store, a consent banner — arrives as a separate plugin, app, or paid add-on. You assemble the site you need from parts.
SGEN ships the whole platform in every plan. Builder, hosting, forms, SEO, analytics, ecommerce, redirects, consent, team roles, and multi-site management are all there from the first login. You are not shopping for capabilities — they are already in the admin, waiting to be used.
Plans differ by how many live sites they cover, not by which features you get. There is no "Pro" tier that unlocks features.
2. No plugins
This is the difference WordPress users feel first. On WordPress, the platform is small and plugins make it big — which is also where update anxiety, conflicts, and the occasional broken site come from. A plugin updates, two others disagree, a page stops working.
SGEN has no plugin layer. Features are first-party parts of the platform, built to work together and updated by the platform itself. There is nothing to install, nothing to keep compatible, no plugin update to schedule around.
The practical effect: when you need a form, you open the Forms module — you do not go find, evaluate, and install a plugin first. The same is true for SEO, redirects, popups, and the rest.
Forms — built in
Open the Forms module. No plugin required.
SEO — built in
Every page has an SEO panel. No plugin required.
Redirects — built in
URL redirect management is in the admin. No plugin required.
Tracking & Consent — built in
Consent banner and tracking controls are built in. No plugin required.
Ecommerce — built in
Store, orders, and catalog management are built in. No plugin required.
Analytics — built in
Traffic and attribution analytics are built in. No plugin required.
3. Pages are rendered server-side
Many builders assemble the page in the visitor's browser, then ask you to bolt on a caching plugin to speed it back up. SGEN renders pages on its own servers and delivers them ready to view. The speed is in the platform, not a tuning step.
You do not manage a cache plugin, and there is no plugin to misconfigure. Server-side rendering is also part of why search engines see your pages cleanly.
What the public page emits is clean, crawlable markup — no client-side rendering framework to unpack, no inline bundle to load before content appears:
What a public SGEN page looks like to a search engine
SGEN delivers the full page HTML from its servers. The title, description, and content are all in the initial response — search engines and visitors read the same thing.
SGEN delivers the full page HTML from its servers. The title, description, and content are all in the initial response — search engines and visitors read the same thing.
<!DOCTYPE html>
<html lang="en">
<head> <title>About Your Business — Your Site</title> <meta name="description" content="Meet the team behind Your Business."> <meta name="robots" content="index, follow"> <link rel="canonical" href="[your-domain]/about">
</head>
<body> <h1>About Your Business</h1> <p>We have been serving customers since 2019 ...</p>
</body>
</html> 4. You rebuild — you do not import
This is the one to plan for. There is no one-click importer that lifts a WordPress, Wix, or Squarespace site into SGEN intact. Moving to SGEN means rebuilding your pages in SG-Builder, bringing content and media across as you go.
That sounds like more work than it is. The rebuild guides walk through it page type by page type — and because you rebuild rather than import, you arrive with a clean site: no plugin cruft, no theme leftovers, no half-migrated layouts.
| Coming from | Guide |
|---|---|
| WordPress | Move your WordPress site to SGEN |
| Wix | Move your Wix site to SGEN |
| Squarespace | Move your Squarespace site to SGEN |
| Webflow, Shopify, Ghost, HubSpot | A dedicated rebuild guide exists for each — see the migration section |
| Starting fresh, no existing site | Skip migration entirely — go straight to building your first site |
What stays the same
Most of what you already know carries over. You still build pages visually, drag components into place, set up navigation, manage media, write blog posts, and preview before you publish. The vocabulary shifts slightly; the work feels familiar.
Familiar concept
Visual page editor
SG-Builder — drag components, edit in place, preview, publish.
Familiar concept
Pages and blog posts
Pages and Posts in the admin — the same idea, same workflow.
Familiar concept
Themes and templates
Templates and the Theme Editor control the shared look of your site.
Familiar concept
Navigation menus
Menus in the admin — build and assign site navigation.
Familiar concept
Media uploads
Media Library — upload, organize, and reuse images and files.