Skip to main content
All CollectionsGlossaryContent
Introducing saved filters
Introducing saved filters

A filter can now be saved in Oncrawl and be reuse across the platform among: data explorer, segmentations, alerts, reports.

Updated over 3 weeks ago

It allows you to create an Oncrawl Query Language and saved its definition in a given project.

You can embedded a saved filter inside an Oncrawl query language which enables you to reuse existing queries across the applications.

With the saved you can easily leverage the datas across the app to get SEO insights

How to use it?

On the Crawl report, you can click on the Filter Icon

A new “Add saved button” has been placed between the ‘add condition” And the “add group” button

Create a saved filter

1/ You can write down an OQL

2/ “Save filter” button is displayed when an OQL have been written

3/ if you click on “Save filter”, then, a “Saved filter” is displayed and you can provide a name to your “saved filter”

4/ Save

5/ Congratulations! Your saved filters has been created and is by default apply as filter

OQL is saved and is available in the following objects:

  • Alerts

  • Segments

  • Custom charts

  • Data explorer

Apply a saved filter

You can apply a filter without being able to save it

  • 1/ User clicks on “add a filter”

    • a new dropdown is display

  • 2/ All saved filters are display if user clicks on the button

  • 3/ Users apply their OQL

FAQ

What’s the difference between a saved filter and a page group?

They are different entities

  • A saved filter is a filter and act as a scope or a zoom on the data we want to drill down. It can be used within a segmentation.

  • A page group is a field which could act as a dimension inside a chart OR a column in the data-explorer. This entity could not be embedded in a segmentation.

Why applying a “saved filter” could result in displaying error message on my charts?

A “saved filter” may contain technical fields which are not compliant with a given segmentation (rely on page dataset) or logs charts (work only with URLs based filters) or with a crawl report (some fields are missing from a crawl to another)

  • For segmentation

    • ⚠️ field in error for segmentations and invalid segmentation will be displayed in the analysis part

  • Charts

    • ⚠️ An error with the right API error message

Be precautious before deleting a saved filter?

A saved filter can be reuse across the Oncrawl platform.

Meaning that, an alert or a segmentation may rely on a “saved filter” created some days ago in the data explorer.

As a result a workspace member whishing to to delete a “saved filter” need to be cautious and ensure no dependencies exist between a “saved filter” and an object like Alerts nor segmentations.

Did this answer your question?