Skip to main content

Setting up SEO-friendly URLs in htaccess/PHP

This is something I feel like I've done dozens of times over the years, and always have to waste some time googling before I figure it out. Maybe next time I'll remember to look here?

So, you're writing a custom site, and you need to be able to handle SEO-friendly URLs. You know, the kind where instead of something like "category=my_category&page=233" you the URLs to look more like "/my_category/my_page"

Those are called SEO Friendly URLs and really they're also just plain friendlier for people too. They're really kind of a leftover from when a lot static HTML sites were really organized with subdirectories full of HTML files - and Apache will still work like that "out of the box"

My usual approach to this has two parts. First, there's a custom .htaccess file in the main site directory, that redirects all requests (that are not for actual files/directories) to index.php

Then, in the index.php there's a bit of code to figure out how to route stuff based on the URL requested.

The .htaccess
A .htaccess file is a little file you can put in a directly (under Apache) that tells Apache to do various special things with requests that involve that directory. In this case, we're going to rewrite the requests so a request for "/foo/bar" ends up getting process by index.php (while still looking  like "foo/bar" in the browser). Here's the .htaccess, we'll discuss it.

RewriteEngine On

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^ index.php [L,QSA]

The first part just tells Apache to make sure Rewrite processing is "on" and working. Then there are three conditions set before rewriting can occur. These are (in order) - that the request is not for an existing file, that it's not for an existing directory and finally that it's not a request for the 'favicon.ico' file. That last one may not be strictly necessary, I took this from an existing site's .htaccess file :)

Then is the actual rewrite rule. It rewrites every to the index.php file in the directory. The two flags at the end tell Apache that this is the Last rule, and to also pass all query arguments (QSA)

The PHP
Now, you're going to have these requests passed into your index.php file, and you'll need to do stuff with them. This can work however you want/need - for me I keep it simple. This code takes the query string, splits it into an array of segments called $URL

$URL = explode('/', $_SERVER['REQUEST_URI']);
array_shift($URL);

The array_shift call just removes the first empty element that will always be there.

With this $URL variable it's easy now to just grab the segment needed and use it as necessary. "/foo/bar" requests will end up with a $URL variable where $URL[0] = "foo" and  $URL[1] = "bar". Easy!



Labels:

Comments

Post a Comment

Popular posts from this blog

Another VI tip - using macros, an example

God I love VI. Well, actually, vim but whatever. Here's another reason why. Suppose you need to perform some repetitive task over and over, such as updating the copyright date in the footer of a static website. (Yes, yes I know you could do a javascript thing or whatever, just bear with me.) Of course you could just search and replace in some text editor, changing "2007" to "2008" (if you're stupid) - and you'll end up with a bunch of incorrect dates being changed, most likely. What you need to do is only change that date at the bottom. And suppose that because of the formatting, you can't use the "Copy" part of the string in a search replace - perhaps some of the pages use "©", some spell out "Copyright" etc. This is where vi macros come in handy. A macro in vi is exactly what you expect, it records your actions and allows you to play them back. To start recording, press q followed by a character to use to "stor...
6 comments
Read more

Using FIle FIlters in FileZilla

Here's a handy tip for situations when you want to download a large number of files - but only of a certain type. For example, perhaps you want to download all the PHP files from a largish website, scattered through many subdirectories. Perhaps you're making a backup and don't want any image files, etc. FileZilla (still the best FTP in my opinion) has a handy feature called filename filters - located under the Edit menu. Here you can set various filters that filter out files based on their filename. Took me a minute to figure that out - you're saying show only PHP files, rather you're saying filter out files that do not have ".php" as their suffix. For some reason, that seems a little backwards to me, but whatever. It works quite well. You can also check whether the filter applies only to files, only to directories - or both. In this example, you'd want to check only files, as otherwise you won't see any directories unless they happen to end in...
1 comment
Read more

Great google article

Over on Maximum PC - there were a few things I didn't know you could do with the various Google apps. One is uploading files to google docs - any file. Which ties in well with my previous post about storing passwords - I uploaded a copy of my password safe file to google docs as a backup. Can't hurt, right? Also, I wasn't aware that you could set up forms in google docs that act as surveys, and then store the results in a google docs spreadsheet. This is a little alarming, as a decent amount of my work involves coding up custom surveys similar to this...
1 comment
Read more