Analyses, index watches and announcements

Always stay informed about new blog posts Sign up for notifications

New feature alert: Competitor Clusters in the News Dashboard

You can now create Competitor Clusters in the KPI Dashboard reports, to keep track of different publishers in your vertical, region, or even for a certain series or story in the Trisolute News Dashboard.

We’ll use the KPI Dashboard>Mobile Visibility Overall report as an example. Go to the Filter menu, and under the Filter Configuration section, you’ll see the Competitor pre-sets: Top 5 (most visible publishers for the filter settings) Top 10 (most visible publishers for the filter settings).

Filter menu in the KPI Dashboard

Here you can create the Competitor Clusters


Edit Competitor Clusters – If you have one or more specific publishers you’d like to see visibility for, choose this option.

When you click on Edit Competitor Clusters, you’ll go to a dialog box where you can choose your own set of competitors.

Competitor Cluster overview

Add the name of the new Competitor Cluster

To create a new Cluster, start by typing the name of the Cluster and clicking Create. Open the field for adding competitors by clicking on the pen icon next to a Competitor Cluster name.

You can add any publisher that’s indexed in Google News. Click on the checkmark to save your changes.

You can add more Competitor Clusters, change existing ones or close the overlay now. Once you’ve created Competitor Clusters, the names will appear next to Top 5 and Top 10.

Your Competitor Clusters flow through to all of the KPI Dashboard ranking reports.

This new feature came directly from a customer request – so if you have any idea of how we can improve the tool, never hesitate to reach out!

Read more

Coronavirus disinformation, get started with FAQ schema: What we read this week (6/19)

Zero search results, SEO copywriters and image rankings: What we read this week (6/12)

How Yahoo News ranks on the Google SERPs, Google News

Updated feature snippets, Google indexing for the non-technical and AMP out? What we read this week (6/5)