What is Moz's Error.aspx?aspxerrorpath HTTP Status 302 error message?

[jessential]

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!

[jessential]

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?

[DavidLee]

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!

[jessential]

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 ...

[DavidLee]

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!

[jessential]

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.

[DavidLee]

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.

[jessential]

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.

[DavidLee]

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.

[jessential]

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....

[jessential]

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.

[jessential]

Several test now and no sign of the error again.

[DavidLee]

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

[jessential]

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.