A practical store-page product-research guide for premium running retailers

What On Holding’s premium store expansion changes for its online store pages

For retailers building practical store-page product-research guides, the visit starts before arrival. In September 2026, TradingView reported that On Holding was expanding its premium physical retail presence to build closer direct relationships around performance footwear and apparel, according to TradingView’s report and the announcement. Location research joins the buying journey online. While they’re deciding which shoe deserves their money, runners will investigate a retailer.

Consider the On Cloudmonster 2. A shopper may like its cushioning on the product detail page. Before ordering, though, they need to know whether a nearby store has the men’s version available to try. An address and opening hours don’t confirm stock.

Before asking for a visit, a premium retail page should answer buying questions.

The location page becomes part of the product decision

Each new retail site needs a destination page. It should tell shoppers what makes sense for their situation. A runner who needs to feel the heel hold in the Cloudmonster 2 requires different guidance from someone who knows their size and wants delivery. State whether staff provide fit help, whether appointments are available, and how online returns work at that location. A useful product-page research strategy connects those local answers to the catalog facts shoppers are already evaluating.

Often, premium retailers give store pages the structure of a basic locator. That’s fine when shoppers only need directions. It fails, though, when a runner is comparing a max-cushion shoe with a daily trainer and is still deciding where to spend Saturday morning.

For On, the useful structure connects the location with footwear research already happening across the site. Cloudmonster 2 shoppers need clear try-on messaging. The page should also link to the men’s model and offer a direct online purchase route when staff can’t confirm their size. This reduces uncertainty. It keeps the page useful instead of becoming another tab to close.

Why a premium running store creates high-intent search questions

On’s premium locations drive search behavior that a map listing cannot support. Runners search for a model with a neighborhood or city. Local support affects their choice. At that stage, they’re ready to decide. This is a key decision point.

Location searches become purchase research when the shopper has a product question.

Discovery and decision happen in different places

Brand discovery can begin in a map result, where a shopper checks the hours and confirms that the nearest On location exists. Purchase research begins when they need details about a fit concern or product variation related to a planned order. Accurate details support both stages.

Someone searching for a women’s Cloudrunner 2 in a wide width needs to know whether the retailer can help compare options and assess the fit before traveling across town. That matters. Generic copy such as “Running shoes available” or a glossy photo of a shoe wall doesn’t provide enough information to justify the trip.

These searches become transactional quickly. Shoppers want to avoid wasted trips and return shipments caused by incorrect sizing, so the content should reduce that risk with direct, useful specifics. Strong local SEO content answers these questions on the location page instead of leaving them to a map listing or support call.

• This location can help you assess the Cloudrunner 2 wide fit.
• Do I need to reserve a fitting time before arriving?
• Can I return an online footwear order at this address?
• Does the store host a run club or product trial event?

Build pages around the decision the runner is making

This destination should link to relevant shoe families and explain which features shoppers can compare side by side. For a running shop, that may mean concise sections for stability footwear and neutral daily trainers, with a visible link to sizing and fitting guidance. The copy at that address must reflect the service available.

Shoppers need to know what to expect before visiting. A narrower service promise reduces that friction. “Our team can help compare fit across selected running models” sets a clear expectation before the shopper visits, while “Find your perfect run” is a slogan that leaves shoppers to do the research.

Events follow the same rule. If a location hosts a community run, publish the meeting point and explain the run’s pace expectations, including whether product trial pairs are offered at the event. Event details can attract search traffic. Their real job is helping runners decide whether the visit fits what they need today.

Inventory claims fail first when store content is built like a directory

A directory may say a location carries running shoes. That alone is insufficient. A useful shopping destination should explain the product lines available for try-on, flag items that require confirmation before a visit, and note when shoppers need to start online before traveling, preventing trips for items the store was never positioned to stock.

Inventory language must match the reliability of the underlying inventory feed.

Exact counts require an exact data connection

Publishing “two pairs left” creates a promise. It may expire quickly. Inventory feeds can lag after staff hold an item for another customer or after a fitting or return affects availability, so the number shown online may no longer match the sales floor. Slow updates turn exact counts from helpful information into a source of support tickets.

