Prismic.io CMS and SEO?

[ArcherMalmo]

Looking for community feedback:

Some of our In house developers want to use Prismic.io over Wordpress for it's alleged ease of organizing and "deploying" content. It's essentially a repository for content from which you make API calls to. It's a rather new platform. There a few posts in Quora around SEO but looking to see if anyone has had experience with platform.

My concern is around  page load times, excessive server requests, and content viewed as code.

Any thoughts/ experiences would be much appreciated!

[KaneJamison]

Another couple notes:

URLs are ugly on their demo site at http://lesbonneschoses.prismic.me/blog/

• Example post: http://lesbonneschoses.prismic.me/blog/UlfoxUnM0wkXYXbi/one-day-in-the-life-of-a-les-bonnes-choses-pastry (Post ID subfolder needs to go)
• Example category: http://lesbonneschoses.prismic.me/blog?category=Announcements (would prefer to see these parameters as subfolders like /blog/category/announcements/ and also keep them lower-cased.)

Looks like the /UlfoxUnM0wkXYXbi/ subfolder can be removed - see "Link Resolver" on this page https://developers.prismic.io/documentation/developers-manual.

Here's some of their notes on caching: https://developers.prismic.io/documentation/developers-manual#cache.

[KaneJamison]

I have not used it, but here are my early thoughts:

Seems valuable if you're trying to roll out a Create Once Publish Everwhere (COPE) platform, which means you'd be publishing to not just a blog, but mobile apps, syndicated sources, etc. However, that's a rare need for the average company blog.

Other than that, it looks like they're essentially offering the Wordpress admin/editor and the Wordpress database as a cloud service, and letting your devs call the database from the front end of the site.

So the biggest question that poses in my mind is how the content can be cached on your site. Once it's cached, load time shouldn't be any different from the rest of your website, since you're not calling a database, and you're serving any static files from your own CDN, and there shouldn't be any additional HTTP requests.

If they allow for easy caching like that, then the rest of the SEO is on your developers' shoulders to format correctly on the front end of the site, and to handle things like canonicalization properly.