Going live — KorDent HTML
Publishing the KorDent HTML edition means replacing the demo’s clinic, pictures and video, pointing the forms 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
Section titled “Before you upload”| Where | |
|---|---|
| Demo domain replaced by yours | Every .html file, sitemap.xml, robots.txt: find https://kordent-html-templategum.vercel.app (Editing the site) |
| Your clinic’s name instead of “KorDent” / “Kordent”: the copy, the footer, the services’ texts, the posts and the legal texts | Search the folder for both spellings |
| Contact details: the e-mail, the address and the four phone numbers are made up | Every page (the header’s “Call Now”, the call to action), Contact, About: search for “555” |
| The map and “Get Direction” show your address | contact.html (Editing the site) |
| Opening hours and the emergency panel | contact.html |
| Social links (they open the networks’ home pages) | The footer of every page |
| The footer: the line about the clinic, the Dental Services column, the copyright and the disclaimer | Every page |
| Titles and descriptions written for your clinic | 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) and its description, og:image:alt |
| Demo photos and portraits replaced | assets/images/ |
| The video replaced (or removed) | assets/videos/cta.mp4 (Editing the site) |
| Your own figures: the review count and rating, the facts, the badges and certifications | Home, About |
| Your services with your prices, durations and dentists | The service pages and the grids (Editing the site) |
| Reviews and outcomes from your own patients, with their consent | Home, Services |
| Claims that must be true for your clinic: the call to action’s special offer and promises, the safety banner, the memberships | Every page with the call to action, the services grids, the Home hero |
| Legal texts of your own (the demo’s three are samples) | legal/ |
| The 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 “KorDent”, the sample phone numbers, the prices, the dentists, the reviews, the legal texts or the stock video on
a live site is the most common mistake — and on a clinic’s site, a made-up review or certification is more than a
mistake. Search the folder for “KorDent”, “Kordent” and “555” one last time (the forms’ placeholder hello@example.com
can stay).
What to upload
Section titled “What to upload”Everything except the tools and the documentation:
| Upload | Leave out |
|---|---|
The .html pages, service/, blog/, legal/ |
node_modules/, src/, docs/ |
assets/ |
package.json, package-lock.json |
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
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, 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 with their file names (about.html, service/general-dentistry.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, /index.html), because hosts show it at any address: if your site lives in a sub-folder of
its domain (example.com/clinic/, or a GitHub Pages project site), add that folder to those paths.
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:
- the menu, the phone menu and the header’s two buttons (does “Call Now” dial your number?);
- the department tabs and the search over the services, a service page with its contents and its booking form;
- the outcomes’ index on desktop, the dentist tabs (rows on a phone), the accordions;
- the video of the call to action;
- the Contact page’s map and links, and the 404 page (open an address that doesn’t exist).
- Send yourself one of each form — a booking, a contact message, a review, a newsletter sign-up — and reply to one.
- Verify the share card. Paste the URL of the home page and of a service or a post 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. A clinic also gains from a Google Business Profile with the same name, address and phone as the site. - 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. - Keep it current. Add services and posts as described in Editing the site, and keep
sitemap.xmlin step.
Performance and SEO
Section titled “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.txtand 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, with their size written so that they keep their space while they load; the video loads only when it scrolls into view.
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 hero, the wide photos of About, the services and the posts) matter most on phones.