The voting board nobody else bothers to index

The web page problem

Most feature voting tools treat the public board like a second thought. You build it because customers expect it, but it lives in a modal, behind a login, or nested three clicks deep. The URLs don't persist. Search engines shrug. If someone types 'dark mode feature request [your app]' into Google, they get noise instead of your own roadmap.

We kept hearing the same frustration from studios. Users were jumping through hoops to find feature updates. Some studios had resorted to Reddit threads and Twitter polls just because they ranked better than their own tool's voting board. There's an absurdity in that.

The thing is, a public voting board is valuable content. It's real feedback from real users. It answers the question 'what are people asking for?' Better than marketing copy ever could. Google wants to rank that. We just needed to make it rankable.

Building for search, not just screenshots

When we designed the voting board for Shpd, we didn't start with design mockups. We asked: what would make this page useful to someone finding it via Google six months from now?

Each feature request gets its own URL. Stable. Permanent. The page title reflects what the feature actually is. The description pulls from the feature and early comments, so search engines see real content, not a placeholder. We made sure the comment threads render properly so Google crawls the whole conversation, not just the feature headline.

No JavaScript loading tricks. No modals that hide the content. The board itself is just HTML and links that work. A founder can embed it on their own domain if they want to. It breathes with the rest of the web.

The result is that when a user searches for what they want, they often find the exact request in your app's voting board. They can see who else is asking for it, what the team's said, and when it might ship. It's the conversation they were looking for. And now they're on your page, not someone else's.

Why this matters for studios

Every search result is a conversation starter. When someone lands on your voting board because they Googled a feature idea, they're already invested. They're not cold. They're not a prospect yet. They're a user who cares enough to ask for something specific.

From there, they can vote. Comment. See what else people are asking for. Download your app if they haven't already. Invite friends if the feature resonates. The voting board becomes a discovery engine for your own community.

We also noticed studios started using their voting board differently. Instead of treating it as a dusty archive of requests, they treated it like public documentation. Teams would link to specific features in support replies. Product managers would post updates directly in comments. The board became the source of truth, not a side project.

For studios running multiple apps, this compounds. A parent company with ten iOS and Android apps can see, across the voting board, which features matter most to their user base. Which audiences overlap. Which apps need attention. Public doesn't just mean 'users can see it.' It means the signal becomes real data you can use.

The cross-app angle

There's another reason SEO matters more for studios with multiple apps. When you run 5, 10, or 20 apps, your users are often the same people, just in different contexts. A user who votes on 'better export options' in one app might also want it in another. The cross-app voter identity we built into Shpd (we call it Passport) lets that user be recognized across every app in your portfolio with a single login.

But for that to work, the boards need to be discoverable. If a user searches for a feature and finds the board for App A, they see voting from App B and App C too. They realise they're part of a bigger community. They're more likely to stay, to vote on other apps, to come back.

SEO isn't just about ranking. It's about breaking the isolation between your apps. It's about making the user's request feel like it matters at scale, not just to one team.

A simple decision with long tail returns

Indexing the voting board didn't require a rewrite. It required thinking about fundamentals. Permanent URLs. Descriptive titles. Real HTML content. Clean navigation. The things that made the web work before SPAs, and the things that still matter.

Studios who've been with us since launch have noticed the effect quietly. Over months, their voting board traffic grows. Not from ads. Not from campaigns. From search. From users who were looking for something specific and found it.

One studio told us they cut support email volume by 15% because users were finding answers in the public voting board instead of emailing. Another said onboarding improved because new users could see the roadmap before they decided whether to download. Neither metric was our goal when we built the feature. Both matter.

The studios most interested in this are the ones who've just left Canny, especially after their December 2025 pricing changes. They're looking for a tool that treats users like they deserve to be found, not hidden behind a paywall or a login form. They're looking for the voting board to be the centrepiece, not the afterthought.