SEO and site settings
Forma supplies translated Next.js page metadata, canonical language URLs, language alternates, Open Graph/Twitter fields, a favicon, a social image and a generated language sitemap. These are editable starting points; they do not guarantee search rankings or a particular social preview.
On this page
Titles and descriptions
Edit the top-level title and description in both src/content/primary.ts and src/content/secondary.ts. For example:
title: '{name} — simple project planning for small teams',
description: 'Keep your small team aligned with shared priorities and clear next steps.',
The shared name is siteSettings.name in src/config/site.ts. {name} inserts it where used; changing the name does not rewrite text without that token. Supply a suitable title and description for each language.
Expected result: each direct language URL has its own translated browser title, description and social metadata. Keep copy concise and accurate for your product. Page metadata is assembled in src/lib/metadata.ts; font setup is in src/components/document-frame.tsx, with viewport settings in src/app/[[...lang]]/layout.tsx.
Set the real public origin
Create a plain-text .env.local file beside package.json, or set the same public build variable in your host's build settings:
NEXT_PUBLIC_SITE_URL=https://www.your-domain.example
Replace the example with your final HTTPS origin, without a language path, query or fragment. The helper adds configured language paths itself. These guides assume a domain/subdomain root; a subdirectory requires additional base/asset-path configuration and testing.
On Windows ensure the filename is .env.local, not .env.local.txt. You may copy .env.example as a starting point. The value is public, not a credential; never put private keys in NEXT_PUBLIC_ variables.
Rebuild after changing the origin. The preview server cannot rewrite already-built metadata. Without a public origin, local preview uses http://127.0.0.1:3100 for its metadata base, sitemap and robots file, and omits canonical/alternate metadata. Do not publish that local configuration as your final site.
Canonicals, alternates and sitemap
With the real origin set, /en/ and /el/ in the supplied pair receive canonicals for their own URL and hreflang alternates for both languages. Changing codes in languages.ts changes generated language paths; no metadata path edits are required for an ordinary replacement pair.
The root / is a default-language entry and points its canonical to the configured default language URL. A saved preference can affect root navigation in a browser, but an explicit language URL always remains that language. Review Languages for the exact behaviour.
The build produces out/sitemap.xml for the configured language pages and out/robots.txt pointing to it. Upload both with the complete export, after setting your real origin. A sitemap is a discovery aid, not a promise of indexing. Additional pages require corresponding metadata and sitemap work.
Social image and favicon
Replace public/og-image.png with your own licensed artwork. Its path and declared 1200×630 dimensions are in siteSettings.brand.socialImage in src/config/site.ts. Set src, width and height there to match your file; no metadata-component edit is needed for a standard replacement. Both languages use the same image by default, with translated metadata text. Use artwork suitable for both audiences or implement per-language artwork deliberately.
Replace public/icon.svg or update siteSettings.brand.favicon to your new public path. The visible logo is separately configured by brand.logo; see Appearance. Browser/social caches can delay changes; first confirm that the deployed asset URL serves the expected file.
HTML language, direction and truthful structure
Language code and reading direction come from src/config/languages.ts. Translate interface labels as well as marketing text, including media captions, testimonials, appearance, cookies, newsletter and dialogs. Changing a code does not translate a content file. Check font glyphs and mixed-script rendering; the bundled Manrope file is Latin-only. In Kit mode, configure the provider's own Form language/messages for each slot too.
Keep one clear main heading, logical section-heading order, descriptive links and meaningful alternative text. Replace fictional testimonials, people, prices, metrics and claims. Forma includes no blog, CMS, analytics, automatic translation or ranking guarantee. Cookie controls manage its own optional preferences rather than added third-party services.
The supplied metadata permits indexing/following. Review indexing settings for a private staging site and restore the intended live settings before launch. Host access restrictions can affect crawlers independently.
Production verification
- Confirm both languages' title/description, shared logo/favicon and social image belong to your product.
- Set the final origin before the build; run
npm run format, review changes, thennpm run check. - Stop development and use
npm run start. Inspect page source at each direct language URL for title, description, HTML language/direction, canonical, alternate links and absolute social-image URL. - Inspect
out/sitemap.xmland confirm the same two published language URLs. Openout/robots.txttoo: itsSitemapURL must use the same public origin. - Publish the complete
out/tree and verify direct visits, refreshes and the same metadata on the host. - Open live favicon/social-image URLs, confirm HTTPS loading, then use your chosen social platform's preview tool if needed.
See Deployment for upload steps and Troubleshooting for stale output or broken paths.