Skip to content
Tutorials Center
My learning

Topics

Lesson 37 of 37 ยท Projects and Practice

Launch Checklist and Maintenance

Move a Joomla site from staging to live safely and keep it healthy: go-live steps, redirects, search visibility, monitoring, a maintenance calendar and practice exercises.

Launching is not the finish line. A site that went live perfectly and was then ignored for two years is often the one that gets hacked, slows down or quietly breaks its forms. This last lesson gives you a go-live routine and a maintenance plan, and ends with practice exercises that combine everything in the second half of this tutorial.

Joomla cannot run on this site, so the checklist is written as precise actions, and the TryIt blocks are JavaScript stand-ins: a calendar that works out which maintenance tasks are due, and a redirect-map checker for migrations.

Before launch: staging and content freeze

Build and test on a staging copy (a separate address, ideally password-protected). Agree a content freeze: after a certain time nobody edits the old site, so nothing is lost when you copy.

On staging, search engines must not index the site. Set Robots to noindex, nofollow in Global Configuration > Site > Metadata and protect it with a password. Remember to reverse this at launch: one of the most common launch mistakes is a live site that keeps telling Google to go away.

Go-live steps

  1. Full backup of the staging site (files and database) and of the old live site, if any.
  2. Create or choose the production hosting: current supported PHP version, database, enough memory, HTTPS certificate, cron access.
  3. Copy the site: restore the backup (an Akeeba-style restore script or manual file copy plus database import). Edit configuration.php for the new environment: database host, name, user and password; $log_path and $tmp_path; and leave $live_site empty. See the care points in Security Hardening and Updates.
  4. Point DNS to the new host, lowering the TTL a day before so the change spreads fast. Keep the old host available for a few days.
  5. Enable HTTPS and set Force HTTPS in Global Configuration once the certificate works.
  6. Switch on search visibility: Robots index, follow, remove password protection, check robots.txt does not block the site.
  7. Turn off debug and error display, check Site Offline is No.
  8. Clear caches (Joomla and any CDN), and enable the page cache and compression described in Caching and Compression.
  9. Submit the sitemap and verify the site in Google Search Console and Bing Webmaster Tools.
  10. Smoke test the key paths: home, every menu link, search, contact form (receive the email!), login, registration, a download, a 404 page, mobile view.
flowchart LR
    A["Freeze content"] --> B["Backup"]
    B --> C["Restore on production"]
    C --> D["Fix configuration.php"]
    D --> E["DNS + HTTPS"]
    E --> F["Open to search engines"]
    F --> G["Smoke test + monitor"]

Order matters: do not open to search engines before the site is correct.

Replacing an old site: redirects

If an old site had URLs with ranking or links, map every important old URL to its new equivalent with a 301 redirect (see SEO-Friendly URLs and Metadata). Export a list of old URLs from analytics or a crawl, map them, import them into Components > Redirects (or write server rules for large numbers), and test them all. This stand-in checks a redirect map for typical mistakes: chains, loops and missing targets.

JS Check a redirect map

Press Run (or Ctrl + Enter) to see the console output here.

No output.

After launch: the first week

  • Watch the error log, the 404 report (Redirects component) and Search Console for crawl errors; fix with redirects or restored pages.
  • Confirm analytics works, with consent handled correctly.
  • Compare speed with your tests (Images, Assets and Core Web Vitals); real-user data arrives within weeks.
  • Keep the old host and backup for a couple of weeks.
  • Hand over documentation to the client or team.

Maintenance plan

Maintenance is a calendar, not a mood. A reasonable baseline for a small site:

Frequency Tasks
Daily (automatic) Backup, uptime monitoring
Weekly Check Joomla and extension updates, read the error log, scan form spam, test the contact form
Monthly Install updates after testing on staging, review users and Super Users, check the User Actions Log, look at Search Console and 404s
Quarterly Test a restore, review plugins and extensions (remove unused), check PHP version support, run a speed test, review privacy policy and consent
Yearly Renew domain and certificate (if manual), review hosting plan, plan major upgrades, content audit

Add a major-version plan: when a new Joomla major release arrives, read the migration notes, check whether your extensions and template support it, and migrate on staging with real data. Check the official Joomla roadmap for the end-of-life dates of the version you use, so that you never end up on an unsupported release.

JS Which tasks are due?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Copy the idea into whatever calendar or ticket tool you use, and assign each task a person.

Practice exercises

  1. Template: duplicate the default style, change the brand color so the link contrast is at least 4.5:1 and put the change into user.css (Cassiopeia and Template Styles).
  2. Override: create a child template and an alternative article layout that hides the author for one menu item (Template Overrides and Child Templates).
  3. Extensions: choose a gallery extension for a site using the scoring approach from Choosing and Vetting Extensions and write down why you rejected the others.
  4. Access: set up a Partners group and level and test with a guest, a member and a partner (Users, Groups and Viewing Levels).
  5. Speed: record LCP, INP and CLS of your home page, make three changes, and measure again.
  6. Code: write the manifest and service provider of a content plugin that replaces with the current year (Plugins and Events).
  7. Automation: write the curl command that lists the five newest articles through the API, and the cron line that runs the scheduler (Web Services API and CLI).
  8. Security: run the audit from Security Hardening and Updates on your own site and fix the first three findings.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a classic mistake at launch?

    Staging is hidden from search engines; forgetting to reverse that keeps the live site out of search results.
  2. 2. Why lower the DNS TTL before moving hosts?

    A short TTL makes caches expire quickly, so the new address spreads in minutes rather than hours.
  3. 3. What is wrong with a redirect chain?

    Each hop slows the visitor and crawlers; map old URLs straight to the final destination.
  4. 4. How often should you test restoring a backup?

    An untested backup may fail when you need it.

Summary

  • Build and test on staging with noindex; reverse it at launch.
  • Follow an ordered go-live routine: backup, restore, fix configuration.php, DNS, HTTPS, open to search engines, smoke test.
  • Map old URLs with direct 301 redirects and test the map.
  • Keep a maintenance calendar with weekly, monthly, quarterly and yearly tasks, and plan major upgrades.
  • Practice by applying the second half of this tutorial to a site of your own.

Next: Back to the Joomla track