Simplify user access management for your team with Enterprise Team Management. Get more details!

Guides & Tutorials

Improve your SEO and Social Sharing Cards with Next.js

Guides & Tutorials

Improve your SEO and Social Sharing Cards with Next.js

Look, we’ve all done it. We’ve shared a post of our latest blog or project to Twitter, or LinkedIn, or Slack, or something, and it ends up looking like a blurred mess on the timeline, or has a boring default thumbnail. We've taken a stroll over to check your Lighthouse score and find that SEO is in the red. We've thought about how our users will React to our apps, realizing they don't have the Context when they see our links in the feed. Heyo.

On the left, a generic, unhelpful link. On the right, a properly tagged site!

When you want something to look decent on a feed, you can use something called the Open Graph Protocol. It allows you to customize your <meta> tags on your site so that it looks nice and beautiful when you share the URLs around.

Here’s the problem though: if you want different metadata on different pages of your website, you have to go beyond the “single page application” route. As much as I love SPAs, they simply are more restricted when it comes to custom metadata per page.

But, there is a solution! With a static site builder, you can programmatically customize <meta> tags on every page. Let’s go through an example with Next.js.

Let’s say that you have a site with multiple pages (say, a blog post, perhaps?), and you have some Layout component that pulls in Next’s built-in next/head:

import Head from 'next/head'
import Header from './Header'

export default function Layout({ children, pageTitle, description, ...props }) {
  return (
        <meta name="viewport" content="width=device-width, initial-scale=1" />
        <meta charSet="utf-8" />
        <Header />
        <div className="content">{children}</div>

The <Head> component from Next appends elements into the <head> of your rendered HTML page. So, if I wanted to add a “description” tag for example, I could just stick it in right inside <Head>:

        <meta name="viewport" content="width=device-width, initial-scale=1" />
        <meta charSet="utf-8" />
 +       <meta name="description" content={description} />

Now, let’s add your custom Open Graph tags. Right now in your Layout component’s props, we have the pageTitle and description passed in. We can use that right away to add og:title and go:description tags.

        <meta name="viewport" content="width=device-width, initial-scale=1" />
        <meta charSet="utf-8" />
        <meta name="description" content={description}></meta>
 +       <meta property="og:title" content={pageTitle} key="ogtitle" />
+       <meta property="og:description" content={description} key="ogdesc" />

Note that we add some key props to these tags. This is to avoid duplicate tags, just in case!

Now, there are other Open Graph tags to add. This is where you can look at your page components that are rendering your Layout components, and pass in more information, like images, the preview URL, and the site name. Twitter also has some proprietary tags for their cards too, some of which have Open Graph fallbacks.

Here’s the tags that I try to always include in my projects!

{/* Twitter */}
<meta name="twitter:card" content="summary" key="twcard" />
<meta name="twitter:creator" content={twitterHandle} key="twhandle" />

{/* Open Graph */}
<meta property="og:url" content={currentURL} key="ogurl" />
<meta property="og:image" content={previewImage} key="ogimage" />
<meta property="og:site_name" content={siteName} key="ogsitename" />
<meta property="og:title" content={pageTitle} key="ogtitle" />
<meta property="og:description" content={description} key="ogdesc" />

If you’re curious about image sizes, there are many guides out there for this. Generally though:

  • The minimum size you should use is 200 x 200 pixels
  • Images smaller than 600 x 315 pixels will often be styled differently on Facebook and Twitter (it will be on the side of the link text, rather than big and in the middle of everything)
  • For most cards that appear on Twitter and Facebook, images that are 1200 x 630 pixels have the best display on high resolution

I hope this is helpful for you, and here’s a great list of resources for more information!

Useful resources

Keep an eye on this space. We'll have more posts on leveling up your SEO coming soon!

Keep reading

Recent posts

Book cover with the title Deliver web project 10 times faster with Jamstack enterprise

Deliver web projects 10× faster

Get the whitepaper