Skip to content
Sign inJoin waitlist

Going live — Goeboek Astro

Before the Goeboek site goes public, replace the demo’s agency, listings and agents with yours and point the three forms at you; then build it and upload it to any static 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.

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
Your name instead of “Goeboek”: the logo’s label, 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.json
The Contact page’s map map.query in src/content/pages/contact.json
Social links (they open the networks’ home pages) socials in src/content/site.json
Home’s facts (“150” Property Available, “87” Property Sold are typed, not counted) hero.stats in src/content/pages/home.json
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.json
The Add property form’s Location and Category choices match your collections src/content/pages/add-property.json
Logo and browser icons replaced Making it look like your brand
Placeholder photos replaced (properties, agents, posts, testimonials, About, the call to action) src/assets/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/pages/style-guide.astro
npm run check 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.

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 (property/marble-house.html) and served at clean addresses (/property/marble-house). Netlify and Cloudflare Pages do that by default. On Vercel, the vercel.json next to package.json does it with "cleanUrls": true. It also holds "git": { "deploymentEnabled": false }, which stops Vercel from deploying on every push: remove that entry if you want each push to your repository to publish the site.

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’s links and buttons, and the menu on a phone;
    • Home’s slideshows, a hovered property card, “Load More” on /property, the filter (and its toggle on a phone);
    • a property page with its gallery, video and “Show on map”, an agent page, a post;
    • the three forms and the thank-you pages they open.
  2. Send each form from the live site with your own address and check that all three arrived.
  3. 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.
  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 listing is one entry in src/content/collections/properties.json and its photos in src/assets/images/; a sold one is deleted (or moved down the file, out of Home’s first ten). A new post is one entry in posts.json with today’s date, and it shows first by itself (Editing the content). Rebuild and upload after each change, or let your host rebuild on every push. 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 property and post (the cards past the first six on /property 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.txt and share cards;
  • sized, lazy-loaded images that keep their space while they load, and alt texts on every photo;
  • no framework in the browser: a few small scripts.

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 main photos and the post covers, 1200 for the gallery); the placeholders show the size of each demo photo. Astro then writes scaled, compressed copies when the site builds. The property videos and the Contact map are embeds from YouTube and Google Maps: they load those services’ files on the pages that show them.