goldencheetah.org

GoldenCheetah is a free, open-source desktop application for cyclists and triathletes who want to download, store, and analyze their own ride data on their own computer. It runs on Linux, macOS, and Windows, imports data from a wide range of devices and file formats, and provides analysis tools covering power, heart rate, and other training metrics. If you want full control over your training data and the freedom to analyze it however you like, GoldenCheetah is built for exactly that purpose.

What GoldenCheetah Does

The project's stated belief is that athletes "should be able to download their power data to the computer of their choice, analyze it in whatever way they see fit, and share their methods of analysis with others." That philosophy shapes what the software offers:

• Direct device import — pulls ride data straight from many devices.
• File import — reads data already downloaded with other programs.
• Analysis tools — a rich set of charts and models for examining rides.
• Cross-platform — Linux, macOS, and Windows builds.
• Open source — released under an open-source license, with source code freely available on GitHub.

Supported Data Formats

GoldenCheetah imports "all popular file formats," including:

It also supports direct download from devices such as SRM PowerControl 5/6/7, PowerTap Cervo, CycleOps Joule, and the Moxy muscle oxygen monitor.

Cloud Integration

Beyond local files, GoldenCheetah connects to a range of cloud services, including Google Drive and Calendar, Dropbox, Strava, Today's Plan, Xert, SixCycle, SportTracks.mobi, Withings Weight, Cycling Analytics, ErgDB, Ride With GPS, SportPlusHealth, Velo Hero, Selfloops, and Trainingstagebuch.org. A Cloud Wizard walks you through selecting the service type and downloading directly.

Analysis and Modelling

GoldenCheetah's analysis side goes beyond simple charts. Its modelling topics include:

• Power and Duration — Critical Power and W′ (the work capacity above critical power).
• Bioenergetics — the energy systems behind your efforts.
• Motor Units — recruitment and fatigue.
• Forensic Ride Analysis — multiple charts to examine a ride in detail.

These tools are aimed at athletes and coaches who want to understand why a ride looked the way it did, not just record that it happened.

Versions and Downloads

• Current stable release: Version 3.8, with builds for Windows (10/11) x86-64/AMD64, Apple Silicon macOS (15+) ARM64/Mx, Intel macOS (12.7+) x86-64/AMD64, and Linux (AppImage) x86-64/AMD64. Source code is available as zip and tarball.
• Older versions and resources: Older releases, a user guide, and a FAQ are available.
• Snapshot builds: Published automatically when significant enhancements or major bug fixes land. These are developer-tested only and may contain regressions — the project explicitly warns to always take a backup before running snapshot builds.

Who It's For

GoldenCheetah suits cyclists and triathletes who:

• Want their training data stored and analyzed locally rather than only in a vendor's cloud.
• Use power meters, heart rate monitors, or other sensors and want deeper analysis than a basic ride log.
• Are comfortable installing desktop software and, if needed, working with file imports.
• Value open-source software and the ability to inspect or contribute to the code.

If you prefer a purely browser-based tool with no installation, or you only need basic ride tracking, GoldenCheetah's depth may be more than you need. But if you want to own your data and dig into the physiology behind your rides, it's a strong fit.

If you're new to Ahrefs and want to run your first SEO audit, the fastest path is: open Site Explorer, enter your target URL, review the Overview for a health snapshot, then dig into Organic Keywords, Top Pages, and Site Audit to find specific problems. From there, build a short prioritized to-do list instead of trying to fix everything at once.

This tutorial walks through that workflow using a realistic starting scenario, explains what the numbers mean, and shows how to turn findings into actions.

Before You Start: Pick a Narrow Scope

A common beginner mistake is auditing an entire large website on day one. The reports become overwhelming, and you can't tell which issues matter.

Instead, choose one of these starting points:

• A single important page (your homepage or a key product/service page)
• A small site (under ~50 pages, e.g., a personal blog or small business site)
• One section of a bigger site (e.g., /blog/)

For this tutorial, assume you're auditing a small business site with about 30 pages. The same steps scale up later.

You'll need an Ahrefs account to follow along. Ahrefs offers paid plans, and pricing and feature limits change over time, so check the current Pricing page for what's included in each tier before committing.

Step 1: Enter Your Target in Site Explorer

Site Explorer is Ahrefs' core tool for analyzing any website or URL.

1. Open Site Explorer from the top navigation.
2. In the search box, paste your domain (e.g., example.com).
3. Choose the Exact URL or Domain mode depending on scope. For a full-site view, use Domain or Prefix; for a single page, use Exact URL.
4. Press Enter.

You'll land on the Overview report. Don't try to absorb everything — focus on four numbers first.

Reading the Overview Snapshot

Important caveat: Ahrefs' traffic and keyword numbers are estimates based on its own data. They won't match Google Search Console or your analytics exactly. Treat them as directional, not absolute.

