Skip to content
SOSEI

Help center

The questions we hear the most. If your answer isn't here, email [email protected] — a real person reads everything.

Step-by-step guides

Short how-tos with pictures of the studio, for the things owners ask us most.

Going live — publishing your site

While you're on the free trial your rebuild is already viewable on its public /s/your-slug link. To keep it online for good — on your own domain, with the secure padlock — you subscribe. Three short steps:

  1. 1

    Subscribe

    Pick the site to publish and choose monthly or yearly.

  2. 2

    Add your domain

    Settings → Domain, type your bare domain, Save.

  3. 3

    Point your DNS

    Add the records at your provider, then Check status.

You choose which sites to pay for. Open Account and each of your sites has a checkbox:

  • Checked — the site is published and included in your subscription. Each selected site is billed individually.
  • Unchecked — the site stays a private draft: not public, not billed. Turn it on whenever you're ready.

Pick monthly or yearly (annual includes two months free), then Subscribe — your site comes back online immediately. Current prices are on /pricing.

You can change which sites are selected right up until you subscribe. Need to adjust the set afterwards? Email [email protected] and we'll sort it out.

Connecting your own domain

Point your own domain at the rebuild instead of the public /s/your-slug link (custom domains are part of a paid plan). Your dashboard walks you through it and always shows the exact records to add — here's what to expect.

  1. In your project, open Settings → Domain and enter your bare hostname — example.com, not https://example.com, no www., no trailing slash. Click Save.
  2. The dashboard lists the records to add at your DNS provider. For a root domain (e.g. example.com) that's two A records on @ plus one www record, so both example.com and www.example.com reach your site:
DNS records to add
TypeName / HostValue / DataTTL
A@162.159.140.98default
A@172.66.0.96default
CNAMEwwwproxy.sosei.sitedefault

Example for a root domain like example.com. Your dashboard always shows the exact, current values — copy them from there.

  • Works on GoDaddy, Zone.ee, Namecheap, Bluehost, Hostinger and any DNS that supports A records on the apex — no nameserver change needed.
  • On a subdomain (e.g. go.example.com) it's even simpler: a single CNAME → proxy.sosei.site.
  • If your dashboard also lists one or two TXT records, add those too — they confirm ownership and issue the certificate. Many domains don't need them, so add only what your dashboard actually shows.

Your email keeps working. SOSEI hosts your website, not your email. Connecting your domain only changes its website records — your email (MX) records are never touched, so your inbox keeps running exactly as before. Full walk-through in Adding your DNS records below.

SSL certificates are issued automatically once DNS resolves — no extra step. Stuck for more than an hour? Email us with your domain and we'll diagnose.

Adding your DNS records (any provider)

The steps are the same wherever your domain lives — GoDaddy, Namecheap, Hostinger, Cloudflare, Squarespace, Zone.ee, anywhere. You add the same handful of records; only the menu location differs. You stay in control the whole way — nothing on your live domain changes until the new records take effect. The most important part first:

Your email keeps working — untouched.

