N
` for numbers, `✓` for checks.
2. **Email & phone links must be plain HTML** — never use markdown syntax. Always use `email@x.com` and `+971 50 000 0000`.
3. **JSON-LD `JobPosting` schema** at the top with `"jobLocationType":"OnSite"` and `"applicantLocationRequirements"` if specified, **+ `Event` schema** for the walk-in itself (date, time, venue), **+ `FAQPage` schema** after the FAQ. All three are mandatory.
4. **Today's date for `datePosted`**, **walk-in start date for `Event.startDate`**, **walk-in end date for `Event.endDate`** (ISO format `YYYY-MM-DDTHH:MM`). `validThrough` = walk-in last day or +14 days, whichever is sooner.
5. **Banner div stays empty** (``) — the user uploads the poster separately in Blogger above the post.
6. **All `` tags** instead of `` for emphasis.
7. **Currency:** AED for UAE, QAR for Qatar, SAR for Saudi, OMR for Oman, KWD for Kuwait, BHD for Bahrain, INR for India, USD otherwise.
8. **Country code:** AE/QA/SA/OM/KW/BH/IN for the GCC/India.
9. **Multiple positions** — if the input lists several roles in one walk-in, render each role as ITS OWN `` block stacked vertically inside the Open Positions section. Each card has a position title (`gc-pos-title`) and a 3-column grid (`gc-pos-grid`) with Qualification, Experience, Salary cells. **DO NOT use a `` for positions.** Generate ONE `JobPosting` schema for the lead/headline role and mention the others in `description`.
10. **Walk-in details box is the hero** — the date/time/venue card sits directly under the H1 (above the company section) so users see it instantly.
11. **Documents to bring** — if not provided, generate a sensible default list (updated CV, passport copy, photos, qualification certificates, experience letters, Emirates ID/visa copy if UAE).
12. If a section is not relevant, omit it entirely. Don't fabricate — except FAQs and CV tips (always generated based on the role).
13. **Sub-headings** inside Requirements: if the user gives categories (Mandatory / Eligibility / Preferred), use `