13 {{ upvoteCount | shortNum }}
13 {{ upvoteCount | shortNum }}

What Would You Do In This Situation?...

by Jamie Iaconis
11 replies
Hi,

Something that hasn't really been discussed....

I just had an idea and wanna run it by you guys...

I want to use the same script I am using
on my other site, on another one also...

Would you use the site and DB that is already
populated etc or would you start a new one?

I am wondering this because, having the site already
populated would be easier than stink, but if I start a
new one I will be getting new/other KWs etc that I wouldn't
be getting if I used them twice (on both sites) although
I would probably be ranking for both sites in different
spots... a new DB would have more coverage, I believe???

What's your take on this???

I hope you understand the above, lol!

Jamie
#database #keywords #ranking #rankings #script #situation
  • Profile picture of the author Jamie Iaconis
    No one has any input on this?

    At all??
    Signature
    {{ DiscussionBoard.errors[530961].message }}
  • Profile picture of the author JohnMcCabe
    Originally Posted by Jamie Iaconis View Post

    I hope you understand the above, lol!

    Jamie
    Jamie, I think this might be the problem. I read your post three times, and I have no clue what it is that you are asking...
    {{ DiscussionBoard.errors[531490].message }}
    • Profile picture of the author Jamie Iaconis
      OK...

      Let's see, there's site A and site B...

      Should I use site A's DB on site B, or start a new DB for site B?

      Pros/Cons... Effectiveness?
      Signature
      {{ DiscussionBoard.errors[531758].message }}
      • Profile picture of the author tim_buchalka
        Originally Posted by Jamie Iaconis View Post

        OK...

        Let's see, there's site A and site B...

        Should I use site A's DB on site B, or start a new DB for site B?

        Pros/Cons... Effectiveness?
        Better to have all the functionality of site a on site a, and functionality of site b, on site b.

        Just imagine how messy this could get 2 years down the track when you have completely forgotten what you did and are selling the website.

        My vote is start a new db for site b.

        Cheers



        Tim
        {{ DiscussionBoard.errors[531779].message }}
        • Profile picture of the author Jamie Iaconis
          Originally Posted by tim_buchalka View Post

          Better to have all the functionality of site a on site a, and functionality of site b, on site b.

          Just imagine how messy this could get 2 years down the track when you have completely forgotten what you did and are selling the website.

          My vote is start a new db for site b.

          Cheers



          Tim
          IC... this makes sense too, indeed!
          Signature
          {{ DiscussionBoard.errors[531792].message }}
          • Profile picture of the author Michael Mayo
            Will you be linking the sites to each other?
            If not and the DB info is relevant to both, I would copy the data base
            and create a new DB for site B using site A's info.

            You don't want both sites going down because one DB failed right?

            Plus, using the existing data to start the new DB can give you a content
            boost also the two data bases will eventually contain different info over
            time as they grow.

            From what I know Duplicate content is only penalized when the sites reside
            on the same DNS/IP. <=Remember that the SE's can change this at any
            time and rule differently.

            Just my .02
            Have a Great Day!
            Michael
            {{ DiscussionBoard.errors[531821].message }}
  • Profile picture of the author LoveLinguist
    Pros- lazy, easy
    Cons - problems in the long run

    Sherrie Rose
    The Love Linguist
    {{ DiscussionBoard.errors[531769].message }}
  • Profile picture of the author jrailsback
    Okay... so why wouldn't you just start a new database on site B? something about keywords? DB does mean database right? Like MySQL?
    Signature

    Please read the sig file rules

    {{ DiscussionBoard.errors[531772].message }}
  • Profile picture of the author testaccount9998
    If you are just worried about copying database A to database B site because of duplicate content then I would go ahead and do it.

    Several prominent Warriors have proved many times that duplicate content is a myth, as long as you NEVER link the two.

    I am not sure if that helps at all, but good luck.

    Rebtl
    {{ DiscussionBoard.errors[531776].message }}
    • Profile picture of the author Jamie Iaconis
      Originally Posted by Rebtl View Post

      If you are just worried about copying database A to database B site because of duplicate content then I would go ahead and do it.

      Several prominent Warriors have proved many times that duplicate content is a myth, as long as you NEVER link the two.

      I am not sure if that helps at all, but good luck.

      Rebtl
      Yes, this is EXACTLY what I mean!

      I would get new/different KW's in SE's by starting a
      new DB, but 2 listings/chances with the same one.

      HHMM...
      Signature
      {{ DiscussionBoard.errors[531788].message }}
  • Profile picture of the author jrailsback
    Those responses make sense

    Second database it is! lol
    Signature

    Please read the sig file rules

    {{ DiscussionBoard.errors[531823].message }}

Trending Topics