Frontic
Frontic
Changelog
  • Changelog
  • Feature requests
  • Support portal

Frontic changelog

Multi-Locale Routing & URL Management

Pages now delivers everything you need to render any page from a single URL lookup. Give Frontic a URL, get back the content, routing information, and localization data in one response.

What's New

  • Localized URL Resolution - The same content can live at different URLs across locales. my-shirt and mein-shirt both resolve to product ID 123. The API returns the correct content regardless of which URL the visitor hits.

  • Alternates for Hreflang - Each page response includes alternates: a list of the same content across all your locales and regions. Use this to generate <link rel="alternate" hreflang="..."> tags for international SEO.

  • URL Change Handling - When a URL changes, the old URL stays in the system. The API response tells you how to handle it:

  • Permanent Redirect (301) - Content moved permanently, transfer SEO value

  • Temporary Redirect (302) - Temporary change, keep the old URL indexed

  • Not Found (404) - Content is gone, show error page

  • Delete - Remove the URL entirely from the system

  • Multi-Domain Routing - Map domains to region/locale combinations. demo-shop.com serves US English, demo-shop.de serves German. Each domain generates appropriate URLs for its locale.

  • URL Conflict Resolution - When multiple records generate the same slug, choose your strategy: append a unique token (product-name-abc123) or skip the duplicate.

How It Works

Request a page by URL. The API returns:

  • The content block to render

  • The current/canonical URL status

  • All alternate URLs across locales

  • Redirect instructions if the URL has changed

  • Region and locale context

Your frontend uses this data to render the page, set up redirects, and generate SEO metadata.

Documentation

Learn more about Pages in our documentation.