Broad claims create the same problem. That includes “full collection available” when seasonal colors or uncommon widths are missing, forcing staff to explain why the website promised more than the sales floor contains.

Use the level of certainty the operation can support. If On can verify a SKU at a specific store in near real time, show availability with a timestamp; if it can’t, describe the assortment, then give shoppers a clear way to contact the business before traveling. A documented inventory-management workflow should define the feed refresh interval, reservation lag, return posting delay, and the point at which a local availability claim becomes too risky to publish.

Make availability a set of visible modules

A limited-edition Cloudsurfer colorway may be available online, while the store carries core neutral colors for try-on. Make this clear on the site. Explain that special colors can be shipped to customers. Although shoppers do not expect every online variant to be in the back room, the site should not imply that every online variant is there.

Availability module	What the page can safely say
Core try-on assortment	Neutral Cloudsurfer colors and common sizes are generally available for fitting.
Variable local selection	Seasonal colors and uncommon widths vary by location. Contact the store before visiting.
Online-only or special-order items	Limited-edition colorways can be ordered online and shipped directly to the shopper.

This structure gives the shopper a clear path without pretending that each shelf mirrors the ecommerce catalog, and it gives retail teams language they can stand behind when a colorway sells through.

Local content works best as an operational promise, so update it when the assortment changes or a size run ends on a product detail page. A premium retail experience depends on accurate expectations. They must hold up. In the real-world shopping environment.

Fitting services need their own decision details

On’s premium-store expansion creates a practical content issue. A location presented as a premium destination sets expectations for a high-touch experience, including fit and gait guidance; before crossing town, visitors also need to understand how the models differ, so the retailer’s page should make those expectations clear.

Fitting information should set expectations before a runner arrives at the retailer. A vague “expert fitting” line leaves too much work for the shopper. It doesn’t explain whether staff can assess their fit. Runners with wide feet need that information, along with those using an orthotic or preparing for a first race.

Describe the service as an appointment, not a slogan

Business details should explain reservation requirements and expected fitting times, including whether walk-in customers can receive help during busy periods. “Fitting available” tells a runner little. That’s important when planning a lunch-break visit.

A useful On location entry could explain that a 20-minute fitting session is available by booking, that walk-ins are welcome when capacity allows, and that staff can compare cushioning and fit across the range. It covers the booking rules, walk-in availability, session length, and the kind of help offered.

Too many retailers bury service details in a generic paragraph. Then staff answer the same pre-visit questions all day. That generates more phone calls and leaves less time for shoppers already there.

Use the product decision a runner is already making

A first-time marathon runner choosing between On’s Cloudmonster 2 and Cloudsurfer needs to know whether an On location can schedule a fitting, let them test both models, and consider their training goal.

The Cloudmonster 2 may appeal to runners seeking more cushioning over longer mileage. The Cloudsurfer offers a different ride. The product page should say whether an in-person visit will help the runner choose.

Add a short link from the fitting description to each relevant shoe-family page. The product listing can explain construction and intended use, while the local destination explains how shoppers can get human help with sizing and comparison.

Returns and fulfillment rules influence whether shoppers visit or order online

As On adds premium locations, fulfillment becomes part of local product research: a customer choosing between checkout and an in-person visit needs location-specific answers, yet central policy pages rarely make those answers easy to find.

Returns information belongs where the shopper decides between an in-person visit and an online order. Business hours aren’t enough. A phone number isn’t either. This matters most when a visit depends on a return-related service, such as confirming an unavailable size.

Put the local rule beside the visit details

Each On location should state its online return policy and say whether staff can exchange an ecommerce purchase. It should explain order pickup, too, along with what happens when the right size isn’t available on the sales floor, including whether staff can arrange shipment to the customer.

Keep the answer visible near opening hours. Keep it by contact details, too. Then direct readers to the central returns policy, while the local entry answers the immediate question and the policy page covers full conditions, such as the required order record or product condition.

Return rules are often trapped on a legal-style help page. Local search visitors never get there. That gap pushes customers to call a retailer for an answer the website should have delivered in one screen.

A failed return visit damages the next purchase decision

Picture a customer who ordered Cloudgo shoes online and needs a different size. Before driving to a nearby premium On location, they need a direct statement: can it exchange the original order, or can it only help with a new purchase?

