Skip to content
NaturaLife Astro Theme

Deployment and SEO

Prepare your content and production SEO settings, configure deployment URLs and indexing, and build and verify the website on your chosen host.

Review your text, links, contact details, authors, dates, prices, media rights and image alt text. Remove unused demo routes and update links to them. Confirm mobile navigation, keyboard use and visible headings. Read the third-party notices provided with your authorized delivery.

Forms, user accounts, password reset, comments/reviews, checkout and server search need your own service integration. Demo controls do not provide production backends. The language selector does not create translations.

Edit the existing seo object in src/settings/site.json:

{
"mode": "production",
"origin": "https://www.example.com",
"name": "Your site name",
"description": "An accurate description of your website.",
"lang": "en"
}

Replace the example origin and identity with your real values; retain other supported fields you need. The starter uses mode: preview, which emits noindex and no production sitemap. Running npm run build alone does not change this setting. Production requires origin, name and description.

Set NATURALIFE_REQUIRE_PRODUCTION=1 in your production build environment to reject accidental preview mode. Normal check/build still needs no Club or license-server connection.

Page JSON and supported content records can supply lang and seo overrides such as title, description, image and index. Canonical URLs are normally automatic; reserve explicit canonical overrides for intentional duplicates. Keep the shared SeoHead once in a complete custom layout; do not add duplicate metadata.

seo.origin is an HTTP(S) origin without a path, query or fragment. For a subdirectory, set Astro base in astro.config.mjs using the existing configuration; the starter also reads NATURALIFE_BASE. Do not put the same subdirectory in the origin. Theme URL handling adds base once.

Preview and inspect internal links, CSS backgrounds, MDX images and galleries under the actual base. Blog and taxonomy archives use real /page/2/ routes, not just query-string content swaps.

The theme registers its sitemap integration; do not add a duplicate. Production writes sitemap-index.xml and numbered sitemap files for indexable, self-canonical pages. Drafts and excluded pages stay out. Search, cart, checkout, account, maintenance, review, pilot and 404 pages retain their noindex policy; a page override cannot force them into the sitemap.

For subdirectory deployment, merge the generated sitemap line into the host’s origin-root /robots.txt. Crawlers discover robots there, not beneath the base. Preserve other applications’ root robots rules.

Structured data is off by default. Enable it only after visible content and optional site identity describe real facts. Product markup does not infer a live offer, stock, reviews or payment service from demo price text. Do not add fictional facts to obtain a search feature. Actual translated routes and reciprocal language mapping are needed before hreflang is appropriate.

Terminal window
npm run check
npm run build
npm run preview

Upload the contents of dist/ to your static host. Keep the editable source project backed up separately. The static output does not need Node.js on the production host; a custom SSR/backend integration has separate adapter and hosting requirements.

Configure the host to return a genuine HTTP 404 for missing URLs using 404.html. /404-page-not-found/ is a design preview, not a replacement for host error handling. Test a missing URL on the real host.

After deployment, verify canonical URLs, indexing directives, root robots, sitemap and image access. Submit your sitemap in Search Console and use its URL inspection for actual pages. Build success and valid markup do not guarantee indexing or search rankings.