Dates on Opensite Explorer?
-
Hi All,
I was wondering if there is any chance of getting dates out of OpenSiteExplorer, either via the API or the web menu.
This would be hugely useful for competitor research to see how strategies were shifting over time, etc, and I can't imagine it would be that difficult on the development end: just time stamp when writting a new link/domain to the database.
Any chance I am missing this, or getting this?
Brian
-
Hi Brad,
Yeah, GWMT is great for domains I control, but having this for competitor domains would be fantastic.
Thanks!
-
It's probably something that the Moz dev team can look into. I know that GWMT keeps track of when they first crawled a new link to your site, and you get get it by exporting your list of links.
-
Thanks, Brad,
Thats useful. So then the logic would be:
- If the link already exists in the database import the old crawl date
- else, input the current date
That would be, I would think, pretty simple from a development standpoint and make for (in my opinion) much more robust intelligence, allowing you to look at how link velocity and strategy evolve over time, sort for new prospects, etc.
Does it seem useful to anyone else?
-
My understanding is that the Mozscape index is unique every time it's generated. Each time a new index comes out, it is a new craw of your inbound links, and the old index is trashed. At MozCon, it was alluded to that the development team was looking into ways of determining which pages are updated less frequently, and re-crawling those pages less often - allowing the Mozscape index to complete faster and use less resources.
In short - everything you see in OSE was crawled recently (in the 30 days leading up to the last index update).
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 Can links tracking lists help to crawl high authority backlinks by Moz 2024
Hi i am create a link tracking list for my domain, but Moz don,t crawel after 2 weeks completed.
API | | Rawaluij1 -
Unsolved Regarding Moz API token password update
Hi, In March we have updated password for MOZ API and used in our application it worked, but currently the updated password is not working and in the MOZ site the old password is shown and its active. We are using Legacy username and password.
API | | NickAndrews
We see that 5 tokens can be added for API, if we add 2 tokens both will be active.
We are currently using free services. Please help us resolve this issue.0 -
Unsolved "The account does not have access to that quota" - API v1 URL Metrics
Hi! On one of our servers we get the message "The account does not have access to that quota" when pulling data for v1 URL Metrics endpoint in the API.
API | | aheitzman
This only happens on one specific server, others have worked flawlessly. Any idea of what might be going on? Thanks0 -
How can I get "Date First Seen","Date Last Seen" and "Date Lost" from the API?
"Date First Seen","Date Last Seen" and "Date Lost" are columns in the CSV exported from LinkExplorer's Inbound Links page. How do I get that data from the API?
API | | StevePoul1 -
Keyword Explorer
Hope you can help me with a query on 'Keyword Explorer' Currently, I'm able to use only one URL per search.
API | | Alpine9
Is there a way to search keywords for multiple URLs?1 -
January’s Mozscape Index Release Date has Been Pushed Back to Jan. 29th
With a new year brings new challenges. Unfortunately for all of us, one of those challenges manifested itself as a hardware issue within one of the Mozscape disc drives. Our team’s attempts to recover the data from the faulty drive only lead to finding corrupted files within the Index. Due to this issue we had to push the January Mozscape Index release date back to the 29<sup>th</sup>. This is not at all how we anticipated starting 2016, however hardware failures like this are an occasional reality and are also not something we see being a repeated hurdle moving forward. Our Big Data team has the new index processing and everything is looking great for the January 29<sup>th</sup> update. We never enjoy delivering bad news to our faithful community and are doing everything in our power to lessen these occurrences. Reach out with any questions or concerns.
API | | IanWatson2