Please tell me about ASP content

[KidsBeeHappy]

HI

Our website uses a lot of ASP dynamic content. Some of which is frequently changing.

I would like to update my sitemap so that it shows these pages as updating continuously. However, it is the ASP dynamic content that is updating rather than the webpage itself. Does googles "see" this, or does it simply see the asp commands.

The goal that I am after would be to get google picking up all of the new jobs added on boxby - so that they come up under the google alerts etc.

All knowledge tips and advice much appreciated.

Thanks
Sandra

[Subbynet]

Google will see the page as you do, and any ASP processing will take place on the server before its served to a visitor.

[DotNetWebs]

Google will see the page as you do, and any ASP processing will take place on the server before its served to a visitor.

I agree.

Personally I wouldn't even bother with a Google Site Map if your site is already indexed. IMO it is more important to have a well structured site with well-formed dynamic URLs.

We don't have a site map for Visit Horsham (http://www.visithorsham.co.uk), 99% of the pages are [asp.net] dynamically generated and new content is quickly indexed (usually the same day if it linked from the home page).

Regards

Dotty

[KidsBeeHappy]

So, how is the best way for google to pick up on these new jobs coming up on the site?

[dave_n]

how are they rendered to the site - response.write "blah blah blah" ?
perhaps you could throw in a H tag etc

response.write "<h1>blah blah blah</h1>"

[DotNetWebs]

So, how is the best way for google to pick up on these new jobs coming up on the site?

If I was coding your site I would give each 'job' it's own dynamically generated URL with heading tags also generated as suggested above.

Currently all your 'jobs' on this page:

http://www.boxby.co.uk/jobs-for-delivery.asp

Refer to this page:

http://www.boxby.co.uk/open-jobs-details.asp

Try opening the above directly in a new browser session and you will get an error. That's because it requires the postback value from the previous page to load correctly.

Google cannot index multiple versions of this page so your job details will not be indexed.

To get around the above I would dynamically generate a unique URL for each page. Have a look at the way most blogs do it for example.

Regards

Dotty

[FireFleur]

Creating URLs for each Job is a good idea.

You don't have to do this via dynamic content creation, but most do. It is easier to template it out through a build system, not many go that way though at the moment, as it is slightly more complicated for users in the client context.

[KidsBeeHappy]

I will send my developer dotty's idea and see how easily it can be worked into our site.

Kind regards
Sandra

[UKSBD]

The problem with doing this is you will end up with hundreds of out of date
jobs pages, unless you edit the information in the database after the job has gone.

[DotNetWebs]

...unless you edit the information in the database after the job has gone.

EXACTLY

Have a field in the database that shows that the job has been completed. Use this to annotate the page as such.

The historical page will aid your SEO.

Regards

Dotty

[KidsBeeHappy]

This is as it happens already.

[janerikpaul]

Hmmm, well when we've created jobboard websites in the past, we found the best approach was to get ASP to write flat HTML page for each and every job - this meant that you could create customised and highly targetted meta tags for the specific content that describes the job - this 'matching' helps the site overall to peform in the google.

[DotNetWebs]

Yes I agree that all dynamically rewritten URLs should have unique content including Page Title, meta "Description" tags and headings etc.

I haven't used "Classic" ASP for many years but the above is very easy to do in ASP.NET.

Regards

Dotty