Headless sounds bad. Why it’s good.
A headless CMS (content management system) is for all practical purposes a library for your content. Blog posts, page content, images, company testimonials, whatever content you want to store can all be modeled and saved in the headless CMS of your choice. How the headless CMS differs is that is has no presentation layer. No “preview this page” button. The content that you have stored in the headless CMS is access via an API (application program interface) call.
What's great about this set up is that your content can be sliced, diced, linked, and tagged in any way you want. You have complete freedom to design you own content models and internal structures. You also have complete freedom in how you want to present this content to your users.
CSR, SSR, SSG and more ancronyms than you need.
Just to level set here, there are a BUNCH of different ways that a developer can generate the HTML markup that is delivered to a users browser, all with varying degrees of impact on SEO scores. Here's the rundown of the different methods. If you find this all a bit too pedantic, jump to the next paragraph to get to the good stuff.
SSR - (Server Side Rendering) SSR is the bog standard website rendering technique. The web page is assembled on the server, via a complex dance of cookies, sessions, database calls and application logic. WordPress and other platforms all run on a SSR style stack. This is your SEO middle ground. The HTML on the pages is able to be crawled effectively, but ultimate performance will suffer due to the time it takes to assemble your pages.
The impact of SSG on SEO
The impact of SSG on SEO cannot be overstated. By rendering your pages before deployment to the server, and serving those pages with an aggressive caching policy, you can reach unheard of
levels of performance, and all with total control of the UI/UX. Since there is no round trip to the server, no database, and all of the business logic predetermined, there is really nothing to prevent your webpages for loading as fast as the network can manage. Here at Curious Minds, we are regularly seeing static site speeds in the top percentile.
How does a Headless CMS factor into SEO?
In a typical SSG site deployment strategy, The headless CMS is queried during the build process. This setup allows developers to assemble pages from any combination of content stored on the Headless CMS. The build process iterates over content collections, assembles pages, and can even assemble and submit a sitemap. When you need to update content, you would simply update the CMS and then run that build process once again.
How does this help me?
Next time you are looking to refresh your website, consider building a JamStack-powered web presence, to benefit from the SEO increase given by using SSG combined with a headless CMS. This is especially true if your website consists primarily of marketing content and contact forms. (Blogs work extremely well here too, but you need to have a site search strategy in place.)