Welcome to the Q&A Forum

Thank you, Cyrus. Your response is very much appreciated. Since I posted this question, our reports have been showing the links are starting to drop off. I will update this thread if something happens.

In response to you and to add to Rebecca's response it will be a mixture of backlinks and content. Simply migrating content and 301'ing isn't enough sometimes. One thing to remember when 301'ing not all link juice is passed to the new page. I would reach out to whoever was linking to the now closed location and get them to link to the new location. From the new location I would link back to the other page or if the closed location is now redundant I'd 301 to new page. You need to always ask yourself this question before redirecting is the page likely to be used again? This method isn't always easy because you can't always control who links to x page but its best practice.

Hey Mike, One of my friend who owns a software company used their services couple of months ago and he was quite satisfied with the quality they provided. Let's see what other experts suggests.

These are great answers by Andy and David - thanks guys! For the Domain Authority discrepancy in your campaign vs Open Site Explorer, can you write into us at help@moz.com with the specific examples that you're seeing so we can take a closer look at what may be going on? Thank you! Kevin Help Team

I've been doing it for years and have never come across this issue. Look towards an algorithmic penalty too. There is no telling what could have caused this, so you need to cover all bases. -Andy

Hi Alfred, if I mine the logfiles and only deindex stuff that Google sends no further traffic to after a year could this be seen as trying to game the algo or similar? No, this wouldn't be seen as gaming the algorithm. All you are doing is finding those pages that are serving no purpose and removing them. if the articles are noindexed but still exist, is that enough to escape a Panda penalty or does the page need to be physically gone? There are two thoughts on this. The noindex route is seen as the more gentle way to see if this fixes things for Google - in my experience, it is generally not enough. What you need to remember is that even if you noindex a page, Google can still apply a penalty based on the page existing as the content can still be seen / crawled. There is no hard and fast rule to say they will, but it is a real possibility. The advice to my customers is generally to remove the pages in question to avoid all possible doubt. Find the pages that are not delivering benefit to the site or visitors and start there. I would be advising you undertake a content audit to fully assess the site and what really needs to be done. There is little point in killing lots of pages if it isn't lots of pages causing you issues. -Andy

So I made this change 2 days ago... I created a 301 from /business to /enterprise.  Here's what I am seeing so far: Both pages are indexed... why? The /business page is still ranking in the same place for the same terms The /enterprise page isn't ranking well For some reason our homepage ranking for the target keyword fell off the map completely... this is probably unrelated but not sure

be careful with that. dont fall for site that promise to get you links or have your site listed in their directory or submit. do a through check like security and whether the site hasnt been blacklisted by google or maybe the site look to spammy google punish site with trust issues especially when you are linked to malicious sites

That's because Moz taps into Bing for its keyword volume estimates and Google obviously is its own source. As Andy points out, different tools are going to give you different estimates. None of them are particularly accurate - search volumes change all the time. By using more than one, you can at least get an idea as to the relative difference in search volumes between keyword candidates, and understand if you might be missing some opportunities. Another good source of keyword ideas (and volume estimates) is Google search console but understand that it will only share a subset of the queries your content displayed in search results for. So it won't give you ideas for new content. Google Adwords is probably your best bet for getting accurate estimates of search volume and also to gain a sense of how well different phrases convert.

Wow, I feel a little bit embarrassed to share with you what really happened... I was going to take a screenshot and then I realized that I was writting down the URL where should go the keywords and viceversa so it was all my bad I have just come back from my summer vacation yesterday so I guess I am a little rusty and my mind is still adjusting Sorry for the inconvinience! And thanks a lot to both of you anyway

Yep, it's a big, tedious task, but there are no shortcuts here to do it right.

If the pages don't fall within the international element of the site, or aren't covered by HREFLANG, then look at the pages that are being caught as duplication. Are they required pages? Are they there just as filler content / doorway pages? Could the pages be noindexed? Is there an opportunity to set a canonical for them to avoid duplication? -Andy

Hi Johannes! Did Umar answer your question?

