Observed Signal · Aug 20, 2026 · Technical Release · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Building Convertify Week 20 — Extended Existing Post Instead
Serhii Kalyna published a Week 20 update on building Convertify (Aug 20, 2026). Instead of creating a new landing page targeting a competitive keyword cluster (AVIF vs WebP vs HEIC 2026), he extended an existing post—adding sections, FAQs, schema_faq, and internal links—to avoid cannibalization and concentrate authority. He describes a transactional, append-only SQL pattern (BEGIN/UPDATE/SELECT/COMMIT with rollback on bad state) used to extend content safely. He investigated a recurring 30 MB PNG concern and concluded large PNG outputs for full-resolution photos are expected, offering a WebP toggle for users who want smaller files. Search signals show impressions rising (GSC impressions up 77% WoW; baseline impressions and position changes noted) and Bing showing 942 impressions with 1.49% CTR. Next steps include a YouTube demo and a Qwoted pitch.
Practical SEO/content strategy, operational SQL pattern, and product decisions (image output formats) offer actionable technical guidance for web publishers and product teams, but the update is not industry-shifting.
MARKET SIGNALS
Track Forem Signals & Strategic Shifts
Polaris7 connects regulatory filings, primary sources, leadership changes, and M&A activity into structured intelligence. Set up your Polaris7 workspace to monitor relevant companies in your executive briefing.
- Verified primary sources
- Automated briefings
- Instant watchlist setup
Key Takeaways & Evidence Grounding
- Serhii Kalyna published the Week 20 Convertify update on 2026-08-20.
- Author extended an existing blog post (adding sections, FAQs, schema_faq, and internal links) rather than publishing a new landing page to avoid SEO cannibalization.
- Uses an append-only transactional SQL pattern (BEGIN; UPDATE ... || jsonb_build_object/array; SELECT verification; COMMIT) to add content and roll back if needed.
- Investigated and closed the recurring '30 MB PNG' issue as expected behavior for full-resolution images and previously shipped a WebP output toggle for smaller files.
- Reported Google Search Console: 3-month rolling avg pos 52, recent baseline pos 42, impressions up 77% week-over-week; Bing: 942 impressions, CTR 1.49%.
Connected Companies & Entities
“Built on Forem - the open source software that powers DEV and other inclusive communities.”
“DEV Community - A space to discuss and keep up software development and manage your software career”
“Powered by Algolia”
“Week 19: Cloudflare Email Routing, Wikidata citations, and the benchmark that keeps citing itself”
“GSC 3-month rolling: avg pos 52. Last two days baseline: 787 impressions, pos 42.”
“Bing meanwhile: 942 impressions, CTR 1.49 percent.”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Convertify: 0 to 30 Indexed Pages in 3 Weeks
A solo developer documenting the SEO and technical changes behind Convertify, a free image-conversion site, describes how the site moved from zero indexed pages to 30 in three weeks. Key changes included migrating from a Vite React SPA to Next.js App Router with Static Site Generation (186 static pages), adding FAQPage and HowTo JSON-LD schema across pages, expanding each landing page from ~500 to 5,000–7,000 characters, and implementing an internal related-pages linking component to create crawlable clusters. The author also added an About page with Person and WebSite schema for E-E-A-T signals. Early results: indexed pages 0→30, GSC impressions 0→160, unique queries 0→45, and mobile PageSpeed 100/100. The write-up notes weak backlinks and removed Reddit posts as remaining obstacles.
Case study: Google indexes 72 pages in 2 months
Serhii Kalyna published a first-person case study (May 8, 2026) describing early SEO and indexing behavior observed for Convertify, a new site built with Rust + Next.js. At ~2 months the site had 72 indexed pages, ~90 impressions/day, an average position of 40.8 and essentially 1 click. Key interventions that produced measurable early changes were migrating from a client-side SPA to Next.js static site generation (SSG), adding dense internal linking, and applying FAQPage JSON-LD schema. The author outlines an observed timeline for new-site behavior (initial crawl, low-volume query testing, then gradual stabilization over 2–12 months) and reports that short-term backlink efforts had little effect.
Programmatic SEO Case Study: Bing Outperforms Google 2.6×
A developer launched a 200+ page programmatic SEO site on a new .in domain using a static Next.js export deployed to Cloudflare Pages. Over ten weeks the site’s Bing traffic grew faster than Google’s, with Bing sending 2.6× more clicks than Google by week ten. The site uses a JSON-driven taxonomy and a single universal calculator engine to generate plan-specific pages and calculators. The author reports three lessons: Bing appears to reward structured data and has no prolonged sandbox, AI-generated “overviews” (search summaries) suppress clicks to explainer content, and initial organic citations (dofollow links) start the authority flywheel. Monetization remains delayed due to ad-network approvals for new domains with templated pages.
WATCHLIST & BRIEFINGS
Receive future signals for Forem & competitors in your briefing
Stay ahead of material M&A deals, leadership changes, account wins, and product rollouts. Polaris7 connects primary filings, company newsrooms, and trade reporting directly into your executive briefing.
- Regular primary-source checks
- Structured Watchlist briefings
- Preserves current context
Market Signal Monitoring
Follow affected companies in Polaris7 with regular source checks and structured Watchlist briefings.
Monitor Forem
Follow affected companies in Polaris7 with regular source checks and structured Watchlist briefings.
