Forum Moderators: Robert Charlton & goodroi
[webmasterworld.com...]
My website has plenty of outbound links, but they are on relevant pages. The problem my site has always had, was a lack of "inbound links." I got tired of searching for people to link to me (with all the spammy sites around) and gave up. So my pages have acquired some links naturally I guess(and I'll bet I still don't have more than 30 inbound links for the whole site) Still have a PR4, which I've had since it disappeared in Nov.
[edited by: Brett_Tabke at 8:54 pm (utc) on May 27, 2005]
If we only could get some real answers we could get on with building and writing content...
"? Are you saying a 301 redirect in .htaccess causes a loop?"
The htaccess script you present will not take http://www.example.com and redirect it with a 301 to http://www.example.com/
If you try by using htaccess you may indeed create a loop.
This is all he is saying
You can fix the trailing slashes in non root directories but index versions (directory/index.htm, directory/index.html, directory/index.php, etc.) still cause a problem. Again you run into loop problems.
[edited by: arubicus at 7:56 pm (utc) on June 3, 2005]
The results are bad now. Only half the update elements have been applied. It's like a car on an assembly line that is half done being pointed at and called a butt ugly useless car. It isn't finished. Perhaps that is bad for your business, but it still isn't finished in any case.
If these results -- littered with redirects, blog comment spam sites, etc... -- were the end results that would be one thing and Google would have obviously done things wrong. But there is simply no point in complaining that they haven't put the engine in a car because they haven't gotten around to it yet.
Instead of complaining, some folks ought to be using this time to be working on their site construction and related issues. We won't know how good or bad the engine is until they put it in!
Are you claiming in will not? I sense a challenge?
I am not here to give lessons on 301. It is off topic.
Write to Clause, a genius on htaccess. I am sure he will confirm what I said.
Back to Bourbon and the demise of thousands of websites.
notawebmaster,
In a few days I will show number 1 in the serps for that colorful metaphor. And the first to speak out on behalf of angry webmasters who lost their bread and butter like clint who was unfairly treated. Pity I could not make it an anchor link.
Of course the majority of us are wanting to redirect the non-www to the www (only)
Dont want people being put off doing it - thats all. :)
[edited by: Dayo_UK at 8:07 pm (utc) on June 3, 2005]
Surely if a browser is clever enough to not be confused by errors then Google is too. Remember Google wants to add pages to its index, there is no reason for it to punish you for syntax errors. Look at the trouble they go to to find url's on a page so that they can say they've indexed more pages than anyone else.
Also when considering if this is a reason for being dropped think whether the syntax error is recent. It is very unlikely that the new algo has introduced some sort of syntax check on purpose. It's not impossible, just unlikely.
Far more likely to be something else.
One set (set A) of dc's will rank me at 9 while the others (set B) 23.
Then on another shift the dc's will switch...set A at 23 and set B at 9.
This does seem rather curious...is anyone else noticing the same? If so, would this add validity to the theory of rotating algos?
Hope this is not an indication of things to come. Googleguy eluded to the possiblity of "everflux" as being a part of the new algo.
RewriteEngine on
# Because we need rewrite
Options +FollowSymLinks -Indexes
# In particular the -Indexes to prevent the server from providing a list of files to a bot or visitor when there is no index file in that directory
rewriteCond %{THE_REQUEST} ^.*\/index\.shtml
rewriteRule ^(.*)index\.shtml$ http://www.example.com/$1 [R=301,L]
# This stops the exposure of the index file and prevent s someone from linking to both the directory and the index file presented by default and causing a duplicate content problem.
RewriteCond %{HTTP_HOST}!^www\.example\.com [NC]
RewriteCond %{HTTP_HOST}!^$
RewriteRule ^(.*) http://www.example.com/$1 [L,R=301]
# This set redirects all valid server aliases for the site including IP address if allowed..
# Please note the general rewrite rules for joining the aliases is technically correct only for servers on port 80 (default for http)
As japenese said it is best to deal with this before going live, better to deal with this before getting hit, but deal with it and clean up the mess left behind.
The best way of dealing with this is only one valid server ailias.
In addition some rules that work in the httpd.conf files need work before they will function in an .htaccess file.
Please note the index file being talked about in the above example is index.shtml this has to be handled for each index file type you allow.
[edited by: theBear at 8:09 pm (utc) on June 3, 2005]
