Asides WordPress

WordPress no-www

After being frustrated with mod_rewrite mojo, I wrote a quickie no-www plugin for WordPress that redirects people to the non-www version of your URLs, in the spirit of Update: This is now built into WordPress through the “canonical URLs” feature, just go to the General Settings page and remove “www” from the blog and WP URLs.

59 replies on “WordPress no-www”

Hi Matt,

Thanks for wrapping this into a plugin. I’d implemented the no-www Apache script to solve a host of Ajax issues with my WordPress install but it’s good to have a solution that works with WP’s existing .htaccess editing

Heh, DreamHost has a neat little util in the panel that lets you do exactly that. I’m proud to say I’ve been no-www for quite some time now!

Good idea to write a plugin though. I don’t think people realize how much of a hit they take in search engine ranking when they allow both www and no-www. Check out digg’s ranking vs. slashdot on Digg’s combined numbers easily beat out slashdot, but because its numbers are split due to www and no-www, it sits at 6th and 11th.

Awesome! I’ve had the mod_rewrite rule in my .htaccess for a couple months. I just installed the plugin and erased the mod_rewrite rule. Everything works flawlessly.

Does this do the same as the plug-in called Objection redirection? Found here;

I have downloaded this plug-in, but haven’t activated it yet because I found your new plug-in. Obviously I would go with yours over someone else any day.

PS- could you also shed some light on this whole meta tag issue I’ve been reading on the net. The way I figure it, you are expert at all things WordPress; so if meta tags were a necessity, you would have built it all into WordPress to begin with.


Hey sorry guys, my site is messed up for another reason. When the password thing happened my site somehow got delisted from Google without the www, so I’ve been experimenting with changes to bring it back.

Nice plugin..
But after I activated this plugin I noticed one problem.

If I try to setup my blog via a weblog client say Flock or Qumana, I am getting a error while providing the authentication information(User Name/Password) The HTTP status code is 301.

Even I tried to post a new blog from the already configured client and I was getting the same HTTP status.
I deactivated the No-WWW plugin and everything was working fine !!!

Probably you need to check on this.

Ooops ! I guess I gave a feedback too soon.
When registering the blog in the web log client if I give a “No-www” url its working fine 🙂

Appears this error:

It needs to qualify the send of referrers so that this works.

(Necesita habilitar el envío de referrers para que esto funcione.)

I close all windows, and star again and works, strange, do you?



Arrrgggghhh, indeed.

Installed fine. (Except for a false error from WP “Sorry, you need to enable sending referrers for this feature to work.” Got the same error in two different browsers that have “sending referers” enabled.

But… checked back and the plugin reported itself installed and the site reported my blog as a “Class B” compliant site.

Then, I becgan getting emails that my wp-comments-post.php page would not display. Yup. No comments. This plugin was the only change, so… went to deactivate it and… “Sorry, you need to enable sending referrers for this feature to work.” And this time, no deactivation.

Guess I have to nuke the thing via ftp and seek a plugin (or other method) that’ll work w/o hashing things up. Nice idea. Works fine except for the comments issue and the weird “Sorry, you need to enable sending referrers for this feature to work,” error that cropped up for the very first time after installing this plugin.

While this plugin and other like it will indeed work, I really recommend using the .htaccess method instead, if you can get it to work.

It’s actually very simple to do. Go to and scroll down the page until you find the post titled “Make your site Class B”. Copy that htaccess code into the .htaccess file at the root of your webpage. Change the “domain” to your own, obviously.

Done and done.

[…] Did anyone notice it? Wala na akong www. sa website URI ko. I think it looks better kapag walang www. ang URI ko. Ayon sa, www. is deprecated. Tingin ko tama sila. Read their entry, and instructions on how to do it. Pero wordpress users, siguro mas maganda kung ang gagamitin niyo ay yung plug-in ni Matt. […]

[…] Everyone is aware of the continuous conflict caused by search engines indexing multiple variations of identical pages on the same domain. In an attempt to remedy this aggrivating issue, Matt created no-www; a plugin for wordpress developed with the intention on redirecting all www requests to non www location. However, not only is this non www important but what about the index.php issues? […]

[…] I have moved the information for the www-redirect plugin I released yesterday to a page of its own. The continuous plague of several pages being indexed using numerous variations of the same domain name has definately been experienced by most of us.  In an attempt to remedy this extremely aggrivating issue; WWW-Redirect was born.   Originating from the source of Matt’s no-www plug-in, www-redirect takes it a step or so further by allowing users to opt for different redirect settings.  This plugin allows users to have more control over the uri in which their users access their blog.  By doing so, you’re giving search engines and users a consistent link for accessing your content. […]

[…] I posted a couple of months ago about dropping the www from URLs and have been a supporter of it for much longer. All of my sites have been www free for as long as I can remember. The URLs will redirect to the one without www. If you’re using WordPress and have been afraid to try out the .htaccess method Matt released the no-www plugin last month. Visit for more information on the subject. Related Posts Drop the WWWPhotosiWhat?SupercomputerWhat Kind Of Blogger Are You?   […]

I implemented the plug-in on two sites (one running WP2.0.1, the other 2.0.3) using two different (but fully working) themes, and I found that comments got broken on both sites, leading to a blank page of wp-comments-post.php. Deactivating the plug-in fixed comments immediately. Both sites were running php 4.4.2 if that might have an effect…

[…] Recently I spoke about WWW vs Non WWW and the Page Rank Splitting Issue. Today when I was in the process of restoring my favorite plugins, I accidentally deleted my .htaccess file, I tried to make mod_rewrite work, but for some strange reason it didn’t work. So I was in a search for an alternative and then I landed on Matt’s No-WWW plugin page. […]

Comments are closed.