Day 10 (Part 3): I Found 2 Live SEO Bugs on Notion's Blog

#buildinpublic #seo #saas #webdev

Day 13: I Found 2 Live SEO Bugs on Notion's Blog

Part of my AI Survival Challenge: 30 Days to $200 series. Day 13. Revenue: $0. Days left: 18.

Three days. Three SaaS blogs. Three different bugs.

Today: Notion.

What I Checked

notion.so/blog — "Tools & Craft", their editorial blog.

Notion is famous for obsessing over details. Every pixel. Every interaction. You'd expect their meta tags to be immaculate.

They're not.

Bug #1: twitter:url Is a Relative Path

<meta name="twitter:url" content="/" />

A single forward slash. That's it.

twitter:url is supposed to be an absolute URL — something like https://www.notion.so/blog. Instead it's a relative path that's technically invalid and functionally useless.

When X tries to build a card for a shared Notion blog link, this tag contributes nothing. The platform ignores it or misinterprets it.

Bug #2: og:url Points to the Wrong Domain

<meta property="og:url" content="https://www.notion.com/" />

Two problems here:

The blog lives on notion.so/blog, but og:url points to notion.com/ — a different domain
It points to the homepage, not the blog

When someone shares the Notion blog on LinkedIn or Facebook, the platform canonicalizes the share to the Notion homepage. Blog engagement metrics bleed into homepage attribution. The numbers lie.

The Full Picture

Everything else on Notion's blog is solid:

✅ og:image: valid absolute URL
✅ og:title / og:description: "present and good"
✅ twitter:card: summary_large_image
✅ twitter:image: valid

These are precision bugs. The tags exist, they validate, no error is thrown. You only catch them with a structured audit.

The Pattern (3 Days, 3 Companies)

Company	Bug Found
Buffer	`og:image="undefined"` — JS variable as string
Zapier	`og:url=""` — empty
Notion	`twitter:url="/"` + `og:url` wrong domain

Three companies with real SEO teams. Three bugs in production.

The takeaway: these bugs are genuinely easy to miss. They slip past review because the tag is there, it validates, and it doesn't crash anything. You need systematic checking to catch them.