Going live — Ciketo HTML

Publishing the HTML edition means replacing the demo’s details and pictures, pointing the form at you and uploading the folder to any static host.

There is no build command and no server software: the folder you edited is the site.

Before you upload

	Where
Demo domain replaced by yours	Every .html file, sitemap.xml, robots.txt: find https://ciketo-html-framebrick.vercel.app (Editing the site)
Name, contact details, address (hello@example.com, support@example.com, the phone number and the address are placeholders), business hours	Every page (footer), the call to action, the help card on Home, the Contact page
Titles and descriptions written for your business	Each page’s <head>; Home’s still describe the template
Logo, icons and share image replaced	The logo <svg> in every page (Making it look like your brand), icon.svg, apple-icon.png, opengraph-image.png (2400 × 1260; 1200 × 630 or larger)
Demo text, services, lanes, posts, testimonials and placeholder images replaced	The pages, assets/images/; dated lines too, such as “for Q4 2026” in the Home hero
Client logos replaced, or the section removed	assets/images/client-*.svg, Home and About (Editing the site)
Legal pages written for your business	legal/privacy-policy.html, legal/terms-conditions.html, legal/cookie-policy.html (sample text, dated Sep 2, 2026)
The form delivers to you	assets/js/config.js (Forms)
Style guide kept or deleted	style-guide.html
Stylesheet rebuilt if you changed the theme or used new classes	npm run build:css (Making it look like your brand)

Leaving “Ciketo”, the sample contact details or the sample services on a live site is the most common mistake: search the folder for “Ciketo” and “example.com” one last time.

What to upload

Everything except the tools and the documentation:

Upload	Leave out
The .html pages, services/, blog/, legal/	node_modules/, src/, docs/
assets/	package.json, package-lock.json, .gitignore
icon.svg, apple-icon.png, opengraph-image.png	README.md, CHANGELOG.md, LICENSE.md
sitemap.xml, robots.txt	Documentation.html, Documentation.pdf

Uploading the extra files does no harm, but there is no reason to publish them.

Where to host

Host	How
Netlify	Drag the folder onto Netlify Drop. Done; then add your domain.
Cloudflare Pages, Vercel	Upload the folder or connect a Git repository; no build command, the output folder is the root.
GitHub Pages	Push the folder to a repository and enable Pages.
Shared hosting (cPanel, Plesk…)	Upload through the file manager or FTP into public_html (or www).

Pages link to each other as about.html, so no server configuration is needed. Most hosts serve 404.html for unknown addresses automatically; on Apache, add ErrorDocument 404 /404.html to .htaccess. The paths in 404.html start at the site’s root (/assets/css/style.css, /contact.html), because hosts show it at any address: if your site lives in a sub-folder of its domain (example.com/shipping/, or a GitHub Pages project site), add that folder to those paths.

Your domain

Add it in the host’s domain settings and point your DNS where they tell you (usually an A record or a CNAME). Turn on HTTPS: every host above does it for free.

After it is live

1. Check the pages. Click through every page on a phone and a laptop:
   • the header over the Home and Contact photos, and the phone menu;
   • the services accordion, the steps, the testimonials and the FAQ on Home;
   • the client logo ticker;
   • the Blog showing more posts as you scroll;
   • the quote form.
2. Send yourself a quote request from the live site and reply to it.
3. Verify the share card. Paste the URL of the home page and of a service into https://www.opengraph.xyz or a chat window, and confirm the image and title.
4. Tell Google. Add the site to Search Console, verify ownership and submit https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools.
5. Analytics, if you want it. Paste your snippet before </head> in every page (find and replace on </head> does it at once), or use your host’s built-in analytics (Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner.
6. Keep the work current. Add posts as described in Editing the site, and keep sitemap.xml in step.

Performance and SEO

The pages ship with what search engines look for:

• real HTML, with links in it to every page;
• one <h1> per page, and a title and description for every page;
• canonical links, sitemap.xml, robots.txt and share cards; the 404 page and the style guide are kept out of search results (noindex);
• lazy-loaded images below the top of each page.

Each image is one file, used at every screen size. Keep the site fast by exporting photos at the size they are shown and compressing them; the photos at the top of each page (the Home and Contact covers, the service and post photos) matter most on phones.