About

Hi! We’re launching a lightweight WordPress news site that automatically publishes short posts whenever restaurant inspection results change (closures or grade changes). You’ll stand up an SEO-ready WordPress install using a fast theme (e.g., GeneratePress/Astra), configure RankMath or Yoast with clean URLs, sitemaps, and breadcrumbs, and create two reusable post templates: an “Inspection Alert” (facility, address, date, grade, closure flag, source link) and a “Weekly Digest” that summarizes the last seven days. The site should be mobile-first and performant, with Core Web Vitals of 85+ on mobile. In parallel, you’ll build a daily n8n workflow that pulls inspection data (API preferred—Socrata/Open Data; scraping only if necessary), detects new closures and grade changes versus a stored “last known” state, and formats a 120–180-word post with details and a source link before publishing to WordPress via the REST API (configurable as draft or publish). Please persist state in either Google Sheets or PostgreSQL (your recommendation) and add a scheduled job to generate a weekly digest every Monday at 9am PT. I’ll handle GoHighLevel (GHL) embeds and downstream email/SMS automations on my side. For handoff, I’d like a brief Loom or README covering configuration, schedules, how to add cities, and how to toggle draft/publish. Acceptance looks like this: you simulate one grade change and one closure and the system creates two correct posts with the right taxonomy and custom fields; the Monday digest renders properly; the site is indexable and meets the PageSpeed target on mobile. You should be comfortable with WordPress setup and SEO best practices, n8n (or Make/Zapier with willingness to use n8n), REST APIs (including WordPress), and basic ETL with JSON/CSV from open data sources; Playwright/Puppeteer scraping is a plus. We work API-first where possible, keep things simple and maintainable, prefer env vars for secrets, ship to staging first, and then promote to production once the acceptance test passes. I’m in Pacific Time and prefer a 30–45 minute kickoff, short daily async updates (progress, blockers, next steps), and one brief weekly sync; please flag blockers early. This is a fixed-price project in the $1200 range over 2–4 weeks, with milestones for WordPress foundation, n8n test post to staging, and full automation to production with docs. To apply, please share 1–2 examples where you automated data → WordPress publishing, outline briefly how you’d implement change detection and WP posting, tell me whether you’d use Sheets or Postgres for state (and why), confirm a 2–4 week timeline, and include any assumptions or questions you need clarified. Looking forward to working with you!