Share facts rather than copy
A content record already knows an article’s title, description and slug. Use that record for both the visible page and its metadata. Maintaining a second title map invites drift when an editor renames a guide. The goal is a single reliable source for factual fields, while allowing the visible headline and preview copy to have intentional editorial differences.
Choose the appropriate metadata export
Static page information can use a metadata object, while route-dependent information can use generateMetadata. These APIs belong on the server side in the App Router. Keep a stateful editor or search component in a child Client Component instead of moving the page boundary and then attempting to export unsupported metadata from it.
Build a small route example
Suppose /tools/[slug]/ looks up the color-converter record. The route can construct its title, description, canonical and Open Graph URL from that record and the production origin. If no record matches, use the missing-page path consistently. Do not return metadata for a generic tool while the body renders an error or an unrelated fallback.
Inspect inherited nested fields
A title template is helpful for a short identity suffix, but inherited objects need deliberate handling. Ensure a page’s social title and URL actually describe that page instead of leaving the homepage values in place. Resolve relative URLs against the intended metadata base, and confirm that a preview environment has not become the canonical production origin.
Keep metadata accurate at build time
For static output, the generated records must be available when the build runs. An asynchronous lookup does not automatically require request-time behavior, but a private live dependency can still fail or make a build nondeterministic. Validate required fields before rendering so missing descriptions or malformed dates become actionable content errors rather than silently inconsistent head tags.
Audit generated HTML as a set
Inspect several routes manually, then extract titles and canonical URLs across the export. Check uniqueness, expected destinations and social metadata correspondence. Include articles with long names and missing slugs in the sample. A helper function is only a convention; the final HTML is the artifact that reveals whether templates, inheritance and route data produced the result you intended.
Further reading
Put the idea to work.
Explore free browser tools for images, text and developer workflows.