Build an SEO Destination Website (WordPress) + AI Content-Monitoring Tool: Tourism Niche, Pakistan

This job is for anyone based in Pakistan only - or if anyone understands the local language, towns etc. Overview We are building thandiani.pk, an SEO-focused destination guide for a mountain destination in northern Pakistan. All content (six pillar pages, blog copy, sitemap and architecture) needs to be written. We need a developer to build the site to a high standard, and to build a lightweight AI monitoring tool that tracks new web mentions of the destination and generates SEO-ready draft content packs for our review. This is a two-milestone, hourly rate project. Bid for both, but each milestone is approved and paid independently. Milestone 1: WordPress build (or propose an alternative CMS with justification) on hosting we provide Six pillar pages + blog hub with five categories, per the site architecture Clean, fast, mobile-first design; Core Web Vitals in the green; image optimisation and lazy loading Full on-page SEO setup: schema markup (Article, FAQ, Breadcrumb), meta fields, XML sitemap, Search Console and GA4 connected Blog templates designed for recurring post formats (e.g. monthly report posts) A simple ad/featured-placement slot system on designated pages (dormant at launch, activatable later) Admin training: a 30-minute handover call and a short written guide so our team can publish without you Milestone 2: A tool that does three things on a schedule (daily or weekly): Scans the web: news, blogs, YouTube, and social where feasible for new publications and mentions of our destination and defined related keywords Summarises each finding: source, link, what it's about, and why it matters (or doesn't) Generates an SEO-ready draft pack for items worth responding to: suggested angle, target keywords, headline options, and a draft outline or post, delivered to us by email, dashboard, or Google Doc for human review before anything is published. We are open on implementation (n8n, Make, custom Python + LLM API, etc.): propose your stack and explain why. Nothing publishes automatically; the tool suggests, we approve. Must run on our accounts/keys and be documented well enough that we are not dependent on you to operate it.