Going live — Metuo Next.js
Before the Metuo site goes public, replace the demo’s content and point the booking form at you; then deploy it to any Next.js host and check it again.
Replacing the demo’s content means the practice’s name, the founder, the details, the plans, the stories, the photos, the videos and the legal texts; pointing the form at you means giving it a destination. Once the site is deployed, click through the live address once more.
Before you deploy
Section titled “Before you deploy”| Where | |
|---|---|
Your domain in site.url (until you change it, it is the demo’s address) |
src/content/site.ts. Share links, sitemap.xml and robots.txt are built from it. |
| Name, title and description (they describe the template, and they are Home’s title and description: write yours) | site in src/content/site.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| Your practice instead of “Metuo”, your founder instead of “Dr. Amelia Hart”, your town instead of London: the copy, the footer, the founder, the stories | Search src/content/ for “Metuo”, “Amelia” and “London” (Editing the content) |
Contact details (hello@example.com, the phone number and the address are placeholders) |
contact in src/content/site.ts |
| Social links (they open the networks’ home pages) | socials in src/content/site.ts |
| Your plans and prices, and the discount next to “Yearly” | src/content/pages/pricing.ts |
| Your own figures and rating (“500+”, “4.9/5”, “65+”) | stats in src/content/pages/home.ts; clientRatings and the trust line of ctaBand in shared.ts |
| The questions and answers, and the support person beside them | src/content/pages/faq.ts |
| Stories from your own clients, your team, your services | src/content/collections/ |
| Your own posts, or none | src/content/collections/posts.ts |
Legal pages written for your practice ([Your Company Name], [URL] and the sample text) |
src/content/collections/legal.ts |
| Logo replaced | src/design-system/components/brand/Logo.tsx (Making it look like your brand) |
| Browser icons replaced | public/icon-light.svg, public/icon-dark.svg, src/app/apple-icon.png |
| Share image replaced and described | public/opengraph-image.png, its description in src/lib/meta.ts |
| Placeholder photos replaced | public/images/ |
| The two videos replaced (they play from the Pexels website) | video in src/content/pages/home.ts and about.ts (Editing the content) |
| Page titles and descriptions written for your practice | The meta of each file in src/content/pages/, descriptions in legal.ts |
| The form delivers to you | Forms |
| Style guide kept or deleted | src/app/style-guide/ |
npm run lint and npm run build pass |
— |
The demo content is there to be replaced. Leaving “Dr. Amelia Hart”, the sample e-mail and address, the sample prices, the figures, the client stories or the sample legal texts on a live site is the most common mistake.
Deploy
Section titled “Deploy”The site is a normal Next.js app: it builds to pre-rendered pages and runs on Node.js, which also handles the booking form, so any host that supports Next.js works. It can’t be published as plain static files, because the form needs the server.
Vercel (made by the Next.js team, free for personal sites)
Section titled “Vercel (made by the Next.js team, free for personal sites)”- Push the project to GitHub, GitLab or Bitbucket.
- https://vercel.com/new → import the repository → Deploy. The framework, build command and output are detected.
- Add your form variables under Settings → Environment Variables, then redeploy.
- Settings → Domains → add your domain and follow the DNS instructions.
Netlify
Section titled “Netlify”Import the repository, keep the detected settings (npm run build), add the environment variables, deploy.
Cloudflare
Section titled “Cloudflare”Cloudflare runs Next.js through the OpenNext adapter (@opennextjs/cloudflare); follow Cloudflare’s Next.js guide to
build and deploy with Wrangler.
Your own server
Section titled “Your own server”npm cinpm run buildnpm start # listens on port 3000Run it under a process manager (pm2, systemd) behind nginx or Caddy for TLS, or in a container: an LTS Node image such
as node:24-alpine, copy the project, build, CMD ["npm", "start"].
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 turning solid as you scroll;
- the service rows, the process steps and the questions opening;
- the plans’ Monthly / Yearly switch;
- the videos, the story card on Home and the stacked stories of the Testimonial page;
- Blog loading more as you scroll, a post page and a legal page;
- the booking form.
- Send yourself a booking from the live site and reply to it.
- 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.
- 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. Add your snippet to
src/app/layout.tsx, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. A new post is one entry at the top of
src/content/collections/posts.ts, with its photo inpublic/images/; see Editing the content. Connect a CMS (Using a headless CMS) if someone else will publish.
Performance and SEO
Section titled “Performance and SEO”The template ships with what search engines look for:
- pre-rendered HTML, with links in it to every page (the later posts of Blog included);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; - sized, lazy-loaded images that keep their space while they load, and alt texts on every photo that says something.
Keeping the site fast is mostly about images and videos. Export photos at the size they are shown, not the size your
camera produced (about 2400 px wide for the full-width photos, 2280 px for the post covers); the placeholders show the
size of each demo photo. next/image then serves each visitor a scaled, compressed copy. Keep each video to a few MB:
they load only when they come into view, but every visitor who scrolls that far downloads them.