📘 This article explains how to set up your project segmentation to group your site pages by their intent.
Overview
Your website pages have multiple purposes, such as listing and detail pages. Classifying pages by their purpose gives Botify a clear picture of your website structure, enabling relevant alerts and triggered actions for each purpose. Some Botify capabilities, such as SmartLink and SmartIndex, require segmenting your site pages according to their purpose.
To identify page purposes, you will add page qualifiers to the project segmentation for each website area. SmartIndex will create sections for every segment with these qualifiers, enabling unique rules to be applied to each area.
👉 SmartIndex section names are automatically generated from the combination of the purpose and object defined in the project segmetnation.
Adding Page Qualifiers
To classify pages by purpose, add the following flags to each relevant segment, using the examples for reference:
Purpose
Add the purpose flag to identify how pages are used within each object:
Detail pages (e.g., PDPs for e-commerce sites, articles for publishers)
Subdetail pages (e.g., product reviews)
Listing pages (e.g., PLPs for e-commerce sites)
API
Paid search
Object
Add the object flag to identify each website section with a schema.org-compatible object. For example, “product” for PDP and “category” for PLP.
For subordinate pages, such as product reviews, define a
subdetailobject with theparent_objectflag.For listing pages (i.e., purpose = listing), include the
listing_objectsflag with a comma-separated list. For relevant alerts and recommendations, also include pagination flags.
Common Objects
While all structured elements are supported in Botify as objects, the following are the most commonly used:
Product
Category
NewsArticle
Article
Blog
BlogPosting
Recipe
HowTo
Event
JobPosting
Course
FAQPage
Book
Item
Race
❗️The purpose and object flags are case-insensitive. Duplicate flags with varying case will cause unexpected results (e.g., object FAQPage and object FAQpage).
Determining Which Segments to Qualify
You should qualify all page segments for all pages with an SEO purpose. For example, qualify your product and blog pages, not checkout pages and contact forms. In SmartIndex, all segments matching a purpose + object combination are included in SmartIndex sections, which identify rules applied to pages of the same type. For example, the segments with purpose = details + object = product in the first example below define the pages in the “product details” section in SmartIndex.
Examples
The following examples show how to identify page qualifiers for the “pagetype” segment group.
Multiple Segments
This segmentation example will push product detail and list pages, plus the homepage, to SmartIndex while keeping pages with no SEO purpose in the project segmentation.
[segment:pagetype]
@product
path /p/*.html
purpose detail
object product
@listing
path /category/*
purpose listing
object category
listing_objects product
@search
path /search/*
purpose listing
object searchItem
listing_objects product
@homepage
path /
purpose detail
object homepage
Product Pages
The following example identifies product detail, listing, and review pages.
[segment:pagetype]
@pagination
path /l/*
path rx _([0-9]+).html$
flag p+
@mylistings
path */l*
flag p1
purpose listing
object category
listing_objects product
@myproducts
path /p*
purpose detail
object product
@reviews
path /p/reviews*
purpose subdetail
parent_object product
object review
Article Pages
The following example identifies articles with article category pages.
[segment:pagetype]
@home
path /
@article_category
path /category/*
purpose listing
object category
listing_objects newsArticle
@article
path /article/*
purpose detail
object newsArticle
@author
path /author*
purpose detail
object person
Blog Pages
This segmentation defines blog home pages and blog posts.
[segment:pagetype]
@blog_homepage
path /blog/
purpose detail
object Blog
@blog
path /blog/*
purpose detail
object BlogPosting
Home Pages
The following example identifies the home page.
[segment:pagetype]
@homepage
or (
path /fr/
path /
)
query ''
purpose detail
object other
API Pages
When identifying API pages in segmentation, only the purpose flag is required, not the object.
[segment:pagetype]
@api
path /api/*
purpose api
Identifying Paid Search Pages
This is an example segmentation for paid search product pages.
[segment:pagetype]
@paid-search-products
path /google-shopping/*
purpose paid_search
object product
Pages with SEO purpose but no detail or listing pages
This example defines the home page and pages with no SEO purpose.
[segment:pagetype]
@homepage
or (
path /fr/
path /
)
query ''
purpose detail
object other
@notforSEO
or (
path /fr/cgu/*
path /fr/cgv/*
path /fr/mentions-legales/*
path /fr/confidentialite-des-donnees/*
path /fr/recrutement*
path /cdn-cgi/*
path *.zip
path *.pdf
)
@unknown
path /*
See also: