# Never the Same Site Twice > How the variance engine gives every generated site its own structure, so two clients built from the same template pack never receive a recognizably identical site. Template packs make [generated sites](/docs/help/generate-a-site) fast, but a plain template would hand two clients in the same trade a recognizably identical layout - same sections, same order, same image sides, same colors. The variance engine solves that by construction: it gives every generated site its own structure, and it proves the site is distinct before you ever see it. --- ## What Varies Each generated site gets its own take on the template within brand-safe bounds. The things that vary include: - **Layout** - which side images sit on, and how columns are arranged - **Color rhythm** - how brand background tones are distributed down the page - **Spacing and typography** - section rhythm, heading scale, and weight - **Grids and imagery** - column counts, image shapes, and icon treatment - **Hero treatment** - text alignment in the opening section - **Photography** - the stock photos pulled in, drawn from a wider pool so two sites do not share the same shots - **A subtle color shift** for clients who have not locked in a brand yet A confirmed client brand is never altered. Variance changes structure and treatment, never the words on the page. --- ## Distinct, and Proven Varying a site is not enough on its own; the platform also checks that the result actually is different: - **Every build is compared against your prior builds** on the same template pack. - **A near-identical build is automatically re-rolled** into a distinct variant. The expensive copywriting is not redone in the process, so a re-roll costs you nothing. - **If a build genuinely cannot be made distinct** - typically two clients sharing the same locked brand with no other room to move - it is flagged for your review rather than shipped blindly. The build is never failed; you decide at the review board. On top of that structural check, the platform compares full-page screenshots of each new site against earlier ones, so two sites that somehow look alike even after varying are caught too. --- ## Stable for the Same Client Uniqueness across clients does not mean instability for one client. The same client always rebuilds to the same site, so a rebuild after an edit reproduces the layout the client already approved rather than reshuffling it. Re-rolling only ever happens to pull two different clients apart, never within one client's own history. --- ## On Brand and Accessible, Always Every variation is bounded. Text stays readable against its background at accessibility-standard contrast, brand colors are respected, and spacing and typography stay within a tasteful range. A varied site is never an off-brand or broken site; it is the same quality of build wearing a different arrangement. --- ## Operator Note The stock-photo pool is one of the strongest ways two same-trade sites are told apart. Connect a stock photo source in your instance configuration so photography is one of the axes that vary between clients. Without it, sites are still varied structurally, just with less to draw on for imagery. --- ## Summary | | | |---|---| | What varies | Layout, color rhythm, spacing, typography, grids, imagery, photos | | What never varies | A confirmed client brand, and the copy itself | | Proof of distinctness | Each build checked against prior builds and re-rolled if too close | | Same client, rebuilt | Reproduces the same site - edits stay stable | | Safety | Every variation stays on brand and readable at accessible contrast | --- Source: https://seedlysites.com/docs/help/site-variance