We host your website, not your email — SOSEI doesn't provide email hosting, so there's nothing to move: your mailbox simply stays with your current provider. When you point your domain at the new site you only change the website records; your email (the MX records, including any Microsoft 365 or Google Workspace mailbox) is never touched, so your inbox keeps running without interruption.

  1. Preview first. Open your project and use the Open button (top right, next to the Live badge) to see the full rebuilt site. Your real domain is untouched until you switch.
  2. Add your domain in SOSEI. Open Settings → Domain, type your bare domain (e.g. example.com — no https://, no www., no trailing slash) and click Save.
  3. Open your provider's DNS screen. Sign in wherever your domain is managed and find the DNS records page — usually labelled DNS, Manage DNS, DNS Zone, or Advanced DNS (per-provider pointers are listed below).
  4. Clear the old records on the root (@). Delete any existing A, AAAA, or CNAME on the root name, and turn off any domain Forwarding / Redirect (a leftover AAAA keeps some visitors on your old site). Leave everything else exactly as it is — especially the MX records, which run your email.
  5. Add these three records. Add each row below. The Name / Host is @ for the two A records and www for the CNAME — some providers want that field left blank or the full domain instead, and all three mean “the root.” Leave the TTL on its default:
DNS records to add
TypeName / HostValue / DataTTL
A@162.159.140.98default
A@172.66.0.96default
CNAMEwwwproxy.sosei.sitedefault

Example for a root domain like example.com. Your dashboard always shows the exact, current values — copy them from there.

  1. Back in SOSEI, click Check status. We validate ownership and issue the SSL certificate automatically — usually live within minutes, occasionally up to an hour or two while DNS spreads. The page refreshes itself when it's ready.

Where the DNS screen lives, by provider

GoDaddy
Your name (top right) → My Products → your domain → Manage DNS.
Namecheap
Domain List → Manage → Advanced DNS. Remove the default parking / URL-redirect records first.
Hostinger
hPanel → Domains → DNS / Nameservers → DNS records.
Cloudflare
Your domain → DNS → Records. Set the A records to DNS only (grey cloud) — see the note below.
Zone.ee
my.zone.ee → your domain → DNS. Supports an ALIAS record on the root.
Squarespace / Google Domains
Domains → DNS → Custom records.

Not listed? Any provider works — find its DNS records screen and add the same three records. The values never change; only the menu location and the field name (“Host” vs “Name”) differ.

Using Cloudflare for your DNS?

Our A-record IPs are Cloudflare-owned, so a proxied (orange-cloud) record to them fails with Error 1000. Set each A record to DNS only (grey cloud). Cloudflare also flattens a root CNAME, so you can instead add a single CNAME on @ → proxy.sosei.site.

Prefer one record on the root? If your provider supports ALIAS, ANAME, or CNAME-flattening (Cloudflare, Zone.ee, Namecheap, DNSimple), you can add just ALIAS/ANAME on @ → proxy.sosei.site instead of the two A records. Your dashboard offers this option too.

What does not change:

  • Your domain stays registered where it is. You're not transferring it away — just pointing it at the new site. You can move it back anytime.
  • Your email and mailboxes keep working as before (see the note above).

Want a hand? Email [email protected] with your provider's name and we'll walk you through it, click by click — or set it up for you.

What happens during a rebuild

We follow the same five-step flow whether the input is a personal domain or a multi-page site:

  1. Crawl — up to 50 pages of your existing site (fewer when the site only answers a browser), plus catalog items and blog posts on their own budgets. Brand colors, fonts, logo, favicon, and tracking codes are detected and kept.
  2. Rehost images — every photo and logo is copied into our storage so the rebuild doesn't hotlink.
  3. Plan — the AI decides on the page structure, fonts, and visual style based on your industry and content.
  4. Write — the pages are written to one voice, so the site reads as the same brand throughout.
  5. Publish — the site goes live on the preview URL in minutes. You receive an email when it's ready. The first build is what visitors see; later rebuilds are saved as drafts until you publish them.

Editing the rebuilt site

Step-by-step guides with pictures: change text, replace a photo, edit the menu and ask the AI for changes.

Three ways to make changes after the first rebuild:

  • Regenerate a single page or the entire site. For the whole site, choose New look (keep the current pages and wording, redesign them) or Start over (rebuild from the original site). Either way you can add plain-English instructions (“tighten the hero, swap to a darker palette”). The result is a draft until you publish it.
  • Edit with AI — open a section, describe the change, the AI rewrites just that section.
  • Restore any previous version from the version history if a regeneration goes wrong.

Adding a page. Your pages are built from your existing site during the rebuild, and you can edit any of them freely. To add a brand-new page (say a separate Services or Booking page), open your site's editor and just ask the AI chat — e.g. “add a Services page about…”. It writes the page, adds it to your navigation, and updates your sitemap; it can rename or remove pages the same way (your home and legal pages are protected). Prefer a hand? Email [email protected] and we'll add it for you.

Deleting a site. Each project card on your dashboard has a small trash icon. Deleting moves the site to Trash — it goes offline and stops being billed straight away, but it's kept and fully restorable for 14 days. See Undo & restore for how to bring it back.

Each site includes a set number of generation runs per calendar month (fewer on a trial): the first build and every rebuild, whole-site or single-page, count as one. The Regenerate button shows how many you have used, and runs beyond the allowance come from credit at the price on /pricing. AI work (chat edits, translations and AI images) is included up to a monthly allowance shown on /pricing; after that it comes out of credit. Small inline edits (text, links, contact info) do not use that allowance.

Pages the first build left out

A rebuild writes up to 7 content pages straight away, plus the legal pages. Up to 30 unique pages are included in the subscription. Template pages, blog posts and legal pages do not count toward that number.

The dashboard lists the old site's pages that were not built. Adding one up to 30 is free. Past that, each page is priced before it runs and paid from your credit — you pay what the page actually takes, never more than the quoted maximum, and a page that is not built is refunded. Current amounts are on pricing.

You can also ask the chat to write a brand-new page that the old site never had. Blog posts can be imported from the crawl, or pushed in later from Zapier, n8n or another webhook once you turn on the project's ingest key. Posts land as drafts unless you turn on auto-publish.

Undo a delete & restore your site

Nothing you delete is gone right away. Deleted projects wait in Trash for 14 days, and a deleted page comes back by rolling your site to a version from before you removed it.

Restore a deleted project (a whole site). Deleting a project moves it to Trash — offline and unbilled, but kept:

  1. Click your avatar in the top-right corner, then Trash.
  2. Find the project and click Restore.
  3. It returns to your dashboard with its pages, versions, and backups intact. An unpaid site simply stays a private draft until you publish it again.

You have 14 days — after that a trashed project is permanently deleted. Opening an old link to a deleted project also shows a Restore banner at the top of that page.

Restore a deleted page. Pages don't have a separate trash — you roll the whole site back to when the page still existed. Three ways, quickest first:

  • Just deleted it? Click Undo last change in the editor's chat panel, or press Ctrl/⌘ + Z. The page comes straight back.
  • Restore an earlier version. Open the editor, click the history (clock) icon at the top-left, preview a version from before the deletion with the eye icon, then click Restore.
  • Restore a backup. If that version has aged out of history, open ⋯ More → Backups and restore a daily or manual snapshot from before the deletion.

Restoring is always reversible — it saves the restored content as a new version on top, so you can undo it too. Backups are automatic daily snapshots of your live site (kept 7 days, or 30 with the extended-backups add-on) that survive even if your version history is cleared — your safety net if something breaks the whole site.

Billing, trials, and cancellations

  • Trial: 14 days from your first generation, no card required. The site goes offline at the end of the trial if you don't subscribe.
  • Plans: see /pricing for current tiers. Personal is per site. Agency is per site too, with pricing tailored to the portfolio — contact us. Enterprise is custom.
  • Credits: AI work is included up to a monthly allowance. Rebuilds beyond the monthly allowance, extra pages, translations and AI images past it are paid from prepaid credit you top up yourself. Nothing in that list charges your card on its own.
  • Cancellation: open your dashboard → Account → Manage subscription. Cancellation takes effect at the end of the current billing period; you keep the site live until then.
  • Refunds: fees already paid are non-refundable and partial periods are not pro-rated, except where mandatory law requires otherwise — EU/EEA consumers keep their statutory 14-day right of withdrawal as described in the Terms. For any billing question, reply to a SOSEI email and a human will look at the account.

Monday report and the checks behind it

A subscribed site is watched without you having to remember:

  • Monday report — a short email on traffic, whether AI assistants still name you, and anything new the audit found. It is not sent when there is nothing to say.
  • Site audit — about every two weeks. A subscribed site can also refresh its own audit 5 times a month; the saved report stays readable after that.
  • AI visibility — ChatGPT, Claude and Gemini are asked the questions buyers ask. You can run it again after 20 hours, and a subscribed site is checked on a schedule so the stored report stays within about 30 days.

The checks run on their own. A rebuild does not: when you want the site rewritten against today's standards, you regenerate it, and the result is a draft until you publish it.

Translations

A rebuild comes back in the language the source site is already written in, including the legal pages. From the dashboard you can publish the same site in another language at its own address (for example /es/). Images, paths and tracking stay as they are; the copy is what changes.

Translation draws on the monthly AI allowance (included up to the amount on /pricing, then credit), the same pool as chat edits.

Analytics, contact forms, and tracking

If your source site already had analytics (GA4, GTM, Meta Pixel, Hotjar, LinkedIn, TikTok, Plausible, Umami, Clarity), the tags are detected during the crawl and preserved on the rebuilt site. Trackers that set cookies stay behind the cookie banner; cookieless ones such as Plausible and Umami run as before.

Adding your own tracking. You can also add or change tracking codes yourself under Settings → Tracking & pixels. Paste your Google Analytics 4 Measurement ID (it looks like G-XXXXXXXXXX, from Google Analytics → Admin → Data Streams), or a GTM, Meta Pixel, Hotjar or other ID, and Save. New or edited codes ship on your next regeneration — consent-required trackers stay gated behind the cookie banner automatically.

Google Business Profile. There's nothing to connect on our side — Google Business Profile links to your site by its web address. Once your domain is live, open your Business Profile and paste your website address into the Website field.

Contact form submissions land in your dashboard under the Messages tab and trigger an email to your project notification address.

Your data, GDPR & deletion

Every rebuilt site ships GDPR-ready. A cookie-consent banner is mandatory, and any analytics or tracking carried over from your old site stays gated behind it until a visitor opts in.

  • Legal pages included — a privacy policy, terms, cookie policy, impressum, and an accessibility statement are generated for every site.
  • Your content stays yours — we rehost your images and copy to serve the rebuild instead of hotlinking; we don't sell or share your data.
  • Deletion — cancel anytime from the dashboard, and email [email protected] to have your project data removed.

The full detail lives in our Privacy Policy and Cookie Policy.

Reach a human

Reply to any email we've sent you, or write to [email protected]. Average response time is under one business day. If the site itself is broken, /api/healthz will tell you whether the application is up before you write.