PHP vs ASP vs HTML

[daemon61]

We are creating a new website with plenty of data. The thing is that the data will be extracted from database for this site. Now the problem is - If we will go with html version, the site will be OK for SEs, but then it will request manual updates of new data. If we will go with php or asp, then it can be constantly linked with original database which will send new data automatically on the site.

Now, as I have seen while searching on google, it will show .asp pages, but has a problem with .php pages? Im assuming that .asp is better solution? Will it be the best to go with hmtl version, or asp? The pages have to be optimised for few keywords per page, is this possible in asp, and how do SEs crawl asp or php sites?

[pedstersplanet]

Any type of page is ok, as long as:

1. You refrain from using sessions;
2. You stick to short page variable (i.e .php?blah=blah);

Or if your server allows it, use the "mod_rewrite" technique....

[buddhu]

Any type of page is ok, as long as:

1. You refrain from using sessions;
2. You stick to short page variable (i.e .php?blah=blah);

Or if your server allows it, use the "mod_rewrite" technique....

Yep.

ASP and PHP are fine. I have #1 positions in Google for sites using both of those extensions. The PHP one is a database driven site with simple page variables after the '?'.

[pedstersplanet]

The pages have to be optimised for few keywords per page, is this possible in asp, and how do SEs crawl asp or php sites?

I forgot to say...... SEs see these pages as html, they dont see any (php/asp) coding, just like the browsers do.
So just optimise them just like you do html pages.

HTH

[emils]

We are creating a new website with plenty of data. The thing is that the data will be extracted from database for this site. Now the problem is - If we will go with html version, the site will be OK for SEs, but then it will request manual updates of new data. If we will go with php or asp, then it can be constantly linked with original database which will send new data automatically on the site.

Now, as I have seen while searching on google, it will show .asp pages, but has a problem with .php pages? Im assuming that .asp is better solution? Will it be the best to go with hmtl version, or asp? The pages have to be optimised for few keywords per page, is this possible in asp, and how do SEs crawl asp or php sites?

We use .asp, .php, .cf and so on... they all work the same. Stick to the advices given so far in the thread, they are all good. Avoid querystrings as possible - or definitely make use of mod-rewrite.

[GiftsForYouBiz]

If you saw PHP pages that didn't rank as well as ASP pages, that could be that the ASP pages have been "marketed" or have links back to them, or just plain optimized better.

I thought perhaps they didn't like the ".php" ending, but I know now I was wrong. I simply never marketed my php pages whereas I did submit the static versions of the same pages to SEs. So, my PR ended up better for the static (.html) versions.

[corporateface]

I was going to say the same thing.
One tip though.

As far as it is possible ... put as many of the php or asp pages in the sitemap with the variables

ex.
pagename.asp?id=1
pagename.asp?id=2
pagename.asp?id=3
etc...

Keith
Free Custom Website Design

[raquellbell]

Are you considering ASP or ASP.NET ?

[solohelp]

PHP will work on IIS and Apache so you wont have hosting issues later on. Just my 2 cents and I have change. Oh and Winblows sucks..... but thats a different debate.

[Grinler]

You should stick with PHP as it is not platform dependent. That way in the future if you decide to switch to a *nix based platform you do not have to rewrite your code.

One thing you should definitely do from the beginning is use rewrite rules to make your website SE friendly. If you decide to go IIS then you can use:

http://www.isapirewrite.com/

If you are going to use apache, then you can use the built in rewrite rules.

These rules will allow you to make something like:

http://www.blah.com/index.php?n=1&to...lah=thisislong

to www.blah.com/1/2121/1/thisislong

Due to this site I was able to finally figure out the missing piece as to how this was done, which is the rewrite rules. Doing this in the very beginning of your site creation process will save you some huge headaches later on down the road.

You can see an example of how I used rewrite rules here:

Search Engines & the world see this:
http://www.bleepingcomputer.com/forums/topict3616.html

but it is actually rewritten to:

http://www.bleepingcomputer.com/foru...showtopic=3616

This may not seem like a big difference, but dynamic urls can get very very very long.