Prices and Product Categories

Read from your structured data, never guessed from the page text

Prices and Product Categories

On a product page, Opensolr reads the price, the currency and the category path (for example Clothing > Shoes > Running) and stores them with the page. Your shop gets price filters, price sorting and category filters without any extra work.

They come only from the page's structured data. Opensolr never guesses a price from the visible text, so a number in a sentence never becomes a price.

Where they are read from

  • Price and currency: the product meta tags (product:price:amount, the sale price first), then the JSON-LD Product offer, then microdata.
  • Category: the JSON-LD Product category, then the JSON-LD breadcrumb list of a product page, then the product:category tag, then microdata inside the product.
  • Breadcrumbs: the breadcrumb trail shown on the page, up to 6 levels, each level in its own field.
  • Everything else structured: the other values of your JSON-LD and microdata (brand, colour, size, material...) become fields of their own, ready to be filters.

What visitors get

  • The price shows on each result of the hosted search page.
  • Add the field price_f (label Price) as a Min/Max Slider and visitors filter by price. Every field you add as a filter also appears in the sort list next to Relevance, so visitors can sort by price too.
  • Add product_category_sm as a List (checkboxes), or the breadcrumb levels breadcrumb_1_sm, breadcrumb_2_sm... as Hierarchical (drill-down), and visitors narrow down category by category.
  • The chat bot quotes the price of the products it finds.

You add these filters in WebCrawler > Settings > Search Facet Filters > Configure Facet Filters: Configure facet filters, Facet widgets.

Pushed documents

Documents you send with Data Ingestion keep the fields you send. Send the price and the category as your own fields, with the type suffixes in Type suffixes.

What every page gets

Back to Enterprise Site Search