1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Websites all are published in /home

Discussion in 'Web Presence Builder' started by wagaboom, May 21, 2012.

  1. wagaboom

    wagaboom New Pleskian

    10
     
    Joined:
    May 21, 2012
    Messages:
    2
    Likes Received:
    0
    I am running Web Presence Builder on my Plesk server and allow some of my clients to access it.

    However: i found that those pages are NOT being indexed by Google.

    I think one of the reasons must be, that all site are published to http://www.whateversitename.com/home/

    I could imagine that the /home is a problem.

    What do you think and HOW can I change this to publish those sites on root level (http/www.whateversitename.com/) ?

    Thanks for your help.

    Alexandra
     
  2. dave-ha

    dave-ha Regular Pleskian

    17
    85%
    Joined:
    Feb 21, 2012
    Messages:
    201
    Likes Received:
    0
    Location:
    Switzerland
    Did Google visit?

    Hi Alexandra,

    Did Google crawl these sites? I could imagine that Google is not aware that those sites exist and therefore has not visited them yet. Check the server log for visits of Google bot. If it did not visit the sites then add backlinks or initiate Googlebot through Google's Webmaster Tools. Those tools also can help you to find crawling issues.

    Best regards,
    dave-ha
     
  3. custer

    custer Administrator Staff Member

    33
     
    Joined:
    Apr 24, 2007
    Messages:
    593
    Likes Received:
    101
    Hi Alexandra,

    Thank you for reporting this, we'll check into this issue.
     
  4. wagaboom

    wagaboom New Pleskian

    10
     
    Joined:
    May 21, 2012
    Messages:
    2
    Likes Received:
    0
    did you find out anything?
     
  5. custer

    custer Administrator Staff Member

    33
     
    Joined:
    Apr 24, 2007
    Messages:
    593
    Likes Received:
    101
    Hi,


    I can confirm that there's a problem with website home page always having a URL with page slug in it. Google doesn't like the fact that the same page/content has two addresses -- http://domain.com and http://domain.com/home. We are planning to fix this issue in 11.1. The question we have at the moment is whether somebody needs current behavior (two addresses for the same page) for some reason. I would appreciate if you can share your opinions on this topic. Thank you!
     
  6. hugosnel

    hugosnel Basic Pleskian

    15
    60%
    Joined:
    Dec 5, 2011
    Messages:
    43
    Likes Received:
    0
    home page and navigation restrictions

    home page and navigation restrictions ...Yes I suggest the two in one go because the seem related.

    1 I agree that the /home is messy and not useful.
    2 How do you construct multi languanguage sites , more or less identical?
    I prefer having their roots in /english /french /german etc
    The problem I run into now is that my site has three levels of navigation and a fourth level (language) is not possible in the actual version of wpb ..... in general this is a real handicap!
    I am working around this problem using in line links.
    A mutilanguage version will be online at the end of the day:
    http://essaouira.in-folio.com/home/
     
    Last edited: Nov 15, 2012
  7. custer

    custer Administrator Staff Member

    33
     
    Joined:
    Apr 24, 2007
    Messages:
    593
    Likes Received:
    101
    Hi hugosnel,

    For multi-language websites I suggest you to use subdomains. For example, your main website could be hugosnel.com, and your Spanish website could be es.hugosnel.com. These are two physically separate websites that link to each other and are basically the same except language (you can use snapshots to sync content between these sites).

    The reason why WPB doesn't have a proper multi-language website support yet is that this feature is very complex and difficult both in implementation and for user management. That's the reason why many powerful CMS (like Typo3, etc) don't have multi-language website support out of the box. If we find a way to make the user experience clear and easy, we'll add this feature right away. Let me know if you have any ideas of how it would be easy and understandable for you as a website admin to manage a multilanguage website. Thanks!
     
Loading...