/ Cloudways Deployment Internal
Landing Pages — Deployment

Cloudways Deployment Guide

How to deploy a finished LP from GitHub to Cloudways under the client's domain
1

Overview

All MM client landing pages will eventually live on Cloudways under a client subdomain (e.g. services.corediesel.com.au). GitHub Pages is used as a temporary preview environment while the page is being built and reviewed.

Once a page is ready to go live, Teddi handles the Cloudways deployment. This guide documents the process so Guy can understand what happens — and eventually do it himself.

⚠️
Route Cloudways deployments through Teddi for now. Once you're comfortable with the process and have Cloudways access, you can deploy yourself.
2

Before you deploy

Confirm all of these before touching Cloudways:

  • Copy reviewed and approved
  • Logo and hero image uploaded to the repo
  • GA4 tag in the <head>
  • Google Ads conversion tag added
  • Phone number correct and showing in all button labels
  • Map zoom level correct (z=14–15)
  • All "Read More Reviews" links point to real Google URLs (not #)
  • Form submission handler confirmed working
  • No broken images (no placehold.co placeholders visible)
  • PR merged to main on GitHub
3

Deployment steps

1
Log into Cloudways dashboard. Go to the client's application (or create a new one if this is a first deployment).
2
In the application settings, navigate to Application Management → Application Files.
3
Upload the index.html from the GitHub repo (download it from GitHub first — go to the file, click Raw, Save As). Also upload any images in the assets/ folder.
4
Confirm Varnish Cache is disabled and HTTPS Redirection is disabled in the Cloudways app settings. Both cause infinite redirect loops on static HTML sites if left on from a previous WordPress install.
5
Visit the Cloudways staging URL to confirm the page loads correctly.
🚨
Varnish and HTTPS Redirection must be OFF. These are WordPress-era settings that break static HTML pages. If the site shows an infinite redirect or a blank page, this is almost always the cause. Disable both in the Cloudways app settings.
4

Pointing the domain

Once the page is confirmed working on the Cloudways staging URL:

1
In Cloudways, go to Application Settings → Domain Management and add the client subdomain (e.g. services.corediesel.com.au).
2
In the client's DNS settings (usually their registrar or Cloudflare), add a CNAME record pointing the subdomain to the Cloudways server address.
3
Enable the SSL certificate in Cloudways — use Let's Encrypt, it's free.
4
Wait for DNS propagation (usually 5–30 minutes). Test by visiting the subdomain in a browser.
5

After deployment

  • Update the client table in the LP Editing Guide with the live Cloudways URL
  • Update the canonical tag in index.html to point to the Cloudways URL (not the GitHub Pages URL)
  • Confirm GA4 is receiving data — check GA4 Realtime while loading the live page
  • Submit the URL to Google Search Console if the client has an account
6

Troubleshooting

ProblemCauseFix
Infinite redirect loopVarnish or HTTPS Redirection still onDisable both in Cloudways app settings
Blank white pageSame as above, or a file path errorCheck Varnish/HTTPS first, then check file paths
CSS or images not loadingFile paths are relative and the root directory is wrongCheck the Cloudways webroot — should be /public_html/
SSL certificate errorDNS hasn't propagated yetWait 30 minutes and try again
Old WordPress site showing instead of LPWordPress files still in /public_html/Remove WP files before uploading the static HTML