# Broken CSS

CSS files which return a broken page status code such as 404 or 501

**Priority**: Critical

**Impact**: Negative

## What issues it may cause

Broken CSS files may result in errors on pages causing a poor user experience and may affect the indexing of the page if the rendered content is not visible to Googlebot.

## How do you fix it

Restore the CSS file on the so it responds with a 200 status, or update the URL in style link to a working CSS file.

## What is the positive impact

The user experience may be improved if the broken CSS file was used for the page styling, potentially resulting in improved rankings for the page and all other pages on the site.

## 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:


```graphql
query GetReportStatForCrawl(
      $crawlId: ObjectID!
      $reportTemplateCode: String!
      $after: String
     ) {
        getReportStat(
          input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode}
        ) {
          crawlUrls(after: $after, reportType: Basic) {
            nodes {
              url
              foundAtUrl
              level
              httpStatusCode
              disallowedPage
              failedReason
              css
              fileExtension
              foundInGoogleAnalytics
              foundInGoogleSearchConsole
              foundInBacklinks
              foundInList
              foundInLogSummary
              foundInWebCrawl
              foundInSitemap
            }
            totalCount
            pageInfo {
              endCursor
              hasNextPage
            }
          }
       }
     }
```

**Variables:**
```json
{"crawlId":"TjAwNUNyYXdsNDAwMA","reportTemplateCode":"broken_css"}
```