@keys-i/seer · Build-time i18n + SEO

SEO and localisation—from 50 manual steps to one build.

Author locale JSON. Seer validates every locale file's structure and generates the content and search files your static or server-rendered site needs. No Seer runtime ships to the browser.

The 50-step shorthand models ten repeated checks across five locales; your checklist will vary.

Start with two commands

Install Seer, then run it before your site build.

npm install --save-dev @keys-i/seer
npx seer build

One build replaces the checklist

  1. Author locale JSON

    Store shared data once and translated copy in one file per locale.

  2. Validate before deploy

    Seer fails on missing keys, unsafe paths, malformed metadata, and inconsistent locale structure.

  3. Ship discoverable pages

    Consume locale JSON and emit canonical URLs, hreflang, JSON-LD, robots.txt, and sitemap.xml.

Use your framework, not ours

Load the project once at build or start time, then map neutral metadata through your framework's native head API.

import { headData, readProject } from "@keys-i/seer";

const project = await readProject();
const metadata = headData(project, "en", "home");

Generated here, not mocked

5
locale files with validated structure
0 KB
browser localisation runtime