Always glad to help, Hugh!

Hi Hugh,

Regarding the duplicate titles, we only report that if the titles are 100% similar. It may not be considered a huge problem in terms of SEO, but we do still think it is important to report on it as it can have some effect on the pages competing against each other.

As for the duplicate content, campaigns have a 90% tolerance for duplicate content, which means they will flag any content that has 90% of the same code between pages. This includes all the source code on the page and not just the viewable text. Although the pages in question may appear to be different on the front end, they are actually duplicates based on this percentage (at least the example URLs I checked in your campaigns.)

You can run your own tests using this tool: http://www.webconfs.com/similar-page-checker.php

We don't know what standard Google uses, but it's safe to say they are a bit more sophisticated than us - so you might be okay in this regard as long as you have a couple hundred words of unique text per page. Google won't say how much duplicate content is too much, so we think it's better to be safe than sorry.

Hey Hugh,

I took a look at your crawl diagnostics and we aren't actually reporting the homepage http://venture.photo as missing the meta description. It looks like most of the pages with that error are the /tag/ or /category/ pages, http://venture.photo/tag/family-shoot for example. Looking at a few of those pages, I do see that we are correctly reporting that they are missing the meta description: http://www.screencast.com/t/bYlGJRw9

Some of the pages do have the code meta property="og:description", but our crawler only recognizes meta name="description", so we would not count the meta property as a meta description in our crawl report.

I hope this helps! Please let me know if I can help you with anything else.

Chiaryn
Help Team Ninja

Always glad to help!

Hi there!

I took a look at your campaign and it seems that we crawled a lot more page of the site this week in general than we did the previous week. Two weeks ago, we crawled about 500 pages and this week the crawl jumped up to 2800. So it isn't that there are more duplicate pages on your site now, it is just that we are able to crawl more pages now than we were before, which led to us finding even more duplicate pages that had not been reported before.

As for why we are crawling so many more pages, it could be for a few reasons. If you made changes to the links on your site, the page hierarchy of the site, or if you remove noindex tags or updated the robots.txt file for the site, those things could all affect how we are able to crawl the site.

I hope this helps! Please let me know if I can help you with anything else.

Chiaryn
Help Team Sensei

Hey There!

I responded to your support request with more information on how we view canonicals. I hope it was helpful!

If you can send me examples of pages that you believe are being counted incorrectly, that will help me determine if there is an issue with the crawl or if the pages correctly fall into how we determine duplicates based on the canonical tags.

I look forward to hearing back from you there soon!

Chiaryn
Help Team Sensei

Update from the Moz Support Team: Please read our update timeframes guide for avoiding delay.

Hey Arthur,

Thanks for reaching out and your interest in Moz Local!

In terms of our direct partners, when you publish a listing using Moz Local, the time it takes our partners to update the listing really depends on how long it takes them to accept the data we push to them and update the information across their servers. This can be anywhere from 1 to 8 weeks but generally is completed by around 4 weeks.

As for our Check Listing tool, that data is pulled live each time a check is run, so we display exactly what the different directories (including our partners) are providing through their backend APIs. It can take those directories up to 8 weeks  (with an average of about 4 weeks) anytime you update the data through the directories and engines directly.

I hope this helps! Please let me know if I can help you with anything else.

Chiaryn
Help Team Ninja

Hey Julie,

Thanks for writing in and sorry for the confusion. Our link index is not created using our crawl test or campaign crawls of a site. The index is actually a completely separate database compiled by crawling the web and following the links we find there. Your site will only be included in Open Site Explorer if we find links to your site from outside sources.

Just so you know, here's how we compile our index:

• We grab the most recent index.
• We take the top 10 billion URLs with the highest MozRank (with a fixed limit on some of the larger domains).
• We start crawling from the top down until we've crawled 90,000,000,000 pages (which is about 35% the amount in Google's index).

Therefore, if the site is not linked to by one of these seed URLs (or one of the URLs linked to by them in the next update) then it won't show up in our index. Most new sites and links will be indexed by our spiders and available in Mozscape and Open Site Explorer within 60 days, but some take even longer for many of reasons, including the crawl-ability of sites, the amount of inbound links to them, and the depth of pages in subdirectories.

As Pixelbypixel mentioned, Majestic SEO and Ahrefs often have a larger index than we do because their tools are exclusively focused on links, while we have a wide variety of tools with an overview of a site rather than on one specific aspect of SEO or marketing.

I hope this helps! Please let me know if I can help you with anything else.

Chiaryn
Help Team Ninja

Hey Dan,

Unfortunately, our crawler is not able to access password protected content on your site. If you create a staging subdomain that is not password protected, you could use the robots.txt file to allow rogerbot and block other crawlers, but I'm afraid our crawler will not crawl anything that a normal search engine crawl would not be able to crawl so we cannot crawl password protected pages.

I hope this helps.

Chiaryn

Hey Carmelo,

It looks like you are encountering a bit of a different issue. It sounds like you are receiving the error when you try to connect with Google Analytics rather than when you try to make an API call. I'm really sorry about that.

Google is currently having some authentication issues on their end. The issue seems to be clearing up and we are monitoring the issue as it resolved. If you are still encountering the issue, please contact our Help Team here: http://moz.com/help/contact for further assistance.

Chiaryn