Week 10+11: PDF cluster, blog launch, 143 indexed, and a new compression feature
Combining two weeks into one update since week 10 was heads-down building.
What shipped
PDF cluster (week 10)
Launched 4 PDF conversion pages: pdf-to-jpg, pdf-to-png, pdf-to-webp, pdf-to-tiff. Multi-page PDFs export as a ZIP.
Backend handles it via libvips + pdftocairo for normalization. Took longer than expected.
Blog infrastructure (week 10)
Built a full blog from scratch: JSONB content structure in PostgreSQL, article components, JSON-LD schema. Published 3 posts targeting informational keywords: "What Are HEIC Files?", "How to Convert PDF to JPG", "AVIF vs WebP vs HEIC 2026".
Image compression (week 11)
Added JPG, PNG, WebP compression: same Rust/libvips backend, new /compress/jpg, /compress/png, /compress/webp landing pages. Uses imagequant for PNG (same engine as TinyPNG) and libjpeg for JPG. Real benchmarks: Q=80 gives ~40% savings on JPG, ~36% on PNG. Wrote a technical deep-dive on dev.to about the quality/size tradeoffs.
Numbers
Indexed pages: 75 -> 100 -> 143 (+68 in two weeks)
Impressions (3 months): 520 -> still growing
Blog post already appearing in GSC (what-are-heic-files)
The clicks problem
143 pages indexed, decent impressions, zero click momentum. Top pages by impressions:
- avif-to-png (86)
- avif-to-jpg (67)
- png-to-webp (61)
all sitting at positions 40–50. Need to break into top 20 for any of these to convert.
What's next
Internal linking blog converter (was P0 debt from T10, now done), Semrush on-page fixes for top-5 pages by impressions, and pushing the compression cluster. Longer term: RAW formats (CR2/NEF) for photographers, REST API for B2B.
Week 12 focus: getting at least one page into top 20.
Open to feedback, criticism, and ideas what would you focus on to break through the clicks plateau?
convertifyapp.net: Rust + libvips + Next.js SSG week 11 of 52
The technical progress is strong, especially the Rust/libvips backend, PDF cluster, compression pages, and the B2B API direction.
The click problem may not only be an SEO problem though. “Convertifyapp” explains the utility, but it also puts you in the same mental bucket as every other converter site. When users see positions 40 to 50, they are probably comparing dozens of nearly identical “convert X to Y” tools, so trust and memorability matter more than usual.
I’d think about the brand frame before you build too many more indexed pages around it. If this stays a simple converter library, the current name is fine. But if the longer-term direction is image/PDF infrastructure, compression, RAW formats, and a REST API for B2B users, the name should feel more like a serious file-processing platform than another SEO converter site.
Xevoa .com would fit that broader direction better. It keeps the product on your side: same fast conversion/compression engine, but with a cleaner platform name if you move beyond consumer landing pages into API, developer, and business use cases.
For week 12, I’d focus on getting one cluster to feel more trustworthy and differentiated, not just better internally linked.
Convertify don't sound how serious company or brand?