# Production Consistency Audit

This package uses one public rendering path and one database-backed content source for visitors and ordinary crawlers. It does not implement crawler-specific content, Googlebot/AdsBot detection, referrer-based content switching, geolocation cloaking, or ad-review-only destinations.

## Public pages
- `/`
- `/about-us/`
- `/chicken-food-recipes/`
- `/contact-us/`
- `/terms-of-service/`
- `/privacy-policy/`
- `/cookie-policy/`

## CMS-controlled content
Homepage sections, recipe-page sections, About Us, Contact Us, header/navigation labels and URLs, footer/contact details, recipe records and PDFs, FAQs, popup copy, and policy text are stored in MySQL and rendered by the same templates used for all visitors.

## Forms and storage
- Recipe downloads: `leads.lead_type=recipe_download` and `recipe_id`.
- Recipe information requests: `leads.lead_type=resource_request`.
- Contact messages: `contact_messages`.

## Download behavior
Recipe PDFs are served through `download.php` after a successful recipe-download submission and temporary session authorization. Direct access to `uploads/recipes/` is blocked.

## Policy hygiene
The final package contains only the published legal pages listed in the footer and sitemap. Public policy pages contain only the actual policy text and no developer instructions.

## Deployment note
Google Ads approval cannot be guaranteed by code. Before advertising, make sure the live content, contact details, privacy disclosures, consent language, and advertised offer remain accurate. Do not introduce crawler-specific content, hidden review content, or redirects intended to disguise the promoted destination.
