---
title: "List all web ranking findings of a company."
method: GET
path: "/api/v2/companies/{id}/findings/webranking"
tags: ["Findings"]
---

# List all web ranking findings of a company.

`GET /api/v2/companies/{id}/findings/webranking`

Cisco, Alexa, and Majestic track web sites and rank them according to popularity, back-links, references, etc. This subcategory shows Alexa and Majestic trends, Google Page insight speed test results as well as Web Content Accessibility Guidelines (WCAG) 2.0 parsing compliance findings.
 This category has 2% effect on total scan score.

## Path parameters

- `id` integer, required

## Query parameters

- `page_number` integer
- `page_size` 10 | 20 | 30 | 50 | 100 | 250

## Response `200`

Success

- WebRankingFinding[]
  - `Domain` string — The domain which this finding is related.
  - `Rankings` object
    - `AlexaRankingAndTrend` RankingAndTrend
      - `Rank` number, nullable — Rank
      - `TrendImageUrl` string, nullable — Rank trend as an image.
      - `ControlId` string — The unique identifier of the control that this finding relates to.
    - `CiscoRankingAndTrend` RankingAndTrend
      - `Rank` number, nullable — Rank
      - `TrendImageUrl` string, nullable — Rank trend as an image.
      - `ControlId` string — The unique identifier of the control that this finding relates to.
    - `MajesticRankingAndTrend` RankingAndTrend
      - `Rank` number, nullable — Rank
      - `TrendImageUrl` string, nullable — Rank trend as an image.
      - `ControlId` string — The unique identifier of the control that this finding relates to.
    - `WebRankCountryImage` string — The image of web rank by country.
  - `GooglePageSpeedInsightsPerformanceFindings ` object, nullable — Google PageSpeed Insights tools is used to measure the website performance and usability. PageSpeed Insights measures the performance of a page for mobile and desktop devices. PageSpeed Insights checks to see if a page has applied common performance best practices and provides a score, which ranges from 0 to 100 points.
    - `ControlId` string — The unique identifier of the control that this finding relates to.
    - `Severity` 'Info' | 'Low' | 'Medium' | 'High' | 'Critical' — The severity of a finding.
    - `DesktopSpeedGrade` 'Bad' | 'Poor' | 'Average' | 'Good' | 'Excellent' | 'Not Applicable' — The level of desktop speed as a grade string.
    - `MobileSpeedGrade` 'Bad' | 'Poor' | 'Average' | 'Good' | 'Excellent' | 'Not Applicable' — The level of mobile speed as a grade string.
    - `MobileUsabilityGrade` 'Bad' | 'Poor' | 'Average' | 'Good' | 'Excellent' | 'Not Applicable' — The level of usability as a grade string.
    - `Findings` object[], nullable — Check list and results for mobile usability
      - `Status` 'Passed' | 'Failed' — The result of the testing control.
      - `Name` string — The name of the testing control.
      - `Category` 'Mobile Speed' | 'Desktop Speed' — Category of the testing control.
      - `Description` string — The details of the usability testing control. It's always a good idea to whitelist HTML sanitize this value before rendering it as HTML.
      - `References` string[]
  - `WCAGParsingParsingComplianceFindings` object[], nullable — Web Content Accessibility Guidelines (WCAG) 2.0 Parsing Compliance results are listed. The core reason to run your HTML documents through a conformance checker is simple: To catch unintended mistakes—mistakes you might have otherwise missed—so that you can fix them. Beyond that, some document-conformance requirements (validity rules) in the HTML spec are there to help you and the users of your documents avoid certain kinds of potential problems. This validator checks the markup validity of Web documents in HTML, XHTML, SMIL, MathML, etc.
    - `ControlId` string — The unique identifier of the control that this finding relates to.
    - `Severity` 'Info' | 'Low' | 'Medium' | 'High' | 'Critical' — The severity of a finding.
    - `Title` string — The title of the finding. It's always a good idea to whitelist HTML sanitize this value before rendering it as HTML.
    - `Location` string — The location of the finding in the code.
    - `Code` string — The code block that triggers the finding. It's always a good idea to whitelist HTML sanitize this value before rendering it as HTML.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `default` — Failure

---

[API](https://skmtc.net/blackkitetech/apis/black-kite-api.md) · [All operations](https://skmtc.net/blackkitetech/apis/black-kite-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/blackkitetech/black-kite-api/revisions/7dadaba760fb/schema)