I Audited Notion's Blog for SEO — Here's What I Found

Notion is famous for obsessing over design. Every pixel matters. Their product is beautiful, their marketing is beautiful, and their blog — "Tools & Craft" — is no exception visually.

But what happens when you look under the hood at the meta tags?

I ran a free SEO audit on notion.so/blog and found not one, but two Open Graph bugs. Both live right now.

Bug #1: twitter:url Is a Relative Path

The twitter:url tag is supposed to specify the canonical URL that Twitter (now X) associates with a shared card. When it's set to /, the platform either ignores it or interprets it relative to the page — which means it points to the wrong URL entirely.

The correct value here should be https://www.notion.so/blog. A simple, absolute URL. Instead, it's a single slash.

Bug #2: og:url Points to the Homepage, Not the Blog

There's also a domain mismatch here. The blog lives on notion.so/blog, but the og:url points to notion.com/ — the main marketing homepage, not the blog.

This means when someone shares the Notion blog on Facebook or LinkedIn, the platform canonicalizes the share to the homepage. Blog engagement bleeds into homepage metrics. Attribution is muddled.

What's Actually Good

In fairness, the rest of Notion's blog meta holds up well:

• og:image: valid, absolute URL, proper image
• og:title / og:description: both present and reasonable
• twitter:card: summary_large_image — correct
• twitter:site: @NotionHQ — correct
• twitter:image: valid absolute URL

The fundamentals are there. These are precision bugs — the kind that slip through review because the tags are present, they validate, and they don't throw errors. You only catch them with a proper structured audit.

The Pattern

Three SaaS blogs audited in three days. Three different bugs:

• Buffer: og:image="undefined" — JavaScript variable rendered as a string
• Zapier: og:url="" — empty Open Graph canonical URL
• Notion: twitter:url="/" + og:url pointing to wrong domain

Every single one of these companies has SEO teams. Every single one has these bugs in production. The takeaway isn't that they're bad at SEO — it's that these issues are genuinely easy to miss without systematic checking.