Docs
Feature Overview
Every feature area of the Seedly Sites platform - what it does and where to learn how to use it.
Last updated
What each part of the platform does, and where the detailed guide lives. If you are brand new, read Core Concepts first.
The Visual Builder#
A real drag-and-drop builder on a Section, Row, Column hierarchy with 46 element and block types: headings, text, lists, images, galleries, video, buttons, grids, accordions, FAQ, reviews, slideshows, tab switchers, before/after image sliders, popups, and a local-business pack (NAP, hours, service area, maps, click-to-call). Every element styles through native fields - sizes, colors, alignment, per-breakpoint column widths - so pages stay consistent and portable. Sixteen section presets and a saved-blocks library let you reuse the sections you have already perfected.
See the guide: Builder basics, Element reference
Branding & Design#
Each site's identity lives in one place: logo, favicon, site name, colors, fonts, navigation, and calls to action. Those brand tokens drive the rendered site, the preview, and the builder canvas, and a brand component layer applies consistent, vetted styling across sections so a rebrand is an edit, not a rebuild.
See the guide: Site settings, Brand DNA
Pages#
Create and manage each site's pages with drafts, scheduled publishing, password protection, featured images, an internal-link picker, and a content and SEO analysis panel. Choose which page serves as the home page, and edit the system templates (404, blog archive, single post) in the same builder.
See the guide: Pages
Blog#
A full blog per site: rich-text posts, categories and tags, scheduled publishing, excerpts, and author profiles that render real bylines and author archive pages. The archive and post layouts are builder-editable templates.
See the guide: Blog
Media Library#
Per-site media with folders, required alt text, automatic WebP conversion, and storage on R2. Images place into pages with focal-point control and responsive variants. Media belongs to its own site, and a cross-site check runs across every site you operate so one client's pictures can never surface on another's.
See the guide: Media
Merge Tokens#
Type a token such as {{site.name}} or {{location.phone}} into any heading, paragraph, button, or link, in a page, the header, or the footer, and the published site fills it from Settings. Tokens resolve in SEO titles and descriptions too. Change a value once and every page that references it is right on the next publish. An unset value publishes blank; an unknown token stays visible and gets flagged, so mistakes are loud rather than silent.
See the guide: Merge Tokens
Smart Locations#
Bind a section to one of a site's locations and everything in it fills from that record. Unbound location tokens fall back to the page's location, then to the primary, so one template serves single and multi-location businesses without edits. A grid can render every location as a service-area block that maintains itself, and each location can name the cities it serves.
See the guide: Smart Locations
AI Agent Access#
An AI agent you run can read a site, edit content, build pages from sections you have already vetted, and write blog posts. Everything it writes lands as a draft, it cannot publish or deploy, and its access is scoped to the one site you granted.
See the guide: Letting an AI Agent Edit Your Sites
SEO Tools#
Per-page meta titles and descriptions, Open Graph and social cards, canonicals, noindex control, and focus-keyword analysis. Site-wide: local-business structured data, title templates, automatic sitemaps, robots controls, redirects with a 404 monitor, and broken-link and orphan-page detection.
See the guide: Page SEO, Site SEO, Technical
Website Analytics Dashboard#
First-party, consent-gated analytics you own, per site: click maps, scroll depth, attention maps overlaid on page screenshots, top campaigns, UTM attribution that carries into embedded CRM forms, bot watch, and experimental A/B tests. It is your data on your infrastructure, not a third-party tag.
See the guide: Analytics
Hosting & Deployment#
Published sites are static files on Cloudflare Pages - one project per client site, provisioned automatically, each on its own custom domain. Deploys are manual and operator-controlled: publishing content updates the CMS, and the live site changes only when you press Deploy. A readiness gate checks each page before it ships.
See the guide: Preview vs Publish vs Deploy, Deploying, Hosting & domains
Filling a New Site: Port, Generate, Clone#
There are three ways to put content into a new client site, and all three land as drafts on a review board - nothing publishes or deploys on its own.
Port an Existing Site#
Point the migration pipeline at the client's current website and it crawls the source, reproduces it closely as builder pages, carries over SEO fundamentals (canonicals, internal links, redirects for changed URLs), and scores content parity so you can see exactly what to finish by hand. This is the measured takeover path.
See the guide: Port a site
Generate from Brand Inputs#
Build a fresh site from a client's brand inputs - business details, services, service areas, and brand. You invite the client and they fill out a guided intake questionnaire themselves, or you complete it with them, and those answers drive the site. The output is a set of draft pages built from real builder sections, written in the client's own voice, made unique to that client, and checked for honesty before anything is saved. You review and finish it in the builder.
See the guide: Generate a site
Clone a Live Site#
Make a plain, near-exact copy of a live site into a tenant as editable drafts - real content, chrome, images, brand, and business details - without keyword research or rewritten copy. The fast path when you just want a faithful copy in the platform.
See the guide: Clone a site
Copy in the Client's Voice#
Generated copy is written to sound like the client, drawn from their own intake words and tone, not a generic template register. Honesty gates keep it grounded: a build cannot ship a statistic, rating, or superlative the client did not actually provide, so generated copy stays truthful by construction.
See the guide: Copy in the client's voice
Unique by Design#
Two clients built from the same template pack never receive a recognizably identical site. Each generated site gets its own structure, color rhythm, spacing, imagery, and photography within brand-safe, accessibility-checked bounds, and every build is checked against your prior builds so a near-identical one is re-rolled into a distinct variant.
See the guide: Never the same site twice
Tenants & White-Label#
Create a tenant per client site and manage them all from one login. White-label delivery: a branded client login screen, no powered-by badge on published sites, and custom domains per client. Deploy status is visible per tenant.
See the guide: Tenants
Client Access & Roles#
Invite clients with WordPress-style roles (Administrator, Editor, Author, Contributor, Subscriber), scoped to their own site, with per-tenant overrides and a separate deploy permission. There is a short, non-technical guide you can hand directly to clients.
See the guide: Users & roles, Client guide
Billing#
Native Stripe billing per client site: a hosted checkout for the client to subscribe, a customer portal for card and invoice self-service, an operator dashboard showing every tenant's billing state, and configurable enforcement on non-payment (freeze editing, or suspend the site) with a per-tenant override.
See the guide: Billing
For Operators Running the Platform#
Install, provisioning, updates, backups, and disaster recovery have their own operator-focused guides: