Reversing Bareksa's traffic decline through a Google Core Update

Bareksa had been experiencing a consistent decline in organic traffic entering 2021. The situation became more difficult as Google Core Updates hit in both June and July of that year. What made it complex: the updates weren't the root cause. Google's algorithm changes simply accelerated the impact of long-standing technical issues that had never been resolved. Conflicting canonicals, unindexed pages, inconsistent mobile vs. desktop serving, HTTPS failures on a YMYL platform. All of it had been quietly accumulating. The question wasn't "how do we recover from the update?" It was "what was already broken long before the update arrived?"

The consultation ran across three phases over nine months. Phase 1 (May–August 2021): the priority was stabilization. A comprehensive audit uncovered numerous fundamental technical issues: conflicting canonicals, different user-agent serving between Googlebot Desktop and Smartphone, missing or contextually wrong H1 tags, and HTTPS failures. Critical, because Bareksa falls under the YMYL (Your Money, Your Life) category that Google holds to its strictest standards. The most significant project in this phase was migrating Bareksapedia from a Single Page Application to a multi-page architecture with proper meta tags and Open Graph. A technical decision whose real impact would only be felt in the next phase. Phase 2 (August–November 2021): with the foundation stable, focus shifted to performance and content. The CSR to SSR migration was finally completed, the most critical pending item since client-side rendered pages often appear empty to Googlebot. In parallel, new product pages were optimized for visibility, and CTA A/B testing in articles began with dedicated tracking codes. Phase 3 (November 2021–February 2022): no longer about major fixes. The focus was maintaining achieved positions while pushing content toward more concrete business conversions.

In the first phase alone, organic impressions grew more than 13x and error pages dropped more than 85%. Organic traffic started moving even as technical fixes were still underway. The biggest momentum came from Bareksapedia. From near-zero organic visitors, it grew to tens of thousands of monthly visitors within six months. This wasn't just a new traffic source: Bareksapedia was designed as a direct conversion funnel, with CTAs into Bareksa's financial products embedded naturally within an investment glossary. By the end of the engagement, organic clicks had grown more than 50% compared to the start of the consultation, error pages were down to less than 3% of their original volume, and key product pages had established stable search rankings. Most importantly: when the engagement ended, Bareksa's internal team had the systems, standards, and understanding to continue independently.