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.

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

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

You will find both reports here:

https://moz.com/researchtools/crawl-test

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,

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.

Hi Dan,

Thank you for the clarification!

o you think this percentage has changed sine summer 2013?

"When done properly, we know from testing and statements from Google that a 301 redirect passes somewhere around 85% of its original link equity."

If my tests and recent tidbits of 2014 news, I am guessing the percentage of link juice lost has widened.

Do you have tool or WP plugin to recommend to help migrate the content in .html web pages best? I am familiar with Screaming Frog for URL's and metadata. How can I possibly streamline the rest of the time to migrate the website?

Thanks for all your high value insights.

Hi Dan,

Thanks again for your response.

I can see that I need to do a better job of stating the end result desires.

I need to assure my client in advance that there is reasonable cause to believe that if they spend thousands of dollars on the migration, it benefits their situation and increases SEO and thereby conversions.

There is no call to "Build out the new wordpress site exactly how you(they) want it." They are not seeking a WP "design", The request is to move to gain SEO functions, to NOT have the schema metadata stripped out as it is now in BC , to gain "juice" while not loosing back-link value (with unwanted and additional "link juice loss" from redirects). There are back links to many of those pages and they need to be read by the search engines in a manner that does NOT loose any link juice.

NOTE: In preparation for a better menu, I have some new 301 redirects added (without the move!) and immediately dropped over 70% page visits every day since. The last thing my client want is to loose more link juice.

The entire goal is to avoid any additional losses of link juice with redirects - because we already  have huge losses with redirects. Therefore, we are seeking any viable, sustainable route to not have redirects. The entire migration is for SEO gains.

There is no draw t o simple gain a WP site or design.

Or is this simple not possible?

Or are the benefits of Yoast so powerful that we will have SEO gains that outweigh the losses of thousands of 301 redirects?

Does that help clarify? I guess if someone simply wanted to be in WP and was willing to pay for it, and THEN find out how it hurts or helps that would be another matter.

Hi Peter,

It sounds encouraging to know that there is a way to get the perma-link structure of WP to match the old pages. Do have a plug-in to recommend? A service provider? I sought to hire CMSHelpLive. Fortunately, after no service, communications, warrantee or the promised test URL during development, I was able to retrieve my funds through my cc fraud protection plan.

I am wondering just how someone else has actually accomplished it.

Or, what percentage of "link juice" to you think I might loose with apx.1,400 redirects?

I appreciate any lead you can  give me toward a workable path forward.

Hi Dan,

Thank you for answering my query. I value learning from someone who has already successfully accomplished the task ahead of me.

Could you help me sort out what you are saying? It seems that you mean I should go with the 800 + page redirects. Then I would be adding over 400 blog post that do not need the .html extension. However, WP skips the "/real-estate-blog/" that come between the domain and the post name. (example: it is: http://www.homedestination.com/real-estate-blog/how-to-insulate-your-attic-for-a-warm-and-cozy-home  it becomes: http://www.homedestination.com/tips-on-how-to-insulate-your-attic-for-a-warm-and-cozy-home/

Now that would mean adding another 400+ 301 redirects. Or is there a way to eliminate the added "/" WP attaches at the end? And a way to custom add the real-estate-blog folder?

Four years ago I inherited the site. As a real estate site, all the content was duplicate from an agency affiliate site and thereby is still operating under 200+ 301 redirects that are still live and would cause loops.  The article you sent says I will have the following losses:

Issues caused by those 301 chains include;

• Slow PageSpeed – for users or web crawlers to pass through those 301s, for every one you have, that page takes longer to load or the crawler has to work harder.We all know that site speed is a small ranking factor. And speeding up your site can have numerous benefits. We also know that Google will drop your mobile ranking if your mobile site does not load quickly.
• Poor User Experience – what’s that statistic we hear all the time? Users will bounce if your page takes longer than 3 seconds to load? Improving UX through speeding up your site has been researched and talked about many times. It’s benefits are well documented.
• Lost Link Value? – I believe so. Many interpretations and questions surrounded this video by Matt Cutts ”What percentage of PR is lost through a 301 redirect?” – I even recently wrote my own interpretation of Matt’s video here on Google Plus. Bottom line? Chains of 301′s dilute PageRank. PageRank isn’t everything, but if you can preserve it … while at the same time improving SiteSpeed and UX … why NOT?
• Conversion Rates Can Suffer – check out this post on KissMetrics demonstrating how a slow site can even hurt your bottom line.

NOTE: In preparation for a better menu, I have some new 301 redirects added (without the move!) and immediately dropped over 70% page visits every day since.

Your help is directing to the best solution is much appreciated!

What do you recommend for moving a static html website into WordPress that has over 800 pages:

What is the better option for long-term SEO?

1. Stay in the Adobe BC CMS (where all schema meta data keeps being stripped out)

2. Move to WordPress and have 800+ 301 redirects that loose link juice

3. Move to WordPress and add .html extension to all pages and face risks of being off the WP structure? ( What would happen? html extension fails to update at some point? Search engines would see it as link manipulation? WordPress would crash more often? Something else that I am not thinking of?