SEO and schema guide

The template includes JSON-LD for the site, home page, catalog pages, articles, and collection-style views. Keep schema conservative. Do not add ratings, prices, launch dates, events, or claims unless the real project has source-backed evidence for them.

Use visible page content as the source of schema. If a claim is not visible to users, it usually should not be asserted in structured data. Keep canonical URLs, sitemap entries, and robots rules aligned with the generated pages.

When adapting the site, search for old domain-specific terms before shipping. The template should not leak placeholder claims into metadata, schema, or llms.txt.

Adaptation Notes

Use this guide as a working pattern, not as fixed product copy. Replace the example nouns with your project’s real terminology, then verify that each internal link still points to a generated page. If a claim depends on external evidence, attach the source in the relevant content record instead of burying it only in prose. This keeps the guide readable for users and maintainable for editors.

Before publishing, inspect the rendered page on mobile and desktop. The template is intentionally dense, so headings, cards, tables, and callouts should be checked with real text rather than short placeholders. When a section no longer applies to your niche, remove it cleanly or replace it with a more useful workflow; do not leave empty headings behind.