Going live
Before you upload
Section titled “Before you upload”| Where | |
|---|---|
| Demo domain replaced by yours | every .html file, sitemap.xml, robots.txt — find https://nitip-html-marcframe.vercel.app (Editing the site) |
| Name, contact details, address | every page (header, footer, Contact page) |
| Titles and descriptions | each page’s <head> |
| Icons and share image replaced | favicon.ico, icon.svg, apple-icon.png, opengraph-image.png (1200 × 630 or larger) |
| Demo text and placeholder images replaced | the pages, assets/images/ |
| Forms deliver 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 “Nitip”, the London address or the sample case studies on a live site is the most common mistake — search the folder for “Nitip” one last time.
What to upload
Section titled “What to upload”Everything except the tools:
| Upload | Leave out |
|---|---|
all .html files, services/, projects/, blog/, careers/ |
node_modules/, src/, docs/ |
assets/ |
package.json, package-lock.json |
favicon.ico, icon.svg, apple-icon.png, opengraph-image.png |
README.md, CHANGELOG.md, LICENSE.md |
sitemap.xml, robots.txt |
(Uploading the extra files does no harm, but there is no reason to publish them.)
Where to host
Section titled “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, 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). |
No build command, no server software. Pages link to each other as about.html, so no server configuration is needed
either. Most hosts serve 404.html for unknown addresses automatically; on Apache add
ErrorDocument 404 /404.html to .htaccess.
Your domain
Section titled “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
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop: menu, sliders, accordions, Load More, both forms.
- Send yourself a submission from the live site and reply to it.
- Verify the share card. Paste your URL into https://www.opengraph.xyz or a chat window and confirm the image and title.
- 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. - 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.
Performance and SEO
Section titled “Performance and SEO”The pages ship with what search engines look for: real HTML, one <h1> per page, titles and descriptions per page,
canonical links, sitemap.xml, robots.txt, share cards, lazy-loaded images with fixed dimensions, and a Lighthouse
score of 98–100 on the demo. Keep it there by compressing the photos you add.