Skip to content
New: Customize your theme with an AI assistant. Read the guide

Deployment & Launch

Plumbo builds a static site into dist/, so it runs on any static host. It ships ready-made settings for Netlify (netlify.toml), Vercel (vercel.json, vercel.sh), and Cloudflare Pages (wrangler.toml). The three editions all build a static site. See Theme Editions and the settings for your edition below.

SettingValue
Build commandnpm run build
Output directorydist
Node.js version22.12 or later. The Tina edition needs 22 (22.23.4 or later) or 24
Package managernpm (package-lock.json)

Settings For Your Edition

Astro: nothing extra. The site needs no account or environment variables.

Tina: a deployed site has no live editor. Its /admin/ page says online editing is off until you run npm run setup:tina, and your site works the same either way. To edit online, give your host PUBLIC_TINA_CLIENT_ID and TINA_TOKEN. See Tina.

Sanity: give your host PUBLIC_SANITY_PROJECT_ID, PUBLIC_SANITY_DATASET, and PUBLIC_SANITY_STUDIO_URL. Don’t set SANITY_API_READ_TOKEN or SANITY_VISUAL_EDITING there. .env.example explains every variable. Most items in the list below are in the Studio, such as Site settings > Site > Base URL and Site settings > Business. The site must rebuild to show what you publish. See Sanity.

Before You Launch

Go through this list once. Each item links to the page that explains it.

Address and identity

  • [site] baseUrl is your real address, not the shipped https://example.com placeholder, and npm run build shows no [site] warning (SEO & AI Visibility)
  • title and logoText in [site], author in [seo], and seo.tagline, seo.siteDescription, and seo.keywords in each src/i18n/<lang>.json describe your business. The tagline is added to every page title (Config Reference)
  • The logo, favicons (npm run generate-favicons), social image (npm run generate-og-image, after the two items above), colors in theme.css, and fonts in fonts.json are yours (Site Identity & Logo, Colors & Fonts)

Business details

  • [business] in config.toml has your name, business type, phone, email, address (or show = false if you have no public address), opening hours, time zone, and closed dates, and the build prints no [business] warning (Business Info)
  • The sample service areas in src/content/areas/ are replaced with yours, with real postal codes, and the area links in the Areas and Pages menus point to them (Service Areas)
  • zipPattern under [settings.booking] matches your country’s postal codes

Forms

  • contactFormAction and contactFormProvider post to your own account (Formsubmit, Formspree, or Netlify Forms), and the build prints no [forms] warning (Forms)
  • formAction under [settings.booking] is set if booking requests go to a different inbox (Booking Request)
  • The Mailchimp formAction under [settings.subscription] is your list, or enable = false there if you don’t send a newsletter
  • The careers apply address (mailto:[email protected] in src/content/careers/english/-index.md) is yours, or the sample roles are removed

Prices and sample content

  • Every rate card, add-on, and maintenance plan price in src/content/pricing/ is yours, with the same numbers in every language (no [pricing] warning) (Pricing & Estimator)
  • currency under [settings.estimator] is yours
  • The services and their included lists match what your plumbers really do (Services & What’s Included)
  • Sample facts are replaced: reviews and ratings, licence and insurance details, team members, projects, job roles, blog posts, and the guarantee and warranty periods. They are marked # sample in the content files (Reviews & Projects, Collections)
  • The review links in src/content/sections/english/trust-strip.md (and each other language folder) point to your real review profiles, not https://example.com/review
  • The coupons, codes, and financing terms on /specials/ (src/content/pages/<language>/specials.md) are your own offers, or the page is removed (Emergency & Specials)
  • Every sample photo is replaced. IMAGE-CREDITS.md lists them all (Icons & Images)
  • A project-wide search for example.com and 555 finds nothing you still need to change

Pages and menus

  • The privacy policy, terms, cookie policy, and cancellation policy in every language folder of src/content/pages/ are rewritten for your business and reviewed. They ship as sample text with a notice at the top
  • The Pages demo menu is hidden ("enable": false in every menu file), and the menus point at your pages (Menus)
  • The demo homepages you don’t use are deleted (Homepages), and /elements/ and /components/ are removed if you don’t want the layout and shortcode galleries online (Pages)
  • [settings.layoutSwitcher] enable = false
  • footer.description and footer.copyright in src/i18n/<language>.json describe your business, and the links in src/config/social.json are yours

Analytics and checks

  • Analytics tags are in [head], marked with data-consent while the cookie banner is on (Cookies & Analytics)
  • npm run astro-check and npm run build finish without errors, and you have looked at every page whose section files you changed (astro-check doesn’t check section files or the contact page file)
  • The Arabic text has been reviewed by a native speaker, if you keep Arabic
  • You checked the site at phone width, in dark mode, and in every language you keep

Deploy

  1. Push your project to GitHub, GitLab, or Bitbucket.
  2. In Netlify, choose Add new site → Import an existing project and pick the repository.
  3. Netlify reads netlify.toml: build command npm run build, publish folder dist, Node.js 22. Click Deploy.

The build uses baseUrl from config.toml unless you add a SITE_URL environment variable in the Netlify site settings.

netlify.toml also sets long-term caching for /_astro/* and /images/*, and sends missing /fr/... and /ar/... URLs to that language’s 404 page. When you add a language, add its own block by hand: the language script doesn’t write it.

Using Netlify Forms? Set contactFormProvider = "netlify" and contactFormAction = "/", enable form detection under Forms in the Netlify dashboard, and redeploy. Booking requests use the same provider.

After You Launch

  1. Open the live site and click through the main pages, on a computer and on a phone, including the mobile menu, the Call button, and dark mode.
  2. Send a test message through the contact form, and a test booking request through all the steps on /book/, and check that both arrive.
  3. Try the estimator on /pricing/ and compare one result with what you would really charge.
  4. Type one of your postal codes into the area finder on /areas/, and one you don’t cover.
  5. Submit https://your-domain/sitemap-index.xml in Google Search Console and Bing Webmaster Tools.
  6. Check the homepage and a service page with Google’s Rich Results Test.
  7. Share a link in a chat app to check the preview image.

Tell Search Engines About Changes With IndexNow

IndexNow tells Bing, Yandex, Seznam, and Naver which pages changed, so they visit them sooner. Bing also feeds ChatGPT search and Copilot. It is off until you set a key:

  1. In config.toml, set indexNowKey under [seo.ai] to a key of 8 to 128 letters, numbers, or dashes that you make up:

    [seo.ai]
    indexNowKey = "a1b2c3d4-your-own-key"
  2. Build and deploy. The build publishes the key file at https://your-domain/<key>.txt, which the search engines check.

  3. After each deploy is live, run from your computer:

    Terminal window
    npm run build
    npm run indexnow # pages changed in the last 7 days
    npm run indexnow -- --all # every page: use it after your first launch

    npm run indexnow -- --dry-run lists the pages without sending them.

Updating The Live Site

With a git-connected host, every push to your main branch deploys automatically. Build locally first (npm run build) to catch errors before they reach your visitors.

Type something to search...