A no-code website generator — from a blank form to a finished, uploaded website.
WEBZENith is an editor where you build a website through a form: fill in content and settings on the left, and see a live preview on the right. There's no coding involved — the app generates finished, working files at the end (HTML, plus optionally manifest.json and sw.js for PWA support, sitemap.xml, and robots.txt) that you simply upload to a host. This manual walks through the app section by section, in the same order the settings appear in the left panel.
Right at the top of the panel you fill in the basics everything else builds on:
| Field | What it's for |
|---|---|
| Website name / brand | Shown as the name in the site's left-hand menu and in the footer (©). |
| Page title (<title>) | The browser tab text and the main headline in search results. |
| Meta description (SEO) | The short description under the link in search results, aim for around 150 characters. |
| Domain (for canonical / OG) | The actual address the site will run on — used for search-engine and social-media links (og:url, canonical). Fill it in once you know the final domain. |
In the Favicon section you upload a browser-tab icon — either a square image from your device (the app embeds it directly into the exported HTML as base64, so it works with no extra upload), or a URL to an existing favicon file. If you leave it blank, the HTML just keeps a link to favicon.ico and you'll need to upload that file to your host manually.
The hero section is the first thing a visitor sees. You fill in:
Tip: be clear rather than clever — a visitor decides whether to stay within a few seconds. The subheading should add a new detail, not repeat the heading in different words.
Below the hero text you can add one or more buttons. Each can link to a section of the site (Hero, Features, FAQ), a custom URL, a specific custom page, or straight to the FAQ. For each you choose whether it's primary (solid, prominent) or secondary (outlined), and whether it opens in a new tab.
You can optionally add an image to the hero section — by uploading from your device (embedded as base64) or pasting a URL. Add alt text for it — it helps SEO and visitors using a screen reader.
The optional "Video / Audio" section adds a playable video and/or audio recording to the homepage, right after the cards/features.
The simplest option is a regular YouTube or Vimeo link (e.g. straight from your browser's address bar) — the app converts it into an embedded video automatically. Alternatively, upload your own file (.mp4, .webm) or provide its URL. If you fill in both, the URL takes priority.
Works the same way as video — an uploaded file (.mp3, .wav), or a URL (again, the URL takes priority). It shows up as a player with standard controls.
When to upload a file vs. use a URL: an uploaded file is embedded directly in the exported HTML and works without hosting it elsewhere, but for video this significantly increases the file size. For longer video or audio, it's more practical to host it elsewhere (YouTube, your own storage) and just paste the link here.
You can add an optional short caption above either the video or audio player.
The fastest route to a finished look is the "Site style" section with 16 ready-made presets (colors + fonts together). You can then fine-tune the result by hand:
Contrast tip: text needs to stay readable against its background. If you're unsure about a color combination, pick the stronger-contrast option over the one that looks "stylish" but is harder to read.
The "Site layout" section chooses arrangement, not color:
The Navigation section lets you show/hide and rename the Home, Features, and FAQ links in the site's left-hand menu. The "Show custom pages in menu" toggle decides whether custom pages (see below) are added to the menu automatically on every page, or whether you link to them manually via buttons and cards instead.
Further down in the same section you can add social icons (Instagram, Facebook, TikTok, YouTube, email…) — they show up as a row at the bottom of the left-hand menu on every page.
In "Custom pages" you add any number of subpages. Each is exported as its own separate .html file (named after the menu text, e.g. about-us.html) with its own URL, title, meta description, and canonical/OG tags — better for SEO and link sharing than hiding sections inside one file.
For each page you choose a type:
If "show in menu" is on, the page appears automatically as a menu item; otherwise you link to it manually (CTA buttons and clickable cards can both point to a specific custom page). Sitemap.xml then automatically includes the URLs of all custom pages.
In the Cards / features section you describe individual benefits or services — icon, heading, text. The card layout (grid, list, steps, minimal) is chosen in the Page layout section above.
In the FAQ section you add frequently asked questions and answers. The app automatically generates structured FAQPage data from them for Google, which can make the questions appear directly in search results as an expandable list.
Tip: use questions people actually ask (email, phone, social media), not invented ones. The answer should come in the first sentence, with detail after it.
The optional "Contact form" section adds a form to the homepage (after the FAQ), with a choice of where it sends to:
You can also add an optional Phone field and a required consent checkbox with your own text. The form includes basic spam protection (a honeypot field invisible to human visitors).
In the Footer section you decide whether to show "© year brand", an optional custom text (e.g. company registration number, address), and links (terms, contact, privacy policy, etc.).
In the advanced options, the app can generate:
These files are downloaded separately with their own buttons and, after export, uploaded alongside the main HTML file. The generated sw.js automatically accounts for the main page under both its actual downloaded filename and index.html, so the offline cache works no matter how you rename the main page on your host.
Don't forget the actual icon images — favicon, apple-touch-icon, 192×192 and 512×512 icons, og-image. The app links to them but doesn't generate them itself.
The "404 page" section generates a standalone 404.html file, which most hosts (Netlify, GitHub Pages, Vercel…) automatically show instead of the browser's own error message for a missing address. It's downloaded separately and deliberately kept out of search-engine indexing (meta robots "noindex").
The "Cookie bar" shows a one-time notice at the bottom of the page — it's remembered in the visitor's browser and won't show again afterward. If your Footer has a link whose label contains "privacy", "gdpr", "personal", or similar, the bar links to it automatically.
In "GDPR / Privacy Policy" you can generate a privacy.html page whose text adapts to whether (and which) service your contact form uses. It's a general template, not legal advice — depending on your site, you may need to adapt it or have a lawyer review it.
The "Custom code" section lets you add your own CSS, code for <head> (e.g. verification codes, custom fonts), and code before </body> (e.g. a chat widget or tracking script). It's inserted on the homepage, every custom page, and the 404 page, so you only fill it in once.
Careful: whatever you put here goes straight into the site exactly as written, with no validation — a mistake in the code can break the page.
On the right side of the app you switch the preview between Desktop and Mobile, so you can see how the site will look on a phone. If you're editing the app directly from a mobile device, a top switch for "Edit content / Site preview" appears for easier work on a small screen.
The app continuously autosaves your in-progress project to your browser's localStorage (locally, not on a server) — closing the tab won't lose anything. In addition:
The "↓ Download" button in the top right expands a menu:
Upload all the downloaded files together to any static-site host (e.g. GitHub Pages, Netlify, or a regular web host). You can keep the homepage under its downloaded name, or rename it to index.html if you want the site to load at the bare domain with no filename in the address — the PWA offline cache works automatically either way. If you're also using PWA, sitemap/robots.txt, the 404 page, or the GDPR page, download their files separately from their own sections and upload them alongside the rest.
The page title should include the site name plus a keyword that describes the offer (e.g. "Downtown Hair Salon — book online"). The meta description acts like a short ad in search results — aim for around 150–160 characters.
If a site covers several topics, it's better for SEO to have them as separate custom pages with their own address, title, and description, rather than hiding them as anchors on one long page.
Use JPEG or WebP for photos, and PNG or SVG for logos and icons with transparency. Resize an image to its actual display size before uploading — unnecessarily large files just slow the site down. Always add alt text.
Most visitors arrive via mobile — check the site on a small screen first, not only after finishing it on a computer.
| Situation | What to do |
|---|---|
| The preview is blank / unresponsive | Try refreshing the app's page (autosave means your data won't be lost) and, if needed, open the app in an up-to-date browser (Chrome, Firefox, Safari, Edge). |
| An uploaded image/video made the export huge | Uploaded files are embedded directly into the HTML as base64. For large files (especially video), use a URL to external hosting instead. |
| The site doesn't work after uploading to hosting | Check that you uploaded every downloaded file (HTML, manifest.json, sw.js, any custom pages) into the same folder, and that image paths match where you actually saved them. |
| The cookie bar doesn't link to the privacy policy | Check that the Footer link's label contains the word "privacy", "gdpr", or similar — otherwise the app can't match them up automatically. |
| I lost my in-progress project | The app stores it in the browser's localStorage — unless you cleared your browser's site data, it should restore itself the next time you open the app. Use "Save project" regularly as a backup too. |