3 Replies Latest reply on Aug 27, 2017 10:29 PM by Sanford Whiteman

    Google Crawl Error report

    Tim Ball

      Hi all

       

      We are getting a lot of Crawl Errors in our Google Search console.

      One of our dev's did some investigating and concluded that our pages are showing up in the report due to encode issues.

      The pages are all from our company website which has the munchkin tracking code embeded on this domain

       

      It seems like these 404s are generating via a script named '

      ' //app-sj02.marketo.com/js/forms2/js/forms2.min.js' where you have a function being called '

      .decode=c.parse=a("./decode"),c.encode=c.stringify=a("./encode")}'

      When search engines crawl the URLs, these get amended to the URL I guess.

       

      Has anybody had any experience with this issue.
      Cheers
      Tim

        • Re: Google Crawl Error report
          Sanford Whiteman

          Please provide the actual errors from the console: your reference to the code doesn't make sense (those are just module loading statements in the Forms JS library; they don't get replaced by anything).

            • Re: Google Crawl Error report
              Tim Ball

              Thanks for the quick reply Sanford.

               

              No real console error just a log and a response code

               

              {{url}}/encode       404

                • Re: Google Crawl Error report
                  Sanford Whiteman

                  No real console error just a log and a response code

                   

                  {{url}}/encode 404

                  There's no reason for anything to assume a quoted string of format "./blah" to be a relative path on a server. Of course it gives a 404, but it isn't supposed to be a remote path (it's just a local module).

                   

                  This would be like assuming a quoted string "my.name.is.luka" must represent a valid domain name on the net (even if it's never used in any context in which it would be requested as a webserver).

                   

                  It sounds like you need to exclude forms2.min.js from crawling, but certainly the problem isn't with the library, it's with the crawler.

                  1 of 1 people found this helpful