What this prompt does
This prompt designs a complete meta-tag and social-sharing strategy for [site_url] across your defined [page_types]. It produces title and meta-description templates per page type, Open Graph tags, Twitter Card tags using summary_large_image for [twitter_card_pages], dynamic OG image generation via [og_image_tool], a canonical strategy covering pagination and filtered pages, robots rules for indexing, structured-data alignment, hreflang for [languages], and an audit checklist with a validation script — delivered as ready-to-use HTML head templates.
The structure works because meta tags are inherently per-template, not per-page-written-by-hand, and the prompt treats them as templates keyed to [page_types]. That is exactly how a multi-template site stays consistent. The [twitter_card_pages] variable decides where large image cards make sense, [og_image_tool] shapes the dynamic image pipeline, and [languages] drives hreflang. The detail people skip — canonical rules for filtered or paginated pages — is precisely where indexing quietly breaks, and this prompt forces it into the open. It also aligns structured data with the meta tags so the two never disagree, and bundles a validation script, which turns the strategy from a one-time write-up into something you can re-check every time you add or change a template.
When to use it
- You have multiple page templates needing consistent, unique meta tags
- You want dynamic OG images with consistent branding across share previews
- You need a canonical strategy that handles pagination and filtered URLs
- You are running a multi-locale site and need correct hreflang tags
- You want robots rules deciding which pages to index versus noindex
- You need ready-to-paste HTML head templates rather than abstract advice
Example output
Expect per-page-type HTML head templates: title and description templates within length limits, full Open Graph and Twitter Card tags, canonical and robots rules, and hreflang blocks for your [languages]. It describes a dynamic OG image setup using [og_image_tool] and includes an audit checklist plus a validation script, so you can both implement and verify the tags across templates. The robots rules spell out which page types to index and which to noindex, keeping thin or duplicate variants out of search results.
Pro tips
- Define
[page_types]to match your real templates so each gets its own correct title and description pattern - Use
[twitter_card_pages]to reserve large image cards for pages where the visual actually helps, like posts and projects - Get the canonical rules right for filtered and paginated pages — that is where indexing silently breaks
- Match
[languages]exactly to your active locales so hreflang does not point at missing pages - Keep titles under 60 and descriptions under 155 characters as the prompt specifies, or they get truncated in results
- Run the generated validation script after deploying to catch conflicting or missing tags across templates
