API and SEO
norio - August 22, 2008 - 10:17
| Project: | Disqus |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Are there any plans to use the API (instead of the generic JavaScript integration) for the Drupal module?

#1
Course! Going to have to get over the "coming soon" hump though...
#2
Well I'd be happy to slap something together which you could then tweak? I have some spare time and it'd be great to have indexable comments on my site.
Let me know
#3
You'd have to de-construct the Wordpress plugin that they put together to decipher their API. Might be worth it to just wait...
#4
That's pretty much what I was thinking of doing :P
But, yeah, waiting sounds like a good plan too!
#5
Any news on this?
#6
Just to add a data point re: switching to an API version...
I've seen some talk that Disqus has some negative implications for SEO.
There seem to be at least two problems:
1) If you're using the embed Javascript version of Disqus, your comments are NOT indexed on your site, but are indexed on Disqus.com
2) If you use an API plugin that handles things right, then your comments are indexed on both your site and Disqus.com (I believe), putting you at risk of taking "duplicate content" damage.
I'm no SEO expert, so I'm not sure if all of the incoming links from Disqus offer any benefits to offset these problems. Regardless, problem #2 is still better than problem #1, so I'm very much looking forward to an API version...
Thanks for the great module, Rob!
#7
I'm not certain that duplicate content is an issue. The post the comments are contained on will include other content and the page displaying comments on Disqus will be an aggregate of numerous comments. This will likely dilute and scatter the content enough to pass. For example, if you combined two books, you would now have a third, new work.
The javascript issue may or may not be a concern. Are there examples of live Drupal/Disqus sites? I'd like to look at the source.
Thanks.
#8
Subscribing. I'm interested to see this feature as well.
#9
The disqus function will create an instance of the Disqus 1.1 API: http://groups.google.com/group/disqus-dev/web/api-1-1
#10
Just installed the latest dev version, entered my Disqus API key, ran update.php, enabled Drupal comments and ran the import (though I think that's done automatically during update.php).
Everything seems the same. The comments are still dependent on the external Disqus javascript. Is there something I'm missing? Perhaps I misunderstood the benefits of using the API.
#11
Nice, thanks for testing. Update.php moves the comment threads from the path alias to the straight node/% URLs. Did you run into troubles during the update?
#12
The update went fine but I'm not sure what I'm supposed to see after the update. Was it necessary to re-enable Drupal comments?
#13
Nope, the update shouldn't introduce anything new visually. The update just performed backend tasks. Well technically, you should see the new Disqus design, but that's about it. I'll do a bit more cleanup on the update, and then make a release. Thanks a lot!
#14
I see. The original feature request said "instead of the generic JavaScript integration" which threw me off since I noticed that this latest dev version still requires Javascript from disqus.com to be inserted.
#15
Automatically closed -- issue fixed for 2 weeks with no activity.
#16
A bit confused... are there plans for integrating Disqus in such a way that the comments are actually kept and indexed on my drupal pages, instead of only at disqus.com? This seems like a big deal from an SEO perspective...
Thanks for any clarification on this issue.
#17
No word on this? I'm ready to migrate to Disqus for comments, but the SEO thing is a deal breaker for me...
#18
subscribing as well