The only differences between the campaign crawl and the crawl test are that the campaign is an automated tracking that updates once a week and the crawl test is an on the spot crawl that can be requested at any time, though the crawl test is limited to crawling only 3000 pages of a site. (This shouldn't be an issue for the Stop Wobble site, as we have only found about 600 pages.) The type of audit you get between the two tools is the same. The purpose of the crawl test is to audit sites that you don't necessarily want to create a full campaign for yet, but it is often used check site updates between regularly scheduled campaign crawls.

I think your answer is in the question All our old pages were 301 redirected and content is relatively the same on the new redesigned website. So if you recently remodeled and redid your URLs that's a much more likely suspect in your drop. 301s past most, but not necessarily all, page juice

John: Did you see TorontoV's most recent response? TorontoV: Thanks for your question, and congrats!

Your article pretty much sums of my situation. The warning that I saw a couple of months ago was a "partial match manual penalty", but it is gone now. I want to see if I can get a few more things to come do or add the no follow and then I will go ahead with the disavow. Thanks for your response.

WPEis run on a base server using Apache with a Nginx proxy so you can use the WP engine  301 redirect system built-in or you can simply add a redirect to the HTAccess file. If you would like to use a tool to do this I recommend this one another alternative is to ask WP engine to make a change for you.https://www.aleydasolis.com/htaccess-redirects-generator/non-slash-vs-slash-urls/ApacheJust copy to your htaccess:``` https://example.com/page/ **https://example.com/page** ```  <label for="nonslash">**Slash to Non-Slash URLs**</label> > <ifmodule mod_rewrite.c="">RewriteEngine on > RewriteCond %{REQUEST_FILENAME} !-d > RewriteRule ^(.*)/$ /$1 [L,R=301]</ifmodule> **Non-Slash to Slash URLs** ``` ****Apache** https://example.com/page** https://example.com/page/ > <ifmodule mod_rewrite.c="">RewriteEngine on > RewriteCond %{REQUEST_FILENAME} !-f > RewriteRule ^(.*[^/])$ /$1/ [L,R=301]</ifmodule> USEING Nginx to do **https://example.com/page/** https://example.com/page As you see, there is one tiny difference between those two URLs, and it’s the trailing slash at the end. In order to avoid duplicate content, if you are using Nginx you can **remove the trailing slash from Nginx** URLs. Place this inside your virtual host file in the server {} block configuration: > ``` > rewrite ^/(.*)/$ /$1 permanent; > ``` Full example: > ``` > server { > listen 80; > server_name www.mysite.com; > rewrite ^/(.*)/$ /$1 permanent; > } > ``` All done, now Nginx will remove all those trailing slashes. USEING Nginx to do https://example.com/page https://example.com/page/ Add a trailing slash by placing this inside your virtual host file in the server {} block configuration: > ``` > rewrite ^(.*[^/])$ $1/ permanent; > ``` Full example: > ``` > server { > listen 80; > server_name www.mysite.com; > rewrite ^(.*[^/])$ $1/ permanent; > } > ``` From now on, Nginx should add your trailing slash automatically to every url * https://www.scalescale.com/tips/nginx/add-trailing-slash-nginx/ * https://www.scalescale.com/tips/nginx/nginx-remove-trailing-slash/  I hope this helps, Tom

Hi Rodrigo, OK - so I was able to find the page functionality in question on your actual site just to double check what was going on. Since this content isn't important to the page from an SEO standpoint, it makes sense to just remove these pages from the index. To do that your best bet is probably robots.txt. Here's a good stackexchange with John Mueller confirming that. I believe any one of the following entries can do the trick, but highly recommend you double check my work and test this before you implement it. This is also a good time for me to add a liability disclaimer if you accidentally noindex your whole site. Disallow: /AjaxPages/PopUp/CheckPrice Disallow: /AjaxPages/PopUp/CheckPrice.aspx Disallow: /CheckPrice (choose one of these, you don't need to use all of them) Pretty sure Robots.txt is case sensitive, so /checkprice may not work. There is also something called an X-Robots-Tag that could do this instead of your robots.txt file. Instructions on that at https://developers.google.com/webmasters/control-crawl-index/docs/robots_meta_tag?hl=en Finally, consider testing this on your staging server before rolling it out live.