Skip to main content

Pages with Mixed Content Warnings

Priority: Low

Impact: Negative

What issues it may cause​

Browsers and search engines may attempt to fetch the resources on the HTTPS protocol, and if they work the user-experience and rendering/indexing of the pages may be unaffected.

If the resources do not function on the HTTPS protocol then they will not be used to render the pages and could result in content not being loaded. This may result in a poor experience for users, or issues with content not being indexed by search engines, impacting rankings, traffic and conversions.

How do you fix it​

The resources should be checked to see if they can be served through HTTPs, and all references updated to use the HTTPS URLs.

What is the positive impact​

Crawler and browsers will be able to render and index these pages correctly, potentially resulting in a better user-experience, improved rankings, traffic and conversions.

How to fetch the data for this report template​

You will need to run a crawl for report template to generate report. When report has been generated and you have crawl id you can fetch data for the report using the following query:

query GetReportStatForCrawl(
    $crawlId: ObjectID!
    $reportTemplateCode: String!
    $after: String
   ) {
      getReportStat(
        input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode}
      ) {
        crawlUrls(after: $after, reportType: Basic) {
          nodes {
            pageTitle
            url
            foundAtSitemap
            deeprank
            level
            mixedContentWarnings
            foundInGoogleAnalytics
            foundInGoogleSearchConsole
            foundInBacklinks
            foundInList
            foundInLogSummary
            foundInWebCrawl
            foundInSitemap
          }
          totalCount
          pageInfo {
            endCursor
            hasNextPage
          }
        }
     }
   }

Try in explorer