garnishlisted

# garnish Garnish checks the metadata and indexing controls that surround a site's actual content. It works with the framework and policy already present in the target repository. It does not carry domains, account names, brand values, or fleet conventions from one site into another. ## Choose the mode - **AUDIT** is read-only. Use it when the user asks what is wrong, whether a site is ready, or why a page is not appearing correctly in search or social previews. - **FIX** applies an accepted audit backlog, or a narrowly requested metadata change. Use the site's existing components and conventions before adding anything. If the request says only "audit", stop after the report. Never turn an indexing review into an unrequested production change. ## Read project policy first Before checking tags, find the site's declared policy and public identity: - framework configuration and deployment configuration - the shared layout or head component - repository instructions, docs, or an SEO reference file - the production site URL and canonical path policy - robots, sitemap, and preview-environment rules Project policy wins over generic advice. If the repository does not declare a production domain or indexing policy, report that gap and stop before inventing one. ## AUDIT Walk five stations. Score each 0-5, where 5 is correct and verified, 3 works with material gaps, 1 is mostly absent, and 0 actively blocks discovery. | # | Station | What to verify | |---|---|---| | 1 | Page