Comments on: All copywriting should be from an SEO standpoint http://talkincblog.com/2009/07/all-copywriting-should-be-from-an-seo-standpoint/ Just another WordPress weblog Tue, 22 May 2012 04:31:34 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: facebook-40511955 http://talkincblog.com/2009/07/all-copywriting-should-be-from-an-seo-standpoint/comment-page-1/#comment-426 facebook-40511955 Thu, 23 Jul 2009 14:18:30 +0000 http://talkincblog.com/?p=2751#comment-426 Hey Thom, I appreciate the weigh in, and I think you make a good point.<br><br>Just to be clear (since you mentioned the social media press release), when I am talking about an SEO optimized release, I am speaking to both traditional releases and SMPR. That is, SEO should be in both your traditional releases AND your SMPRs.<br><br>To what you said about SMPR's, I agree that, in the current time, if someone is sending out an SMPR they ought to also distribute a traditional release that is touting the SMPR. But both releases should be SEO optimized. Hey Thom, I appreciate the weigh in, and I think you make a good point.

Just to be clear (since you mentioned the social media press release), when I am talking about an SEO optimized release, I am speaking to both traditional releases and SMPR. That is, SEO should be in both your traditional releases AND your SMPRs.

To what you said about SMPR's, I agree that, in the current time, if someone is sending out an SMPR they ought to also distribute a traditional release that is touting the SMPR. But both releases should be SEO optimized.

]]> By: Nathan Snell http://talkincblog.com/2009/07/all-copywriting-should-be-from-an-seo-standpoint/comment-page-1/#comment-190 Nathan Snell Thu, 23 Jul 2009 10:18:30 +0000 http://talkincblog.com/?p=2751#comment-190 Hey Thom, I appreciate the weigh in, and I think you make a good point.<br><br>Just to be clear (since you mentioned the social media press release), when I am talking about an SEO optimized release, I am speaking to both traditional releases and SMPR. That is, SEO should be in both your traditional releases AND your SMPRs.<br><br>To what you said about SMPR's, I agree that, in the current time, if someone is sending out an SMPR they ought to also distribute a traditional release that is touting the SMPR. But both releases should be SEO optimized. Hey Thom, I appreciate the weigh in, and I think you make a good point.

Just to be clear (since you mentioned the social media press release), when I am talking about an SEO optimized release, I am speaking to both traditional releases and SMPR. That is, SEO should be in both your traditional releases AND your SMPRs.

To what you said about SMPR's, I agree that, in the current time, if someone is sending out an SMPR they ought to also distribute a traditional release that is touting the SMPR. But both releases should be SEO optimized.

]]> By: ThomRansom http://talkincblog.com/2009/07/all-copywriting-should-be-from-an-seo-standpoint/comment-page-1/#comment-188 ThomRansom Wed, 22 Jul 2009 20:33:07 +0000 http://talkincblog.com/?p=2751#comment-188 Hey Nathan-<br>Picked your blog post off of Twitter and thought I might throw in.<br>It's been my impression that PR and marketing professionals should consider publishing two versions of copy: One SEO optimized and one content-rich, depending on the media they're targeting. Though media sources are changing preferences from traditional press releases to SMPR's, I wouldn't think you'd want to automatically exclude those that prefer the former. I'm sure it depends on the type of copy you're writing too. Hey Nathan-
Picked your blog post off of Twitter and thought I might throw in.
It's been my impression that PR and marketing professionals should consider publishing two versions of copy: One SEO optimized and one content-rich, depending on the media they're targeting. Though media sources are changing preferences from traditional press releases to SMPR's, I wouldn't think you'd want to automatically exclude those that prefer the former. I'm sure it depends on the type of copy you're writing too.

]]>