Side project indexation sample before 800-page publish
Publish and monitor a small indexation sample before sending hundreds of similar programmatic pages at a new domain.
Why this can grow a startup
The painful lesson from the side-project thread is that publishing is not the same as ranking, or even indexing. The founder shipped roughly 800 location-style pages with unique data, internal links, a clean template, and an XML sitemap, then found that most pages were stuck in “discovered” or “crawled” but not indexed. That makes a strong case for a smaller sampling loop: publish a cohort, watch Search Console buckets, improve internal links and unique sections, then scale the pages that Google is willing to keep. It saves weeks of guessing on a new domain.
Source-backed example
A nights-and-weekends side-project founder described shipping roughly 800 location-style pages, then rebuilding navigation, resubmitting sitemaps, testing submissions, and learning that indexation had to be treated as an operational loop.
Source-reported evidence
Source: Reddit r/SideProject: 800 SEO pages indexation thread
The founder reported about 120 indexed pages after a month, later rising to roughly 530 indexed pages after monitoring and submission workflows.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when SEO, Technical SEO, Programmatic SEO is relevant to indexation, search console, new domain SEO and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to SEO and Technical SEO, using evidence from Reddit r/SideProject: 800 SEO pages indexation thread as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.