Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
Hm - that's a bit outside the scope of what the Onboarding Specialists normally cover. They're experts at helping you get set up in Moz Pro and understanding the reports and data there, but they don't really touch on Moz Local at all.
I'm afraid we don't have any kind of internal Moz training program for our tools like what you're describing. Sorry about that! You can always check out our Help Hub to see if the information you need is there, but I'm afraid we don't have training programs.
Oh, how we wish that it could be mobile friendly! Our forum runs on a bit of a clunky system, though, so it'll need some pretty major overhauling to be mobile-friendly. We're working on optimizing our forum to make it better for all our customers and community members, so it's definitely something we've got in mind going forward!
Hi there - Tawny from Moz's Help Team here.
This is something we'd love to help you out with! If you write in to help@moz.com or use our Contact Form with your question, we should be able to help get things straightened out! 
Hey there! Tawny from Moz's Help team here.
Sounds like you might be running into a bug! We'd love to help you out here. If you write in to help@moz.com with the details of what's going on with your listings, we'll do everything in our power to help!
Thanks!
Hey there! Tawny from Moz's Help Team here.
Unfortunately, our tools only track the first 50 places of SERP results - beyond that, our tools don't track where your site is ranking. That's partially because results beyond the 5th page of results typically fluctuate a good deal, and so it would be really difficult to show your rankings accurately with any confidence.
I'm afraid there's no way to use our tools to find out where your site is ranking beyond the first 50 results. Sorry about that!
If you still have questions or need a bit of extra help, feel free to write in to us at help@moz.com and we'll do our best to sort you out!
In this case, it looks like it could be two things: a formatting issue, and the fact that these pages are canonicalized to themselves. Here's the canonical tag as it appears on http://thespacecollective.com/space-memorabilia/page/3:
href="http://thespacecollective.com/space-memorabilia/page/3/" rel="canonical" />
From looking at https://moz.com/learn/seo/canonicalization, it looks like that's sort of backwards from how canonical tags are normally formatted:
I think it's possible that if you switched the formatting around, you might see these duplicate title issues stop showing up.
Hey there! Tawny from Moz's Help Team here.
I'm afraid I have to be the bearer of bad news - we don't have an API that would allow you to export all your crawl issues from all your campaigns at once. The only way to export that data is to get the Crawl CSV from each campaign individually.
Sorry about that! If you've got more questions we can help with, feel free to shoot us a note over at help@moz.com and we'll do what we can to sort things out for ya!
Hi there!
There's nothing wrong with your listing - we're just currently unable to contact Bing and YP for listing details. This is happening for all listings. There's nothing much we can do to fix it from our end—we're working with those sites to establish a better data connection so that we can update Moz Local with their data accordingly.
If you hover over that exclamation point, it'll give a brief explanation. Sorry there's not more I can do to help you out, though!
If you have any further questions, feel free to shoot us a note at help@moz.com and we'll do our best to take care of it for ya!
Hi there! Tawny from Moz's Help Team here!
I think I can help you figure out what's going on with your robots.txt file. First things first: we're not starting at the robots.txt URL you list. Our crawler always starts from your Campaign URL and goes from there, and it can't start at an HTTPS URL, so it starts at the HTTP version and crawls from there. So, the robots.txt file we're having trouble accessing is khadination.shop/robots.txt.
I ran a couple of tests, and it looks like this robots.txt file might be inaccessible from AWS (Amazon Web Services). When I tried to curl your robots.txt file from AWS I got a 302 temporary redirect error (https://www.screencast.com/t/jy4MkDZQNbQ), and when I ran it through hurl.it, which also runs on AWS, it returned an internal server error (https://www.screencast.com/t/mawknIyaMn).
One more thing — it looks like you have a wildcard character ( * ) for the user-agent as the first line in this robots.txt file. Best practices indicate that you should put all your specific user-agent disallow commands before a wildcard user-agent; otherwise those specific crawlers will stop reading your robots.txt file after the wildcard user-agent line, since they'll assume that those rules apply to them.
I think if you fix up those things, we should be able to access your robots.txt and crawl your site!
If you still have questions or run into more trouble, shoot us a note at help@moz.com and we'll do everything we can to help you sort everything out.
Hey there, Steve!
I've just talked to the engineers who work on Open Site Explorer and Just-Discovered Links, and I can give you a bit of an update on our data sources, since our partnership with bit.ly has ended.
Currently, the only sources for JDL are some tweets, which we get through our Followerwonk credentials, and the feeds that go into Fresh Web Explorer. Unfortunately, that means that there's currently no guaranteed way of making sure your links end up in the Just-Discovered Links section of the tool. The tweets are a probabilistic sample, so something that's tweeted enough times by the right people would show up in that section eventually, but it's not a guarantee, and currently there's no way to gauge how long it would take to show up in that section.
I hope that helps to clarify - I'm sorry that I don't have an answer for how to get your links into that section!
Hi there! Tawny from Moz's help team here.
The best way to prevent our crawler from reporting duplicate content for pages you aren't concerned about and don't intend to change would be to block our crawler from these pages using the robots.txt file for the site. For example, it looks like most of the pages reported as duplicates include URL parameters, so you should be able to add a disallow directive for that parameter and any others to block our crawler from accessing them. It would look something like this:
User-agent: Rogerbot
Disallow: ?type
etc., until you have blocked all of the parameters that may be causing these duplicate content errors. You can also use the wild card user-agent * in order to block all crawlers from those pages, if you prefer.
Here is a great resource about the robots.txt file that might be helpful: https://moz.com/learn/seo/robotstxt
I'd recommend checking your robots.txt file in this handy Robots Checker Tool once you make changes to avoid any nasty surprises.
Let us know if we can help with anything else! Just drop us a line at help@moz.com and we'll do our best to get things straightened out for ya.
Hi there!
Since this involves sensitive account information, please write in to help@moz.com so that we can assist you further. Thanks!
It's not that the data is false, just that it's outdated. The last time our crawler crawled your site it found those callto links were returning a 404, but if they're no longer doing so, you don't need to worry about them. That's why I suggested a robots.txt disallow for those pages — if you know those pages are fine and you're not worried about them, you can just tell our tools to skip crawling those pages entirely so we don't report those issues anymore.
The rest of the data in the report should be as accurate as possible, given that the freshest data in our index is about 60 days old or more.
It will take our tools some time to pick up on recent backlink growth. With any luck, our tools will find and index those new links to your site that you've been earning, and you'll start to see your Domain Authority increase over time.
Hi there!
Thanks for reaching out, and sorry for the trouble! I'm afraid there's not much you can do to your site to prevent this issue - it has to do with our crawler.
Unfortunately at this time our crawler isn't compatible with Server Name Indication (SNI), which appears to be in use on your site. In general, SNI is a totally acceptable security configuration, but our crawler simply isn't equipped to be able to handle these settings.
The good news is that our team has been working hard on a new crawler that will support this configuration and this crawler is currently in its Beta phase. If you're interested in being a part of the beta testing, the link to the sign up page is here: http://goo.gl/forms/LCvL9Ix8JDHfbAvr1. Once you fill out that form, you will automatically be added into the Beta during the next round.
We will be rolling the new crawler out to all of our users once it's out of it's Beta phase, but I don't have an exact timeframe of when that will be at this time, as it's still being actively worked on.
In the meantime, I apologize for the inconvenience. If you have more questions or if there's anything else we can do to help, feel free to shoot us a note at help@moz.com and we'll do our best to sort things out for you.
Update from the Moz Support Team: Please read our update timeframes guide for avoiding delay.
Hey there,
Tawny from Moz's Help Team here.
Moz Local is a real-time service that instantly distributes your business listing data to both data aggregators and online directories. Each of our distribution partners has their own approach for processing new and updated listings on their platform. As part of our active listing management process, we continuously verify the accuracy of each listing down to the Name, Address, Phone Number and URL across our entire partner network. We don't consider your listing to be completely accurate until a customer would find it that way.
For most partners, new data is published within 4-5 days, and the majority becomes fully accurate within a few weeks. Given how closely we track accuracy, we have seen instances where some listings have taken as much as 8-12 weeks to become fully accurate. If you're noticing an unusual delay, please let us know at help@moz.com so we can take a look at your account and see if there is anything causing the delay.
If you claim a listing on a third-party site that isn't one of our direct partners, it's up to their system to determine how long it will take for your business information to become accurate there. You'll need to work with that third-party site directly.
Moz Local should sync that info for you automatically, as long as it's one of our partners! Here is a full list of the partners that are currently supported for US business listings:
Infogroup
Acxiom
Neustar/Localeze
Factual
Foursquare
Superpages (1st Tier)
Best of the Web (2nd Tier)
Citysearch
CityGrid
Insiderpages
Hotfrog
Bing
Apple
HERE
TomTom
NavMii
We focus on top-tier data aggregators with the idea that your data will naturally trickle down throughout the local search ecosystem. And you can see the big picture of the Local Ecosystem here: https://moz.com/learn/local/local-search-data-us
If there's anything else you need, just let us know — feel free to reach out to us at help@moz.com.
Message Input
Jot something down
Hi there! Tawny from the Help Team here.
The new ranking CSV functions a bit differently than the previous CSV. With our new rankings format, you can select any timeframe from your campaign history, with the default timeframe being three months (12 weeks) or the age of the campaign (whichever is shorter). When you export that data using the new ranking CSV option, it exports every update within that data set, so you will see multiple rows of data for each keyword if your timeframe encompasses any more than one week.
For example, if you choose the "Last 3 months" or default timeframe option from the calendar controls, you will get up to 12 rows of data for each keyword, as there are 12 weekly updates in that timeframe. You may get less rows of data for a particular keyword if the keyword was added less than 12 weeks ago.
If you want to limit the export just one row of data per keyword, you would need to choose dates within one week of an update. I hope this helps! Feel free to write in to help@ if you have any other questions or if there's anything that needs clarifying!
That sounds correct to me - if the number of Linking Root Domains associated with SearchEngineLand is 135,000, that's links pointing to SearchEngineLand's domain, not Moz's domain.
It's not necessarily that those links you're seeing with other tools but not with Moz's tools aren't relevant; it could just be that we haven't crawled and indexed the sites linking back to yours recently enough to include links from them in our index. If you're seeing 0 internal links reported, then that definitely means we haven't fully indexed your site, or if we have it was long enough ago that the linking data is no longer stored in the index, and we'll need to re-crawl and re-index.
The best thing you can do to get your site indexed by our tools is to search for it and the sites linking to it in Open Site Explorer. That should prompt our tools to visit your site and crawl and index it within the next few index updates.
Hi there! Tawny from the Help Team here. It looks like, from this screenshot, the referring URL does not contain the www - it could be that there's something not quite right about the redirect from http://premier-hd.com/ to http://www.premier-hd.com/ that's tripping up our tools.
I found this article about 406 HTTP status codes that might be helpful to you: http://www.hostingflow.com/http-error-406-not-acceptable/
It might be worth going over what you're seeing in your Site Crawl section with your web developer or whoever manages your web page for you. They'll be in a good position to help you address the issues that Site Crawl brings up.
I hope this helps! If you have more questions, feel free to write in to help@moz.com and we'll do everything we can to assist you!
Hi there! Tawny from Moz's Help Team here.
This is a great question! The reason you might be seeing different inbound link information for mywebsite.com and www.mywebsite.com is because of the way other sites link back to yours. Some folks might link directly to the root domain, mywebsite.com, while others might link to the www subdomain. In that way, the two links might have slightly different backlink profiles, and could turn up different results in Open Site Explorer.
Typically if a site has both a www subdomain and a root domain page for their homepage, they'll redirect from one to the other so that visitors only see one version of the page, and so that link equity gets passed along to the correct page. In those cases, Open Site Explorer will see the redirect and offer to analyze the main page instead.
Hope that helps explain! If you've still got questions or need some clarification, feel free to drop us a line at help@moz.com and we'll do our best to sort you out!
Using the disallow directive in the robots.txt file is probably the better bet as far as making sure that our tools don't crawl those pages and report duplicate page titles. I think the disallow directive is the way to go!
That said, I'm not an SEO expert, so it might be worth checking in with a web developer to see if they have different suggestions.
Hey there! Tawny from Moz's Help Team here.
You'll want to add a robots.txt file for that subdomain, and then add a Disallow command to that robots.txt file. So, using your example, you'd want a file like mediabank.mywebsite.org/robots.txt that had a Disallow command for any robots you don't want crawling that subdomain.
For all user-agents, that would look something like this:
User-agent: *
Disallow: /
That would stop any user-agents from crawling any pages on that subdomain.
I hope this helps! If you've still got questions, feel free to send us a note at help@moz.com and we'll do our best to sort things out for you.
Hey there! Tawny from Moz's Help Team here.
Unfortunately, there's no way to change the URL a campaign is tracking once the campaign is started. If you need to track a new domain, you'll need to archive or delete a campaign to make room for the new one.
I hope that helps! If you still have questions, feel free to write in to us at help@moz.com and we'll do our best to help with any and all issues you might run into.
Hey there! Tawny from Moz's Help Team here!
The only way to make bulk checks in Open Site Explorer would be to use our Mozscape API to do those bulk checks! You can read more about the API over in our Help Hub pages, here: https://moz.com/help/guides/moz-api/mozscape/overview
It's pretty technical, so you'd likely need a web developer to help you decipher the results you get back.
I hope this helps! If you've got questions about the API or how to use it, feel free to send us a note at help@moz.com and we'll sort things out for ya!
Hi there! Tawny from Moz's Help Team here.
It looks like you've already got some good answers here, but if you're still looking for clarification or a bit more help, feel free to write in to help@moz.com with the details of your campaign and we'll do what we can to sort things out!
Hey there! Tawny from Moz's Help Team here.
The reason you're getting those 804 errors is just like Joe Stoffel has suggested — SNI settings and our old crawler's inability to handle SNI compatibility settings. The new crawler, which populates data for the Site Crawl section of a Moz Pro campaign, doesn't have this issue — we've developed a solution for it and the issue is solved for campaign crawls. It's just out Crawl Test tool that still uses our old crawler and can still run into those errors.
Unfortunately, there's not much of a workaround I can offer for this one; the Crawl Test will continue to have those 804 errors and not be able to crawl any further into your site. I would recommend setting up a Moz Pro campaign for any sites you need to see Site Crawl data for.
I hope this helps! If you still have questions, feel free to drop us a line at help@moz.com and we'll do our best to sort everything out with you.
Hey there!
It looks like someone has already helped you out here — the only invoice I see on your account has already been refunded. It typically takes a few business days to see the funds returned to your account, so keep an eye out!
If you still have questions, feel free to reach out to us at help@moz.com and we'll do our best to sort everything out.
Hey there! Tawny from Moz's Help Team here. I think I can help explain why you're not seeing all the same links you might see with other tools. It has to do with our Mozscape Index, which powers Open Site Explorer.
Open Site Explorer and the Link Analysis page of campaigns are both tied to our Mozscape index, which tends to update roughly once a month.
Just a few points on how we compile our index:
The idea here is that we're focusing on the highest-quality links we can find, coming from the most prominent pages of authoritative sites. So, while you may not see every link for a site within our index, we're aiming to report the most valuable ones available!
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 reasons - including the crawl-ability of sites, the number of inbound links to them, and the depth of pages in subdirectories. This biases our tool slightly in favor of newer links; Open Site Explorer only caches older links for about 180 days, so unless the tools re-crawl and index those links, they may fall out of our index after a while.
You can see our most recently updated schedule here as well as some more technical metrics on our Mozscape API Updates page. You can also see when the last and next updates happened on the Open Site Explorer (OSE) homepage at any time.
Since Moz focuses on quality of links over quantity, we are always focused on the most relevant links to display to our users. It's possible that Moz's index will leave out some of the lower-quality (non-link juice providing) links out of our index because of this. So, that might explain why you may see some discrepancies with what other tools may be showing.
I know this is a ton of information, so if you have any questions or if I didn't make anything clear enough, please don't hesitate to ask! Just shoot us a note over at help@moz.com and we'll do our best to help you out.
No problem at all! Happy to help!
Hey there! Tawny from Moz's Help Team here!
If you need to delete your account, please write in to us at help@moz.com and we'll help you out. Thanks!
Hey Neil,
We used to use bit.ly links for this purpose, but we've switched over to feed.ly links. When I said that both a) and b) would help to get your links indexed and picked up by Open Site Explorer, I suppose I meant that a two-pronged approach would be best. I would recommend doing both!
Hope that helps! If you've got more questions, feel free to drop us a line at help@moz.com and we'll do our best to help!
Hello there! Tawny from Moz's Help Team here.
So, when a Moz Pro Campaign is connected to Google Analytics during creation, Google allows us to backfill data for 12 data cycles (i.e. 12 days, 12 weeks, and 12 months.) However, if GA is connected after the Campaign is already running, they will only allow us to collect data going forward from the date of the connection.
I'm afraid the only way to see the historical traffic data in a Campaign for this site would be to create a new Campaign and to connect to your GA profile during the set-up process. Unfortunately, we aren't able to transfer data for the other Campaign sections from the Campaign that you currently have running for the site, so the new Campaign would not include the data you have already been tracking historically for the rest of the Campaign.
Feel free to reach out to help@moz.com if there's anything else we can help with!
Hey there! Tawny from Moz's Help Team here!
Unfortunately, there's no way to go back and view the previous week's Site Crawl data. If you need to see each week's data after the fact, it would be a good idea to set up a Custom Report with Site Crawl modules and set it up to run weekly. That way you'll get a report each week sent to you that includes your Site Crawl data, and you'll be able to keep those reports as a historical record of previous week's data.
I hope that helps! If you've still got any questions, feel free to shoot us a note at help@moz.com and we'll do our best to help you out.
That's one of the most common reasons for losing connection to a GA profile, yes. Those tokens expire or are revoked, and as a result we lose access. 
Give me a shout if there's anything else I can help with!
Hi there! Tawny from Moz's Help Team here.
Thanks for writing in! I'm afraid there's no way to pause a subscription at the moment. That said, the best option we have right now is for you to go ahead and cancel your subscription — you can do this from https://moz.com/subscriptions
In fact, cancellation works a lot like pausing — we archive all your Campaigns so they'll stay safe and sound while you're away. We don't continue to gather new data while your Campaigns are archived, but we keep all your historical data for around 12 update cycles. For weekly updates, that'd be 12 weeks and 12 months for monthly updates. A couple notable exceptions would be for rankings and link histories, which we'll keep forever!
Then, if and when you decide to give Moz Pro another shot, it's easy to unarchive those Campaigns and start gathering data for them again. At that point, you'd just head back to the "Manage Campaigns" screen, choose "Archived Campaigns" from the dropdown at the left, and you'll be just a few clicks away from getting up and running again!
I hope this helps! If you've still got any questions, just feel free to reach out to us at help@moz.com. Thanks!
Hey there! Tawny from Moz's Help Team here.
Whoops! Oh dear. That's an error in our guide. So sorry about that! The URL will take you to the page in question that's ranking for that keyword, not to Open Site Explorer. We'll get that page updated shortly!
So sorry for the confusion there!
If the reauthorization worked, you should see a success banner. You may need to refresh a couple of times in order to see the correct profiles and successfully reconnect.
Hi there,
Tawny from Moz's Help Team here. I can confirm that we are getting a 500 response from your server. Unfortunately, other than making sure you're not blocking AWS and that Rogerbot is allowed, I'm not sure what else you can do. Have you checked over your server logs with your web developer to see if you can find any additional information as to why your server responded with a 500 error when we tried to crawl your site?
If you've got any more questions, feel free to reach out to us at help@moz.com and we'll do our best to sort things out!
So glad it's working for you now! Nice detective work on sniffing out that solution, too! High fives all around.
Success! So glad you were able to get that hooked up. Have a great rest of your day!
Pages canonicalized to the same page aren't duplicates, but their titles may still be. Canonicalization only affects the content of the page, not the title; the pages can still be resolved separately in the browser, so their titles may still be duplicates of one another.
If there are pages you don't want to surface in search results, you can noindex, follow those pages to prevent them showing up.
Sorry if my previous answer was a bit confusing! Hope this helps! If you've got more questions, feel free to write in to help@moz.com and we'll do what we can to sort things out for ya!
Hey Kevin! Tawny from Moz's help team here.
I'm not 100% sure on this — I'm not an SEO, just a helpster — but I think 301 redirects are probably your best bet for passing on link juice. According to our resource on redirection, which you can find here: https://moz.com/learn/seo/redirection
301 Permanent Redirects pass on between 90% and 99% of their link equity (ranking power), so that's probably the kind of redirect you should use if you're hoping to pass link juice from one page to another.
I hope this helps! Maybe one of our illustrious community members can chime in here and weigh in on the topic, either to confirm what I've said or to demonstrate that I'm wrong. If you've still got questions, feel free to write in to us at help@moz.com and we'll do our very best to answer all your burning questions.
Hey there! Tawny from Moz's Help team here.
It looks like our community members have already offered some helpful advice here. I just wanted to add that we have the Mozscast (http://mozcast.com/), which is a measure of how turbulent things are in the SERPs. Looks like the "weather" lately has been pretty stormy, so lots of changes are taking place.
As others have already pointed out, it's hard to pinpoint WHY the rankings are changing, but there are a few things to keep in mind as you go along.
There are a ton of factors that go into ranking well, so your best bet is to be very diligent and attentive to the issues affecting your SEO. There are a few things to keep in mind as you go along:
I hope that helps you out a bit! If you've still got questions, feel free to reach out to us at help@moz.com. Cheers!
Hi there! Tawny from Moz's Customer Support team here.
I think it's pretty unlikely that we'll change the behavior of our crawler, unfortunately.
When we crawl your site we adhere to the “Politeness Policy” so that we don't impact the performance of your site:
We do this by dynamically controlling (throttling) the number of URLs that we crawl per minute, per hour. If we determine that your site is responding slowly or there are network issues, we extend the crawl intervals. Following the Politeness Policy protects your site from excessive load.
Roger Mozbot schedules and crawls thousands of sites a day.
Other items can affect the crawl, including changes to your site, network conditions, how your site crawl is scheduled compared to other crawls, etc.
Hope this helps!
Hey there! Tawny from Moz's Help Team here.
Shoot! You've already ruled out the only suggestions I have: either using the canonical tag to tell search engines (and our crawler) which version of the page has the best info on it and should rank highest, or add in some extra content on each page to differentiate them from one another.
Our tool has a 90% tolerance for duplicate content, meaning it'll flag anything that's 90% similar or more at the source code level, not just the viewable text on the page. In order to stop getting these duplicate content issues, you'll need to find some way of making each of those pages different enough from one another that they're not fighting each other for rankings anymore.
If you don't want to add a canonical tag or more text to the pages, the last option would be to just Ignore the issue in your Dashboard. If you do that, we'll stop reporting duplicate content issues for those pages going forward—we'll just ignore that class of issue for those pages. It won't fix the issue for search engines, but it would help you clean up your Moz Pro Dashboard.
I know that's not super helpful—I really wish I had some better advice to offer! Maybe one of our esteemed community members will have a suggestion for you that'll do the trick. If you want to follow up or have more questions for us, feel free to reach out to help@moz.com and we'll do our best to answer all your questions.
Hey there! Tawny from Moz's Help Team here.
For really specific, in-depth questions about why a Campaign isn't working quite right, it's really easier to help you out through our normal support channels. Please write in to us at help@moz.com with all the details of what you're seeing, and we'll do our very best to help you figure things out.
Thanks!