srunck

Thanks. One of our programmers used the double (curly?) quotes on the Redirectmatch 301 line. I have since removed them. Last month, one of our support people went into Google Webmaster Tools and marked all of the crawl errors (well over 100 of them) as fixed because a programmer had set up this redirect. Since then, however, we have seen these same errors creep back onto the crawl error list (again as 404s) at the pace of a couple per day. I have to assume that if I don’t find and resolve the real issue, we will eventually see the 100+ ‘404 not found’ errors that we had before.

• This reply was modified 8 years, 2 months ago by srunck.

Thanks for your response. There is no referrer link listed for these errors. Also, the person who has been in charge of the blog says we’ve always used URLs that had the date directories ahead of the title directories (“/2016/09/14/my-post”, not “/my-post/2016/09/14”).

Here’s an example of the redirect we’re doing. This would be the .htaccess file in the root of the old domain. I’m still learning about building proper 301 redirects. Maybe you can spot an issue here:

<IfModule mod_rewrite.c>

RewriteEngine On
RewriteBase /
Redirectmatch 301 “^/(.*)” “https://www.example.com/blog/$1&#8221;

</IfModule>