Skip to content

Sports & outdoors · ecommerce growth

Running gear marketing agency

A runner buys the shoe their training plan says they need, in the week their long runs pass a certain distance, and they compare stack height, drop and weight across three models before they trust a store with the size. Triathletes add a wetsuit season, a race calendar and a bike they already own. We build running stores around the training calendar: shoe pages that survive the yearly version change, spec comparisons that rank, race-week timing for ads and email, and a mileage clock that brings the runner back for the next pair.

The buyer, in brief

Consideration
Days for a shoe they have worn before, one to two weeks for a new model or a GPS watch, a month for a wetsuit or a race-day setup
Purchase frequency
Shoes every few hundred kilometers, nutrition and socks through a training block, a watch every few years, a wetsuit when the old one tears
Seasonality
Spring and fall race seasons peak, January starts training plans, summer brings triathlon and trail, and Black Friday and the holidays carry watches and gifts
Price band
Mid for shoes and apparel, high for GPS watches and wetsuits, low but frequent for gels and socks; most orders are one shoe and a few consumables
Return risk
High on shoes, driven by size and fit between versions, moderate on wetsuits, low on nutrition and watches
Young woman ultra marathon runner tying shoelace on forest trail, running & triathlon gear ecommerce
Running & triathlon gearRunners on a training plan for a named race, from a first 10K to a marathon, and triathletes with a swim, a bike and a run to outfit. They check stack height, drop, weight and cushioning, read reviews from runners with the same gait, and want to know whether last year's version fits the same.

How running & triathlon gear makes money

Four levers, and what limits each one here

Revenue is traffic times conversion rate times order value times purchase frequency. In this niche each lever has its own ceiling.

Traffic

Traffic: model names, versions and the spec comparison

Runners search by model and version, then by spec and purpose. The name of a shoe plus a version number, that shoe versus another, stack height and drop for a stated purpose, best shoe for a marathon on a training plan. Triathletes add wetsuit thickness and buoyancy queries, and race-specific searches. A store that lists the current version only, under a Shoes collection, loses the version comparisons and the runners who loved the previous version. The traffic work is a page per model that persists across versions with the changes written out, spec-led collections by stack, drop and purpose, and race and training content that links to the shoe the plan calls for.

Conversion

Conversion: does the new version fit like the old one

The runner's objection is fit, and the version change is what makes it hard. A page that says whether the new version runs the same size as the last, how the fit changed, what the stack and drop are, and who the shoe suits converts far better than a spec table alone. Reviews from runners with the same gait and the same previous version matter more than star counts. Free returns on shoes are close to expected in this niche, so the policy has to be visible. Wetsuits need a size chart by height and weight and a note on how the neoprene should feel. Race-week shoppers need a delivery date, not a shipping estimate.

Order value

Order value: the training block, not the shoe

A shoe buyer on a plan needs socks, gels, a hydration setup and often a second pair for easy days. Order value grows when the store presents the training block: a marathon build kit with the daily trainer, the race shoe, socks and a nutrition plan, a first triathlon kit with the wetsuit, goggles, a race belt and a tri suit. Two-pair rotation pages (a daily trainer and a speed day shoe) raise the ticket honestly, because rotating shoes is how many runners already buy. Nutrition sold as a block's worth rather than a single box moves the basket up without a discount.

Frequency

Frequency: the mileage clock and the race calendar

Running has a replacement cycle that is roughly predictable. Shoes wear out after a range of kilometers that the manufacturer publishes, and a runner on a plan runs a predictable weekly volume. A store that knows the shoe bought and the race the runner is training for can send a replacement reminder near the end of the shoe's life and a race-week note with the essentials. Nutrition runs out on a training block rhythm. The race calendar is the second clock: spring marathon buyers come back in the fall, and a runner who bought a wetsuit in May will race a triathlon in August. Recording the race and the plan turns both into flows.

Search visibility

Search: the model page that outlives the version, and the spec comparison that ranks

Running search is dominated by model names and version numbers, and the page structure has to match. Each shoe model gets one page that persists across versions, with the current version selectable, the previous version still buyable while stock lasts, and a section that explains what changed in fit, stack, drop and weight. That page earns the model searches for years and stops the store from starting over each release. Comparison pages between two models the store sells (a daily trainer against a max-cushion shoe, two race shoes) earn the versus queries with real intent.

Spec-led collections (by stack height, by drop, by purpose such as race day, easy days or trail) are built from product data with copy that explains the trade-off. Training and race content (what to buy for a first marathon, a triathlon kit list, a race-week checklist) links to the products the plan calls for. Product pages carry stack, drop, weight, cushioning, width options and the fit note as text, with Product markup per size and color that validates.

Technical notes: the previous version keeps the same URL as the current one, size and color filters stay out of the index, and nutrition pages carry ingredient and allergen text because those queries are searched.

