Welcome to the Q&A Forum

Wow, that's awesome Joy! Thank you so much for reaching out and helping! Nothing more infuriating to me than a half completed job, and you were pivotal in getting it done. Thank you so much!

Is there a chance to use Moz API in Python? According to the pricing of Moz maybe it is free?

What you ideally want to do is set up the mobile site as a standard site.  Then utilize javascript to call each page in an order defined by the users actions with dynamic loading. This has two benefits: SEO and SERP.  The pages will be indexed as they should.  If you have one huge page you are still limited to the 2 or 3 keywords as always.  When you see a good infinite scroll website it is not one page, it only looks this way due to JavaScript calling additional pages at triggers that have been set. No JavaScript graceful fallback (or fallforward as it is actually the native state).  If you have one page, lazy loading with JavaScript and they do not support it then you have 2,000 pages worth of images loading at one time which is otherwise known as a bounce. You will want to build out the site with no consideration to the infinite scrolling (except in design ie. tile-able backgrounds for a smooth non stop flow) then apply the script after you have a logical site structure using silo'ed categories.  Google bot, Google bot mobile and users who do not have JavaScript will all have a useable site and the SERPS will rank pages as they should. Tip:  Keep any page wide bar or graphic styles in the header or the footer of the page.  You will normally only call the content or article portion of the page to the infinite scroll so you have a non-stop flow on the site. Hope this helps I know your not using WordPress but I am assuming you are using some sort of templated PHP script for a 2K product store.  This WP plugin is pretty easy to understand and what I first used to grab the concept.  Also, if wanting to go a more Pinterest route look into Masonry JavaScript.  http://www.infinite-scroll.com/

It turns out it was an issue with schema.org tagging overwriting any opengraph or the actual HTML attributes. The itemscope "name" property was just set to the company name. I had a LocalBusiness schema.org markup on the page which takes precedence on Google+.

I believe we had a couple of blips earlier with our crawler. Your best bet for support is to go to http://www.seomoz.org/help and use the red "contact our help team" button -- the help team will get back to you on Monday and help you work out what's going on and find a fix.

That works but you can also use the SERP Control Panel and select US

They may look at the following (just a guess): follower to followed ratio number of people followed against length of time account has been running number of updates in relation to followed/follower numbers whether they have a naughty profile picture

Based on the below two facts, I would put the snippet length for your videos in your sitemap: Google can crawl the videos and may know that the actual length doesn't match what you are saying it does. Google has a published policy for newspapers that have paywalls and don't allow free full access at http://googlenewsblog.blogspot.com/2009/12/update-to-first-click-free.html Basically, "We will crawl, index and treat as "free" any preview pages - generally the headline and first few paragraphs of a story - that they make available to us. This means that our crawlers see the exact same content that will be shown for free to a user. Because the preview page is identical for both users and the crawlers, it's not cloaking."