Cms Design Problem - Dynamic Vs Static Content Keyword availibility for search and ad-e

CMS Design problem - dynamic Vs static content - Keyword availibility for search and ad-engines

 

Here is the problem I am facing. I want method so that context sensitive ads can be put on my webpages.

 

I am on my way to create my own simple CMS. The basic structure is that, I would be using CSS for presentation. The database would be holding the content. I would use the PHP to fetch the content from database and then show the HTML to any requests that come.

 

Now, if I plan to put it up as a dynamic serving pages, the context sensitve ads may not be able to home in on the keywords. For example, I contacted Google Adsense people, and they said that Adsense would not be able to parse the dyanamicaly generated html page properly to serve the adspace from their inventory. They adviced me to have static pages of HTML.

 

Come to think of it, if it cannot be seen properly by the ad-engines, I think it would not be parsed easily by the search-engines either. It would be like commiting a web-hara-kiri interms of page ranks. I would be designing the death, right into the inception of my website.

 

How can I incorparate this into the already designed system I have? The overall structure of my design can be seen in the following picture:

 

Can any of you think, how I should proceed with the design here? How should I put it into the design so that it can be parsed by ad-engines and search engines alike?

CMS Design problem - dynamic Vs static content - Keyword availibility for search and ad-engines

 

Here is the problem I am facing.  I want method so that context sensitive ads can be put on my webpages.

 

I am on my way to create my own simple CMS.  The basic structure is that, I would be using CSS for presentation.  The database would be holding the content.  I would use the PHP to fetch the content from database and then show the HTML to any requests that come.

 

Now, if I plan to put it up as a dynamic serving pages, the context sensitve ads may not be able to home in on the keywords.  For example, I contacted Google Adsense people, and they said that Adsense would not be able to parse the dyanamicaly generated html page properly to serve the adspace from their inventory.  They adviced me to have static pages of HTML.

 

Come to think of it, if it cannot be seen properly by the ad-engines, I think it would not be parsed easily by the search-engines either.  It would be like commiting a web-hara-kiri interms of page ranks.  I would be designing the death, right into the inception of my website.

 

How can I incorparate this into the already designed system I have?  The overall structure of my design can be seen in the following picture:

 

Can any of you think, how I should proceed with the design here?  How should I put it into the design so that it can be parsed by ad-engines and search engines alike?

1064336287[/snapback]

Some CMS systems create .html static output pages. I know with Drupel with the "search friendly" settting on that it creates static pages. Then if you edit it, then it generates a new static page at the same spot. So that is an idea you might want to explore.

 

Although if you look at many forums, the'll have adsense ads that are displayed that advertise Macs if the topic is apple related, etc.

On a vague note, I did explore the idea of having the CMS system output a static HTML page. Yes, I would agree that it is a novel idea. I have seen that happen on the Google Blogster systems. I do not know if it stores the data in database, but once we have entered a post, we need to do a 'publishing' that outputs HTML pages. Thanks for bringing that out and making it clear.But, with that in place, would there not be a kind of unneeded redundancy in the system. I mean, there would be the content in the database, and there would be the same as HTML pages. I know, if there is no other meathod, I would go for this option itself.Keeping this aside, is there anyother meathod anyone of you can think of?

For one thing - usually, dynamically generated pages contain a lot of variables in the URL, something like:

 

http://www.somedomain.com/somepage.php?id=x&page=y&section=abcd

 

That's what both Ad engines and Search engines hate like anything causing them to avoid such pages like plague.

 

One easy alternative would be to take advantage of Apache's MOD_REWRITE module, to serve the web-pages in such a manner that they appear as static content to the Search & Ad Spiders alike. Take for example this forum itself - it uses mod_rewrite to it's fullest to generate what is known as SEF or Search Engine Friendly URLs.

 

While in reality the pages are still dynamically generated by the forum software, when you view them in your browser, the URL appears to be that of a static page as shown in your address bar. This is the doing of mod_rewrite.

 

About the exact process you'll find plenty of articles on the net - just google for mod_rewrite and search engine freindly url.

 

Invision Power Board has a module called FURL or Friendly URL, which can be downloaded from invisionize.com. You can study the php code and get an idea how this is done. It's not a very complicated process actually - although my limited knowhow doesn't permit me to get into an indepth discussion. That would be OpaQue's speciality.

Apache's MOD_REWRITE module, you say.Hmmm... is it available here at Xisto? It surely looks like it is worth a try.May be at first, I would go about serving pages in the earier method, and then by that time, I would have learned this method and then start using it. So, is this module available here in Xisto, and how would my luck go at OpaQue reading this thread?

Yup - mod_rewrite is pretty much at work. Our board gives you a live demo of it and in case you're using IPB or any other forum software that supports the SEF URLs, then you can generate them from your own hosting account to with the help of mod_rewrite. My advise would be for you to get your CMS up and working with dynamic pages first. Get all your units to work in harmonious conjunction - only then start delving into the mod_rewrite issue - coz I can assure you it's gonna take you just a day or two to get the static url generation working. It's the CMS part that's going to take you for the real ride

Thanks for that piece of advice, miCRoSCoPiC^eaRthLinG (Did I put all the caps and small right? ).Yes, I am putting much of effort in designing the CMS. Even though, I plan for it to be very basic, I want it to be very stable and robust. So, it is taking a long time, but I hope, I do not get desperate and start rushing things up.