Queries that matter

  • does the new version of this shoe fit the same
  • best marathon shoe for slow runners
  • low drop daily trainer
  • triathlon wetsuit for cold water
  • first triathlon gear list
  • gps watch with training load
  • running shoes wide toe box

Model pages that explain the version change, spec comparisons between two shoes the store sells, and training kit lists with buyable products rank in running. A collection of shoes with a brand filter and a blog of race recaps do not.

AI answers

AI answers: runners asking whether the new version fits the same

Runners ask assistants whether a new version fits like the last one, which shoe suits a stated pace and distance, how many kilometers a shoe should last, and what a first triathlon needs. Stores get cited when the model page states the version change in plain sentences, when the spec is written as text with the purpose named, when the wetsuit size guidance is clear, and when the product markup agrees with the feed on price, size availability and version. We write the model and comparison pages so each fit or spec answer stands alone, keep the version naming consistent everywhere, and make sure the assistant crawlers can read the size grid as text.

Does the latest version of this shoe fit the same as the previous one?
What shoe should I use for a marathon at a 5:30 per kilometer pace?
How many kilometers do running shoes last?
What do I need for my first sprint triathlon?

Questions shoppers put to assistants. A store gets named when its pages answer them in plain text.

Google Shopping and Merchant Center

Shopping for shoes, wetsuits and nutrition: sizes, versions and apparel attributes

A running feed is an apparel feed with version numbers. Each size, width and color of a shoe is an item in one item group with its own GTIN, and the title reads brand, model, version, gender, purpose and color. Size, gender, age_group and color are required for apparel and footwear in the US feed, and size_system matters when the store sells across Canada and the US. The version belongs in the title and in product_detail so the query for a specific version matches, and the previous version stays in the feed while stock lasts with its own version stated rather than sharing the current version's title.

Wetsuits are sized by height and weight, so size and product_detail carry the chart's terms. Nutrition products carry ingredient and allergen details, and the food and supplement policies apply to any claim on performance, so descriptions state what the product is rather than what it will do to a race time. Availability breaks at size level: popular sizes sell out before a daily feed updates, so the schedule has to be frequent in race season.

Campaigns split by margin and cycle: nutrition and socks in a campaign that accepts a lower return because they repeat through a block, shoes bid to margin with the previous version in its own campaign at clearance, watches and wetsuits in a high-ticket campaign, and free listings on for every size and version.

Feed attributes that decide eligibility

  • item_group_id per model with size, width and color variants
  • size, gender, age_group and color for footwear and apparel
  • size_system for cross-border sizing
  • product_detail for version, stack, drop and weight
  • gtin per size
  • custom_label for version and clearance

Disapprovals we see in this niche

  • Size-level availability mismatch in race season
  • Missing apparel attributes on footwear in the US feed
  • Performance claims on nutrition products flagged under health policies
  • Previous version listed under the current version's title

Meta and social ads

Meta and social: the training block, the run club and the version change

Running creative works when it is inside the training block. The version change explained by someone who ran both, a long run in the shoe with the pace on screen, a run club's shoe rotation, a triathlete's transition setup laid out, the race-week checklist. Model-launch creative with the previous version still available at a lower price converts both audiences. Nutrition creative that shows the block's worth of gels and how they are used in a long run sells the block rather than the box.

Policy is where fitness and health meet: no before-and-after body imagery, no implication that the viewer is unfit or overweight, and no performance claims for nutrition beyond what the product is. Audiences start with customers and site visitors, then people interested in named races and run clubs in the store's regions, then lookalikes of shoe buyers. UGC from runners and club members needs rights and a check that the shoe shown is the version being sold.

  • Version change explained by a runner who has worn both
  • Long run in the shoe with pace and distance on screen
  • Run club shoe rotation: who wears what and why
  • Triathlon transition setup laid out piece by piece
  • Race-week checklist with the delivery date stated

Policy line

No before-and-after or body-transformation imagery, no personal attribute targeting or implication that the viewer is unfit, no performance claims for nutrition products, and manufacturer names inside trademark rules.

Conversion and the store

The store: size across versions, free returns and the race-week delivery date

The shoe page has to answer fit before spec. Whether the new version runs the same size as the last, width options, a fit note in plain words, then stack, drop, weight and purpose. The previous version selectable on the same page while stock lasts. Free returns on shoes stated near the size selector, because that is what lets a runner try a new model. Reviews filtered by gait and by previous version. A delivery date stated as a date, because race week is a hard deadline.

Wetsuit pages need a size chart by height and weight, a fit note on how the suit should feel, and a return policy for unused suits. Kit pages (marathon build, first triathlon) need one-click add for the whole list. On mobile, the size grid with stock per size, the version toggle, the returns line and the delivery date decide the sale, and the cart should show the socks and the nutrition for the block without slowing checkout.

