In addition to filtering your data, Botify fields define your Explorer reports as metrics and dimensions. Metrics define the quantity of your data (e.g., number of URLs, % of new sessions), and dimensions describe your data (e.g., URL, country). Dimensions define report rows, and metrics define report columns, calculated based on the selected dimensions.

In this report, Keyword is the dimension and Impressions, Clicks, CTR, and Average Position are metrics:

Planning what to measure before configuring your report is crucial to getting the expected results. Some Botify capabilities support only single-dimension reports, while others support multi-dimensional reports. Review the descriptions and examples below to help you determine the best report configuration for you.

LogAnalyzer and SiteCrawler URL Explorer reports are always grouped by URL as a single dimension, so you do not select metrics and dimensions when working with columns in these reports. These reports are best for diving into SEO details by URL, as shown in the following examples.

Using structured data, you can create interesting reports such as this one that provides impressions by author as a single dimension in RealKeywords:

Filter for URLs with a duplicative title tag with at least one other page in SiteCrawler. Ensure each page has a unique title tag to aid your site’s optimization efforts and address unintended duplicative content:

Reports in the RealKeywords Keyword Explorer, AlertPanel, and SpeedWorkers URL Explorers can be based on multiple dimensions. When defining multi-dimensional reports, the first dimension you configure defines how the data will be grouped. Other selected dimensions are grouped with your report's first configured dimension. These reports are best for diving into SEO details by property, as shown in the examples below.

Find keyword clicks and average position grouped by keyword, URL, and pagetype together in RealKeywords:

In SpeedWorkers, find the number of bot requests grouped by URL and whether the page was in cache at the time of the request: