# OG Images Full Guidance (Archive)

Last Updated: 2026-04-03
Source Rule: `.cursor/rules/og-images.mdc`
Status: Archive companion for pointer rule.

## Requirements

- Output complete OG/Twitter image tag set (`og:image`, secure URL, width, height, type, alt, twitter image/alt).
- Use absolute HTTPS URLs.
- Prefer 1200x630 dimensions unless specific override is required.
- Keep assets performant (target low file size while preserving visual quality).

## Generation Flow

1. Generate assets with OG scripts under `v2/scripts/og-images/`.
2. Register/update mapping in `v2/config/og-image-registry.php` when needed.
3. Render tags through helper-based flow (`get_og_image_for_page`, `render_og_meta_tags`).
4. Run validation/audit scripts before shipping.

## Publishing Rules

- New landing/content pages should have dedicated OG assets (no accidental fallback reuse).
- Index pages may use a page-type default only when no page-specific asset exists.
- Keep alt text descriptive and page-accurate.

## Validation Commands

- `python3 v2/scripts/og-images/validate-og-images.py`
- `python3 v2/scripts/og-images/validate-og-logo.py`
- `php v2/scripts/dev-helpers/validate-og-images.php --local`
- `php v2/scripts/og-images/audit-og-registry-vs-disk.php`

## Canonical SSOT

- `docs/systems/og-images/OG_IMAGE_GUIDE.md`
- `docs/systems/og-images/OG_IMAGE_GENERATION.md`
- `docs/systems/og-images/OG_IMAGE_ASSET_CHECKLIST.md`