Forum Moderators: open
My problem is when I update pages via ftp (I upload it to the subfolder not through its own ftp address) and then visit the site on its own address I have to refresh it for the new pages and updates to show. Its like it cached it or something.
How do I get around this issue? The site hasn't launched yet but I want it to be perfect.
Also are there any possible problems I might have running it as a separate site from an seo standpoint?
Thanks in advance.
[b]subdomain1[/b].example.com
[b]subdomain2[/b].example.com Sometimes a hosting company will have another alias by which you can reach the site via the server's URL, but that doesn't sound like what you're talking about.
It's very possible you have an ISP that caches information for you. This is quite common. Many people who access your site will have similar proxy caches storing your site's info. If you want the user's browser to fetch the page anew from the server each time they visit it you could try these meta tags:
<meta http-equiv="Expires" content="0">
<meta http-equiv="Pragma" content="no-cache">
Surely it will act as a completely new site to the search engines if there are no links to the sub folder it actually resides in, how could they find it?
...the site is still not indexed by google even though their are two links to it from my other sites that get spidered daily.
I think it will just take more time - for a new site to appear in the search results - despite it possibly having already been crawled by G. Presumably your two links are to the new FQDN and not just the sub directory...? And also, that is only two links.
How long has it been?
It resides in a sub folder and you can get to it via site.othersite.com and othersite.com/site
but also just site.com
That's quite usual, but bare in mind that if you access the site by the subdomain (site.othersite.com) or by your add on domain (site.com) then the webroot of your site will be the sub folder (which is, I assume, what you require). If you access it via the plain old 'sub folder', then the webroot is still 1 folder up. (In terms of paths to scripts, stylesheets and images etc.)