Forum Moderators: open
I see that .aspx is the extension for ASP.NET pages within the new .NET framework. I don't really understand what that means but does it matter? Could somebody explain to me in nonprogrammers terms what this will mean to me from an Optimization standpoint?
There's alot of javascript in the <head>. Can you just treat this like a normal html page & move that to an external file?
Some posters have said these pages are indexed just fine by Google, other say they're not. There seems to be no consensus & noone commenting from specific experience. For this site, it looks like all 34 pages are indexed and show on Google's site: Command with a current cache. But all pages except the home page (PR5 on TB & Directory) showed grayed out (not white) on the toolbar. Additionally, the homepage shows PR 5 at www.foo.com but is grayed out when you follow internal links to www.foo.com/home/default.aspx
I'm beginning to think there's a flaw in the Toolbar.
A search for a 4 word phrase that appears twice on their www.foo.com/about/history.aspx page gives 66,000 results and that page ranks #9. Right where I'd expect it to rank.
So maybe the TB just can't handle .aspx yet?
rmjvol
To have my pages indexed, I had to create a program which produces HTML output and saved them in that format. Google will index your default.aspx and it will show your PR in the bar but this is as far it will do.
To show your PR you have to set your default.aspx as default document in IIS .
The .Net likes to put a lot of javascript and hidden state field in the header. Another trick I do is to serve HTML optimized content for Google so page gets better relevance. do not over use it, may get you in trouble :)
on pageload event check
sIP=Request.ServerVariables("Remote_Addr").Tostring
if IsGoogle(sIP) then' check if IP is in my database
dim sOut as string="<HTML>.....</HTML>" 'your optimized HTML
Response.Write(sOut)
Response.End
end if
thanks
Since I'm not a techie, if I pass that code to my client, they'll know what to do & it'll make the Toolbar PR work?
Is there a simple way to stick all that js in an external file (& do other normal SEO stuff)? Or are you saying that generating the html files is the only way you really know to get good results?
rmjvol
I don't think the javascript may cause problems, it is already kept in client folder as js file, but I think the ViewState may give you some trouble since writes hidden values (sometimes huge) in the header area.
Google does not like this and sometimes you may find your ViewState included in index, it happened to few of my pages. Sometimes it is better to disable ViewState on default page. This is the reason I like to cloak aspx page
good luck with your project!
So I'm looking at 2 options. Cloaking is not an option.
1) Optimize the content & onpage stuff within the ASP.NET structure. The pages have a ton of extra code that the SE's don't want but I'm thinking that ranking well is still possible, just need to see if we can beat the competition with fat pages.
2) Create some new content pages in plain old html that are linked from the home page. Is there anything special I have to do to have html pages on the same site? Can you even do that?
I've got to start my competitive analysis so that may shed some light on which method I try.
Any comments?
rmjvol