Step 2: See What You Already Rank For

Go to Organic Keywords in the left sidebar. This shows queries where your site appears in search results.

Sort by Traffic (descending) to see which pages bring the most estimated visitors. Then look for:

• Keywords ranking in positions 4–15 — these are often the easiest wins. A small content or on-page improvement can push them onto page one.
• Keywords with high volume but low position — potential opportunities if the topic is relevant.
• Irrelevant keywords — if you rank for something off-topic, it may signal thin or mismatched content.

Write down 5–10 of the position 4–15 keywords. These become your first optimization targets.

Step 3: Find Your Best and Weakest Pages

Open Top Pages. This ranks your URLs by estimated organic traffic.

Look for two things:

1. Your top performers — understand what topics and formats work. Can you create more content like this?
2. Pages with traffic but poor rankings — these may need on-page fixes (title, headings, internal links).

If a page gets zero traffic and targets a topic you care about, it's a candidate for a rewrite or consolidation.

Step 4: Run a Technical Site Audit

Now move to Site Audit. This crawls your site and flags technical and on-page issues.

1. Click Site Audit → New project.
2. Enter your domain and set crawl settings (default is usually fine for a small site).
3. Start the crawl and wait for it to finish.

Once complete, you'll see a Health Score and a list of issues grouped by category.

Which Issues to Fix First

Not all issues are equal. Prioritize in this order:

Ignore low-impact warnings (like minor meta description length) until the big items are handled.

Step 5: Turn Findings Into a To-Do List

You now have raw data. Convert it into a short, actionable list. Example:

1. Fix 3 broken links found in Site Audit.
2. Rewrite title tags on 5 pages with duplicate titles.
3. Improve 4 pages ranking in positions 6–12 by adding missing subtopics and internal links.
4. Remove or update 2 thin pages with no traffic.

Keep the list to 5–10 items max for your first audit. Finishing a short list beats starting a long one.

Common Beginner Mistakes

• Chasing every red flag. Site Audit flags many minor issues. Fix what affects rankings and users first.
• Trusting estimates as exact numbers. Ahrefs data is modeled, not measured from your analytics.
• Auditing a huge site too early. Start small to learn the interface.
• Ignoring search intent. A page can be technically perfect but still fail if it doesn't match what searchers want.
• Forgetting to re-crawl. After fixes, run Site Audit again to confirm improvements.

Where to Go Next

Once your first audit is done:

• Compare with competitors using Site Explorer's Competing Domains and Content Gap reports.
• Track keyword rankings over time with Rank Tracker.
• Explore backlink opportunities in the Backlinks and Link Intersect reports.
• Set up recurring Site Audit crawls so new issues surface automatically.

Your first audit isn't about perfection — it's about building a repeatable habit: enter a target, read the key reports, pick the highest-impact fixes, and act. Do that once a month and your site's health compounds.

GoldenCheetah is an open-source desktop application for Linux, macOS, and Windows that imports ride data from a wide range of devices and file formats, then provides a rich set of analysis tools for examining it. Its analysis features are aimed at cyclists and triathletes who want to download their power data to their own computer, analyze it however they see fit, and share their methods with others. If you already record power, heart rate, or related metrics and want modelling and charting tools rather than just a file viewer, GoldenCheetah is built for that purpose.

Power and duration modelling

GoldenCheetah's modelling section covers the relationship between power output and how long you can sustain it. The site names two specific models:

• Critical Power and W' — the power–duration model that estimates your sustainable "critical" power and the finite work capacity (W') above it.
• Bioenergetics — analysis of the energy systems underpinning that power production.

These are the tools to look at if your question is "how fit am I over different durations, and where does my limit sit?" rather than "what did I average today?"

Fatigue and neuromuscular analysis

Beyond whole-ride averages, GoldenCheetah includes modelling of how fatigue develops:

• Motor Units – Recruitment and Fatigue — analysis of how motor units are recruited as intensity rises and how they fatigue.

This is relevant when you want to understand why power falls off during sustained efforts or repeated surges, not just what the final number was.

Forensic ride analysis

The site describes "Forensic Ride Analysis" with multiple charts to examine a ride in detail. This is the part of the toolset for dissecting a single session — looking at the ride from several angles at once rather than a single summary metric.

Importing data to analyze

Analysis depends on getting your data in first. GoldenCheetah imports many popular formats directly, including:

It can also pull data from cloud services including Google Drive and Calendar, Dropbox, Strava, Today's Plan, Xert, SixCycle, SportTracks.mobi, Withings Weight, Cycling Analytics, ErgDB, Ride With GPS, SportPlusHealth, Velo Hero, Selfloops, and Trainingstagebuch.org. Some devices — SRM PowerControl 5/6/7, PowerTap Cervo, CycleOps Joule, and the Moxy muscle oxygen monitor — can be downloaded from directly.

