Forum Moderators: Robert Charlton & goodroi
1 - just keep them as "index.htm" (which lets me test on hard drive)
2 - keep them as "index.htm and use a 301 redirect to send index.htm to the root /
2 - re-write them all as "/"
3 - re-write them all as an absolute url ie "http: // www .domain .com/"
I know this has been addressed, but i keep reading different opinions, and wondered if there's a general concensus.
If you can implement a 301 from index.html to http://www.example.com, that would also address your legacy issues from previously using index.html in links. There might be a dip in rankings for a short while as Google processes the new information, but soon all should be better.
Redirect for all common filenames: (index¦home¦default).(html?¦php¦pl¦cfm¦aspx?¦jspx?)
All internal links to point to the slash-ended URL too.
Never have to worry about technology changes forcing a URL change in the future.
why would you expect a dip in rankings?
I don't expect a dip, but depending on the way Google has indexed the current urls, I felt I should mention that there might be a dip. Each situation can differ, and only a few people have reported the dip. But even if it does occur, recovery is almost always fast, assuming no other issues are in the way of course.
However, I have some old legacy links from external sites to http://www.example.com/index.html and it was these I was thinking of redirecting - and would be expecting it only to have a beneficial effect (if at all) with no risk whatsoever of a dip. Am I right in my particular case?
A good example woudl be if you use index.htm then recreate your homepage using php your internal home links will all need to be modified. My pointing to www.example.com you have resolved this issue before it can become a problem.
Mack.