Technical SEO Webmaster — Build & Manage 10 Casino Content Sites (SEO-Optimized)

Customer: AI | Published: 20.08.2025

ABOUT THE PROJECT We’re launching a network of 10 independent casino information websites, each with its own brand and editorial focus. We provide domains, site concepts/architecture, and content. You’ll handle infrastructure, builds, publishing, and monthly management with a strong emphasis on SEO optimization, footprint diversity, performance, and compliance. Most sites will be affiliate properties with casino ranking/comparison modules and partner links; a smaller subset will be editorial/tools-led. We’ll provide all partner links, deep links, subIDs, logos, offer copy, and (if needed) brand assets for casino listings. SCOPE OF WORK Infrastructure & setup We provide domains. You research & recommend hosting per site to ensure diversity (different providers/ASNs/IP ranges); we pay once approved. Set varied DNS/nameservers (not identical across the network). Implement separate analytics per site (unique GA4 + GTM or equivalent) and separate Google Search Console properties. Create unique brand assets per site (favicon, OG images, logos, email inboxes). If needed, we can supply brand assets (logos, color palettes, typography/style kits). Build & tech stack (SEO-first) 7–9 sites on WordPress (no cloned “golden image”); mix themes/builders/plugins/permalink structures. 1–3 sites on a non-WP stack (e.g., Hugo/Next.js/Statamic) to reduce platform fingerprints. On-page SEO: title/meta templates, H1/H2 hierarchy, topical-silo internal linking, indexation controls (robots/canonicals), XML sitemaps, breadcrumbs, schema coverage (Organization, Article/Review/FAQ, Breadcrumbs) with unique id. Non-identical robots.txt/sitemaps/404 pages across the network. Publishing & on-page Publish 8–20 pages per site at launch (we supply content) with staggered cadence (not batch-posted). Create About / Editorial Policy / Contact / Responsible Gaming pages. Add normal editorial outbounds to trusted sources. Affiliate modules (majority of sites) Implement casino ranking/comparison tables (mobile-friendly, sortable/filters), review cards, pros/cons, badges, disclosure labels. Integrate partner links (we supply tracking links, deep links, subIDs, logos, offer copy). Configure link attributes properly (rel="sponsored"/"nofollow" where appropriate) and show clear disclosures. Performance, security & compliance Solid Core Web Vitals (mobile-first), tuned caching/CDN, optimized images and lazy load. Backups, updates, and security hardening (WAF/brute-force protection, least-privilege). GDPR basics (cookie consent, privacy). MONTHLY MANAGEMENT (WHAT IT INCLUDES) Uptime, SSL, backups & security: monitoring, certificate validity, daily/offsite backups, malware scans, user/access audits, staged updates. Performance & CWV: monthly field-data review, image/JS/CSS tuning, cache/CDN adjustments, TTFB/error investigations. SEO tech health: GSC Coverage/Crawl Stats, log-level crawl checks, sitemap & robots integrity, canonical/duplication cleanup, broken link fixes, structured-data QA (valid, brand-unique entities). On-page SEO upkeep: refresh titles/metas, expand internal linking within silos, update FAQs, prune/redirect thin or outdated pages, maintain clean URL hygiene. Analytics & monetization hygiene: strict tracking separation (unique GA4/GTM/GSC), affiliate link health & subID tracking, landing/offer checks, rotation of expired offers, light CRO tweaks. Add new casinos to rankings: add/update casino entries in comparison tables and review cards (we provide all content, tracking links, logos, offer copy, and terms); verify attributes/disclosures; QA across devices. Content ops (light): publish supplied articles on non-synchronized schedules, verify facts/screenshots, unique alt text/media hygiene. Compliance & trust: disclosure/labeling checks, responsible-gaming links, privacy/cookie banners functioning. Footprint hygiene: confirm ongoing diversity (DNS/host/ASN), avoid convergence of plugin/theme stacks, no sitewide links to our main site, only relevant in-content editorial links. Reporting: consolidated monthly report + per-site notes (traffic/rankings by intent cluster, CWV, indexation fixes, monetization checks, footprint audit, next-month actions). DELIVERABLES Infra map per site: DNS, host, IP, ASN, stack, caching/CDN. Access list: GA4, GTM, GSC, CMS, hosting, inboxes. Build sheet: theme/plugins (versioned), SEO/on-page configuration, schema approach, performance settings. CWV/performance report at go-live. Monthly maintenance log & action plan. MUST-HAVE EXPERIENCE Managing multi-site builds with diversified footprints (DNS/hosts/ASNs). WordPress at a high level and at least one static/headless stack (Hugo/Next.js/etc.). Technical SEO (crawl/indexation, canonicals, internal linking architecture, schema) and on-page SEO execution. GA4/GTM/GSC setup hygiene (no cross-site contamination). Core Web Vitals, image/CDN optimization, security hardening. NICE TO HAVE Ability to implement simple tools (e.g., bonus/wagering calculators, data dashboards). Comfort adapting provided UI patterns into non-identical implementations. COMPLIANCE & QUALITY NOTES We are building genuine, standalone editorial sites. We do not want cloned builds, identical tracking IDs, synchronized publishing, or look-alike link patterns. Advertising modules must be transparent and labeled; affiliate links configured responsibly. ENGAGEMENT MODEL Pilot first: 2 sites (1 affiliate-monetized, 1 editorial/tool) as a paid test. If successful, roll out the remaining 8 in 2–3 waves. If the collaboration is successful, we foresee a long-term partnership and scaling beyond the initial 10 sites. PRICING (WHAT TO QUOTE) Per-site price for build & infrastructure setup (excluding hosting fees — we pay those separately). Per-site monthly management fee (as described above). Proposed timeline for the 2-site pilot. Proposed budget for buidling 2 initial sites. HOW TO APPLY (ANSWER ALL) How will you ensure DNS/host/ASN/IP diversity across 10 sites? Show a sample robots.txt + sitemap strategy that avoids templated footprints. How do you guarantee separate GA4/GTM/GSC setups with no cross-site leakage? Share a schema plan showing unique id/Organization per brand. Provide your CWV playbook for WP (and for one non-WP stack). List 2–3 multi-site projects you’ve built/managed; describe what you did to avoid footprints.