Mod re_write not working yet...

Am I too impatient?

[SoleDrag]

*was posted at Google News [webmasterworld.com]*

jdMorgan

thanks for your advice... I read your posts on other mod_rewite threads and they helped.

Question for you or anyone:

How long does it take to eat up the URL's? I've seen nothing happen good yet, in fact, when I do the site:www.mysite.com command, it even shows less URL's indexed than before.

Also, when you see the SERPS, does it show the new .html or the old?.asp for the pages? Still has the?.asp for my URL's.

I want to tell my programmer good job, but I'm not seeing anything productive after about 5 days. Should I be patient?

I read something one time about someone that rewrote and it did nothing because they only redid it internally or something? Does that make any sense? I'm just paranoid that it's not done right, but unfortunatly, I'm too dumb to figure most of this out.

[edited by: jdMorgan at 7:11 pm (utc) on Mar. 10, 2005]
[edit reason] Linked to previous discussion. [/edit]

[jdMorgan]

If this is a Google question, then it really belongs over there. But don't expect Google or any other SE to do anything in less than 30 days, and it might take 90 days. We're so used to instant results these days that this may come as a shock, but rememeber that they fetch and analyze 8 billion URLs. It takes awhile.

A rewrite is a server-internal change to the relationship between a URL and a filepath. A redirect is an HTTP transaction involving the client that tells the client to use a different URL to fetch a requested resource.

To fix a problem with a %20 or space character in a URL so that the change is noted by search engines, you'll need to use a 301-Moved Permanently redirect.

Check your old URL using the WebmasterWorld Server Headers [webmasterworld.com] checker. You should see a 301 response code. If so, good job!

Jim

[SoleDrag]

HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Thu, 10 Mar 2005 21:20:25 GMT
Connection: keep-alive
Connection: Keep-Alive
Content-Length: 40116
Content-Type: text/html
Set-Cookie: ASPSESSIONIDSSSRSRDD=CIBIEDODKBMJCDCOGPNFPIGA; path=/
Cache-control: private

It says that, but I have no idea what it means. I'm more than a little frustrated, sigh.

[jdMorgan]

First, it says your server is not an Apache server, so none of the mod_rewrite solutions are going to help you. Look into using ISAPI Rewrite, a module that can be purchased to run on IIS servers (it may already be installed if you use commercial-grade hosting). Or just do the rewriting and redirections in your asp scripts.

The response was 200-OK, rather than 301-Moved Permanently, which is what you wanted. But since it's an IIS server, mod_rewrite isn't available, so the redirects won't work, and this is the expected result.

Jim

[SoleDrag]

Jim

I guess I confused the two, because this WAS a ISAPI Filter that was applied. I just hope it was done correctly, because it was my programmers first time, and obviously, I'm no help.