runindia.in, reimagined.

The page title reads 'Welcome to runINDIA' and jumps straight into event cards. There is no headline explaining the platform's purpose — discovery, registration, results, community — leaving new visitors to infer it. Platforms like this live or die by runner acquisition; every confused first-timer is a lost registration fee.

The homepage simultaneously serves runners looking to register and event organisers looking to list (the 'Create an Event' link sits in the main nav). Neither audience sees copy written for them. A short split message — 'Find your next race' for runners, 'List your event' for organisers — would immediately lift relevance.

The footer tagline 'Join the running revolution. Connect with fellow runners across India.' is the only platform-level claim on the page, and it appears at the very bottom. No runner count, no events listed, no cities covered — the revolution is asserted but never evidenced.

The Pet Run Virtual Challenge runs until October 2027; the Goa Marathon is January 2027. Without a 'Registration closes [date]' or 'X spots left' label on the card itself, there is no prompt to register now rather than later. Countdown timers or spot counters on high-value events like the 40th Pune International Marathon would directly increase conversion.

The 'Stay in the knowing' subscribe block asks for an email with no stated benefit beyond 'upcoming events and offers'. A specific hook — 'Be first to know when Goa Marathon 2027 early-bird pricing opens' — would meaningfully improve sign-up rates and grow a re-marketable audience.

The Results link goes to results.runindia.in/StartPage.aspx?CId=19898, which looks like a third-party timing system. Post-race, runners sharing their results will share that URL, not runindia.in — a missed retention and referral loop. Wrapping results in a branded page would bring finishers back to the platform.

The blog post 'Goa Marathon 2027 registration is ON' presumably links to the event, but the homepage shows the blog card with no inline 'Register Now' button. Blog readers are warm prospects; a direct CTA from editorial content to the registration page would shorten the funnel.

The homepage shows the same featured and trending events to every visitor regardless of location, past registrations, or browsing history. A logged-in runner in Nagpur should see Pulse Marathon 2026 prominently; a Pune-based user should see the International Marathon. Location-aware or history-based recommendations are table-stakes for a marketplace at this scale.

The platform implies a registration flow, but there is no indication of automated pre-race reminders, bib collection notifications, or post-race result alerts. These are high-value touchpoints that keep runners engaged with the platform between sign-up and race day, and they can be fully automated.

Runners searching for 'a half marathon in December near Pune under ₹1,500' currently have to browse the events list manually. A natural-language search or simple filter wizard ('distance / city / month / budget') would increase event page visits and reduce drop-off from the homepage.

The Charity section in the nav implies runners can donate or fundraise, but there is no automation visible — no fundraising progress bars, no automatic receipt emails mentioned, no charity leaderboard. Automating charity communications would increase both donation conversion and runner loyalty.

There are no statistics — number of events listed, registered runners, cities covered, or years operating. For a first-time visitor deciding whether to trust the platform with a ₹2,000 registration payment, these numbers are essential. Competitor platforms lead with figures like '50,000+ runners' or '500+ events'.

Several events are labelled 'This event is trending!' but with no supporting data — no view count, registration velocity, or comparison. Unsubstantiated urgency labels erode trust with savvy users rather than building it.

The 'Create an Event' flow is openly accessible, but there is no copy reassuring runners that listed events are verified or vetted. For an audience paying money to participate in physical events, a brief trust message ('All events are verified by the runINDIA team') would reduce hesitation.

The homepage markup contains three separate navigation structures (desktop nav, mobile nav, and a secondary menu) with partially overlapping links. If these render visibly on any device, they create confusion; even if CSS-hidden, they add page weight and may confuse screen readers and crawlers.

Clicking Results takes the user to a visually different third-party timing portal (the aspx URL structure suggests legacy software). There is no indication this will happen, and no easy way back to runindia.in. This breaks the experience at one of the highest-intent moments — when a runner wants to check their time and share it.

Blog posts link to blog.runindia.in rather than runindia.in/blogs. All backlinks and search authority earned by running content accrues to the subdomain, not the main domain. Consolidating to a subdirectory would concentrate SEO value and is a structural change worth prioritising.

Showing '₹400 – ₹1,100' (Rotary Belagavi) rather than explaining what determines the price — distance category, early-bird tier, t-shirt inclusion — leaves the runner uncertain about what they will actually pay. A single-line explainer ('5K from ₹400 · Half Marathon from ₹1,100') on the card would reduce abandoned registrations.

Serious runners enter multiple events per season. There is no 'save for later' or watchlist feature visible on the homepage, meaning a runner who finds the Goa Marathon and the Pune Marathon in the same session must navigate back and register separately with no memory of their interest. A simple saved-events list would increase multi-registration rates.

The event cards drive directly to registration, but nowhere on the homepage are accepted payment methods, refund policy links, or secure payment badges visible. The Purchase Policy exists but is footer-only. Given that many runners are first-time platform users, pre-empting payment anxiety at the point of discovery would reduce drop-off.