Overview

Tagging schema accurately is crucial for ensuring search engines understand your content—and that means avoiding both missing information and redundant data. The Advanced Filter feature in Milestone Schema Manager gives you more control when tagging by letting you specify exactly what should be included.

Whether you're working on a Contact Point schema or another type, Advanced Filters allow you to filter out extra text and keep only the most relevant information, resulting in cleaner and more compliant schema markup.

Why Use Advanced Filters?

Without filters, some schema properties may unintentionally pull in surrounding or repetitive content—like headers, labels, or extra words ("Phone:", "Email:", etc.).

Using Advanced Filters ensures:

• Only accurate data is included in your schema
• Redundant or unnecessary labels are excluded
• Your structured data is lean, clean, and search-friendly

It’s especially helpful when tagging fields like phone numbers, emails, and contact info, where surrounding text may interfere with clean output.

Step-by-Step: How to Use the Advanced Filter in Schema Editor

Let’s walk through the example of tagging a Contact Point schema and using a filter to isolate a phone number.

Start with Tagging Your Schema

Tag your page using the Contact Point schema type and identify where you're adding contact info like:

• Phone
• Email
• Fax

   
 
Open Advanced Configuration

Next to any property you’ve tagged (like Telephone), click the three dots (•••) to open the menu.

Select ‘Advanced Configuration’.
 
 

Add an Advanced Filter

Inside the configuration pop-up, click on ‘Add Filter’. This opens a dropdown with filter types.

Choose the Right Filter Rule

From the dropdown, select a condition like ‘After’
 

In the text field, enter the filtering keyword, such as 'Phone'. This tells the system to extract only the value that appears after this keyword. Click ‘Save’.
 

Review the Output

Once the filter is applied:

• The redundant label ("Phone:") is automatically removed
• Only the actual phone number remains in the Telephone property of the schema

This keeps your data precise and fully optimized.