# Improve SEO of csound.com

**URL:** <https://forum.csound.com/t/improve-seo-of-csound-com/294>\
**Category:** Community\
**Created:** [April 26, 2021, 4:54pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294 "2021-04-26T16:54:46Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ixiis](https://forum.csound.com/letter_avatar_proxy/v4/letter/i/e56c9b/32.png) [@ixiis](https://forum.csound.com/u/ixiis)\
**Post date:** [April 26, 2021, 4:54pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/1 "2021-04-26T16:54:46Z")

</div>

[NOTE: Periods in urls below are unfortunately switched to slashes because new users cannot post more than 2 urls in a message.]

Searching for an opcode via Google often returns the desired documentation result, but on csounds/com (note the trailing s). Example:

 ![image](https://forum.csound.com/uploads/default/original/1X/2b18d3a88cd0cc25864f3a22db50a322dc13a621.png)

This has been a source of frustration because csounds/com has documentation that isn’t fully up-to-date (as of this writing, it’s reflective of Version 6.06, whereas csound/com is reflective of Version 6.15.0).

If SEO can’t be improved sufficiently to oust csounds/com from the top result, perhaps it’s worth asking its owner to implement [HTTP 301 redirects](https://en.wikipedia.org/wiki/HTTP_301). Having one canonical source of documentation would go a long way to streamlining things.

---

<div class="post-metadata">

**Author:** ![rory](https://forum.csound.com/user_avatar/forum.csound.com/rory/32/7_2.png) [@rory](https://forum.csound.com/u/rory)\
**Post date:** [April 26, 2021, 9:24pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/2 "2021-04-26T21:24:10Z")

</div>

> [@ixiis](#):
>
> If SEO can’t be improved sufficiently to oust csounds/com from the top result, perhaps it’s worth asking its owner to implement [HTTP 301 redirects](https://en.wikipedia.org/wiki/HTTP_301). Having one canonical source of documentation would go a long way to streamlining things.

Agreed. It’s extremely frustrating. A redirect would be great. I asked @Doctor_B about this on the Csound mailing list a while back. He said he would look into it but I don’t think he has the time. If someone with some web chops were to offer to help that would be great…

---

<div class="post-metadata">

**Author:** ![Doctor\_B](https://forum.csound.com/user_avatar/forum.csound.com/doctor_b/32/26_2.png) [@Doctor\_B](https://forum.csound.com/u/Doctor_B)\
**Post date:** [April 26, 2021, 11:30pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/3 "2021-04-26T23:30:12Z")

</div>

When Rory asked, I essentially took down the home page and put up a big square (when you land) that takes you to [csound.com](http://csound.com).

- that button has the title: Csound (and so, there should be no confusion)

After the end of the semester, I will look things over and do more to make it less confusing.

- sorry about the ‘frustration’

---

<div class="post-metadata">

**Author:** ![Doctor\_B](https://forum.csound.com/user_avatar/forum.csound.com/doctor_b/32/26_2.png) [@Doctor\_B](https://forum.csound.com/u/Doctor_B)\
**Post date:** [April 26, 2021, 11:34pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/4 "2021-04-26T23:34:01Z")

</div>

PS: The student who was managing my site for me graduated in 2015 and is doing great in LA now, but… things have not been attended to on the Web side - sorry about that.

---

<div class="post-metadata">

**Author:** ![rory](https://forum.csound.com/user_avatar/forum.csound.com/rory/32/7_2.png) [@rory](https://forum.csound.com/u/rory)\
**Post date:** [April 27, 2021, 8:15am UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/5 "2021-04-27T08:15:30Z")

</div>

Thanks @Doctor_B. Just to clarify, I don’t find it frustrating that [csounds.com](http://csounds.com) is still active. It’s merely the fact that out of date documentation that is hosted there. Thanks for looking into it. 👍

---

<div class="post-metadata">

**Author:** ![ixiis](https://forum.csound.com/letter_avatar_proxy/v4/letter/i/e56c9b/32.png) [@ixiis](https://forum.csound.com/u/ixiis)\
**Post date:** [April 27, 2021, 12:31pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/6 "2021-04-27T12:31:56Z")

</div>

I’ve web chops and can help out here if @Doctor_B isn’t opposed. It shouldn’t involve much more than editing the web server configuration file.

[Here’s](https://www.nginx.com/blog/creating-nginx-rewrite-rules/) an article on how to go about it with nginx.

---

<div class="post-metadata">

**Author:** ![Doctor\_B](https://forum.csound.com/user_avatar/forum.csound.com/doctor_b/32/26_2.png) [@Doctor\_B](https://forum.csound.com/u/Doctor_B)\
**Post date:** [April 27, 2021, 12:34pm UTC](https://forum.csound.com/t/improve-seo-of-csound-com/294/7 "2021-04-27T12:34:59Z")

</div>

Let’s try to redirect the man pages with your help or their help or some help and advice

Dr. Richard Boulanger  
Professor  
Electronic Production and Design  
Berklee College of Music
