Feed Stack and Poster Stack

Hello

Feed Stack and Poser Stack pull data into a template, which I understand.

In my example, the content is recipes and cooking how-to information.

Will this approach negatively impact SEO on a page-by-page because the content being displayed is part of the template and not a static page?

The template content is continuously changing/updating as the visitor changes pages to view different content within a website.

Lastly, recipe schema markup is in portent; where do I my add recipe schema markup for each recipe when using the Feed Stack and Poser Stack so that each recipe has its schema markup, maxiuizing SEO for each recipe?

What’s the best practise for SEO:

  1. Bulding stack pages for each recipe?
  2. Using Feed Stack
  3. Using Poster2 (side note what’s the ETA of Poster3)

Your insight is greatly appreciated.

Successor will be Volt CMS 2 (end of this year) 👍

Jannis I woild appercate your thoughts on the following.

Feed Stack and Poser Stack pull data into a template, which I understand.

In my example, the content is recipes and cooking how-to information.

Will this approach negatively impact SEO on a page-by-page because the content being displayed is part of the template and not a static page?

The template content is continuously changing/updating as the visitor changes pages to view different content within a website.

Lastly, recipe schema markup is in portent; where do I my add recipe schema markup for each recipe when using the Feed Stack and Poser Stack so that each recipe has its schema markup, maxiuizing SEO for each recipe?

What’s the best practise for SEO:

  1. Bulding stack pages for each recipe?
  2. Using Feed Stack
  3. Using Poster2

Google knows nothing about how a page is built. As long as your URLs are unique and your SEO meta tags are good, it will not matter at all.

My SEO Helper stack has a lot of schemas. However, recipe is one that I have not added yet because it’s quite complex. It is on my todo list for the next major release though. As for where you put it. Anywhere on the page should suffice.

No. Every displayed content has a unique URL.

There is no support therefore.