The latest articles on DEV Community by Yoon Hun Kang (@yoon_hunkang_2404b136406). https://dev.to/yoon_hunkang_2404b136406 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4038814%2F0c28ba96-7faa-42a4-9955-4768ff030716.png https://dev.to/yoon_hunkang_2404b136406 en Yoon Hun Kang Mon, 20 Jul 2026 20:42:34 +0000 https://dev.to/yoon_hunkang_2404b136406/i-spent-2-days-debugging-why-google-wouldnt-index-my-new-saas-the-bug-was-in-my-own-canonical-161h https://dev.to/yoon_hunkang_2404b136406/i-spent-2-days-debugging-why-google-wouldnt-index-my-new-saas-the-bug-was-in-my-own-canonical-161h <p>Launched a new site two days ago and Google Search Console showed <br> zero indexing. Spent longer than I'd like to admit assuming it was <br> just "new domain, be patient" — until I actually checked the live HTML.</p> <h2> The bug </h2> <p>My server correctly redirects <code>uxtion.ai</code> → <code>www.uxtion.ai</code> (301/308). <br> Standard setup. But every canonical tag on the page — and the JSON-LD <br> schema, and the sitemap — still pointed back to the non-www version.</p> <p>So Google was getting two contradicting signals on the same page:</p> <ul> <li>"The real URL is www" (from the redirect)</li> <li>"No wait, the real URL is non-www" (from the canonical tag)</li> </ul> <p>Classic case of shipping the redirect and forgetting the metadata <br> has to agree with it.</p> <h2> The fix </h2> <p>Pulled every hardcoded domain reference into a single shared constant <br> tied to the actual production env var, instead of a string typed out <br> in six different files. Once that shipped and the sitemap re-read <br> correctly, the homepage went from "not indexed" to "URL is on Google" <br> within a few days.</p> <h2> Why I'm writing this </h2> <p>I'm building <a href="https://uxtion.ai" rel="noopener noreferrer">UXtion</a> — a tool that audits Lovable <br> and Cursor-built sites and hands back paste-ready fixes instead of <br> another report to interpret. Ironically, this bug was in my own <br> marketing site, not a customer's. Turns out "diagnose the problem vs. <br> actually fix it" applies to your own infrastructure too.</p> <p>If you're running a Next.js App Router site with a www/apex split, <br> worth checking <code>alternates.canonical</code> and any JSON-LD <code>@id</code>/<code>url</code> <br> fields aren't hardcoded to the wrong domain — <code>tsc</code> and your test <br> suite won't catch this, only a live view-source will.</p> seo nextjs webdev saas