Skip to content
Sign inJoin waitlist

Going live — Metuo Astro

Before the Metuo site goes public, replace the demo’s content and point the booking form at you; then build it, upload it to any host and check it again.

Replacing the demo’s content means its name, details, founder, team, stories, plans, posts, legal texts, photos and videos; pointing the form at you means giving it a destination. Once the site is deployed, click through the live address once more.

Where
Your domain in site.url (until you change it, it is the demo’s address) src/content/site.json. Share links, sitemap.xml and robots.txt are built from it.
Name, title and description (they describe the template: write yours) site in src/content/site.json (Home has no meta of its own); the share image’s description, shareImage.alt, in src/lib/meta.ts
Contact details (hello@example.com, the phone number and the London address are placeholders) contact in src/content/site.json; the e-mail also in questionLine (shared.json) and support.cta (faq.json)
Your founder or yourself instead of “Dr. Amelia Hart”: the founder card, the quote band, a client story founder, founderQuote in src/content/pages/shared.json; testimonials.json (Editing the content)
Your place in the Home hero (“London, United Kingdom (GMT+1)”) hero.place in src/content/pages/home.json
Social links (they open the networks’ home pages) socials in src/content/site.json and socialLinks in src/content/pages/shared.json
Logo replaced src/design-system/components/brand/Logo.astro (Making it look like your brand)
Browser icons replaced public/icon-light.svg, public/icon-dark.svg, public/apple-icon.png
Share image replaced and described public/opengraph-image.png, its description in src/lib/meta.ts
Demo photos replaced, each with its alt src/assets/images/ and the content
The two Pexels videos replaced with your own (or the bands removed) video.src in src/content/pages/home.json and about.json (Editing the content)
Your own numbers and ratings (“500+”, “4.9/5”, “65+”) stats in home.json, facts in service.json, clientRatings and ctaBand.trust in shared.json
Your plans and prices, or the plans removed src/content/pages/pricing.json
Client stories from your own clients, with their permission src/content/collections/testimonials.json
Your team, services and questions team.json, services.json; src/content/pages/faq.json
Your own posts (or the demo’s deleted) src/content/collections/posts.json
Terms of Service and Privacy Policy written for your practice (the demo’s are samples with [Your Company Name] and [URL]) src/content/collections/legal.json, their descriptions in src/content/pages/legal.json
Page titles and descriptions written for your work The meta of each file in src/content/pages/ (contact.json holds title and description directly)
The booking form delivers to you, with your own notification title Forms
Style guide kept or deleted src/pages/style-guide.astro
npm run check and npm run build pass, and npm run preview looks right —

The demo content is there to be replaced. Leaving “Dr. Amelia Hart”, the sample e-mail and address, the sample numbers and stories, the sample legal texts, or the template’s description on a live site is the most common mistake.

npm run build writes a complete static site to dist/: HTML files, one stylesheet, a few small scripts, the font files and optimised images. Any host that serves files can run it, with no Node.js needed on the server (unless you chose server-mode forms).

Vercel, Netlify or Cloudflare Pages (free for most sites)

Section titled “Vercel, Netlify or Cloudflare Pages (free for most sites)”
  1. Push the project to GitHub, GitLab or Bitbucket.
  2. Import the repository. Astro is detected: build command npm run build, output folder dist.
  3. Add your form variables (PUBLIC_FORM_ENDPOINT, …) in the host’s environment settings, then deploy.
  4. Add your domain in the host’s Domains settings and follow the DNS instructions.

Pages are built as files (about.html, blog/how-self-awareness-shapes-daily-growth.html) and served at clean addresses (/about). Netlify and Cloudflare Pages do that by default. On Vercel, add a vercel.json next to package.json:

{ "cleanUrls": true }

Any other host (shared hosting, S3, a VPS)

Section titled “Any other host (shared hosting, S3, a VPS)”
Terminal window
npm run build

Upload the contents of dist/ to the web root. For clean addresses, make the server try <path>.html:

  • Apache (.htaccess):

    RewriteEngine On
    RewriteCond %{REQUEST_FILENAME}.html -f
    RewriteRule ^(.+)$ $1.html [L]
    ErrorDocument 404 /404.html
  • nginx: try_files $uri $uri.html $uri/ =404; and error_page 404 /404.html;

If you set PUBLIC_FORM_MODE=server, add your host’s adapter first (npx astro add vercel, netlify, cloudflare or node). Only the form route runs on the server; every page stays static.

  1. Check the pages. Click through every page on a phone and a laptop:
    • the header turning solid as you scroll past the photo, its links and the phone menu;
    • the Home hero’s photo and words on load, the service rows, the steps and the questions;
    • the plans’ Monthly / Yearly switch;
    • the pinned client story card on Home, and the stacked cards of Client Stories;
    • a team member’s bio on About, and the videos;
    • the Journal loading more posts as you scroll, a post with its related posts, the legal pages;
    • the booking form.
  2. Send yourself a booking request from the live site 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. Add your snippet to the <head> in src/layouts/Layout.astro, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner.
  6. Keep it current. A new post is one entry in src/content/collections/posts.json (at the top of the list, to show it first); see Editing the content, and rebuild. Connect a CMS (Using a headless CMS) if someone else will publish.

The template ships with what search engines look for:

  • static HTML, with links in it to every page (the later posts of the Journal included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards;
  • resized, lazy-loaded images that keep their space while they load, each with its alt text.

Keeping the site fast is mostly about images and videos. Astro resizes the photos, but export them at the size they are shown, not the size your camera produced: a 30 MB camera file still slows the build. The placeholders show the size each one was designed for, and the photos of the first screen of every page load first. Keep each video to a few MB; it loads only when it comes into view.