Software as a Service July 6, 2020

I want a blog attached to my website.

Bree @breedaddy

I want to attach a blog to while it is still being developed and after the MVP is launched.

Blogging is great for SEO but, this is a custom built platform.

Should I use Netlify or Wordpress API? What would help with SEO more?

  1. 4

    Have you looked at Ghost, which can be used standalone or as a (quite brilliant) headless CMS?

    1. 3

      +1 for Ghost!

  2. 1

    Have you tried ButterCMS? It's a headless CMS with a preconfigured blog engine and full CMS capabilities. It has support for dozens of new technologies so you can plug in a blog, page etc and be up and running in minutes.

  3. 1

    I use Hugo which is a static website generator and may have a plugin or workflow you can borrow to integrate with Netlify.

  4. 1

    Whats the content of your blog going to be?

  5. 1

    Hey! I'm building, which just launched on ProductHunt a few days back. The goal is to have the network the Medium provides, while giving you the same control/ownership something like Ghost would give you.

    You'll have a natural audience coming in from Imprint. The difference between this and Medium is that you own your content on Imprint. You can use a custom domain, theme your blog, and have a built in newsletter. And it's free! You can see if it works for you! Here's my sample blog for reference (

  6. 1

    I would go with headless CMS + static site generator Gatsby/Gridsome or 11ty.
    You can then host it on your own server or Nellify/Vercel.

  7. 1

    WordPress API —, maybe I'm biased :)

  8. 1

    Hey, try using any static site generator app from here

    This way you only need to host static files. Most of them use SEO best practices, although that doesn't mean you're gonna rank #1.

    If you have questions about how you use this you can schedule a call with me and I will try to help you out

  9. 1

    I like the landing page, clear & clean
    About the blog, you can check netlifyCMS, free and incredibly powerful for the speed

  10. 1

    I am not sure about your current stack, but currently looks like it could be running on top of a static page generator such as Jekyll.

    Personally I'm using Jekyll because of its simplicity. There is no server runtime required, nor extensive front-end coding. It's easy to add additional pieces of content, and because of that it's easy to gradually extend the website over time. I think this lack of complexity is something which will benefit you in these early stages.

    When it comes to SEO I don't really think it matters whether you're using WordPress or any other CMS. As far as I know Netlify is just a hosting platform, so it would depend on what you're planning on using there.

    1. 1

      Would I have to run it on a subdomain? Heard that isn't good for SEO.

      1. 1

        If you're using something like AWS, you could use a sub domain and point it to another instance containing the website.

      2. 1

        I suppose it depends how well it is integrated with the rest of the domain. Integration between different systems can be a pain.

        I'm currently dealing with a situation where a subdomain performs significantly better than the main domain, and which I'm trying to merge back together in a way that they both reap the SEO benefits. When systems flawlessly integrate between one another there shouldn't be too many problems.

  11. 1

    Many, include me are running away form WordPress because of security issues and time you will waste by maintaining plugins update.
    So I think you should go for netlify.

    1. 1

      Hearing a lot of good things about Netlify.

      1. 1

        It because of their free tier . You can host personal projects there.