March 26, 2026 07:22 PM

Next.js Boilerplate Updates: i18n, article language, SEO entities, RUM, AI metrics, and PWA icons

This boilerplate update introduces several practical capabilities that help teams ship faster and make decisions with real data from the first releases.

Thumbnail
Ulggggggly and funy image?

1) Built-in translations (src/lib/i18n)

The project now has a centralized i18n architecture:

  • locale config with a default locale;

  • translation dictionaries (for example en/ru);

  • locale detection on both server and client;

  • a single way to consume translated strings in UI via provider/hooks.

How it works (short)

  1. Default locale is defined in env + i18n config.

  2. Request locale is resolved from cookies/headers.

  3. Root layout initializes i18n provider.

  4. Components read text by translation keys.

Benefits:

  • no scattered hardcoded strings in components;

  • easier multi-language UI maintenance;

  • simpler scaling for admin and public screens;

  • fewer regressions when copy changes.

2) Article language in SEO (optional)

SEO editor now includes an optional article language field (en/ru) with an empty default.

Behavior:

  • field can stay empty (stored as null);

  • if selected, it has priority for:

    • inLanguage in Article JSON-LD;

    • article page metadata;

    • lang on public/preview/private article content wrappers;

  • if empty, site default locale is used.

Benefits:

  • stronger SEO/AI-search language signals;

  • better accessibility and content parsing behavior;

  • clean foundation for future hreflang support.

3) organizationSameAs for SEO and AI search

SEO config now includes organizationSameAs, mapped to Organization.sameAs in JSON-LD.

Typical entries:

  • organization GitHub profile;

  • company LinkedIn page;

  • X/Twitter account;

  • YouTube and other official profiles.

Why it matters:

  • search engines and LLMs can map your brand entity more reliably;

  • lower entity ambiguity in knowledge graphs;

  • stronger authority/trust signals for classic SEO and AI discovery.

If profiles are not ready yet, keep it as an empty list and fill later.

4) RUM metrics: real-user performance visibility

The boilerplate already includes an end-to-end RUM pipeline:

  • Web Vitals ingestion (LCP, INP, CLS, TTFB, FCP);

  • persistence in MongoDB;

  • dashboard API;

  • admin UI with time-window aggregates.

Why it helps:

  • you see real user performance, not only lab numbers;

  • easier regression detection after releases;

  • optimization priorities based on actual impact.

In short, this is ready-to-use frontend observability out of the box.

5) AI metrics: AI-source referral tracking

A dedicated AI-referrals pipeline is included:

  • AI referrer detection (ChatGPT, Perplexity, Copilot, Gemini, Claude);

  • visit persistence in a separate model;

  • aggregated dashboard API;

  • admin UI with sources and top landing paths.

Why it helps:

  • clear view of incoming traffic from AI systems;

  • better understanding of which articles get discovered via AI;

  • additional SEO/content feedback loop beyond classic search.

Important: current implementation tracks AI referrals (click-through sessions), not direct “in-answer citation extraction”.

6) Manifest, favicon, and fallback icons

PWA/metadata configuration was also updated:

  • refreshed site.webmanifest (app naming, icons, start_url, scope, theme colors);

  • manifest and icons wired via root metadata;

  • sw.js uses the current app icon for push notifications (icon/badge);

  • web-app-manifest-192x192.png is used as a fallback thumbnail when an article has no image.

Benefits:

  • consistent brand icon usage across browser/PWA surfaces;

  • more predictable link previews in bots/social platforms;

  • fewer empty cards for pages without custom images.

7) Out-of-the-box value

Instead of a bare template, you get a production-oriented baseline:

  • i18n foundation for product growth;

  • article language support in SEO/rendering;

  • stronger brand entity SEO signals;

  • real-user performance monitoring (RUM);

  • AI traffic observability and discovery insights.

Result: the boilerplate helps not only to “start quickly”, but to move faster with measurable quality and growth signals.