Search Analytics
Track how users discover your project
Top Search Queries from Google
No Google Search data for this project yet.
When players find this project through Google, their top search queries will appear here.
Traffic Sources
No Search Traffic Yet.
Tips: improve title with keywords, add an eye-catching thumbnail, share on social media/communities
1. Short-form video (TikTok, YouTube Shorts, Reels) - Record a 15-30 second clip showing the most satisfying moment of your project. Post natively to each platform, don't cross-post with watermarks. Tag #pixelpad #indiedev #webdev #coding. Algorithms don't care about follower count, a single clip can reach tens of thousands organically.
2. Discord servers - Join coding, indie dev, and genre-specific Discord servers. Share in #showcase and #feedback channels, and genuinely play and comment on other people's projects. The more servers you're in, the more eyeballs on your project.
3. Publish on itch.io - List your project on itch.io with a strong cover image, 3+ screenshots, a GIF, a clear description, and relevant tags. itch.io's browse and search is a passive traffic source that compounds over time. Your project stays listed permanently and can be discovered months or years later.
4. itch.io jams - Submit to active jams that fit your project. Jam players are specifically looking for new projects to rate, and top-rated entries get featured on itch.io's front page. The largest jams have thousands of participants actively playing and rating submissions.
5. Reddit - Post to subreddits that fit: r/SideProject, r/InternetIsBeautiful, r/coolgithubprojects, r/webdev, r/learnprogramming, r/Python, whatever matches your project. Read each sub's rules, one post per sub. A single well-received post can drive thousands of visits in a day.
Google generates search snippets automatically, primarily from your page content. If your opener does not make sense by itself, people will not click.
Structure: First line: what it is. Second line: goal + controls + what makes it unique.
Example: "Play a Chrome dino runner where you jump cacti and dodge birds to beat your high score. Controls: Space or Up Arrow. Play in your browser with no download."
Contains the search term "chrome dino runner" naturally. Mentions "browser" and "no download" (common query terms). Clear controls reduce confusion so players actually start playing instead of leaving immediately.
Put controls in your description. Say what happens when you press each key. Include the goal so players know what they're trying to do.
People search "how to play [name]" constantly. Clear controls also mean players actually start playing instead of leaving confused.
How to do this: Type your project concept into Google (example: "dino runner"). Look at the dropdown suggestions. Pick ONE that perfectly matches your project.
Seed: "pixelpad project"
Autocomplete shows: "chrome dino runner", "dino runner online", "dino runner"
Apply: Pick "chrome dino runner" and use those words naturally in your title and first sentence.
Autocomplete shows common query patterns people use. Using the phrase helps you match how people search, but do not force awkward repetition.
How to find search words: Type your project idea into Google and look at the autocomplete suggestions. Those are common query patterns. Also scroll to the bottom of the search results and check "Related searches."
Title pattern: [what it is] + [core mechanic] + [platform]. Skip usernames, internal IDs, and version numbers.
Search engines match titles to queries. If someone searches "dino runner," the second title is more likely to match than the first.
The formula: [primary search term] + [goal] + [controls] + [platform] in ONE sentence.
Example: "Play a chrome dino runner (search term) where you jump cacti to beat your high score (goal). Controls: Space or Up Arrow (controls). Play free in your browser (platform)."
search engines generate snippets automatically from page content, and may also use your meta description when it describes the page well. This opener answers: What is it? How do I play? Where can I play it? Do I need to download anything? One sentence = one complete answer = higher click rate.
Add 3 to 5 short Q and A pairs at the end of your description. Write the questions exactly how people search online.
Example FAQ:
"How do you play the chrome dino runner?" Press Space to jump over obstacles.
"What are the controls?" Space or Up Arrow to jump.
"Can I play on mobile?" Yes, tap the screen to jump.
People search in questions: "how to play dino runner", "can I play on mobile." Search engines can use clear Q and A text when generating snippets, and each question is a separate search term you can match. If you add FAQ structured data, do not expect FAQ rich results for most sites, because search engines limit that feature.
Add a short "Also known as:" line at the end of your description with 3 specific variant phrases. These should be different ways people might search for the same project.
Example: "Also known as: pixel art dino runner, one-button dino jumper, dino runner for kids"
Your main title targets one phrase. This line targets 3 more without making your title messy. Google indexes all these terms and can show your project for any of them. Think: different age groups ("for kids"), art styles ("pixel art"), or mechanics ("one-button").
The process: Write 2 different titles. Run title A until you have enough views to compare, then run title B until you have enough views to compare. Keep whichever has a higher play rate (plays ÷ views).
Example: Title A: 500 views, 120 plays = 24%
Title B: 520 views, 160 plays = 30.8% ← Keep this one
The play rate tells you which title makes people actually click and play. Higher play rate = better match between the promise (title and opener) and what players get when they click. Don't guess - test. Two rounds of testing beats months of hoping you picked the right title.
