Ongoing Duplicate
-
Hi Everyone,I'm having some on pa duplicate URLs issue .I have spoken to our web company and they have corrected the issue last week and I noted the amount of duplicates dropped significantly. Ive just checked t 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
-
Hi Pete!
Without knowing quite a bit more, I'm going to have to agree with Peter. I took a look at your account and the site, and I'm not seeing rel="canonical" anywhere on the site. If that is how your Web company initially solved the issue, it looks like it's since been removed.
I took a look at the crawl diagnostics CSV, and it looks like a lot of the issue is due to the ecommerce platform itself. This may be difficult to fix, but it also should be extremely harmful. In a lot of cases, though, it looks like there are very minor variations on the same URLs causing them to be picked up as duplicates—for example, a version of a URL with one capital letter is showing up as a duplicate version of the same URL without a capital letter. Rel="canonical" should definitely help with that.
Matt
-
Hi Pete
I would think the web company would have corrected the problem by adding rel="canonical" code to point to the correct page where duplicates occurred. The only thing I can think of is maybe the code has accidentally been removed.
You really need to check the source code of some of the reported duplicates to check to see if the canonical code is there.
Peter
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 -
Unsolved MOZ API for domain authority
I am using the MOZ API to check domain authority (DA). Recently, I noticed a discrepancy: the DA value retrieved via the API differs from the result on the MOZ homepage. Specifically, the API returns a DA of 10, while the homepage shows "NO DATA." Additionally, other services like Ahrefs report a DA of 0. I relied on the MOZ API's result when purchasing this domain and now feel misled. I would like to understand the exact reason for this inconsistency.
API | | Skys0 -
Unsolved Empty Response from API v1
Hi, I always receive a empty reponse from your API v1. Here ist my API call for further investigation:
API | | George4445
"http://lsapi.seomoz.com/linkscape/url-metrics/https://www.moz.com/?AccessID=mozscape-1234567890&Expires=1719916530&Signature=generatedsignaturecode" Reponse: {} Do you experience some problems with the api? Thank you very much
Regards George Shaylen0 -
Unsolved Generate an Access ID and API key
Hello, I can't generate an Access ID and API key for my account.
API | | OlegShavilov
I need a Links API and I'm ready to buy a paid subscription, but I can't do it. Link https://moz.com/products/mozscape/access
Redirected to https://moz.com/api/dashboard And i dont see any options for create Access ID0 -
Duplicate description error: one for meta one for og:type
I am getting the duplicate description error from Moz. I use both the og:description and . I am not sure if that is going to get me penalized by the search engines or my pages somehow discounted if I have meta description and og:description on the same page. What does Moz recommend? NOTE: for years I have followed this in the best practices format put out from other sources. Found at: http://webmasters.stackexchange.com/questions/52600/should-i-have-ogdescription-and-meta-description-together-on-every-page Short Answer: Use both! Long Answer: The OG stands for Open Graph which is apart of the Open Graph protocol of which works on platforms such as Facebook. The meta description element is for search engines such as Google, Yahoo and Bing. Since these are two separate tags that kinda do the same thing but they are designed for different types of platforms, one for Facebook and the other for Search Engines. The reasoning behind this is that the Open Graph protocal is more rich in what content can be feed to Facebook without scrapping the full page, think rich snippets. So images, description and more information is feed to Facebook via the Open Graph. Using both is a good idea.
API | | jessential0