Moz-Specific 404 Errors Jumped with URLs that don't exist

[CJolicoeur]

Hello,

I'm going to try and be as specific as possible concerning this weird issue, but I'd rather not say specific info about the site unless you think it's pertinent.

So to summarize, we have a website that's owned by a company that is a division of another company. For reference, we'll say that:

OURSITE.com is owned by COMPANY1 which is owned by AGENCY1

This morning, we got about 7,000 new errors in MOZ only (these errors are not in Search Console) for URLs with the company name or the agency name at the end of the url.

So, let's say one post is: OURSITE.com/the-article/

This morning we have an error in MOZ for URLs

OURSITE.com/the-article/COMPANY1

OURSITE.com/the-article/AGENCY1

x 7000+ articles we have created. Every single post ever created is now an error in MOZ because of these two URL additions that seem to come out of nowhere.

These URLs are not in our Sitemaps, they are not in Google... They simply don't exist and yet MOZ created an an error with them. Unless they exist and I don't see them.

Obviously there's a link to each company and agency site on the site in the about us section, but that's it.

[effectdigital]

Not a problem! It't great that Moz's crawler picked up on this issue as it could have caused some problems over time, if it were allowed to get out of control

[CJolicoeur]

Just wanted to update quickly. The mistakes in the email links as well as the links to the two company sites proved to be the problem. After recrawling the sites, the 7,000+ errors are gone.

It's interesting because I was about to get very upset with Moz, thinking their bot had caused me half a day of headaches for nothing. Turned out they picked up an error before any other system did that would likely have done a lot of damage given that they were all contact links meant to improve transparency.

Hopefully, we caught and fixed the problem in time. In any case, thanks for your help effectdigital.

[effectdigital]

A more common issue than you might think and strongly likely to be a culprit

[CJolicoeur]

I've just come up on something....

In an attempt three days ago to be more transparent (it's a news site), we added "send me an email" links to each author's bio as well as links to the Company and the Agency in the footer.

Except these links weren't inserted correctly in the footer, and half the authors didn't get the right links either.

So instead of it being a "mailto" link, it was just the email which when you hovered over was the url of the page with the author email at the end... the same thing that's happening in the errors.

Same for the footer links. They weren't done correctly and sending users to OURSITE.com/AGENCY1 instead of AGENCY1's website. I've made the changes and put in the correct links. I have asked for a recrawl to see if that changes anything.

[effectdigital]

At this point that doesn't really matter the main thing is to analyse the referrer URL to see if there genuinely are any hidden malformed links

[effectdigital]

It is assuredly very weird, we just have to determine if Rogerbot has gone crazy in this Summer heat or if something went wrong with your link architecture somehow

[effectdigital]

Yeah that will tell you to look on the referring URL, to see if you can track down a malformed link to the error URL look in the coding

[CJolicoeur]

Other update here..

I've checked about 50 of these errors and they all say the same stats about the problem URL page.

307 words, 22 Page Authority.

I don't know if it matters, just putting it out there.

[CJolicoeur]

True, but it's as if something is creating faux URLs of a current article. Adding company names and emails to the end of the URL... It's very weird.

[CJolicoeur]

The referring URL in this case is the original url without the added element in the permalink.

So

URL: OURSITE.com/the-article/COMPANY1

Referring URL: OURSITE.com/the-article/

Does that give any more info?

[effectdigital]

No need to freak out though as you say "[email protected]" implying they are business emails (not personal emails) so you shouldn't have to worry about a data breach or anything. That is annoying though

[effectdigital]

The ones you want are... URL and Referring URL I believe. "URL" should be the 404 pages, "Referring URL" would be the pages that could potentially be creating your problems

[CJolicoeur]

UPDATE HERE:

I've just noticed that it is also adding the email of the author to the URL and creating an error with that as well.

So, there are three types of errors per post:

OURSITE.com/the-article/COMPANY1

OURSITE.com/the-article/AGENCY1

OURSITE.com/the-article/[email protected]

[CJolicoeur]

Do you mean downloading the CSV of the issue? I tried that and it gives me the following:

Issue Type,Status,Affected Pages,Issue Grouping Identifier,URL,Referring URL,Redirect Location,Status Code,Page Speed,Title,Meta Description,Page Authority,URL Length,Title Pixel Length,Title Character Count.

Which isn't really useful as it relates to the 404 page.

I'm new to Moz, is there a direct line to an in-house resource that could tell us if it's a Rogerbot issue?

[effectdigital]

If you can export the data from Moz and it contains both a link source (the page the link is on) as well as a link target (the created broken URLs) then you might be able to isolate more easily, if it's you or if it's Rogerbot. If Moz UI doesn't give you that data, you'll have to ask if it's at all possible to get it from a staff member, they will likely pick this up and direct you to email (perfectly normal)

[CJolicoeur]

Thanks for the feedback. You're right about the 404 part, I should have phrased it differently. As you figured out, I meant that we are getting 404s for URLs that were never intended to exist and that we don't know how/why they are there.

We are investigating part 1, but my hope is that it is part 2.

Thanks again for taking the time to respond.

[effectdigital]

404s are usually for pages that 'don't exist' so that's pretty usual. This is either:

1. somewhere on your site, links are being malformed leading to these duff pages (which may be happening invisibly, unless you look deep into the base / modified source code). Google simply hasn't picked up on the error yet

2. something is wrong with Rogerbot and he's compiling hyperlinks incorrectly, thus running off to thousands of URLs that don't exist

At this juncture it could be either one, I am sure someone from Moz will be able to help you further