The travel-agency website checklist most developers skip

Placeholder post — full write-up coming soon. The outline below is the spine of the post.

Most travel agency websites are built by developers who have never run an ad. The result: beautiful sites that don't convert. After shipping 50+ travel sites and watching the analytics on Google + Meta ad traffic, I've ended up with a checklist most freelancers skip.

Conversion (the part most devs skip)

• [ ] Sticky WhatsApp button on every page, every device
• [ ] Single-field "WhatsApp me" CTA above the fold — not a 12-field form
• [ ] Package detail pages with: included / not included, day-by-day itinerary, total fare, deposit amount, change/cancel policy
• [ ] Phone number is tel: linked, not just text
• [ ] Real customer photos and dated WhatsApp screenshots — no stock photos
• [ ] Trust signals visible without scrolling: IATA / ATOL / IATAN / verified business badge

Tracking (the part agencies skip)

• [ ] GA4 with custom events for view_package, whatsapp_click, phone_click, form_submit
• [ ] Meta Pixel + Conversion API (server-side) for iOS 14+ attribution
• [ ] Google Search Console linked and submitted sitemap
• [ ] UTM convention enforced on every ad — source / medium / campaign / content
• [ ] At least one weekly view of the data — a Loom report counts

Performance (the part Google Ads quietly scores)

• [ ] Mobile LCP under 2.5s on a real 4G phone (not your laptop)
• [ ] Hero image: WebP/AVIF, properly sized, lazy-loaded below the fold
• [ ] No carousel auto-playing on the homepage — they tank mobile LCP
• [ ] Self-host fonts where you can
• [ ] Pass Core Web Vitals on web.dev/measure

Content the team forgets

• [ ] FAQ on visa, payment, refund, change-of-date — these reduce WhatsApp load
• [ ] Privacy + terms pages (Meta will reject the Pixel domain without them)
• [ ] Refund / cancellation policy explicit on package pages
• [ ] About page with the actual team — photos, names, real locations

SEO basics

• [ ] One <h1> per page, with the package name
• [ ] OpenGraph image per package — not the same site-wide one
• [ ] Schema.org TouristTrip or Product for each package
• [ ] Internal linking between packages ("Travellers who looked at Umrah Standard also viewed Umrah Premium")

What's coming in the full post

I'm expanding each of these into a quick "why it matters + how to do it" section. Subscribe to the RSS feed or book a call if you want help with this on your own site.