Welcome to the Q&A Forum

Hi CKerr, The only reason I would keep a blog off the website is if you do not want the blog to associate with the company directly but instead be an outside perspective. Or if you want to sell the blog one day. Beside that the blog should be on the site in my opinion. You can also refer to the forum below that talks about the same issue. http://moz.com/community/q/should-a-business-blog-be-on-a-separate-site-or-on-the-ecommerce-site-itself 301 re-directs are great for this occasion. Remember that the blogs ranking and trustworthiness will follow it with the 301 re-direct. All the best!

I agree with this. One thing you have to watch out for in using SASS is alienating older browsers or IE. With control like SASS comes problems also. Here lately I have seen a lot of cases where people use SASS and end up with too many selectors for IE to handle. Depending on the size of the site and how it is generated, this can be a real issue. Also, I would precompile and not compile at run time as well. It will add a processing overhead if you don't precompile.

That's probally the only answer I could think of. Thanks.

Is there a risk to no-indexing the listing pages? Thanks, Alan

Excellent. Good luck with your new site.

First off awesome site, can you add more content to your homepage, although it is awesome it doesn't have a lot of text where you can sprinkle in trigger niche key phrases and locations. I agree text messes up a design sometimes but maybe adding an intro paragraph somewhere on the homepage might help.

Turned out to be under functions.php under entry-date. Thanks everyone! Ruben

yep agree with both answers above i just wanna re-quote this "If the page is taking a lot longer (which your website doesn't) to load then this could influence the ranking"

I would suggest Prestashop, but I am not partial by any means. I develop exclusively with it and I am one of their moderators. Magento is also good too. I think one of the biggest considerations is what the store does in business, how many products, and what features do they need that are not in the default package of the e-commerce program. All platforms have good features, but everyone has features others do not.

That's good to hear and thanks for the input! The MOZ page grader told me that over 100 links was too many and so did a commenter from a separate post.  All clear now though.

Schema is designed to let you mark up individual items. For example, when a store has individual product pages, you should have the end page be marked up with data. As far as I know, there is no way to have multiple items maked up at the same time on one page. I'm sure you could code it that way, but I doubt it would be displayed or read correctly. Here are two resources that may help you: http://www.schema.org/Product http://www.schema.org/AggregateOffer

Hi Stephan, Before you spend _too _long on this, I'd make sure it's the best use of your time - regular images do work on retina displays and so you may have higher priorities. In many ways (simplicity, maintainability, design) the best route is to use retina-ready images throughout your site and serve them up to non-retina users as well. This typically results in better images for all and doesn't have to impact filesize too much (see this article about compressing larger images). The downside is that for certain kinds of images, the larger image will still have a much larger filesize and this can be a major speed issue - especially for those on mobile connections. Unless you have evidence that one or other effect (fuzzy images on retina or slow loading) is causing you problems, I would personally take an "if it ain't broke" approach. The complexity of maintaining two sets of images is a step too far for most websites in my opinion and I would tend to stick with regular images up until the point where high resolution displays are significant among your users and plan to switch to high-resolution images for all at that point. I hope that helps.

Yes, this will be totally fine. Google ignores bookmarks (#) like this, so Google will just see a redirect from http://www.mysite.com/shoes/red/description to http://www.mysite.com/shoes/red#desc. Good luck! Kristina

Gotcha. With a "normal" WordPress install it should be pretty easy to make a change to the tags. You just go into the editor and find the right .php file(s). Are you by chance running Thesis or Genesis? I know it can be trickier with those platforms. If not, it sounds like an issue with how this specific theme or customization was done. Because normally it should be pretty straightforward.

Hi There Just to clarify, by definition there are not doorway pages - doorway pages function by redirecting the user to another page than the one that was indexed. These would just be additional pages indexed that more or less show the same content as other pages. That aside though, it's good to still question their validity. What Etsy is doing is a bit more complex and I wouldn't compare your site to Etsy (unless it's going to be millions of pages with hundreds or thousands of categories). But Etsy is doing something slightly different than what you're describing for your site. If you want to create the silo effect you can simply "nofollow" any links you don't want them to continue crawling off of the homepage. And in general I would try to control everything through good architecture. Now, for Etsy, if you have two similar pages showing in search - one a /search/ URL and the other a /Market/ URL - that, in my opinion is not ideal. I would noindex the search pages that are also duplicated by static pages.

I agree with Federico, as long as it's readable to the search engine then you should not have an issue. You could try seo-browser.com to see if the menu is visible to search engines.

Hi Spencer, thank you for your reply. I have not changed domains, the site name is being generated by Wordpress in the settings so can easily be removed.  I think the H1 tags may be another debate, however will take it down to one per page. again most of the H1 are being generated by the theme rather than deliberate acts.

Good advice. When there's a potentially large impact (organic makes up such a large percentage of your traffic) you really do need to tread carefully. I've seen more than one site that rolled out sweeping changes in, shall we say an overly enthusiastic manner, and accidentally remove themselves from search completely! I would recommend doing some research and identifying the real low hanging fruit. What queries/topics/categories is there the greatest search opportunity. If you're already doing well for particular terms then there's not much scope for improvement and the impact of getting things wrong is worse. Can you look at particular pages that are performing badly. Look for landing pages for organic search traffic that have poor engagement metrics. This can identify poorly targeted keywords, or missing/poor content, miss-understood search intent etc. Make sure you document everything (with dates!). Don't try to do too much too fast. Small steady tests are safest and make sure you give your changes long-enough to see any impact. Make sure you have some kind of QA. Run checks before and after you make your changes. It's great if you can have some kind of check list. Watch out for unintended consequences. Are you tinkering with the live site or is there a development/deployment process you need to follow are there other people involved? If there is - stick to the process.

Perhaps even pay someone a small amount for a audit that does not come with it the chance of further work for that person. This is a really good idea.  First ask the guys complaining to point out real stuff that needs to be fixed or give you an example of a page with problems.  Then you have specific stuff to get opinions on. My bet is that these complainers are simply picky code monkeys who can't stand work that does not meet their compulsive tidy standards.   It bugs them that they have to "think:" about somebody else's code that is not formatted or written the way they like it. I am very confident that they would not like my code.

There is a vervices which called cms2cms, you could you it to convert your Drupal site to WordPress. I have more my blog www.nootheme.com/blog from Joomla to Wordpress blog.nootheme.com, which is the same Drupal to WordPress. Their service is quite professional.