After fixing the indexing issues on ZiviTV and rebuilding it cleanly, I wanted to apply what I learned to a domain I touch every day: cloud infrastructure and web hosting. That became HostSage.
Architecture and Stack
The site runs on Next.js, with guides written in MDX so content lives directly in the git repository alongside the application code. No external CMS to configure or synchronize.
I started from an existing magazine template and refactored it:
- Reduced a multi-author demo schema to a single-author workflow with structured metadata.
- Designed the brand identity, wordmark, and vector icons in Figma from scratch instead of tracing raster artwork.
- Stripped unused sections like audio podcasts and refactored the homepage grid around real server categories.
Finding Gaps in Search Data
Most hosting review sites run on autopilot. They generate programmatic pages for every city or provider, swap a few keywords into an identical template, and call it a day.
HostSage starts with search volume, keyword difficulty, and search intent from Search Console and Ahrefs. I look for queries where top-ranking pages are obviously thin.
A clear example: searching for "Atlanta VPS hosting" pulls up dozens of provider pages claiming local presence. Almost none mention that most independent Atlanta VPS hosts colocate inside the same telecom facility downtown. That specific physical reality is what an engineer evaluating latency actually wants to know. Writing to answer real technical questions beats competing against generic affiliate lists.
Operating from Firsthand Experience
Because I configure DNS records, cloud firewalls, and server environments regularly, the articles come directly from terminal sessions and production setups.
HostSage is live at hostsage.dev. I am adding new technical guides every week, sticking to verified setups and clean search indexing.