So, we're a service where you can book different hairdressing services from a number of different salons (site being worked on). We're doing both a male and female version of the site on the same domain which users are can select between on the homepage. The differences are largely cosmetic (allowing the designers to be more creative and have a bit of fun and to also have dedicated male grooming landing pages), but I was wondering about duplicate pages. While most of the pages on each version of the site will be unique (i.e. [male service] in [location] vs [female service] in [location] with the female taking precedent when there are duplicates), what should we do about the likes of the "About" page? Pages like this would both be unique in wording but essentially offer the same information and does it make sense to to index two different "About" pages, even if the titles vary? My question is whether, for these duplicate pages, you would set the more popular one as the preferred version canonically, leave them both to be indexed or noindex the lesser version entirely? Hope this makes sense, thanks!

Hi, I do most of the current copy for our blog which you can find here http://appointedd.com/blog/ I believe having a regular blog structure with a mix of irregular ad hoc posts to go in around these. So, for this blog, I write an article on "Beauty Industry News" every week. Now, I don't want to use the same title for each post, so I've peen butting in the date after each one i.e. "Beauty Industry News - 24/04/13". Is this best practice or is there a better way of naming regular posts? Thanks in advance!

Hi! Do you think it better to: a) have all archives crawled (date, time, category etc.) even though they create duplicate content,. or; b) disable crawling of all archives? Ideally, I'd like to set up just excerpts in the archives and have a unique intro for each, but I'm having trouble doing this just now so was wondering which is the smarter option in the meantime? Thanks very much!