Huge in crease in on page errors
-
Hi guys I’ve just checked my online campaign and I see errors in my crawl diagnostics have almost doubled from the 21<sup>st</sup> of October to the 25<sup>th</sup> of October going from 6708 errors to 11 599. Can anyone tell me what may have caused this?
Also I notice we have a lot of issues with duplicate page titles which seems strange as no new pages have been added, can anyone explain why this might be?
I look forward to hearing from you
-
Just noting that this discussion continues here:
-
Hi Matt,
I hope things are going well. I'm just following up on the duplicate page issue .I have spoken to our web company and they have correct the issue last week and I noted the amount of duplicates dropped significantly. Ive just checked today and i see it's back up (I'm following this up with our web company). Are you able to offer any insights as to why this problem seems to reoccur
I was of the understanding this is a permanent fix so once the change has been made, I cant understand why it then seems to reoccur?. Any insights would be much appreciated.
Regards
Pete
-
Well, it stands to reason that something must've changed is order to cause such a huge increase. Looking through the list of duplicate URLs, I'm seeing a lot that could be fixed by rel="canonical". There's enough of them that adding a canonical link to each would be a huge undertaking or require some careful coding. I'm wondering if this increase could've been partially caused by someone removing rel="canonical" from a lot of pages.
For example, I'm seeing a lot of this:
http://www.health2000.co.nz/shop/aromatherapy/lemongrass-essential-oil/P4494/C56
vs.
http://www.health2000.co.nz/shop/aromatherapy/lemongrass-essential-oil/p4494/c56
The only difference between those URLs is capitalization. The first, capitalized version is the one that appears on your XML sitemap. I'm not 100% sure why both versions would be appearing to Roger—it may be an issue with the CMS—but a rel="canonical" on the former pointing to the latter would solve that problem.
Now, that doesn't look to be the only issue, but it _is _a large one.
Let me know what you find out!
-
That's ok Matt. I've put those two questions to our web company, although I don't think any changes happened then, although I do know that they did work on the 27th of September. I m fairly sure in was rel =canonical in nature. I have asked them to confirm and will let you know in due course. As an aside why do you think the changes you mentioned would be of effect on our web site?
-
Hi Pete,
Sure thing. Sorry it's taken so long!
May I ask what, if any, changes were made on the site between the 21st and 25th of October? In particular, were there any changes made involving rel="canonical"?
-
Hi Matt,
Ive just had a look an I can now see the amount of pages, crawled on our site, is comparable to our competitors, which is great!
However the amount of on page errors is significantly higher. In particularly the amount of duplicate errors is about 10 000 which is the same amount we had, before our web company fixed this issue. Are you able to give me any feed back as to what's happened there?. Thanks again for your help with this!
Pete
-
Hi Matt,
No probs, I look forward to hearing from you
Regards
Pete
-
That's awesome Keri, thanks for following this up : )
-
Hi Pete,
Sorry for the delay! I just wanted to let you know I'm looking into it, and should get back to you shortly.
Matt
-
Hi Pete,
This is going to need a bit more digging than I can do from where I sit. I'm going to ask a colleague of mine to come in and lend you a hand. Thanks for your patience!
Keri
-
Thanks Keri here is our site http://www.health2000.co.nz we have recently asked our IT company to make amendments to offset the duplicates page issue.
The attached graphic shows the problem was in recline but now it seems to have come back. Any idea why that might be? I would have thought 301 redirecting would be an all or nothing solution. Also Ive asked our IT company and they have said this may take a while for google to indexes our page. If that is correct , how long do you think will take?
I’ve set up campaigns for our organisation and four of our competitors and note that on average we have had 6500 pages crawled where as our competitors have over 11000 pages crawled is there any reason why that might be? Thanks again for your help!
Pete
-
If you give him a 301 redirect it should help him, and the search engines, which is the most important part.
If you can touch base with your IT team and see if they changed something and ask them to change it back, that'd be a good place to start. If you can share your URL here, we can look at it and help direct you to the easiest way to fix things (if it is the www and non-www problem), or help identify the source of the problem.
-
Hi Keri,
Thanks for drooping me a line...... How do we make that cheeky little robot unfind one of them? : )
Cheers
Pete
-
Hmmm...my first thought is that if it's sudden duplicate content and doubling of errors is that perhaps Roger found both the www and non-www versions of the site?
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Unsolved Help with API Error: "Query Not Found" for a Specific URL
Hi everyone, I'm trying to retrieve data for a specific URL using the Moz API, specifically the data.site.metrics.fetch method. The URL I'm querying is: https://www.fiftyfiveandfive.com/ai-agents-marketings-new-means-of-production When I make the API request, I receive the following 404 error: { "id": "unique-id-testing", "jsonrpc": "2.0", "error": { "code": -32655, "status": 404, "data": { "key": "site_query.query", "value": "https://www.fiftyfiveandfive.com/ai-agents-marketings-new-means-of-production" }, "message": "That query was not found." } } However, when I check the URL in Moz Link Explorer, I can see that the page has a Page Authority of 23 and a Domain Authority of 36, but no backlinks or ranking keywords. What I'm Trying to Achieve:
API | | Chris_Wright1664
I’m attempting to retrieve metrics for this page via the API, but it seems like the API does not recognise the URL, even though it’s visible in Link Explorer. Questions: Why does the API return "Query Not Found" for a URL that is indexed in Link Explorer? Is there a way to request Moz to crawl or re-crawl this URL to ensure it's accessible via the API? Are there any additional criteria the API requires (e.g., backlinks, ranking keywords) before it recognises a URL? Additional Info: I’ve verified that my robots.txt file allows all bots, including Rogerbot. list itemThe page is included in the sitemap, and the URL is accessible without any restrictions. list itemI’d appreciate any insights on how to resolve this issue or steps to take so that the Moz API can retrieve data for this URL.0 -
Sitemaps and Indexed Pages
Hi guys, I created an XML sitemap and submitted it for my client last month. Now the developer of the site has also been messing around with a few things. I've noticed on my Moz site crawl that indexed pages have dropped significantly. Before I put my foot in it, I need to figure out if submitting the sitemap has caused this.. can a sitemap reduce the pages indexed? Thanks David. TInSM
API | | Slumberjac0 -
Sample API call error
from mozscape import Mozscape client = Mozscape('xxxxx', 'xxxxx') # Now for some anchor text results anchorResults = client.anchorText('http://www.moz.com') # Or for just specific columns anchorTermResults = client.anchorText('http://www.moz.com', cols=Mozscape.ATCols.term) this is the error I am getting **mozscape.MozscapeError: HTTP Error 403: Permission denied: fpalgkadgnamhiblgpakemcfeedbebdcfk** My python is installed in appdata/local/programs and it is an enterprise environment. Thank you in advance!
API | | Sreenivas.Bathula0 -
803 Crawl attempt error
Hello I'd be very grateful for any advice with this: My insights show I have an 803 error. Now, under "pages with crawl attempt error" the page in question is just an uploaded image to wordpress. However, above the graph it says: "We were unable to access your homepage, which prevented us from crawling the rest of your site. It is likely that other browsers as well as search engines may encounter this problem and abort their sessions." Does this really mean my homepage? or is the only issue with the image? I have noticed for the past 8 weeks I'm getting 1 crawl attempt error every 2 weeks (so when viewed weekly I have 1 error one week, 0 error the next week etc) Is this normal? Since receiving this 803 error, I have significantly dropped in SERPS for 3 key terms I was on page 1 for (now dropped to pages 3-4). Could this be related? I realise this is a bit specific, but thanks in advance. Cheers 🙂
API | | wearehappymedia0 -
Bulk Page Authority Tracking
Hi Is there a way in Moz to identify your page authority by landing page, possibly crawling the site and providing this in bulk so you don't have to go through and check each page? I want to track how my page authority for certain pages moves over time. Thank you
API | | BeckyKey0 -
Does on-page grader have an API ?
Hi, I would very much like to include the on-page grader output into my SEO tools. Is there an API for that? thanks James
API | | KMdayJob0 -
Moz Analaytics: What does this error mean? analyze_page_issues.crawl_error.name
The new Moz Analytics are terrific. However, I don't know what this error means. Could anyone offer me further insights? Thanks,
API | | jessential0 -
Batch URL Error 413
Hello, i am using the free mozscape api to get the domain and page authority of urls. i am batching the url as shown in the sample code however i have over 500 URL i need to check and when running the request i get the following: stdClass Object ( [status] => 413 [error_message] => Too many urls in batch. Batches must be less than or equal to 200 urls. ) When i change it to 200 urls the request works fine, now is there a way to enable me to batch all 500 urls at once? i did read that the beta api is capable of batching urls in one request : http://moz.com/blog/400-higher-throughput-mozscape-api-now-in-beta-and-seeking-testers Has this been implemented yet into the current api? Thanks
API | | pauledwards0