Deciding whether it fits your needs

Choose GoldenCheetah if you want power–duration modelling, fatigue and bioenergetics analysis, and detailed per-ride charting on your own machine, and you record in one of the supported formats or sync from a supported cloud service. It is released under an open-source license and runs on Linux, macOS, and Windows.

Before relying on it, check two things: that your device or file format appears in the import list above, and that the specific model you care about (Critical Power/W', bioenergetics, motor units) matches the question you're trying to answer. The project also publishes a user guide and FAQ, which are the right places to confirm current behaviour and any setup steps for your platform.

GoldenCheetah can import ride data from most popular cycling computers, power meters, and training platforms. If your device exports FIT, TCX, GPX, PWX, SRM, or one of the other formats listed below, you can load it into GoldenCheetah for analysis. It also connects directly to some devices and syncs with several cloud services, so you often don't need to export a file manually.

File formats GoldenCheetah imports

GoldenCheetah reads files from these sources:

If your device or app can export any of these formats, GoldenCheetah can import it. FIT and TCX cover most modern Garmin, Wahoo, and similar head units; GPX works for GPS-only rides without power; PWX and WKO are TrainingPeaks exports; SRM files come from SRM power meters.

Direct device import

GoldenCheetah can pull data straight from certain devices without going through an export step:

• SRM PowerControl 5/6/7
• PowerTap Cervo
• CycleOps Joule
• Moxy Muscle Oxygen Monitor

This is useful if you want to download a ride immediately after a session without opening the device's own software first.

Cloud service integration

GoldenCheetah syncs with these services, so rides uploaded elsewhere can flow into your local analysis:

Google Drive and Calendar, Dropbox, Strava, Today's Plan, Xert, SixCycle, SportTracks.mobi, Withings Weight, Cycling Analytics, ErgDB, Ride With GPS, SportPlusHealth, Velo Hero, Selfloops, and Trainingstagebuch.org.

The Cloud Wizard walks you through setup: select the type of service, then select the specific service. Once connected, you can download activities directly rather than exporting and re-importing files.

How to check compatibility before downloading

1. Identify what your device or app can export. Check its export or "save as" options for any format in the table above.
2. If your device is a Garmin, Wahoo, or similar head unit, look for FIT or TCX export — both are supported.
3. If you use a training platform, check whether it offers PWX, TCX, or a direct cloud connection to one of the listed services.
4. If your device appears under direct device import (SRM, PowerTap, Joule, Moxy), you can skip file export entirely.
5. Download GoldenCheetah for your operating system — Windows 10/11, Apple Silicon macOS 15+, Intel macOS 12.7+, or Linux via AppImage — and try importing a sample file.

If your format isn't listed, the source code is freely available on GitHub, and older releases plus a user guide and FAQ are available if you need to check version-specific behavior.

GoldenCheetah snapshot builds are pre-release versions published automatically when significant new enhancements are available or when a major bug is squashed. They differ from the stable release (currently version 3.8) in one critical way: they have only been tested by developers, so regressions are possible. If you want to try new features early, snapshots are the way to get them — but you should always take a backup before running one, and you should not rely on a snapshot as your only copy of training data.

How snapshot builds differ from stable releases

The GoldenCheetah project states plainly that snapshot builds "may contain regressions as they will only have been tested by developers." That is the trade-off: you get fixes and features sooner, but you accept a higher chance of breakage.

Before you run a snapshot build

1. Back up your data. The project's own guidance is unambiguous: "ALWAYS TAKE A BACKUP BEFORE RUNNING SNAPSHOT BUILDS." Export or copy your athlete data and configuration so you can restore it if the build misbehaves.
2. Keep your stable install available. Since GoldenCheetah runs on Linux, macOS, and Windows, you can keep the stable 3.8 install in place and test the snapshot separately rather than replacing your working setup.
3. Expect the unexpected. Snapshot builds are published automatically, so a build may appear without a formal announcement beyond the snapshot page.

What you gain and what you risk

You gain: early access to significant new enhancements and fixes for major bugs, without waiting for the next stable release.

You risk: regressions — features that worked in the stable release may behave differently or fail. Because snapshots are developer-tested only, edge cases in your specific device imports or analysis workflows are less likely to have been caught.

A practical approach

If you depend on GoldenCheetah for regular analysis of ride data imported from devices such as Garmin/ANT+ (FIT, FIT 2.0), PowerTap (RAW, CSV), SRM (SRM), or cloud services like Strava, Dropbox, and Google Drive, treat snapshots as a testing channel rather than your primary tool. Run them on a copy of your data, verify that your import formats and charts still work, and only then consider adopting the changes — or simply wait for them to land in the next stable release.

If you are troubleshooting a specific bug that a snapshot claims to fix, the snapshot is worth trying — with a backup in place and the expectation that other things may break.