Senior Wordpress Systems & Automation Engineer

SENIOR WORDPRESS AUTOMATION & TECHNICAL SEO DEVELOPER We are looking for a senior technical developer to take over and complete an existing internal website operations and automation platform for a large international WordPress website. This is not a web design assignment or a standard WordPress maintenance position. The platform connects website monitoring, technical SEO, task processing, evidence submission, quality control and several external data sources. The selected developer must first understand the existing architecture and codebase. The system must be completed and stabilised, not unnecessarily rebuilt from scratch. TECHNICAL ENVIRONMENT * Large multilingual WordPress website with thousands of pages * 16 language versions * PHP 8.x * Hostinger hosting * LiteSpeed and CDN caching * Custom WordPress functionality * Google Apps Script * Google Sheets * REST APIs and webhooks * Google Cloud services * Google Search Console * Google Analytics 4 * Google PageSpeed Insights * Screaming Frog * Existing Vercel read-only management dashboard * Automated monitoring, evidence and QA workflows * n8n or similar workflow automation where appropriate MANDATORY SKILLS 1. Advanced WordPress development * Strong PHP 8.x experience * WordPress core architecture * Custom plugins and functionality * Themes and child themes * WordPress hooks, filters and actions * WordPress REST API * WP-Cron * MySQL and WordPress database structure * Template-level debugging * Multilingual WordPress websites * Security, version control and rollback * Safe staging and production deployment Applicants whose WordPress experience is limited to page builders or installing plugins are not suitable for this project. 2. Google Apps Script and Google Sheets * Maintaining and debugging existing Apps Script projects * Building reliable triggers and automated workflows * Reading and writing structured Google Sheets data * Data validation * Locking and concurrency control * Preventing duplicate execution * Error handling, retries and recovery * Detailed execution logging 3. APIs, webhooks and automation * REST APIs and JSON * OAuth 2.0 * Secure API authentication * Webhooks * Event-driven architecture * Idempotency and deduplication * Retry logic and exponential backoff * Rate-limit handling * Queue processing * Secure credential management * n8n or comparable workflow-automation platforms 4. Google Cloud integrations * Google Cloud services * Pub/Sub or comparable messaging systems * Push notifications * Secure webhook endpoints * Event processing * Logging and monitoring * Automatic renewal and recovery processes 5. Technical SEO The developer must have proven technical SEO experience with large multilingual websites, including: * Canonicals * Hreflang * Language and regional codes * XML sitemaps * Robots.txt * Crawling and indexing * Redirects, 404 and 410 responses * Duplicate-content management * Metadata * Structured data and JSON-LD * Internal linking * Semantic heading structure * Image alt text * Crawl-efficiency optimisation * Google Search Console * Rich Results Test The developer must understand how a single error in a shared template, plugin or translation configuration can be reproduced across thousands of pages. 6. Screaming Frog automation * Scheduled website crawls * Automated exports * Importing crawl data into Google Sheets or another operational system * Comparing current and previous crawl results * Mapping issues to the correct URLs * Preventing stale crawl data from being accepted as current * Automated re-crawling and validation 7. Performance and Core Web Vitals * Lighthouse and PageSpeed Insights * LCP, CLS, INP, FCP, TBT and TTFB * WordPress performance profiling * JavaScript and CSS optimisation * Reduction of excessive HTML output * Image and font optimisation * LiteSpeed, CDN and browser caching * Cache invalidation * Mobile performance * Root-cause analysis Performance improvements must not break navigation, forms, analytics, structured data, content or commercial functionality. 8. Front-end development and functional QA * HTML5 and semantic HTML * CSS and responsive layouts * JavaScript and DOM debugging * Browser-console analysis * Unique HTML IDs * Accessible forms * Cross-browser testing * Mobile and desktop testing * Fixed and sticky elements * Z-index and overlap issues * Form and link validation Strong visual design skills are not the main requirement. However, the developer must be able to implement approved designs accurately without making unapproved changes. 9. Vercel and live-data dashboards * Existing Vercel deployments * API endpoints * Environment variables * Live-data binding * Google Sheets integration * Production debugging * Error and unavailable-data states * Read-only dashboard restrictions The developer must maintain the existing dashboard and architecture. Creating an unrelated replacement system or sample database is not part of the assignment. WORKING METHOD The project follows strict milestone-based quality control. For every phase, the developer must: 1. Investigate and document the root cause. 2. Propose the smallest safe correction. 3. Explain the risks and affected components. 4. Implement only the approved scope. 5. Test the change properly. 6. Submit complete technical evidence. 7. Wait for independent validation. 8. Correct rejected or incomplete work before continuing. The developer may not approve their own work or mark incomplete work as completed. EVIDENCE REQUIRED Every milestone submission must include: * Root-cause explanation * Exact files, functions, settings or templates changed * Before-and-after evidence * Relevant logs * Test URLs * Source-code or commit references * API responses where applicable * Desktop and mobile test results * Tests across multiple page types and languages * Regression-test results * Rollback instructions * Confirmation that unrelated functionality remains unchanged Screenshots alone are not sufficient when source code, logs or l