Objections the page must answer

  • “Does this version fit the same as the one I wore”
  • “Can I return it if the fit is wrong after a run on the treadmill”
  • “Will it arrive before race day”
  • “Which of these two shoes suits my pace and distance”
  • “Which wetsuit size fits my height and weight”

Email, SMS and retention

Email and SMS: the mileage reminder and the race-week note

Running email follows the training plan and the race calendar. The post-purchase flow for shoes covers break-in, the rotation the shoe belongs in and the socks and nutrition for the block. The mileage reminder is timed to the shoe bought and the runner's likely weekly volume, landing near the end of the shoe's published life with the same model in the same size, or the new version with the fit change stated. Nutrition reorder runs on the block rhythm rather than monthly.

The race-week flow is the highest-value send in the niche: a checklist for the race the runner told the store about, the essentials with a delivery cut-off, and a good-luck note the day before. Post-race, a recovery and next-race note asks what is next, which resets the plan. Triathlon flows cover wetsuit care and the open-water first swim. Launch flows cover the version change for customers who own the previous version. SMS is used for race-week cut-offs and back-in-stock alerts by size.

  1. Break-in and rotation

    Two days after a shoe order

  2. Mileage replacement

    Near the end of the shoe's published life, by model and weekly volume

  3. Nutrition block reorder

    Every four to six weeks during a training plan

  4. Race week

    Seven days before the race the customer named

  5. Post-race next plan

    Three days after the race date

  6. Version launch

    When a new version of a model the customer owns launches

Where revenue leaks

The leaks we find in running & triathlon gear stores

The Growth Analysis ranks these against your own numbers and says which to close first.

Get a Growth Analysis for your running brand
  • A new URL for every version

    The store creates a fresh page each release, so the model searches land on last year's page, the new page starts from nothing, and the fit history that would convert the runner is lost.

  • Size-level stock that lies in race season

    The page shows the model in stock while the popular sizes are gone, and the runner discovers it at checkout the week before the race.

  • Returns that eat the ad margin

    Shoes come back at a rate the ad reporting never sees, so campaigns look profitable on paper and lose money after the returns land.

  • No idea which race the customer is training for

    Every runner gets the same newsletter, so the race-week note that would have sold the essentials never goes out.

Platform notes

Where the platform changes the work

Shopify

One product per model with version, width, size and color as variants stays within the variant limit for most shoes, and where it does not, a combined listing app keeps the model URL persistent. Metafields carry stack, drop, weight and the fit-change note for the page and the feed, and a returns app handles the free-returns policy without support tickets.

WooCommerce

Variable products carry sizes and widths, and the version can be an attribute so the model page persists; the feed plugin must send apparel attributes and size_system per variation, and the returns flow needs a plugin or a portal.

Headless

Size grids and version toggles must render server-side so the fit content is crawlable, and the race-week delivery date needs a real-time shipping estimate that does not delay the page.

Questions

Running & triathlon gear owners ask us

By CartKernel · Last reviewed

How should a running store handle a shoe's yearly version change?

By keeping one page per model with the version as a variant, so the model URL persists, the previous version stays buyable while stock lasts, and the fit change is written out on the page. The feed lists each version with its own title. The previous version gets a clearance campaign of its own, because runners search for it by name for months.

Are free returns necessary for selling running shoes online?

Close to it. The runner's main objection is fit across versions, and a visible returns line beside the size selector is what lets them try a new model. The cost is real, so we track the return rate by model and by size, write the fit notes that reduce it, and report ad performance after returns rather than before.

Can you advertise sports nutrition alongside running shoes?

Yes, with the descriptions stating what the product is and its ingredients rather than what it will do to a race time. Performance and health claims trigger the food and supplement policies on both Google and Meta. We write nutrition pages and feed data to the ingredient and the use, and sell it by the training block rather than the single box.

How do you use race calendars in ads and email for a running store?

By recording the race each customer is training for and by knowing the major races in the regions the store ships to. Race week gets its own ad budget with delivery-date messaging and the highest-value email in the niche, a checklist with a cut-off date. Post-race, a next-plan note resets the cycle, and the spring marathon buyer comes back for the fall.

What makes triathlon different from running for an online store?

Three sports, one race, and a wetsuit sized by height and weight. Tri shoppers buy kits rather than single items, they buy the wetsuit in spring for a summer race, and they need size guidance the shoe buyer does not. We build the first-triathlon kit page, the wetsuit size chart and the open-water first-swim flow as their own pieces of work.

How do you bring runners back for the next pair?

With a mileage reminder timed to the shoe's published life and the runner's likely weekly volume, landing on the same model and size or the new version with the fit change explained. Nutrition and socks run on the training block rhythm. We report replacement rate by model and the share of second pairs that stay with the store.

Grow your running & triathlon gear store.

A free Growth Analysis ranks what your store should fix first, by revenue at stake, in about a week.