Going live — Goeboek Next.js
Before the Goeboek site goes public, replace the demo’s agency, listings and agents with yours and point the three forms at you; then deploy it to any Next.js host and check it again.
Replacing the demo means your name and logo, your contact details, texts, properties, agents, posts and testimonials; pointing the forms at you means giving them 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: write yours) | site in src/content/site.ts |
| Your name instead of “Goeboek”: the logo, the footer, the copyright line and the page texts | Search src/content/ for “Goeboek” (Editing the content) |
Your address, phones, e-mail (hello@example.com is a placeholder) and opening hours |
contact in src/content/site.ts |
| The Contact page’s map | map.query in src/content/pages/contact.ts |
| Social links (they open the networks’ home pages) | socials in src/content/site.ts |
| Home’s facts (“150” Property Available, “87” Property Sold are typed, not counted) | hero.stats in src/content/pages/home.ts |
| Your properties, agents, locations, categories, posts and testimonials (the demo’s are samples; the agents’ phones and e-mails are made up) | src/content/collections/ (Editing the content) |
| A video for each property, or none (the demo’s share one) | video in properties.ts |
| The Add property form’s Location and Category choices match your collections | src/content/pages/add-property.ts |
| Logo and browser icons replaced | Making it look like your brand |
| Placeholder photos replaced (properties, agents, posts, testimonials, About, the call to action) | public/images/ |
| The three forms deliver to you | Forms |
| A privacy page, if your country asks for one (the forms collect names, e-mails, phone numbers and property details) | Pages and sections |
| 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 the sample listings, the sample agents, the sample e-mail or the sample testimonials 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 three forms, so any host that supports Next.js works. It can’t be published as plain static files, because the forms need 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.
The folder’s vercel.json holds "git": { "deploymentEnabled": false }, which switches off automatic deployments (the
demo is deployed that way): delete the entry if you want Vercel to deploy on every push.
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 header’s links and buttons, and the menu on a phone;
- Home’s slideshows, “Load More” on
/property, the filter (and its toggle on a phone); - a property page: “Contact Sales”, the video, “Show on map”, the agent’s links;
- an agent page, a post, About’s “Load More”;
- all three forms, and the two thank-you pages they open.
- Send each form from the live site with your own address and check that every submission arrived.
- Verify the share cards. Paste the URL of the home page and of a property into https://www.opengraph.xyz or a chat window, and confirm the title and description (and, for the property, its photo). Home has no share image, as in the original design: to give it one, see Troubleshooting and questions.
- 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 listing is one entry in
src/content/collections/properties.tsand its photos inpublic/images/; a new post is one entry inposts.tswith today’s date, and it shows first among the posts by itself (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 property, agent, listing and post (the cards past the first six on
/propertyand the testimonials past the first six on About are in the page, hidden until “Load More” is pressed); - 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.
Keeping the site fast is mostly about images. Export photos at the size they are shown, not the size your camera
produced (about 1400 px wide for the property and post photos, 1920 for the full-width photos of About and the call to
action); the placeholders show the size of each demo photo. next/image then serves each visitor a scaled, compressed
copy.