@kc-username

Based on the documentation, in the App Router, metadata title templates are evaluated in order starting from the root segment down to the final page segment [1]. Each segment can define its own metadata, but they follow specific rules for merging and inheritance:

1. Title templates only apply to child segments below where they are defined [2]
2. Each title template requires its own default title [2]

Here's an example of how title templates work across segments:

1
import type { Metadata } from 'next'
2
 
3
export const metadata: Metadata = {
4
 title: {
5
 template: '%s | Acme',
6
 default: 'Acme', // a default is required when creating a template
7
 },
8
}

(https://nextjs.org/docs/app/api-reference/functions/generate-metadata#metadata-fields)

When a child page defines its title:

1
import type { Metadata } from 'next'
2

3
export const metadata: Metadata = { title: 'About', }

If you need to bypass a parent's template, you can use title.absolute in a child segment:

1
import type { Metadata } from 'next'
2

3
export const metadata: Metadata = { title: { absolute: 'About', }, }