Welcome to the Q&A Forum

I am looking for advise on how to best start adopting schema.org for a real estate portal. Would like to get feedback and suggestions on my initial thoughts. Here are the obvious ones: 1. http://www.schema.org/RealEstateAgent(Thing > Organization > LocalBusiness > RealEstateAgent) Plan to use this to wrap realtors' information.We ll start with their profile page but possibly also on other pages with their information (e.g. listing page) 2. http://www.schema.org/SearchResultsPage(Thing > CreativeWork > WebPage > SearchResultsPage) This will mark search results pages where e.g. multiple listings of certain type in certain area are presented. 3. http://schema.org/WebPage(Thing > CreativeWork > WebPage) Pretty generic so we are thinking of using it on every page. e.g. significantLinks and breadcrumb objects seem like they could help in marking important links that will help search engines understand the site's information architecture better. I am not sure how to treat property listings Offer seems a good fit (http://www.schema.org/Offer) but not perfect. maybe it should be combined with place (http://www.schema.org/Place) http://www.schema.org/GeoCoordinates could also be used to mark each listing's location on the map. any thoughts or experiences you would like to share?

For an existing web site we are developing a local info web site section where each area would get a review and information about local bars and restaurants. The site manages areas in the following hierarchy: Country > Broader region > Perfecture > Municipality > Neighborhood e.g. Italy > Northern Italy > Lombardia > Milano > Center Local Info pages would exist for all the above levels so you could have a page for Italy as a whole, a page for Lombardia, and a separate page for the Center of Milano. On certain countries there are many synonyms especially in the Neighborhood level but also a few in the Municipality level. We would like to build a generic SEF url structure/pattern that would be able to represent the above and be as short as possible for the purpose of SEO. 1. the obvious solution would be to incorporate the unique identifier of e.g. www.example.com/local-info/Italy-10
www.example.com/local-info/Milano-12363
www.example.com/local-info/Center-789172 but this does not represent the hierarchy and does not include the interesting keyword of e.g. Milano when looking at the neighborhood level 2. Another option would be to include all levels e.g. www.example.com/local-info/Italy/Northern-Italy/Lombardia
www.example.com/local-info/Italy/Northern-Italy/Lombardia/Milano
www.example.com/local-info/Italy/Northern-Italy/Lombardia/Milano/Center But this would end up with large URLs 3. I am thinking of another solution which would include the current level and its parent at any page.  Not capturing the hierarchy very well but at least it includes the parent name for richer keywords in the url itself. www.example.com/local-info/Northern-Italy/Lombardia
www.example.com/local-info/Lombardia/Milano
www.example.com/local-info/Milano/Center 4. Or a hybrid where the first levels are always there and the rest are concatenated on a single segment www.example.com/local-info/Italy/Northern-Italy/Lombardia
www.example.com/local-info/Italy/Northern-Italy/Lombardia-Milano
www.example.com/local-info/Italy/Northern-Italy/Lombardia-Milano-Center any thoughts? thanks in advance

this has been asked before with not clear winner. I am trying to sum up pros and cons of doing a multilingual site and sharing the same domain for all languages or breaking it into dedicated subdomains e.g. as an example lets assume we are talking about a french property portal with an english version as well. Assume most of the current incoming links and traffic is from France. A) www.french-name.fr/fr/pageX for the french version www.english-name.com/en/pageX for the english version B) www.french-name.fr/fr/ for the french name (as is) www.french-name.fr/en for the english version the client currently follows approach A but  is thinking to move towards B we see the following pros and cons for B take advantage of the french-name.fr domain strength and incoming links scalable: can add more languages without registering and building SE position for each one individually potential issues with duplicate content as we are not able to geotarget differenly on web master tools of google potential dilution of each page's strength as we will now have much more pages under the same domain (double the pages basically) - is this a valid concern? usability/marketing concerns as the name of the site is not in english (but then people looking for a house in France would be at least not completely alien to it) what are your thoughts on this? thanks in advance

For a classifieds web site with medium/high turnover for the various listings: How would you deal with pages of removed listings? a) would you be "honest" and return a 404 since the listing is not available anymore? b) would you maintain historical data about deleted listings so that you can try and 301 redirect to a relevant search results page? c) would you keep the page alive (maybe add a noindex meta tag?) and show links to multiple relevant search results pages in an effort to strengthen internal linking?