What is Security Headers?
HTTP response headers (CSP, HSTS, frame options) hardening a deployed site. Edge hosts should set sensible defaults; generated apps inherit them without per-project configuration.
Related terms
HTTPS
Encrypted HTTP via TLS, a lightweight ranking signal and a trust requirement. Mixed HTTP resources on HTTPS pages still split signals and trigger browser warnings.
Environment Variable
Configuration kept out of code: API keys, project refs, secrets. Builders should request missing values explicitly and store them in project environment, never in generated files.
Mixed Content
HTTP resources loaded on an HTTPS page. Browsers block or warn on them, breaking assets and trust signals, so audits must catch a single insecure canonical, script, or image.
One-Click Deployment
Publishing a site to production hosting without manual configuration. BYOB deploys to an edge network with rollback to known commits when a release misbehaves.
Custom Domain
Your own address (you.com) instead of a builder subdomain, with automatic SSL. The trust baseline for anything commercial: subdomains convert worse and rank no better.
Visual Editing
Clicking page elements in a live preview and asking the AI to refine text, spacing, or layout. It keeps non-developers in flow while the underlying code stays standard and editable.