<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Weblog Tools Collection &#187; permalinks</title>
	<atom:link href="http://weblogtoolscollection.com/archives/tag/permalinks/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<lastBuildDate>Mon, 13 Feb 2012 13:00:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress and the Not Found Permalinks</title>
		<link>http://weblogtoolscollection.com/archives/2011/02/23/wordpress-and-the-not-found-permalinks/</link>
		<comments>http://weblogtoolscollection.com/archives/2011/02/23/wordpress-and-the-not-found-permalinks/#comments</comments>
		<pubDate>Wed, 23 Feb 2011 14:00:27 +0000</pubDate>
		<dc:creator>James</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Troubleshooting]]></category>
		<category><![CDATA[permalinks]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=9701</guid>
		<description><![CDATA[So, you&#8217;ve just switched from the default WordPress permalink structure and now your permalinks are returning Not Found (404) errors, or you didn&#8217;t do anything at all and they&#8217;re return the error. First, there could have been a momentary glitch, so try re-saving your permalink structure at Settings/Permalinks in your admin panel. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving. If that doesn&#8217;t work, contact your hosting provider and find out if mod_rewite is installed and active on your server. If it isn&#8217;t, refer to this guide for some tips on using permalinks without mod_rewrite, or find yourself a nice Apache-based server with mod_rewrite. Permalinks are a finicky thing. They&#8217;ll either work right away, if you re-save, and if you use a work-around, otherwise they just won&#8217;t work at all. If you&#8217;re still having trouble, contact the WordPress Support Forums for more assistance.]]></description>
			<content:encoded><![CDATA[<p>So, you&#8217;ve just switched from the default <a href="http://wordpress.org/">WordPress</a> permalink structure and now your permalinks are returning Not Found (404) errors, or you didn&#8217;t do anything at all and they&#8217;re return the error.</p>
<p>First, there could have been a momentary glitch, so try re-saving your permalink structure at Settings/Permalinks in your admin panel.  If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.</p>
<p>If that doesn&#8217;t work, contact your hosting provider and find out if mod_rewite is installed and active on your server. If it isn&#8217;t, refer to <a href="http://codex.wordpress.org/Using_Permalinks#Permalinks_without_mod_rewrite">this guide</a> for some tips on using permalinks without mod_rewrite, or find yourself a nice Apache-based server with mod_rewrite.</p>
<p>Permalinks are a finicky thing. They&#8217;ll either work right away, if you re-save, and if you use a work-around, otherwise they just won&#8217;t work at all. If you&#8217;re still having trouble, contact the <a href="http://wordpress.org/support/">WordPress Support Forums</a> for more assistance.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2011/02/23/wordpress-and-the-not-found-permalinks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Other Side Of Permalinks</title>
		<link>http://weblogtoolscollection.com/archives/2008/01/27/other-side-of-permalinks/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/01/27/other-side-of-permalinks/#comments</comments>
		<pubDate>Sun, 27 Jan 2008 14:43:41 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[permalinks]]></category>
		<category><![CDATA[tedclaytone]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2008/01/27/other-side-of-permalinks/</guid>
		<description><![CDATA[I recently wrote an article that explained how to configure permalinks in WordPress. In that article, I go over a few different reasons why you would want to use pretty permalinks instead of using the default linking structure. Well, Ted Clayton published an article that took the other side of the permalinks argument. Ted goes into detail on why and how WordPress uses the default linking structure and explains that it&#8217;s not as bad as some would make you think. It&#8217;s an excellent read and I thank Ted for bringing up the other side of the equation. There is, in truth, a maze of trade-offs &#38; counterpoints involved in selecting a strategy &#38; tactics for making nicer, people-friendly URLs, for each &#38; every website. Yes, many typical blog-sites will be able to adopt typical, easily-identified Permalink configurations. In the end, though, only you can do it right for your site. [...]]]></description>
			<content:encoded><![CDATA[<p>I recently wrote an article that explained <a href="http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/" title="http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/" target="_blank">how to configure permalinks</a> in WordPress. In that article, I go over a few different reasons why you would want to use pretty permalinks instead of using the default linking structure. Well, Ted Clayton published an article that took the other side of the permalinks argument. Ted goes into detail on why and how WordPress uses the default linking structure and explains that it&#8217;s not as bad as some would make you think. It&#8217;s an excellent read and I thank Ted for bringing up the other side of the equation.</p>
<blockquote><p>There is, in truth, a maze of trade-offs &amp; counterpoints involved in selecting a strategy &amp; tactics for making nicer, people-friendly URLs, for each &amp; every website.  Yes, many typical blog-sites will be able to adopt typical, easily-identified Permalink configurations.  In the end, though, only you can do it right for your site.</p></blockquote>
<p><a href="http://thuledingles.com/?p=191" title="http://thuledingles.com/?p=191" target="_blank">Permalinks &#8211; The Big Picture </a></p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/01/27/other-side-of-permalinks/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Configuring WP Permalinks</title>
		<link>http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 23:41:02 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[HOW-TO]]></category>
		<category><![CDATA[WordPress FAQs]]></category>
		<category><![CDATA[links]]></category>
		<category><![CDATA[permalinks]]></category>
		<category><![CDATA[prettypermalinks]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[seofriendlyurls]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/</guid>
		<description><![CDATA[Quite often, we hear of the terms (permalinks or pretty permalinks) which can also be called SEO-friendly URLs. These URLs are not only SEO friendly, but I believe they are human friendly as well. By default, WordPress uses URLs that look like a mishmash of letters and numbers with a few question marks mixed in for good measure. These types of links are frowned upon by search engine spiders and as a human being, they are also hard to read. Fortunately, WordPress provides a way for us to change this linking structure to something understandable. WordPress calls these Permalinks. Permalink settings can be configured a number of different ways. One of the ways to quickly configure permalinks is by choosing one of the Common Options. These common options include: Default &#8211; http://www.domain.com/?p=123 Date and name based &#8211; http://www.domain.com/2008/01/15/sample-post/ Numeric &#8211; http://www.domain.com/archives/123 There is no sense in using the default option [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://weblogtoolscollection.com/b2-img/2008/01/permalinks.png" alt="Pretty Permalinks" /></p>
<p>Quite often, we hear of the terms (permalinks or pretty permalinks) which can also be called SEO-friendly URLs. These URLs are not only SEO friendly, but I believe they are human friendly as well. By default, WordPress uses URLs that look like a mishmash of letters and numbers with a few question marks mixed in for good measure. These types of links are frowned upon by search engine spiders and as a human being, they are also hard to read.</p>
<p>Fortunately, WordPress provides a way for us to change this linking structure to something understandable. WordPress calls these Permalinks. Permalink settings can be configured a number of different ways. One of the ways to quickly configure permalinks is by choosing one of the <strong>Common Options</strong>. These common options include:</p>
<p><strong>Default</strong> &#8211; http://www.domain.com/?p=123</p>
<p><strong>Date and name based</strong> &#8211; http://www.domain.com/2008/01/15/sample-post/</p>
<p><strong>Numeric</strong> &#8211; http://www.domain.com/archives/123</p>
<p>There is no sense in using the default option so choose either <strong>Date and name based</strong> or <strong>Numeric</strong> if you don&#8217;t feel like tinkering with the Custom Structure.</p>
<p>The custom structure of the permalinks settings area allows you to customize the way permalinks are displayed by using any combination of the following permalink tags.</p>
<blockquote><p><strong>%year%</strong> &#8211; 4-digit year (for example, 2008)</p>
<p><strong>%monthnum%</strong> &#8211; 2-digit month (for example, 01 for January)</p>
<p><strong>%day%</strong> &#8211; 2-digit day (for example, 15)</p>
<p><strong>%hour%</strong> &#8211; 2-digit hour of the day (for example, 20 for 10PM)</p>
<p><strong>%minute%</strong> &#8211; 2-digit minute (for example, 50)</p>
<p><strong>%second%</strong> &#8211; 2-digit second (for example, 24)</p>
<p><strong>%postname%</strong> &#8211; Text separated by dashes which usually ends up being the post name. (for example, configuring-wp-permalinks)</p>
<p><strong>%post_id%</strong> &#8211; The unique, numerical ID of the post (for example, 124)</p>
<p><strong>%category% </strong>- The text of the category name that the post is filed in (for example, how-to)</p>
<p><strong>%author%</strong> &#8211;  Text of the post author&#8217;s name (for example, ronald-huereca)</p>
<p><strong>Example of custom structure in use:</strong></p>
<p><strong>Custom Structure:</strong> /%year%/%monthnum%/%day%/</p>
<p><strong>Link Output:</strong> http://www.domain.com/2008/01/16/</p></blockquote>
<p>Make sure that you include the back slashes at the beginning of the custom structure, after each tag and at the end. This will ensure that WordPress writes the correct rules in the .htaccess file via mod_rewrite.</p>
<p><a href="http://jeffc.me" title="http://jeffc.me" target="_blank">For my own blog</a>, I seem to have done fairly well in the search engines by using the Custom Structure method and using the %postname% tag. I can&#8217;t say for sure which combination would do better or worst for search engines. The only thing I can suggest is that you configure your permalinks to look whats best for you.</p>
<h2>*WARNING*</h2>
<p>Changing the structure of your permalinks affects all of the permalinks on your blog. This is important to know because search engines will have indexed posts on your site via their permalinks. If you change the permalink structure mid stream, you will end up invalidating all of those links.</p>
<h2>What to do if you don&#8217;t have a .htaccess file?</h2>
<p>If you notice that you don&#8217;t have a .htaccess file within the same directory as your WordPress installation, you can create one by first creating a blank .txt file and saving the file as htaccess.txt. Upload this file via  FTP to the same folder that houses your WordPress installation. Once the file is uploaded, set the permissions to the file as <strong>666</strong>. Next, rename the file to .htaccess. Now you should have a blank .htaccess file for which WordPress can write the proper permalink rules to.</p>
<h2>Servers That Don&#8217;t Use Apache Or mod_rewrite.</h2>
<p>If the webhosting server you are on does not have the apache module mod_rewrite enabled, you can still use the permalink settings in WordPress by placing <strong>index.php</strong> in front of any custom permalink tags.</p>
<p><strong>For example:</strong> /index.php/%year%/%monthnum%/%day%/</p>
<p><strong>Equals:</strong> http://www.domain.com/index.php/2008/01/16/</p>
<p>Using index.php in this way eliminates the need for a .htaccess file.</p>
<p>I hope this little primer on how to configure your permalinks within WordPress was helpful. I&#8217;ve seen too many blogs out on the net that have yet to take advantage of this awesome feature. As I&#8217;ve said before, using any sort of permalink structure is better than the WP default. Not only is it beneficial in terms of SEO, but it also makes it easier for human beings to see at a glance, what a particular link is pointing to without having to visit the page.</p>
<p>If you use the custom structure aspect of permalinks, I&#8217;d be very interested in knowing which configuration of permalink tags you have chosen to use and why.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/feed/</wfw:commentRss>
		<slash:comments>64</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  weblogtoolscollection.com/archives/tag/permalinks/feed/ ) in 0.94038 seconds, on Feb 14th, 2012 at 8:40 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 14th, 2012 at 9:40 am UTC -->
