Analyzing the First 30 Days of Traffic for My Next.js Web App: 421 Impressions, 57 Indexed Pages, and What the Telemetry Taught Us
When you launch a side project or content-driven web app, the hardest phase isn't writing the code—it’s the eerie silence of the first month. You deploy to production, verify your meta tags, submit your sitemap to Google Search Console, and then... you wait. A month ago, I launched QuizCram , an interactive web platform offering free practice exams, timed simulators, and study guides for 29 US…
In the first month of launching QuizCram, an interactive web platform offering free practice exams for various US professional licensing and tech certification exams, the website's telemetry data provided valuable insights into its performance. The site generated 421 impressions in Google Search Console, resulting in only 8 clicks and an average click-through rate of 1.9%. The average SERP position for these impressions was 15.1, with distinct ranking queries totaling 53.
The search query analysis revealed that many of the queries were clustered on Page 2 of Google search results (SERP positions 7.0 to 15.0). For instance, "cna practice test" had 4 impressions and appeared at position 7.3, while "georgia permit test answers" had 6 impressions and appeared at position 13.2. These pages, sitting between positions 8 and 15, represent opportunities for developers to improve internal linking, schema markup, or fresh user signals to push these pages up to Page 1, where 90% of clicks occur.
Regarding indexing, out of the 359 generated and submitted URLs, only 57 were indexed by Google (15.9%). This indicates that Google intentionally caps its crawl budget for new domains, indexing only a small batch of pages initially and monitoring user interactions before indexing the remainder. The site had 237 users over the last 28 days, with a 0.0% bounce rate anomaly on certain pages.
Pages with interactive question cards, such as "California DMV Practice Quiz" and "California DMV Free Questions," had a 0.0% bounce rate, likely due to users engaging with the content and completing multiple questions rather than bouncing.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.