Your domain, your media

April 11, 2026. Every image, video, PDF, and file you upload now serves from your own domain. URLs read like your brand, not like a generic asset host. SEO credit stays with your site. Visitors see one domain end-to-end.

What changed

Before today, media uploaded to a SGEN site lived on a shared media domain. The page HTML referenced your domain, but every embedded image and file had a different host in the URL — somewhere visitors could see it, screen readers could read it, search engines could trace it.

After today, the media URLs match your site domain. An image you upload to a page on acme-coffee.com serves from acme-coffee.com/media/<filename> (or your configured media path). One domain. One brand. One story.

What it means in practice

For visitors. Page-source view shows your domain everywhere. No "what's that other host?" question. The site reads as coherent.

For SEO. Image search results credit your domain. Backlinks to your images count toward your site's domain authority, not a generic asset host's.

For analytics. Every request your visitors make is to your domain. Heat-maps, server logs, request-flow visualizations show one domain instead of mixing in third-party hosts.

For governance. When a client or stakeholder asks "where does this image live?" the answer is your domain. No platform-specific URL leaks into the conversation.

For migrations. If you ever leave SGEN, the link structure is owned by your domain — image URLs don't need rewriting when content moves.

How it works

The setup is silent. You upload an image to Media Library. The URL the public site renders is your domain — every embedded asset reads as part of your site.

Visitors see your domain. SEO and analytics see your domain. Page-source view shows one host everywhere.

No configuration needed. The moment your custom domain is configured (see "Automatic TLS for custom domains"), media starts serving from your domain.

Why this matters

Most platforms make you choose between platform-hosted asset URLs (anonymous, generic) or self-hosted assets (more work, more responsibility). SGEN gives you the branded URL without the self-hosting overhead.

For a marketing operator, this is a substantial difference. The site looks more professional, the brand stays cohesive, the analytics are cleaner, and the SEO credit is yours alone.

For an agency, this also lets them whitelabel SGEN fully. When a client opens DevTools or views page source, every URL is the client's domain. No "you're using a platform" tell.

Common patterns

• A brand refresh. Acme Coffee Roasters rebrands acme-coffee.com to acmeroasters.com. Existing images now serve from acmeroasters.com/media/... automatically — no URL rewriting needed, no broken images, no SEO loss.
• A multi-site operator. Acme runs three sites (acme-coffee.com, acme-wine.com, acme-studio.com). Each site's media serves from its own domain — no cross-site URL collisions.
• An agency client portfolio. Each client site has its own domain, its own media URLs. From a visitor's perspective, no two clients share infrastructure.

What stays the same

• Upload flow. Drop a file into Media Library — same as before.
• Optimization. Images still get format conversion and responsive sizes (see the Media Library Reference page).
• Public-site speed. First-visitor wait time stays low; subsequent visitors load fast.
• Storage limits. Per-plan media storage limits are unchanged.

Only the URL changes — and that change is invisible to the upload flow.

Next steps

• If you have a custom domain configured, your media already serves from it — check page source on any public page.
• If you're on the SGEN-default subdomain, set up your custom domain first (see "Automatic TLS for custom domains") — media domain follows.
• If you're migrating from another platform, point your domain, upload your media to SGEN, and your URLs are immediately your-domain.