Does smart content in blog pages causes confusion for RSS subscribers and can be harmful to SEO?
SOLVE
Hi All,
Would like to ask, is it true that using smart content in blog pages will give confusion for RSS subscribers and can be harmful to SEO? If yes, could you elaborate the reasons.
Does smart content in blog pages causes confusion for RSS subscribers and can be harmful to SEO?
SOLVE
Thanks for the tag @jennysowyrda ... we do have input regarding blog posts and smart content.
Completely agree, "Using smart content in a blog post is not best practice, as each blog post should answer a question for one particular audience. Smart content in your blog may be misleading to RSS readers and may harm your SEO.".
That being said, there are ways to DEFAULT smart content so that Google only sees the most desirable (generic) content for that post. (important) That way, you can still get hyper-specific for certain audiences based on smart content rules without sacrificing SEO value.
An example use case might be where you'd like to make 'smart' links to certain case study examples referred to in a blog post. In such an example use case you'd want to maybe make your links specific based on the industry stored in HubSpot for the reader. That way, readers from manufacturing are referred to manufacturing case studies while readers from professional services are referred to professional services case studies.
It should be noted that this degree of 'personalization' is typically only leveraged on blogs that have high volume traffic. And then only sparingly -- i.e., when posting general topics that apply to more than one large audience segment. The very nature of high traffic blogs is such that they have a large enough audience to warrant a separate blog post for each segment/persona as it were.
It's simply more often easier to just say something like ...
-- Manufacturing Case Studies
-- Professional Services Case Studies
Smart content for the sake of smart content is rarely a good solution to any problem.
Just a few thoughts. Hope they help.
Help answer your question? If so, remember to accept this solution now.
As HubSpot outlines hereUsing smart content in a blog post is not best practice, as each blog post should answer a question for one particular audience. Smart content in your blog may be misleading to RSS readers and may harm your SEO.
Does smart content in blog pages causes confusion for RSS subscribers and can be harmful to SEO?
SOLVE
Thanks for the tag @jennysowyrda ... we do have input regarding blog posts and smart content.
Completely agree, "Using smart content in a blog post is not best practice, as each blog post should answer a question for one particular audience. Smart content in your blog may be misleading to RSS readers and may harm your SEO.".
That being said, there are ways to DEFAULT smart content so that Google only sees the most desirable (generic) content for that post. (important) That way, you can still get hyper-specific for certain audiences based on smart content rules without sacrificing SEO value.
An example use case might be where you'd like to make 'smart' links to certain case study examples referred to in a blog post. In such an example use case you'd want to maybe make your links specific based on the industry stored in HubSpot for the reader. That way, readers from manufacturing are referred to manufacturing case studies while readers from professional services are referred to professional services case studies.
It should be noted that this degree of 'personalization' is typically only leveraged on blogs that have high volume traffic. And then only sparingly -- i.e., when posting general topics that apply to more than one large audience segment. The very nature of high traffic blogs is such that they have a large enough audience to warrant a separate blog post for each segment/persona as it were.
It's simply more often easier to just say something like ...
-- Manufacturing Case Studies
-- Professional Services Case Studies
Smart content for the sake of smart content is rarely a good solution to any problem.
Just a few thoughts. Hope they help.
Help answer your question? If so, remember to accept this solution now.