They may arrive with unworn shoes. Then they learn the retailer can’t process the transaction, wasting time and weakening trust in future purchases.

On’s expansion makes this content more important. Each opening may introduce its own operating boundaries, so if stores vary, say so on the individual entry; if the policy is consistent, use the same concise module everywhere and manage it from one source of truth.

This supports product research, too, when a size decision feels risky. Clear exchange handling gives a runner more confidence to order the model they want, even when their preferred size isn’t available nearby.

Local running events need pages that connect to products and store visits

Premium On locations can turn group runs and race-weekend programming into valuable search content, while athlete appearances can help even though social posts disappear down the feed in a day. A permanent event entry answers the questions runners search for before deciding whether to attend.

Make each listing visit-planning content. Connect runners with the retailer and its footwear expertise.

Build the page around attendance decisions

A Saturday community run from an On premium retail location should include a route map, a pace range, guidance on whether a cushioned daily trainer suits the distance, and details on where to meet. Be clear about registration and bag storage.

That information helps someone considering shoes for a 5K social run or an easy longer effort. It also stops the event page from becoming generic brand promotion with only a time and logo attached.

The best local event pages address concerns that keep people from showing up: pace, route surface, whether the run returns to the store, and whether staff will answer shoe questions afterward. Those details matter.

Connect event intent to the relevant shopping path

Link the run entry to the location’s fitting details and the relevant On shoe family, while the location highlights upcoming activities for people who searched for it. That gives them a reason to visit beyond a standard retail transaction.

Use event structured data only when the page focuses on one real event and includes the required attendance details. Google’s event structured data guidance outlines the fields search engines use to interpret dates and venue availability.

After the run, preserve pages that earned links or continue attracting search visits, then add a brief completion note with route information and links to the next relevant activity. Delete thin announcements that never developed lasting search value.

How On’s store expansion raises the bar for product entities in search

With every location it opens, On’s store expansion raises the content standard. Search systems must connect the shoe in the catalog to the nearby place where a runner can try it or collect an order.

Structured data must reflect what shoppers can verify.

Go beyond descriptive store copy. Search engines need machine-readable facts about the item and its selling terms, along with a local destination supported by visible links that make sense to someone reading the page.

Give product and store different jobs

The Cloudrunner 2 detail page should identify the model and price. It should also show shoppers the available colors and sizes. Product markup should match those facts, while Offer details communicate current purchase terms for a selected variant, including price or availability.

Google Search Central’s product structured data documentation explains that Product markup can make product information eligible for richer appearances in Google Search when implementation requirements are met, as long as the markup is accurate and shoppers see the same information on the page. Use a documented structured-data implementation process to validate that visible product, offer, and local-business facts remain aligned.

Markup becomes unreliable when teams treat it as a hidden shortcut. A structured price that disagrees with the visible variant selector creates a trust problem for shoppers and search systems.

Use local pages. Explain the in-person next step.

A nearby On location can explain that the store offers fitting support for stability-shoe shoppers. It can also link directly to the stability footwear family and Cloudrunner 2 catalog entry.

Local business information should provide the address and explain when and how customers can reach the business. It should also clarify whether the requested service is available. A different research need. The SKU listing owns specifications and variant selection while providing online purchase information.

For store owners, the practical change is a deliberate link map. Each footwear page should point shoppers toward an appropriate nearby service route, while each store destination should send research-minded visitors back to the relevant models in the catalog.

What store page product research must answer before a store visit

The expansion matters because, long before someone leaves home, a store destination can support product research, clarify buying and return options, and help visitors understand what a store visit can accomplish.

A useful location page helps shoppers choose a product before planning their trip to the store.

Vague store content sends people to customer support. Visitors can’t tell whether a visit will solve their problem. Hours alone don’t explain whether someone can get fitted for a stability shoe, collect an online order, or process an eligible return.

Use four permanent content blocks

Build every store destination around the Store-Page Product Research Method: four permanent blocks that turn a locator into a product-decision page. They belong in the location template and should answer practical questions before the visit, so a new opening doesn’t begin with a blank page and an address pasted into it.

