You are viewing a single comment's thread from:
RE: Do you have a WordPress blog and you wanted to post those here in Steem to monetize?
Another reason to consider the option for only posting to Steemit and reading the feeds instead of having a WP db for posts :)
As for that, I'm thinking of co-existing both mediums. As for the feeds, there's already a plan to integrate it on the plugin on WordPress Steem to display your posts, comments, or from other users or specific tags in the next version of the plugin. :)
Having posts published on two websites could possibly end up having the website penalized by search engines.
Hello @moataz, I see. What can you recommend to avoid this? Thanks! Greatly appreciate your input.
Hey mate,
Well that's a tricky question.
But to my best knowledge I believe that since the posts will be published on the blockchain - they also should be retrieved directly from the blockchain; if there's an option to either post on the blockchain only or have a version saved locally on the database as well; that'd be ideal.
So if there's some way to display posts individually through identifiers from the blockchain or have some invisible iframe from steemit; that'd be best.
In a perfect scenario there'd be the option to post comments / upvote / downvote or flag through the blockchain.
Hello mate,
Thanks for that thorough explanation. Yeah, that makes sense. I'm still thinking though about users who have older WordPress posts and they want to post it on the Steem blockchain.
That too will create dupe content which is hated by search engines
Then the website owner will have to decide which traffic is more important:
As more Steem UIs get built, the search engines with have to adapt to the notion of a shared database of content, unless they don't want to encourage other monetization options for the existing Google AdSense etc.
Well I believe that in a perfect world we would have the WP blogs working as a publishing medium + referral tool. Remember that some of these blogs could already have frequent visitors, or search engine traffic, so keeping that in mind it's necessary to avoid any kind of penalties that could be triggered by using this plugin.
I haven't checked the amount of traffic Steemit.com receives, but a handful of powerful blogs could well bring in the same amount of visitors, maybe even a couple.
It's up to the search engines to adapt, and I wouldn't bet on it - Google is fast with updates, they are pretty good at improving their algorithm but I still wouldn't rely on that. For the time being, and until they actually start noticing this new type of database; we should just avoid any conflicts with search engines.
That's just my opinion of course.
Old posts will attract @cheetah unless there is a way to let the bot know that the content is being republished by the original publisher.
As for new posts, how does the bot recognize other Steem UIs so that a post using WordPress Steem does not get flagged for also appearing on the WordPress website?
I added a "canonical" attribute to "json_metadata" attribute to Steem post where I store the WordPress post permalink. That may be be able to help the BOT be able not to flag the Steem post.
@cheetah will eventually have to have site verification as an option where the publishing Steem account is mentioned on the canonical website.