Skip to content
Sign inJoin waitlist

Going live — Metuo HTML

Publishing Metuo’s HTML edition means replacing the demo’s details, pictures and videos, pointing the booking form at you and uploading the folder to a host.

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

Where
Demo domain replaced by yours Every .html file, sitemap.xml, robots.txt: find https://metuo-html-framebrick.vercel.app (Editing the site)
Your name instead of “Metuo” and “Dr. Amelia Hart”: the logo’s name, the titles, the About title, the founder’s card and quote, the footer note Search the folder for “Metuo” and “Amelia”
Contact details (hello@example.com, the phone number and the London address are placeholders) The footer of every page; the e-mail also in the call to action, the booking section and the questions
Social links (they open the networks’ home pages) The footer, the call to action, the booking section
Your place in the hero’s foot line (“London, United Kingdom (GMT+1)”) and “Available for treatment” index.html (Editing the site)
Titles and descriptions written for your practice Each page’s <head>; Home’s title still names the template
Logo, icons and share image replaced The logo <svg> in every page (Making it look like your brand), icon-light.svg, icon-dark.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/ (Editing the site)
The two stock videos replaced or removed (they play from the Pexels CDN) index.html, about.html (Editing the site)
Your services, plans and prices, steps and answers Home, Service, the questions on every page that shows them (Editing the site)
Your own figures and rating (“500+”, “4.9/5”, “65+”, “95%”, “10+”) Home, Service, every call to action and booking section (Editing the site)
Stories from your own clients, with their consent Home, Testimonial (Editing the site)
Your team and their bios About (Editing the site)
Your posts, or the demo’s removed blog/, the Journal page, Home (Editing the site)
Your terms and privacy policy (the samples hold [Your Company Name], [URL] and other placeholders) legal/ (Editing the site)
The form delivers to you, with your wording in its subject assets/js/config.js, the three forms (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 “Metuo”, the sample e-mail, the sample figures, the stories or the legal placeholders on a live site is the most common mistake: search the folder for “Metuo”, “Amelia”, “example.com”, “Kensington”, “pexels” and “[Your” one last time.

Everything except the tools and the documentation:

Upload Leave out
The .html pages, blog/, legal/ node_modules/, src/, docs/
assets/ package.json, package-lock.json
icon-light.svg, icon-dark.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.

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, blog/how-self-awareness-shapes-daily-growth.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/coaching/, or a GitHub Pages project site), add that folder to those paths.

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.

  1. Check the pages. Click through every page on a phone and a laptop:
    • the hero’s opening on Home, the header turning solid as you scroll, and the phone menu;
    • the services, the steps and the questions opening and closing, and the founder’s and the team’s “+” bios;
    • “Why choose us” and “Our core values” lighting up (the photo ticker on a phone);
    • the Monthly / Yearly switch, and the story card on Home turning as you scroll;
    • your videos on Home and About;
    • the Journal loading more posts as you scroll, a post, a legal page;
    • the 404 page (open an address that doesn’t exist).
  2. Send yourself a test from the booking form and reply to it.
  3. Verify the share card. Paste the URL of the home page and of a post 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 journal current. Add posts as described in Editing the site, and keep sitemap.xml in step.

The pages ship with what search engines look for:

  • real HTML, with links in it to every page (the posts the Journal shows later included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards (each post with its own photo); 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 videos load only when they first come 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 page titles’ photos and a post’s cover) matter most on phones.