Content block	What it needs to answer
Visit basics	Address, hours, accessibility notes, and the easiest arrival instructions.
Product access	The main footwear families available to explore and links into their catalog collections.
Service details	Whether fitting is offered, how it works, and whether booking is required.
Fulfillment rules	Pickup availability, online-order return handling, and any store-specific restrictions.

The opening summary should do more than announce a storefront. For a first-time visitor, it should explain the neighborhood and core footwear focus, note fitting availability, and identify the best purchase route.

Write the page around a real shopping task

Consider a documented downtown running-shop implementation serving customers who are evaluating a men’s stability shoe. The opening stated that the store specialized in road-running footwear, offered fitting appointments, and included a direct link to the men’s stability collection for shoppers who wanted to compare models before visiting.

The inventory feed updated every 15 minutes, but did not account for shoes held during fittings or for returns waiting to be processed. The editorial decision was therefore to avoid SKU-level “in stock” counts: the page named core try-on families, labeled seasonal colors and uncommon widths as variable, and directed shoppers to contact the store for confirmation. The fitting block specified a 20-minute booked session and walk-in availability when capacity allowed; the fulfillment block stated whether ecommerce exchanges could be handled locally.

The measured outcomes to review after publishing are clicks into the stability collection, fitting appointment actions, store-contact actions, and repeat support questions about exchanges or availability. A decline in repeated pre-visit questions and an increase in those next-step actions indicate that the four blocks are reducing research friction; if the questions persist, the operating detail,not the slogan,needs revision.

Keep permanent facts on the store destination. A weekend gait-analysis clinic belongs on its own event entry. The individual catalog item should include its product specifications, including the available size range.

That separation avoids a common maintenance mess, because temporary promotion copy expires while a durable local destination stays useful by focusing on ongoing services and purchase rules.

Build a store-page publishing system that stays accurate

Location content stays accurate through an operating routine. Not an annual redesign project. Before outdated copy sends customers toward the wrong action, someone close to store operations needs a clear, reliable way to flag changes as they happen.

Location content stays useful when operational changes trigger editorial updates.

The strongest local destinations draw from operational inputs. A copywriter can’t reliably infer what a store can fulfill on a given day, while the store manager knows when pickup pauses and can explain temporary changes to fitting services and return-desk access.

Assign ownership before publishing

Give one operating owner responsibility for supplying changes. Give one content owner responsibility for updating and checking the page; that handoff is far more dependable than expecting a marketing generalist to catch policy changes through casual internal chatter.

• Store operations confirms hours and service availability.
• Merchandising confirms product-family access language.
• Customer support confirms return and fulfillment wording.
• The content owner publishes updates and checks page links.

Use a straightforward process. Review each location when a new store opens, and after operational updates that affect local fulfillment, using a clear trigger list that keeps the process manageable for a lean team.

Treat temporary restrictions as urgent content changes

When a running store stops accepting online-order exchanges during a renovation, update the local destination before the temporary policy creates avoidable support contacts. The notice should state the affected order type, the alternative return route, and when the restriction applies.

Place the same notice near fulfillment information. Don’t put it in a news feed, since shoppers arriving from search need the rule when deciding whether to travel to the store.

Teams sometimes wait for a wider site refresh. Don’t. That delay turns an accurate policy into a support burden, especially when a shopper stands at a return counter with an order confirmation open on their phone.

Measure whether the page reduces research friction

Page views alone don’t show whether content answered the visitor’s question. Track behavior suggesting someone moved from local research toward a useful next step.

• Search queries and landing-page visits that reach the store destination.
• Clicks from the local page into relevant product families.
• Fitting appointment actions where the store offers booking.
• Support questions that continue after an update goes live.

Review recurring support contacts alongside the page each month. If shoppers repeatedly ask whether online exchanges are accepted, whether fitting requires booking, or whether a footwear family is available, put the answer in the relevant content block.

That’s the goal: a page that reflects the store people will actually encounter, improves its usefulness in search, and helps customers avoid frustrating detours. Explore local SEO resources to map your product, fitting, inventory, returns, and structured-data pages into a clear next-step path for shoppers.

Frequently asked questions

---

Sources

• TradingView’s report
• the announcement

Written by Richard Newton, Co-founder & CMO, Sprite AI.