calvinmicklefinger - 5:40 pm on Jun 7, 2010 (gmt 0)
What WON't go to index.php,
I've come to the conclusion that I may need to be pretty flexible with the filenames. I'm thinking the easiest way would be to put them in a "content" sub-directory which I can control and won't run the risk of being cluttered up with so many files in the root that I get confused.
Just a question, is this experimental or intended for a live site? The reason I ask is
Is not a real fruitful URL in terms of SEO and user experience, but
I hadn't been worried about trying to be SEO fodder. I am running long term email campaigns (into our second year now) with JV partners and wanted their pages to be sort of "hidden" from casual visitors. i.e., no navigation links on the pages. Everyone arrives at a specific landing page by way of a link in an email message or on someone else's site. Mainly this is so Ralph can make one offer for my product and George can make a different one.
I've had feedback that this will cause Google to see everything as "duplicate content" and drop me from a "ranking," but I'm not sure how to adapt for that.
However, being able to name a page ...
is looking more attractive all the time.
A direct request to a domain root won't, but that will probably go to index.php by default if you don't have an index.htm(l). So again, 0.php
I removed the index.htm(l) bunch, and placed this code in the index.php so that a call to the root loads 0.php
I think I'll move the content to some strangely named content folder. That sound worthwhile? Any additional advice. Old fogey's learn slow. (You know, the Old Dog, New Tricks syndrome here.)