Freelance creator SGEN onboarding guide
| Field | Value ||---|---|| Audience | public || Page type | guide || Area | _workflows/role-onboarding || Updated | 2026-05-25 |How to onboard as a freelance creator in SGEN
This guide is your complete setup playbook as a solo creator — coach, consultant, independent designer, writer, or any operator who owns every part of their site without a team to delegate to.
You control brand, content, visuals, and operations in one account. No handoffs. No role hierarchy. No one to catch your mistakes if the backup is missing or the form notification breaks at midnight. That is the upside and the constraint of running solo, and this guide is built around both.
The guide runs through six setup phases: brand kit and globals, core pages, lead capture, first blog post, SEO defaults, and backup activation. By the end of phase six your site is live, inquiries are landing in your inbox, and you can update any part of it without breaking the rest.
Before you start
Before your first session in SGEN, have these decisions made — not half-made, made.
- Positioning is locked. You know what you offer, who it is for, and the one sentence that says so. If this is still fuzzy, SGEN will expose the fuzziness on every page. Resolve it first.
- Brand kit is ready. Logo file (PNG, SVG, or WebP), primary and accent color hex codes, and your font choices. SGEN's Globals screen accepts hex codes and font names directly — showing up without them means your first session stalls at step one.
- Five to ten priority pages are mapped. A list on paper is enough: Homepage, About, Services or Work, Contact, and optionally a Portfolio or Blog index. You do not need copy for all of them — you need the list.
- Payment decision is made if you are monetizing. If you plan to gate content for paid clients or sell directly from your site, decide on your payment processor before you start building. That decision affects how you set up forms and which settings you need to activate.
- Your admin credentials are saved and tested. SGEN does not send automatic password-reset emails unless SMTP is configured in Settings. Confirm your password before your first build session — a lockout mid-session with no teammate to call wastes real time.
If any of the above is missing, stop and fill the gap before opening SGEN. The setup phases below assume all five are resolved.
Where to go
As a solo creator you are also the site administrator. You have full access to every area in SGEN from the moment you log in.
Your primary areas in roughly the order you will use them:
| Area | What you do there |
|---|---|
| Settings → Globals | Set brand colors, fonts, and site-level defaults |
| Settings → Site Info | Site name, tagline, favicon, and admin email |
| Pages | Build and publish your homepage, About, Services, and supporting pages |
| SG-Builder | Visual page layout — drag, drop, configure each section |
| Blog | Draft, schedule, and publish editorial posts and portfolio entries |
| Forms | Build lead-capture and contact forms; review submissions |
| Media | Upload and organize images, logos, and downloadable assets |
| Settings → SEO | Global SEO title format, meta description defaults, robots directives |
| Settings → Backup & Restore | Scheduled and manual backups — your only recovery path when working solo |
| Custom Objects | Optional — structured data for portfolios, testimonials, case studies |
You do not need to visit anything not on this list during your initial setup. Come back and explore further once your site is live and the basics are in place.
What is this for?
This guide is a role-scoped setup path for a freelance creator operating as the sole admin of a SGEN site.
It answers "where do I start and what order does it go in?" rather than teaching individual features from scratch. Each section links to the relevant reference doc for the feature it covers — follow those links when you need field-level detail.
The phases cover the full scope of a solo creator's launch: brand identity (Globals), public pages (SG-Builder), lead capture (Forms), content engine (Blog), discovery (SEO), and continuity (Backup). That is the full stack. You own all of it.
Good use cases
- You are launching your personal-brand site and want a structured setup order rather than clicking around at random.
- You are migrating from a builder that limited what you could customize and want to set up SGEN correctly from the start.
- You are a coach, consultant, independent designer, or freelance writer who runs one site, bills clients directly, and needs the site to capture inquiries reliably.
- You want to run a content engine — regular blog posts, a portfolio, or a newsletter landing page — from the same platform where your main site lives.
- You are setting up for a paid-content model and need to understand how forms, gating, and custom objects fit together before you build.
What NOT to use this for
- Do not use this guide if you are managing a team of content authors. The freelancer path assumes you are the only person writing, editing, and publishing. If you have staff with different roles, start with the Content Editor guide and Marketing Manager guide and add role assignments from Settings → Users before building.
- Do not use this guide if you are running a large product catalog with orders, fulfillment, and inventory. That workflow belongs in the Ecommerce Manager guide.
- Do not use this guide if you are managing multiple client sites from a single dashboard. The solo-admin path covers one site only. Multi-client agency work is covered in the Partner / Agency guide.
- Do not treat this guide as a brand strategy primer. SGEN will not help you decide on positioning, pricing, or offer structure. It will execute your decisions at speed — but you need to arrive with those decisions made.
How this connects to other features
- Build and manage pages — the Pages index where you create, publish, and organize all public-facing pages on your site.
- SG-Builder overview — the visual editor used to lay out each page; each section is built and published from here.
- Create a form — the form builder for lead capture, inquiry, and contact workflows; includes field configuration and notification setup.
- View and manage form submissions — your lead inbox; every entry from every form, filterable and exportable.
- Create and manage blog posts — draft, schedule, and publish editorial posts; also used for portfolio entries when structured as a blog category.
- Upload and manage media — image library and file management; toggle WebP and compression before uploading.
- Site settings — site name, timezone, email, integrations, and SMTP configuration.
- Backup and restore — scheduled and manual backup configuration; the only recovery path when you are working without a teammate.
- Custom Objects — structured content types for portfolios, testimonial libraries, case studies, or service menus that repeat across pages.
What success looks like
After completing all six phases, a healthy solo-creator setup in SGEN looks like this:
Site is live. Your homepage, About, Services, and Contact pages are published and resolving at your domain. A visitor who lands on any page can understand what you do, see evidence of your work, and take an action.
Leads arrive in your inbox. Your inquiry form is active, form notifications are set to your email, and the Notified column in Forms → Submissions shows Yes on every entry. You do not need to log into SGEN to know someone reached out — the email arrives.
Content is in motion. At least one blog post or portfolio entry is published. A second is in draft. You can add new content without touching any page you have already published.
Brand is consistent. Every page uses the same font stack, color palette, and logo — set once in Globals and applied everywhere. Updating your primary color takes one field change, not twenty.
Backups run automatically. Scheduled backups are active. You know where the backup files live and how to trigger a manual restore. Solo operators have no teammate to catch a broken deploy — your backup schedule is your insurance policy.
SEO defaults are set. Your global title format, meta description template, and robots directive are configured in Settings → SEO. Individual pages can override them, but the defaults cover every page that has not been individually configured.
A site at launch-day baseline — four pages live, first lead captured, backup running — looks like this:
What to do if it does not work
Globals changes are not showing on the site. Changes to Globals apply site-wide but may require a hard reload to clear browser cache. Hold Shift and reload the page. If a specific page still shows old styles, open that page in SG-Builder, confirm the section style references the global token rather than a hardcoded value, and re-publish the section.
Form submissions are arriving but no email notification is coming through. Go to Forms → Submissions and check the Notified column. If any row shows No, click the row and use the Re-send button. If re-send also fails, go to Settings → Email and confirm your SMTP credentials are entered and tested. Without SMTP configured, SGEN cannot dispatch outbound email from your domain — notifications will queue and fail silently. See Create a form for the notification field and SMTP test workflow.
A published page is not resolving at the expected URL. Go to Pages, find the page, open the edit form, and confirm the slug matches the URL you expect. If the page was set as the site homepage and then unset, its slug may have shifted. Confirm the page is set to Published status, not Draft or Scheduled.
SG-Builder changes look different in the editor than on the live site. Clear localStorage in your browser and reload the editor. SG-Builder caches editor state in localStorage — a stale cache can display an old version of a section while the published site shows the correct one. If the discrepancy persists, re-publish the affected section from SG-Builder and perform a hard reload on the live page.
The brand font is not loading on the live site. Confirm the font was added under Settings → Custom Fonts with a unique name and the correct source URL. Fonts added through the Google Fonts list load from the CDN automatically. Self-hosted fonts require the correct file path. If the font name in Globals does not exactly match the name entered in Custom Fonts, SGEN falls back to the system font stack silently. See Site settings for the Custom Fonts workflow.
The backup file is missing or older than expected. Go to Settings → Backup & Restore and check the scheduled backup frequency and the timestamp on the most recent file. If the scheduled backup has not run, confirm the schedule is active and that your hosting plan includes scheduled backups. For critical sessions — a major page rebuild, a Globals change, a new form deployment — run a manual backup first so you have a clean restore point before you start.
Phase 1 — Brand kit and globals
Your brand kit goes in first. Everything else on the site inherits from it. One field change in Globals updates every page that references the token — that use only exists if Globals is set up before you build pages.
Steps — brand kit setup
1. Open Settings → Globals
Go to Settings → Globals in the SGEN admin sidebar. You will see fields for your color palette (primary, secondary, accent, neutral tones), font stacks (heading and body), and border radius defaults.
Enter your primary color hex code in the Primary color slot. Enter your accent or secondary color in the corresponding slot. Save before moving to the next field — SGEN auto-saves on field blur but a manual save after each group prevents silent failures.
2. Set your font stack
Still in Globals, locate the typography section. Set your heading font and body font. If your chosen typeface is on the Google Fonts list, select it by name — SGEN loads it from the CDN automatically. If you are using a self-hosted or custom axis font, add it first under Settings → Custom Fonts with a unique name, then reference that name in Globals.
Use a unique name for custom fonts — a generic name like "custom" can collide with existing entries and load the wrong file.
3. Upload your logo and set the favicon
Go to Settings → Site Info. Upload your logo file to the Logo field. Upload a 512×512 PNG to the Favicon field — SGEN scales it to all required sizes. Set your site name and tagline. These fields feed your SEO title defaults and appear in your browser tab and share previews.
A complete Globals and Site Info setup for a solo coaching practice — Maya Reyes, solo coach — reads like this at the end of Phase 1:
Phase 2 — Core pages
With Globals in place, build the three pages every solo creator needs before anything else: homepage, About, and Services (or equivalent work/portfolio page). Build in that order. Homepage first — it sets the layout conventions the other pages will follow.
Steps — core page setup
1. Create and configure the homepage
Go to Pages and click Add New. Name the page Home and set the slug to match your domain root (leave it blank if your platform sets the root automatically, or enter / if the slug field requires an explicit value).
Open the page in SG-Builder. Build the hero section first: headline, supporting statement, and a single primary CTA button. The CTA should link to your lead-capture form or your booking page — give a visitor who is ready to act somewhere to go within five seconds of landing. Publish the hero section before moving to the next.
Add a brief proof section below the hero: two or three lines about who you work with and what changes for them. If you have testimonials, add one here. Publish each section individually — do not build the entire page and then publish all at once.
Set this page as the site homepage from Settings → Homepage after you publish it.
2. Build the About page
Create the About page from Pages → Add New. Open it in SG-Builder. The About page for a solo creator has one job: establish credibility and create a personal connection in under 60 seconds of reading. Include a clear headshot or professional photo, three to five sentences about your background and working style, and a secondary CTA linking to your contact form.
Keep this page focused. One column, clear reading order, no sidebars competing for attention.
3. Build the Services (or Work) page
Create the Services or Work page. If you offer distinct service packages (coaching sessions, retainer models, design briefs), present each as a named block with a brief scope description and a CTA. If you are a portfolio-first creator (designer, writer, photographer), use this page to display selected work samples linked to case-study posts.
A representative Pages index for Maya at the end of Phase 2 — three core pages published and the blog index in draft — reads like this:
Phase 3 — Lead capture form
A published site with no working form is not a lead-generation site — it is a brochure. Set up your inquiry form in Phase 3, before you spend time on blog posts or SEO. Leads in your inbox justify the rest.
Steps — lead form setup
1. Build the inquiry form
Go to Forms and click Add New. Name the form something specific: Coaching Inquiry, Project Brief, Work With Me — not "Contact Form." The name appears in your submission inbox; a specific name makes triage faster when you have multiple forms.
Add the fields your inquiry process needs. A solo coaching or consulting intake typically includes: name, email, the type of work they are inquiring about (a dropdown or radio set works here), a short message field, and optionally a timeline or budget field. Do not add fields you will not act on — every extra field reduces completion rates.
2. Configure notification settings
In the form editor, locate the Notifications section. Set Send To to your working email address. Set the Subject to something identifiable: "New coaching inquiry — [Name]" reads at a glance in a busy inbox.
If you are using Gmail or another hosted provider for your working address, test the notification before publishing — confirm a submission arrives and lands in your primary inbox, not a spam or promotions folder.
3. Embed the form on your Contact page and homepage CTA
Create a Contact page from Pages → Add New if you have not already. Embed the inquiry form using the form embed shortcode from the form editor's Embed tab. Add the embed to the Contact page and link your homepage CTA button to /contact.
If your homepage has a secondary CTA section ("Ready to work together?"), embed the form there directly rather than linking away — a visitor who can submit without leaving the homepage converts at a higher rate.
A form submissions view after the first week live — four inquiries, all notified, one reply sent — looks like this for Maya:
Phase 4 — First blog post
Your first published post establishes the content pattern for everything that follows: what you write about, how long your posts run, what images look like, and how posts link back to your services. It also gives search engines something to index — a site with only static pages ranks on your name; a site with published posts ranks on the topics your clients search.
Steps — first post
1. Draft in Blog → Add New
Go to Blog and click Add New. Write a post that demonstrates your expertise on the topic most relevant to your primary service. A coach who specializes in executive communication might write "Three presentation habits that undermine senior credibility." A designer might write "What a strong visual identity costs a solo business — and what it recovers."
The first post is evidence of your thinking, not a newsletter blast. Write it as if the most discerning potential client you have will read it before they decide to inquire.
2. Add a featured image and set metadata
Upload a featured image to the post — SGEN uses this in list views, share previews, and any blog-index component that pulls featured images. Toggle WebP and Compression in the media upload modal before uploading; the defaults are Format: Original and Compression: Off, which means unoptimized files go to your media library unless you change them.
Set the SEO Title and Meta Description fields on the post. These override your global SEO defaults for this post specifically. Write the meta description as a complete sentence addressed to the reader — "How three common habits undermine senior credibility in high-stakes presentations, and the fixes that take under a week."
3. Publish and link from the homepage
Set the post status to Published and save. Add a Recent Writing or From the Blog section to your homepage in SG-Builder that pulls your latest post. This keeps your homepage current without manual updates — every new post surfaces automatically.
A Blog index after Phase 4 — one published post, one draft in progress — looks like this:
Phase 5 — SEO defaults
Your pages are live and your first post is published. Now set the global SEO defaults so that every page and post that does not have individually configured metadata inherits something accurate rather than a blank title.
Steps — SEO defaults
1. Set the global title format
Go to Settings → SEO. Find the Title Format field. Set it to a pattern that reads naturally in search results: {Page Title} — Maya Reyes or {Page Title} | Executive Communication Coach. The format applies to every page that does not override it individually.
Avoid formats that put the site name first — search engines display roughly 60 characters before truncation, and a site name at the front pushes your page title toward the cut.
2. Write a site-level meta description
In the same settings screen, write your site-level meta description. One or two sentences that tell a first-time visitor what the site is and who it is for. This description is the fallback for any page or post that does not set its own. Write it for a cold reader who has no prior context — "Executive communication coaching for senior leaders who need to influence up, across, and outside their organization."
3. Set your robots directive
Confirm the Robots directive is set to Index, Follow for your public pages. If any page was set to No Index during draft development, verify it has been switched before publishing. A published page with No Index does not appear in search results — a common cause of "my page is live but not showing up" questions.
Phase 6 — Backup activation
No teammate means no one to catch a failed deploy, a broken Globals change, or an accidentally deleted page. Your backup schedule is your safety net. Set it up in Phase 6 — last, because a backup captures the work done in Phases 1-5. After this phase, every significant change you make to the site exists in at least one recoverable version.
Steps — backup setup
1. Enable scheduled backups
Go to Settings → Backup & Restore. Enable the scheduled backup toggle. Set the frequency to daily for an active site (publishing weekly or more) or weekly for a site in maintenance mode. Confirm the backup destination — SGEN stores backups as .sgen files; verify you know where they download to and can retrieve them if needed.
2. Run a manual backup now
Once scheduled backups are enabled, run a manual backup immediately. This creates a clean restore point that reflects your completed Phase 1-5 setup. If anything breaks in your next session — a Globals change that corrupts your font stack, a page accidentally moved to Trash — you can restore to this point.
3. Test the restore path before you need it
Do not assume the backup works until you have seen the restore flow at least once. While you are in Settings → Backup & Restore, locate the most recent backup file and open the restore panel. You do not need to complete the restore — reading the steps and knowing where the control is counts. When you need it at 2 AM you do not want to learn the interface for the first time.
A Phase 6 backup panel for Maya — daily schedule active, latest backup from today — reads like this:
Your site after all six phases
When all six phases are complete, your solo-creator setup is live and functional. You have brand consistency built into Globals, not painted on per page. You have an inquiry path that works while you are offline. You have a content engine that can grow without touching your core pages. And you have a restore point for every future session that matters.
Maya's full launch-day snapshot — brand set, pages published, form live, first post published, SEO defaults active, backup scheduled — reads like this:
Working solo — what breaks first
The six-phase setup above covers launch. The patterns below cover the first 90 days after launch, when solo operators run into predictable friction.
Tab sprawl and decision fatigue
SGEN's admin panel covers a lot of surface area. After launch, the temptation is to explore features that were not in scope during the setup phases — Custom Objects, Popups, advanced SEO, Custom Codes. For a solo operator, exploring too many areas at once fragments your attention and produces half-built features that degrade the site over time.
A working constraint: pick one area to develop per month. Month one is launch and form health. Month two is content cadence. Month three is SEO and traffic. Do not expand the scope until the previous area is working.
Brand drift across updates
When you are the only person updating the site, brand drift happens through small decisions: a slightly different button label here, a different shade of blue on one page, a paragraph font that differs from the Globals default because you hardcoded it in the editor.
The fix is Globals discipline: every style that exists in Globals should be referenced as a token, not hardcoded. When you update, update Globals first, not the individual page. If a section is not responding to a Globals change, that section has a hardcoded style overriding the token — fix the section, not the token.
SEO untouched after launch
The most common post-launch gap for solo creators is SEO defaults that were set once and never revisited. After three months of posting, audit your top five posts in Blog → Published. Open each post and confirm the SEO Title and Meta Description fields are filled. Posts with blank metadata fall through to the global default — a generic site description does less for a specific post than a post-specific one does.
A blog audit at the 90-day mark — two posts with SEO configured, three relying on global defaults — reads like this:
Go back and set individual SEO metadata on any post using the global default. The work takes five minutes per post and compounds over time.
Backup forgotten after launch
The most expensive mistake a solo operator makes is the one they make before checking the backup timestamp. After the first 30 days of active updates — publishing posts, revising pages, adjusting Globals — your launch-day backup is stale. The current state of your site is not protected.
A practical rule: run a manual backup before any session that involves structural changes. Structural changes include: editing Globals, publishing a new page, changing the homepage, adding a new form, or modifying Custom Codes. Blog posts and media uploads are recoverable from drafts and source files; structural configuration is not.
Form notification breaks silently
Form notification failures are invisible unless you check. SMTP credentials expire. Email providers update security settings. A working notification configuration from launch can stop working 60 days later with no error on the SGEN side.
Add a monthly check to your calendar: go to Forms → Submissions, filter to the past 7 days, and confirm every row shows Notified: Yes. If any show No, use the Re-send button on that row and then go to Settings → Email to test the SMTP configuration. See View and manage form submissions for the re-send and notification audit workflow.
Other roles on this site
If your site grows past the solo-creator model — you bring on a writer, a part-time editor, or a virtual assistant — use the role guides below to set up their access correctly. Do not give a VA admin access to an account that includes your billing and SMTP credentials. Create a role-scoped account from Settings → Users and share the relevant guide.
| Role | What they own | Guide |
|---|---|---|
| Content Editor | Blog posts, pages, media library | Add with Editor role |
| Marketing Manager | Analytics, forms, popups, blog cadence | Add with Editor role |
| SEO Specialist | SEO fields, redirects, metadata audits | Add with Editor role; escalate to Admin for redirect config |
| Developer | Custom CSS, Custom Codes, SG-Builder Additional CSS | Add with Admin role; brief explicitly |
| Platform Admin | User management, billing, SMTP, backup | Add with Admin role; trust-gate required |
Related reading
- Build and manage pages
- SG-Builder overview
- Create a form
- View and manage form submissions
- Create and manage blog posts
- Upload and manage media
- Site settings
- Backup and restore
- Custom Objects