All posts
Web Development · 11 min read · Aug 21, 2026

SEO for Generated Pages: Metadata, Structured Data and Links at Scale

Metadata and structured data generated from one template

Generating many pages from a single registry and route changes what optimization means. You are no longer writing a title for a page; you are writing the rule that produces forty titles. Every decision multiplies, which makes this one of the few areas where a small amount of design thinking pays across an entire site at once.

The duplicate content trap

The characteristic failure of templated pages is a set of descriptions that differ by one word. Filling a sentence pattern with the item name produces text that is unique as a string and interchangeable as content, and a set of near-identical pages competes with itself rather than ranking.

The fix is not cleverer templating. It is that each entry must carry genuinely distinct content - what this specific thing is for, when to use it, what it does not do - written once and stored with the entry. That is a real content cost, and it is the cost that makes the pages worth having.

Give each page a reason to exist

A page whose entire content is an interactive widget has almost nothing to index. The elements that make these pages substantial are the same ones that make them useful to a human arriving cold.

  • A short description of what it does, in the words someone would search for rather than internal terminology.
  • Worked examples with real input and output, which is the part visitors scroll to first.
  • A few honest questions and answers, including what it does not handle.
  • Links to the sibling items someone on this page would plausibly want next.

Because all four live in the registry entry, they are also the fields whose absence a build-time check can catch - which is how a set of pages stays substantive as it grows rather than accumulating thin entries nobody noticed.

Structured data comes free, and must stay true

The same entry that renders the visible page can emit its structured data, and that coupling is the point: the markup cannot describe something the page does not show, because both come from one source.

Registry fieldStructured data it produces
The faqs arrayFAQ markup, matching the accordion on the page
Category and slugBreadcrumb trail, matching the visible breadcrumbs
The full item listAn item list on the index page
Name, description, categoryThe page's own entity description
Generated from the same data as the visible content, so the two cannot drift apart.

That last property is the one worth protecting. Structured data describing content that is not actually on the page is a violation rather than a shortcut, and hand-maintained markup drifts into exactly that state within a few edits. Generation removes the possibility.

Filters create pages you did not mean to publish

An index page with category filtering usually implements them as query parameters, which produces a distinct address for every filter combination. Each one serves a near-identical subset of the same list, and left alone they are candidates for indexing as separate thin pages.

  1. Point the canonical on every filtered variant at the unfiltered index.
  2. Include only the canonical index in the sitemap, never the filter permutations.
  3. If a category genuinely deserves its own page, give it a real path and real content rather than a parameter.
  4. Keep filter state out of links that appear in navigation, so crawlers are not led through the permutations.

The third point is the judgement call. A category with a substantial description, its own examples and enough items is worth a real page. A category that is just a filter is not, and giving it one produces exactly the thin content the canonical was meant to prevent.

Internal links are the compounding asset

A generated set of pages defaults to being a flat collection reachable only from one index, which wastes the main structural advantage of having a registry. The related-items field turns it into a graph, where every page links to several siblings and receives links from several others.

Deriving those relationships rather than curating them is what keeps the graph complete as the set grows. A hand-curated cross-link is correct on the day it is written and increasingly incomplete afterwards, because nobody revisits the fortieth page when the forty-first is added.

Titles and descriptions are for people first

Two habits do most of the work here, and neither is technical. Write the title as the phrase someone would type, not as a product name - the thing itself followed by what it is, rather than a brand construction. Write the description as the sentence that would make someone click, which is usually a statement of what they can do and a reassurance about a concern they already have.

The temptation with generated pages is to pack keywords into a pattern, because it is cheap to apply everywhere. It reads as machine-written to a person, which is the audience that decides whether the click was worth it.

Measure at the template level

Because every page shares a template, the useful diagnostic is comparative rather than individual. Pages appearing in results but rarely clicked usually share a description pattern that undersells them. Pages not appearing at all usually share thin content. Both are single edits to the shared template or the missing registry fields, rather than forty separate pieces of work.

Conclusion

Templated pages make optimization a leverage exercise. Write the metadata rules once and they apply everywhere, generate structured data from the same source as the visible content so the two cannot disagree, keep filter permutations out of the index with canonicals, and let the registry build a link graph instead of a flat list. Then spend the time you saved on the part that cannot be generated: giving each page something genuinely its own to say.

Contact

Let’s connect

Have a Liferay or Backend project you’d like to talk through? Fill in the form and I’ll get back to you.

Book Calendar