Database driven articles: SEO effects?

Status
Not open for further replies.

HarveyJ

He is - THE CACTUS!
I'm working with a friend who's running an event.
The stupid thing is this whole event is run by committee, so instead of doing something smart like getting a designer to build p a Joomla platform for this site, and then just reskinning it every year, they actually rebuild the thing from scratch every fucking year.
He's asked me to help him with online stuff because all he knows about SEO is keywords = useful and Google Likes Links.

Anyway, this year's site is a database driven piece of shite where nothing other than the homepage is an actual HTML page.
Every page on it as actually a call on the SQL database... so instead of www.site.com/page.html it's www.site.com/#page

I'm not much on the technical side, so I've got a few questions for those of you that are:


  • Do these things even get indexed? I haven't found them in the first ten pages of Google, but considering that they haven't actually resubmitted the site to anything, and the link building campaign has been non-existent so far, I'm unsure if something would show up yet.
  • Do internal links on something like this build internal authority?
  • Do external links to the database calls pass juice on to the front page? Or does it actually go to the database call? Or does it just disappear because it's not actually a page?


I'm actually at the office today, so I'll post some tit when I get home.
Please nominate the type of tits you want to see with your answer. Arse requests also acceptable.
 


One thing I can tell you for sure is that your tracking is going to be all kinds of fucked up as browsers don't pass anything after a #

I'd be interested to see what google would do with a bunch of # as pages (I'm assuming ajax loading in a div or lightbox). I've always heard this is the drawback to ajax sites, they don't get indexed. But to be honest, I've never even considered trying to build urls like that on purpose so no testing done. Gbot is smart enough to read some js so the indexability really depends on the specifics of howthis piece of shite is coded.

If google chooses not to index it, you can always go the sitemap route and build some static/dynamic pages that don't include #

edit: all link juice will stay on the home page. # is a jump in html terms ... which makes that a one page site.
 
Sorry about the delay guys, I've been up to my elbows in new subs over the last few days.

Oh, and you guys haven't elected what sort of boobs you want posted.

erect: Yeah, that's what I figured. So for SEO purposes, it's basically just going to be all going to whatever's at the root of the domain when visitors arrive. Bugger.

oknetwork: It's all PHP.
Do you know if loading things as .aspx will pass value to those as pages, or index them though?
My biggest issue is that if people end up trying to find specific info on how to register for the event or something, they're likely to have someone's blog rate higher than the page containing info for it. i.e. the Registration page, which is something you'd want showing up in SERPs
My secondary issue to that is that it'll never get recognised as an authority site, which means that you're not going to have those nice little direct links happening underneath it when it does show up in Google.
 
Not even sure how PHP can even parse something like www.site.com/#page since mod_rewrite won't see it, and php won't see it. if you're simply gona use a symbol, try something like ~

But you do get points in a way when the url's name seems to reflect the page's title, something bout url matching content.
 
If the SE spiders stop at #, the pages are gonna have a hard time getting indexed:

site.com/#signup
site.com/#contact
site.com/#faq

there's (logically) no way 3 different pages in the SERPS, with 3 different titles, content, description, etc. can point to the same place (site.com root).

Tell them if they don't use htaccess to make proper urls they are gonna break the internet.
 
Status
Not open for further replies.