34% of My API Notifications Were Duplicates. The Fix Was One Line.
by•
I logged every indexing notification for 58 days. 551 total. 187 were for pages that had already been indexed weeks earlier.
My sitemap was regenerating on every deploy. The API kept seeing "new" URLs that hadn't changed. I gated the sitemap build behind a content hash check.
Notifications dropped to 12 the next week. The fix took four minutes. Finding it took two months of not looking.
What's the duplicate noise in your system that you've been treating as normal?
2 views
Replies
Mine was an attribution callback I treated as "new install" when it was really "app resumed". The SDK delivered the same deep link payload again on every resume and every launch, flagged as not the first launch, and my app took the login code inside it at face value each time. The code was already spent, so a signed in user got bounced through a "link expired" screen to the sign in page whenever they came back to the app. The fix was small: deliver the login code from that path on the first launch only, and have a signed in app ignore a code that is no longer valid. Finding who it hit was the slow part: one IP, one successful redeem, then a run of 404s, two per resume.