Screpy · UX/UI case study

Designing Rank Tracker Segments.

A focused way for SEO teams to separate blog, product, and localized page performance—without repeatedly filtering a large keyword list.

UX/UI DesignUser FlowDashboard UX2026
Screpy Rank Tracker with the Blog pages segment selected and three matching keywords
The problem

One Rank Tracker held every keyword, but users needed to understand different parts of a website separately.

A broad keyword view could not quickly answer focused questions such as “How are our product pages performing?” or “What changed across localized content?” Repeating filters and cleaning exports added friction to an otherwise recurring task.

What needed to change

Make a large keyword set feel focused.

01

Group by site structure

Let users reflect the way their website is already organized: blog, products, languages, or markets.

02

Confirm before saving

Make the effect of a rule visible so users can catch an empty or overly broad segment early.

03

Keep insights in context

Apply the selected segment consistently to keyword rows, summary cards, trends, and exports.

01

Start where the work already happens.

Segment management lives inside Rank Tracker, close to the keyword table and export actions. Users do not need to leave the analysis context to create a focused view.

Screpy Google Rank Tracker before a segment is selected
Users can access segment management directly from Rank Tracker.
Suggested Screpy segments based on ranking URL groups
Screpy surfaces useful URL groups before users build a segment from scratch.
02

Begin with a useful suggestion.

Detected URL patterns turn existing ranking data into practical starting points. Users can review the matched keywords and average position, then save a relevant page group in one step.

03

Or build a segment with URL rules.

When a suggested group is not enough, the custom flow uses URL logic that matches how websites are structured. Users can name the segment, define its rule, preview the result, and save it without moving between separate steps.

Ranking URL path, hostname, and full URL rule source options

Choose the part of the ranking URL to evaluate.

Starts with, contains, ends with, and equals matching conditions

Use a matching condition that fits the site structure.

Create custom URL segment modal in Screpy
Naming, URL rules, match preview, and saving are combined in one focused flow.
Blog pages saved segment selected in Rank Tracker
Saved segments remain easy to recognize, switch, and reuse.
04

Return to a focused, reusable view.

Once saved, the segment becomes part of the Rank Tracker workspace. The selected page group stays visible, while its matching keywords remain ready for focused analysis.

Design rationale

Why URL-based segments?

  • Manual keyword groupsThey would give users control, but would also create an additional structure that needed ongoing maintenance.
  • Temporary table filtersThey could narrow the list quickly, but users would need to rebuild the same view whenever they returned.
  • URL-based segmentsThey use ranking URL data Screpy already collects, turning the site’s existing structure into reusable views.
Outcome

A reusable way to focus Rank Tracker.

Rank Tracker Segments introduced a persistent way to analyze different parts of a website. Users can begin with a suggested URL group or create their own rules, preview the matching keywords, save the segment, and return to the same focused view later.

Evidence note. Adoption and performance metrics were not available for this case study, so the outcome is described in terms of the shipped product capability rather than unverified business impact.