18 {{ upvoteCount | shortNum }}
18 {{ upvoteCount | shortNum }}

WP Put On "Front End" Of HTML Site?

by barq
16 replies
  • WEB DESIGN
    • |
I have a client site that was done in html, really not a good site, dated, disjointed, worked on by many different people ... but ... it's been around for a long time, and the client thinks it ranks really well for their keywords (it does dominate local search). Client is very hesitant to change anything ... but they want a more current-looking site.

We do not "need" any of the old site ... we just want the pages currently ranking well to keep ranking while we build and rank a "new" wp site.

Is it possible to have a wp site as the "main" site and their old html site kind of in the background ... but linked to the wp site somehow? (So, if someone searches for their service and go to the old site, it either redirects them to the wp home page or the html has a link on it, or somesuch?)

And so we don't disturb the old site, but everything done from now on is done on the wp part of it?

If so, generally how would this be done (in lay terms!)?

(I did post a Warrior ad for the html site to be converted to WP, but with some info I've received saying the .html pages would disappear and thus their rankings makes me wonder if what I've "tried" to explain above might be a simpler, better option.)

Thanks much, appreciate any help
#front end #html #put #site
  • Profile picture of the author Johnny Optimo
    just be sure to use 301 redirects from all the old pages to preserve SEO - also make sure you create equivalent pages for them to redirect to.

    And yes, you can certainly 'keep' the old site in the background - probably the only thing you'd need to lose would be the index.html - but I just recommend using 301 redirects, it's confusing and awkward for users to be interacting with two different sites on the same domain.

    So yeah... when you create the new site, I say you should cretae new equivalent pages form the old ones (can use same text even) and then create 301 redirects to the new wp pages.
    {{ DiscussionBoard.errors[5168844].message }}
  • Profile picture of the author UMS
    There are two main ways of approaching this.

    1. Create a new WP site on a temporary domain with all the new content and keeping the same page names as the old HTML site. Then when it is complete, migrate the whole thing to replace the HTML site.

    2. Create a new WP site (easiest to use a temporary domain again), but create your desired layout/page structure.

    When you migrate it, implement 301 redirects to map all of the old pages to the appropriate new page.


    I personally used option 2 to successfully migrate various HTML sites to WordPress, as it can sometimes be too messy/complicated trying to replicate the old navigation/page structure.
    Signature
    {{ DiscussionBoard.errors[5168856].message }}
  • Profile picture of the author Istvan Horvath
    Originally Posted by barq View Post

    I have a client site ...

    ...how would this be done (in lay terms!)?
    The two bold words should NOT be in the same post.

    If you have clients, you should be a pro, not a "layman". Otherwise you are doing a great disservice to them (and to yourself!).

    Actually, it can be done: assuming the "old" site has an index.html file in the root. Install WP in the root leaving all the other html files there. It will create a big mess but that's what you (the client) asked for.

    Rename/delete the old index.html and WP's own index.php will take it over = that will be the main page.

    You can still link to all the existing .html files from it.

    If the instructions above are not enough for you, I suggest you confess to the client the task is above your head and you are not taking the job.
    Signature

    {{ DiscussionBoard.errors[5168932].message }}
  • Profile picture of the author barq
    Johny Optimo and Peter, thank you for your helpful responses.

    Istvan, are you always this confrontational, arrogant and rude? You know nothing about me or my abilities ... I'm a retired CEO of one of the country's largest communications agencies working with some very successful ex-ad guys ... and I would never dream of doing the actual work myself. However, before I make any recommendations to a long-term client, I do my homework. Maybe you should do yours before you make assumptions.
    {{ DiscussionBoard.errors[5168996].message }}
    • Profile picture of the author Istvan Horvath
      Originally Posted by barq View Post

      Istvan, are you always this confrontational, arrogant and rude?
      With those pretending to be "web experts" and going to rip off offline businesses while displaying a complete ignorance about everything web and WP - YES! Always. And I am proud of it. If I could I'd always report them to their clients!

      Just for the record: the majority of questions like yours come from this kind of guys...


      Originally Posted by barq View Post

      You know nothing about me or my abilities ... I'm a retired CEO of one of the country's largest communications agencies working with some very successful ex-ad guys ... and I would never dream of doing the actual work myself.
      By the way your OP was formulated nothing suggested you'd outsource the job. It sounded as a wannabe "off-line cash cow chaser" that got himself into something that he wasn't qualified for. Again, with those I am mercilessly rude: they deserve it.

      To be honest, I don't really care who is behind a nickname. And if you don't plan to do the discussed job yourself but will outsource it to a real WP expert - then I apologize.

      P.S. Even for your outsourced work force I gave the essential steps
      Signature

      {{ DiscussionBoard.errors[5169177].message }}
      • Profile picture of the author barq
        Alright, I apologize for calling you rude.

        I did note, I believe, that I had purchased an ad on the forum for someone to do this work; however, the responses I received were all over the place. And frightening in their disparities. So hence my question here, trying to figure out best option from real experts before outsourcing it.

        So, I thank you for your technical answer, though I'm concerned about your comment about it creating a mess ...


        Originally Posted by Istvan Horvath View Post

        With those pretending to be "web experts" and going to rip off offline businesses while displaying a complete ignorance about everything web and WP - YES! Always. And I am proud of it. If I could I'd always report them to their clients!

        Just for the record: the majority of questions like yours come from this kind of guys...




        By the way your OP was formulated nothing suggested you'd outsource the job. It sounded as a wannabe "off-line cash cow chaser" that got himself into something that he wasn't qualified for. Again, with those I am mercilessly rude: they deserve it.

        To be honest, I don't really care who is behind a nickname. And if you don't plan to do the discussed job yourself but will outsource it to a real WP expert - then I apologize.

        P.S. Even for your outsourced work force I gave the essential steps
        {{ DiscussionBoard.errors[5169246].message }}
  • Profile picture of the author Kezz
    Hey barq,

    Istvan is 100% right on the method he's laid out. Even if you skip his first two lines, you should definitely read the third, fourth and fifth lines as his method will actually be the easiest way to achieve what you're aiming for.

    With this approach there's no need to worry about handling 301 redirects or anything at all, as the HTML site's page will stay exactly the same. Both the WP and the HTML sites just sit on the same domain, peacefully cohabiting.

    Additionally, with this method once you install WP you can then use the custom menu function to create links back to the old site.

    All in all the above method will take you about 10 minutes to roll out with almost zero chance of issues. Easy peasy.
    {{ DiscussionBoard.errors[5169152].message }}
    • Profile picture of the author barq
      Hey Kezz,

      Thanks for the info (as I assume I'll get bounced from forum for my response to Istvan, glad I got it in time!). I have no doubt he knows what he's talking about, don't appreciate the way he does it.

      Though I also noticed his "It will create a big mess but that's what you (the client) asked for."

      (What a response ... the reason I'm asking about this is to make sure we do the best thing, not what I "ask for" ... you would be amazed at the different opinions we've heard, most conflicting with each other. So you keep asking, due diligence.)

      You think it won't create such a mess?

      Thanks again

      Originally Posted by Kezz View Post

      Hey barq,

      Istvan is 100% right on the method he's laid out. Even if you skip his first two lines, you should definitely read the third, fourth and fifth lines as his method will actually be the easiest way to achieve what you're aiming for.

      With this approach there's no need to worry about handling 301 redirects or anything at all, as the HTML site's page will stay exactly the same. Both the WP and the HTML sites just sit on the same domain, peacefully cohabiting.

      Additionally, with this method once you install WP you can then use the custom menu function to create links back to the old site.

      All in all the above method will take you about 10 minutes to roll out with almost zero chance of issues. Easy peasy.
      {{ DiscussionBoard.errors[5169217].message }}
      • Profile picture of the author Kezz
        Originally Posted by barq View Post


        Though I also noticed his "It will create a big mess but that's what you (the client) asked for."

        You think it won't create such a mess?

        Thanks again
        By a big mess Istvan is referring to the fact you'll have all the site's HTML files still in the root of the domain, along with any images folder and CSS files.

        In the root of the domain you'll also have all WordPress' files and folders.

        So the files for the HTML and the WordPress sites will be mixed in together in the root.

        From a dev's point of view this is a mess, i.e. things are not nicely contained in separate folders, but I'd say from yours and your client's point of view it won't pose any great issue.

        I'd guess this type of mess would probably be easier for you to deal with than a mess of redirection management, so the overall end result is more suitable.
        {{ DiscussionBoard.errors[5169364].message }}
    • Profile picture of the author Johnny Optimo
      Originally Posted by Kezz View Post

      Hey barq,

      Istvan is 100% right on the method he's laid out. Even if you skip his first two lines, you should definitely read the third, fourth and fifth lines as his method will actually be the easiest way to achieve what you're aiming for.

      With this approach there's no need to worry about handling 301 redirects or anything at all, as the HTML site's page will stay exactly the same. Both the WP and the HTML sites just sit on the same domain, peacefully cohabiting.

      Additionally, with this method once you install WP you can then use the custom menu function to create links back to the old site.

      All in all the above method will take you about 10 minutes to roll out with almost zero chance of issues. Easy peasy.
      this may be quicker but it's no way to run a web based business imo. Client wants to preserve SEO value from what I understand, not confuse visitors by sending them to one site from search engine results and then show them a different index/etc.

      But - do you really even need wordpress for this? Maybe consider redesigning the html pages with some slick new css, and then add a wordpress blog and tweak it to look like the site - then you get to keep using the old html files, but add on a new blog. just an idea.
      {{ DiscussionBoard.errors[5169387].message }}
      • Profile picture of the author barq
        Originally Posted by Johnny Optimo View Post

        this may be quicker but it's no way to run a web based business imo. Client wants to preserve SEO value from what I understand, not confuse visitors by sending them to one site from search engine results and then show them a different index/etc.

        But - do you really even need wordpress for this? Maybe consider redesigning the html pages with some slick new css, and then add a wordpress blog and tweak it to look like the site - then you get to keep using the old html files, but add on a new blog. just an idea.
        Well, guess there's no "easy" answer ... keeping the html pages is an option, it's just that the site is so outdated and with so much old info that I was hoping for a solution that would keep the client happy (ranking their keywords) but let us start anew ...

        Maybe our best bet is to just get a different site setup (client-name.com v. clientname.com), have unique content on the new site, and let both sites do their thing. Ultimately, the new site will outrank the old site as it would be properly optimized and promoted. Would have to think about whether or not this would confuse their brand or not.

        But, who knows? I appreciate all the feedback.
        {{ DiscussionBoard.errors[5169427].message }}
  • Profile picture of the author Kezz
    That may be the case Johnny, but what they asked for is what they asked for, and the truth is that Istvan's method is the easiest way to achieve what they asked for.

    I'm sure they have their reasons for wanting to do things a particular way.

    And given they only want the old site to keep its rankings while they build up the new one, it seems to me that doing things the quickest and easiest way is a good choice.

    The old HTML files can always be deleted later once their new WP site is fully built and ranking.

    So just using a method that lets them get on with the job makes sense to me, so I can see why they would want to take this approach.
    {{ DiscussionBoard.errors[5169416].message }}
    • Profile picture of the author barq
      Originally Posted by Kezz View Post


      I'm sure they have their reasons for wanting to do things a particular way.

      And given they only want the old site to keep its rankings while they build up the new one, it seems to me that doing things the quickest and easiest way is a good choice.

      The old HTML files can always be deleted later once their new WP site is fully built and ranking.

      So just using a method that lets them get on with the job makes sense to me, so I can see why they would want to take this approach.
      Sorry, not trying to complicate all this ... I don't know what I want, but it's me who wants something, not the client. They are fine with anything we do, but I'm the one trying to figure out what the options are. (Though they DO want to keep their search rankings.)

      My ideal is that they use their existing site address (clientname.com) if at all possible. I do not want a visitor to see the old site if possible, as it is poorly written and is not setup for any conversion. I'd rather not build a separate new site (just because it could be confusing). Most new visitors should come from our promotions and new search rankings in the near future (we're marketers, btw, not site builders from a technical side ... the latter is pretty apparent I'm sure).

      Thanks again.
      {{ DiscussionBoard.errors[5169478].message }}
  • Profile picture of the author Istvan Horvath
    The "mess" means:
    - in the root directory (@ example.com) WP has to have 24 files and 3 directories;
    - as you described the old site, I dared to think all their html files might also be in the same root folder (people rarely organize their files neatly in sub- and sub-sub-folders);

    In my books having zillion different files in the same folder = mess. They will not conflict with each other but for a webmaster could be a nightmare to find anything in such a setup...

    As for getting different answers to your query:
    most of the time the wannabe WP experts
    a) don't read carefully the job description
    b) don't really know anything else about the web besides installing WP automatically with Fantastico
    c) they are not really familiar with the internal working of WP

    Happened even in this thread: most of the replies did NOT pay attention to this line:
    so we don't disturb the old site, but everything done from now on is done on the wp part of it
    Because if they did... nobody would have mentioned any redirects
    The site would need redirects ONLY if the old html files would have been replaced by WP created entries (posts and Pages).

    The simplest way to achieve what you described in OP (assuming I understood it correctly!) is the steps I outlined in my first reply.

    HTH
    Signature

    {{ DiscussionBoard.errors[5169432].message }}
    • Profile picture of the author barq
      Originally Posted by Istvan Horvath View Post


      The simplest way to achieve what you described in OP (assuming I understood it correctly!) is the steps I outlined in my first reply.

      HTH
      Part of the problem here, or most of it actually, is my ignorance. I apparently don't know enough to even ask the right questions.

      At my firm, we have great marketing people, most of our work is in marketing, we use sites in our marketing. Though our sites are extremely well-designed for marketing purposes (and range from basic to gorgeous depending on the market we're going after), we have always had the luxury of creating all sites from the ground up in WP.

      Maybe I need to regroup here, try to figure out the options as kindly given here and what we really "need." I appreciate all the feedback. Thank you.
      {{ DiscussionBoard.errors[5169518].message }}
    • Profile picture of the author Johnny Optimo
      Originally Posted by Istvan Horvath View Post

      The "mess" means:
      - in the root directory (@ example.com) WP has to have 24 files and 3 directories;
      - as you described the old site, I dared to think all their html files might also be in the same root folder (people rarely organize their files neatly in sub- and sub-sub-folders);

      In my books having zillion different files in the same folder = mess. They will not conflict with each other but for a webmaster could be a nightmare to find anything in such a setup...

      As for getting different answers to your query:
      most of the time the wannabe WP experts
      a) don't read carefully the job description
      b) don't really know anything else about the web besides installing WP automatically with Fantastico
      c) they are not really familiar with the internal working of WP

      Happened even in this thread: most of the replies did NOT pay attention to this line:

      Because if they did... nobody would have mentioned any redirects
      The site would need redirects ONLY if the old html files would have been replaced by WP created entries (posts and Pages).

      The simplest way to achieve what you described in OP (assuming I understood it correctly!) is the steps I outlined in my first reply.

      HTH
      sometimes you need to correct the client and tell them when they're trying to do something that doesn't make much sense - like trying to have two websites, one of which is very outdated.

      Also, looking at OPs latest reply - seems like they were just looking for the best way to handle the situation - which is probably 301 redirects.. or maybe the second option I posted - creating a new html/css design around the existing html files (really just preserving the copy and meta) and possibly using wordpress for an addon blog
      {{ DiscussionBoard.errors[5169539].message }}

Trending Topics