What is Moz's Error.aspx?aspxerrorpath HTTP Status 302 error message?
-
Hi,
I am not sure what this error message is: "Error.aspx?aspxerrorpath". It immediately follows pages that are given at 302 status in Moz's crawl report.
The same pages have never had this error before:
| http://www.homedestination.com/news/2013/Minneapolis-home-price-appreciation.html |
| http://www.homedestination.com/mortgage-worksheet.html |
| http://www.homedestination.com/foreclosure-eligibility.html |
Each page has a 100% score with WC3. Could you give me more insight as to what Moz may suggest I do to give the page a 200 HTTP status as before?
Thanks.
-
Thanks for your superb help walking through this.
I am thankful for the random error as I learned more valuable information about the Moz platform.
-
Awesome to hear!
As for other tools to measure traffic drops we don't have any but I recommend creating a new post on the Q&A as our community may be able to provide some tips
-
Several test now and no sign of the error again.
-
The latest Moz crawl returns a normal http status for the four pages.
I can only conclude that this was a one-off misread "somewhere".
As my traffic has dropped and I cannot determine just why, is there another tool or Moz resource that may help me gain better insights?
Backlinks to the site and social shares are both up.
-
Which highlights how very helpful the Moz Crawl Test Tool is. I use it often. I really appreciate Moz offering this tool.
Waiting for the new results....
-
Hi Jessential
Changes to a page don't always affect HTTP requests. In some cases these errors can be ignored as they can be a one time occurrence. The best way to isolate any web server issue is if the errors are consistent. If you do not see the errors in the latest crawl then you are all set. If the same errors appear then it will have to be investigated by the hosting provider. The only way for our crawl to create entires in a report is from a server response. If our crawler fails, there will not be a report available which is something we would address on our side. The crawler is working as intended.
-
Hi David,
The web developer cannot find any cause nor has made changes on the pages that would generate this intermittent error.
The web host says there is no recognizable cause for the error on the server, that MOZ is a third party tool, and that we should ask them (you).
With a fresh day ahead and a cleared Moz cache, I am rerunning the Moz crawl test tool.
-
The link is just an example to show you how the error is from a web server so it's not specific to your issue. Our crawler cannot generate error codes, only webservers can, so any codes or paths you see are what was returned to us during the crawl. You would have to reach out to your web developer or hosting provider to check your server configuration for any errors that appear in your reports.
-
The link provided relates to a 404 error. All four of these pages exist and have never had a 404 error.
Wish we could find some answers as to why Moz threw this "Error.aspx?aspxerrorpath" this one time out of many successful Moz app crawls on the same page.
-
Anytime Jessential
For the "aspxerrorpath" error is something returned by the web server. You would have to consult your web developer to isolate any possible issues from the host. It is not a Moz error code.
Here is someone not related to Moz that has experienced the error: http://stackoverflow.com/questions/4222226/how-to-prevent-aspxerrorpath-passed-as-a-query-string-in-asp-net-error-pages-t
Hope this helps!
-
Hi David,
Thanks for the helpful answer about how MOZ tools cache.
However, does my question as to "what this MOZ error message is: "Error.aspx?aspxerrorpath" have no answer?
NOTE: The pages are not missing. As stated above, "Oddly, these 4 web pages are not under a "Moved Temporarily" status that I know of. I have doubled checked the pages with Screaming Frog, Image and Link Analyzer, and Xenu and cannot find a differentiating error on them."
I am trying to understand precisely why and what error MOZ is saying they have. Could you please explain what MOZ means by saying these four pages have "Error.aspx?aspxerrorpath"?
My secondary question is, since the pages do in fact exist, is MOZ seeing something that keeps the existing pages from being indexed? However, I have answered that secondary question. All four of the pages that MOZ gives a 302 http statues with the "Error.aspx?aspxerrorpath" are indexed by Google.
Example:
Foreclosure Eligibility - Home Destination
<cite class="_pd">www.homedestination.com/foreclosure-eligibility.html</cite>
- Cached
- ShareView shared post
by Jeannie Hill - in 72 Google+ circlesForeclosures and foreclosure eligibility tips from Home Destination. Certified Distressed Property Expert helps with short sales, foreclosures effecting ...
-
Hi Jessential
Your browser cache is not connected with how you view your crawl report. The cache will be for our backend. The crawl test tool and Moz app crawls store data separately so your Moz app crawl will be newer than the previous crawl test or current. Our cache for the crawl test should be cleared to update tomorrow just to be safe
I'm afraid if we can't find pages we won't know what they are to list them. The best way to know is to keep a copy of your full csv to compare results with for missing pages.
Hope this helps!
-
Hi David,
The newest crawl was released shortly after our last comments. Would it help if I cleared my cache? Or used another browser?
Does Moz have a tool to help me see which pages/posts that are not being indexed?
-
Thank you. I look forward to the new crawl and your follow-up with this error.
I have updated the site to Universal Google Analytics so have had no page views or moz activity to help me diagnose errors lately.
Moz has become a mainstay for me!
-
Hi Jessential
It appears our crawler may have had issues accessing those pages on your web-server. I would take a look at the newest crawl that will complete later today. For the crawl test wait another 24 hours which will give time for the cache to clear.
Hope this helps!
-
You will find both reports here:
-
Hi Jessential
I re-downloaded your full crawl diagnostics report for Home Destination and cannot find the 302 errors. The latest crawl is from April 22nd with a current crawl in progress. Is there another report you are referring to?
-
Hi David,
Thanks for you interest in helping me decipher this error.
In the April 28th report, you will find the error in lines 100, 108, 111 and 443; each line immediately follows a 302 http. Oddly, these 4 web pages are not under a "Moved Temporarily" status that I know of. I have doubled checked the pages with Screaming Frog, Image and Link Analyzer, and Xenu and cannot find a differentiating error on them.
If you review the April 18th report of the same pages, found in lines 99, 107, and 435 were not indicated in such a manner. (The fourth page did not exist at that time.
Oddly, several pages have been dropped from Google's index and I have yet to determine why or which ones.
Your insights are appreciated.
-
Hi Jessential
I have never seen that error before. Can you tell me where you see it in your campaign? I took a look at your crawl csv for homedestination and could not see that error.
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 I get Moz keywords via API?
Hi, my boss is asking if you "have any API for keyword research -- e.g., as soon as a user creates a card title in [our application], we can auto-recommend keywords from Moz within [the application]. I shared a link with him to your Links API page, but he says he doesn't think that API does the above. Can you help? Thank you, Renae
API | | CarolinaRen0 -
Error Code 803
Hello all, With every new Moz report that comes in, an error code 803 appears. I check each link that comes up as an 803 but they work perfectly. What could be causing this to happen? Error Code 803: Incomplete HTTP Response Received Your page did not send a complete response to the Moz Crawler's request. Our crawler is pretty standard, so it's likely that other browsers and crawlers may also encounter this error. If you have this error on your homepage, it prevents the Moz crawler (and some search engines) from crawling the rest of your site.
API | | moon-boots0 -
Alternatives to Supermetrics to get Moz metrics into Google Sheets?
Hi, Interested in getting Moz API metrics into Google Sheets on an automated scheduled. Supermetrics can do this, but I am curious to know if there are any alternatives, free or paid. Thanks! 🙂
API | | GOODSIR1 -
Is Moz's rank checker driving referals (and bounces) in my analytics?
I see 200+ referral visits per month from "rank-checker.online" and they all bounce with one second session durations. Are these bounces hurting my SEO? They are definitely distorting my referral metrics. Can I block them somehow?
API | | 10516VT1163000 -
New Moz reports
The new MozPRo reports do not give me the same level of data as my previous reports on the old platform, including detailed keyword reporting. I recently discovered that even if I schedule a monthly report, I still only get weekly data. Is it just me or is anyone else struggling with these new reports?
API | | Discovery_SA0 -
Can't remove "insights" section from report.
The items in the "insights" section of the Moz report have an "x" which can be clicked in the designer to dismiss this data from the report. However, these items still shows up in the report anyways. Buggy. How can we work around this bug?
API | | Webformix0 -
Are EC2 servers blocked from using the Moz API?
Hi I've created a script that I'd like to use to check a list of domains using the Moz API. It works totally fine on my local machine. However, when I run it from my EC2 instance, it fails every time. To be specific, the response is always empty (the response is an empty json array) when the request is sent from EC2. Is, for some reason, EC2 blocked by the Moz API? Many thanks for your help, Andrew
API | | csandrew0