Member Sign In
Not a member?

A Wired.com user account lets you create, edit and comment on Webmonkey articles. You will also be able to contribute to the Wired How-To Wiki and comment on news stories at Wired.com.


It's fast and free.

Sign in with OpenID
Sign In
Webmonkey is a property of Wired Digital.
processing...
Join Webmonkey

Please send me occasional e-mail updates about new features and special offers from Wired/Webmonkey.
Yes No

Please send occasional e-mail offers from Wired/Webmonkey affiliated web sites and publications, and carefully selected companies.
Yes No

I understand and agree that registration on or use of this site constitutes agreement to Webmonkey's User Agreement and Privacy Policy.
Webmonkey is a property of Wired Digital.
processing...

Retrieve Sign In

Please enter your e-mail address or username below. Your username and password will be sent to the e-mail address you provided us.

or
Webmonkey is a property of Wired Digital.
processing...

Welcome to Webmonkey

A private profile page has been created for you.
As a member of Webmonkey, you can now:
  • edit articles
  • add to the code library
  • design and write a tutorial
  • comment on any Webmonkey article
Close
Webmonkey is a property of Wired Digital.

Sign In Information Sent

An e-mail has been sent to the e-mail address registered in this account.
If you cannot find it in your in-box, please check your bulk or junk folders.
Sign In
Webmonkey is a property of Wired Digital.

Google Requests No Funny Stuff With Dynamic URLs

Google’s Webmaster blog posted some dynamic URL advice that essentially says don’t try to make dynamic URLs look static.

“We might have problems crawling and ranking your dynamic URLs if you try to make your urls look static and in the process hide parameters which offer the Googlebot valuable information.”

Here’s a typical dynamic URL: example.com/list_items.php?category=34&color=red
And the same URL rewritten to appear static: example.com/list_items/34/red/

Rewriting is the process of telling the server to change a URL of a particular form to instead point to another real location. Developers use rewrites to make a URL look better (either to users or search engines), or to obscure the underlying technology a site uses.

Unlike in the past, Google says, crawlers are now able to deal with dynamic URLs. In fact, the post claims that non-static URLs that attempt to appear static cause problems when pages evolve to need different criteria–i.e., gaining or losing parameters.

Reading between the lines, Google wrote this post because some developers do not rewrite URLs accurately. As one commenter noted, that’s not fair to those who rewrite correctly:

“That is like saying people shouldn’t drive because if you do it wrong, you may cause an accident. Come on. Give people proper guidelines. Identify the parameters you guys trip on like session IDs and teach the uneducated how to best eliminate the problem.”

If you’re new to URL rewriting, you should probably be careful with advanced techniques. You can get started by using simple rewrites, which can make URLs short and guessable. There’s a classic A List Apart article about making everything a directory. And directories are a good way to think about rewrites. If your URL makes sense as a static content hierarchy, it’s a reasonable rewrite.

At least, that’s what I think. Do you use rewritten URLs? What do you think about Google’s rewriting guidelines?

Post Comment Comments Permalink Print
Reddit Digg

 
Subscribe now

Special Offer For Webmonkey Users

WIRED magazine:
The first word on how technology is changing our world.

Subscribe for just $10 a year