Keyword pattern research: finding modifiers, head terms…

Video lecture

Keyword pattern research: finding modifiers, head terms and intents

14 chapters · about 8 min · full transcript

Coming soon

Chapter 1 of 14

Keyword pattern research

Patterns, not keywords
Where to find them
Regex and Python mining
Intent validation
Localization

The narrated lecture is in production

Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.

Chapters

Transcript of the narration, chapter by chapter.

0:00 Keyword pattern research

Traditional keyword research hunts for individual keywords. Programmatic research hunts for patterns, a structure that repeats hundreds or thousands of times with different values plugged in. Find the right pattern, and you've found a whole content system. In this lecture you'll learn how to discover patterns, mine your own Search Console data with regular expressions, cluster modifiers with Python, validate intent, and handle languages like Arabic and Urdu properly.

0:30 Why it matters

Why does this matter? Because the pattern you choose sets the shape of everything you build. Here's an analogy. A cookie cutter decides the shape of every cookie. If the cutter is the wrong shape, it doesn't matter how good the dough is. Your pattern, head term plus modifiers, is the cookie cutter. Research is how you find a cutter that matches what people actually search for, in the words and languages they actually use.

1:03 What a pattern is

A pattern is a head term plus modifiers in a consistent structure. Service in area. Tool A plus tool B integration. Job title salary in city. Product versus product. You're looking for patterns where many modifier values have real demand, the intent stays consistent across values, and you've got data to answer each one. Miss any of those three, and the pattern isn't worth building.

1:31 Pattern sources

Where do patterns come from? Your own Search Console, where queries already reaching you reveal structures. Keyword tools, including Google's Keyword Planner, to expand head terms. Autocomplete and people also ask, which reveal modifier types like cost, near me, versus and for beginners. Your own product data: every location, product, integration or category is a potential modifier. Competitor URL folders and sitemaps. And your internal site search logs.

2:01 Regex in Search Console

Search Console supports regular expressions in its query filter. The lesson includes examples: one catches comparison queries with words like versus or compare, one catches city names across the Gulf, Pakistan and the UK, and one catches integration language. It's case-insensitive and quick. For larger datasets, pull the data through the Search Console API instead of the interface.

2:26 Simple example: Lahore driving school (illustrative)

Here's a simple worked example. A Lahore driving school runs a Search Console regex filter for driving and city area names. The results show queries like driving school in DHA, driving lessons Gulberg, and female driving instructor Johar Town. So they have two patterns: driving school in area, and female driving instructor in area. They build a grid of twelve areas by two patterns. Most cells show impressions. They also notice Roman Urdu queries like gari chalana seekhna Lahore, and add a check on whether those results favor English or Urdu pages. The grid becomes the plan for the first twenty-four pages.

3:10 Cluster with Python

Then cluster with Python. Load your exported queries, define lists of services and areas, tag each query with the service and area it mentions, and pivot into a grid: services down the side, areas across the top, impressions in the cells. That grid instantly shows where demand exists. Blank cells might mean no demand, or might mean you're simply not visible yet, so check a keyword tool before deciding.

3:40 Validate intent

Now validate intent. For ten to twenty modifier values per pattern, look at the actual search results. What type of result ranks: listings, a map pack, guides, tools, products? Your page type must match. Are the results consistent across values, or do some values show a different need? Which features appear, like map packs or AI Overviews, that affect clicks? And how good are the incumbents? Thin pages ranking at the top are an opportunity.

4:13 Estimating demand

A word on demand estimates. Keyword tools are rough, especially for long-tail and non-English queries. Arabic and Urdu queries are often under-reported, and many people in Pakistan and the Gulf search in Roman Urdu or mix Arabic and English. So add up demand across the whole pattern rather than trusting any single keyword's number, and treat long-tail volume as upside.

4:39 Localize natively

Localization matters. Gulf market pages should be written natively in Arabic with a right-to-left layout and Arabic modifiers, not just translated. For Pakistan, check which query forms the search results favor: English, Urdu, or Roman Urdu. And use hreflang correctly when you have language or region variants. Here's an illustrative example: a Riyadh home services platform found Arabic and English district patterns, built a twelve-by-forty grid, and focused pages on what the map pack lacks: verified providers, price ranges from real jobs, and response times.

5:16 Mistakes + try this now

Common research mistakes. Researching only in English for Arabic or Urdu-speaking markets. Treating zero-volume modifiers as having no demand. Forcing one template onto modifiers with different intents. Copying a competitor's URL structure without understanding why it works. And trusting a single keyword's volume estimate. Try this now: open Search Console, filter queries with one regex for your main service or product word, and export the results. Count how many distinct modifiers appear. That count is your first estimate of pattern breadth.

5:51 Quick self-check

Quick self-check. Your keyword tool shows zero searches for tutor for O level chemistry in Bahria Town, but Search Console shows your site got impressions for similar queries last month. Should you ignore it because the tool says zero? Pause. No. Tools under-report long-tail and regional queries. The impressions are real evidence of demand. Treat the tool's zero as unknown, add the area to your grid, and let the pilot measure it. That's why aggregating across a pattern beats trusting any single keyword number.

6:28 Watch me do it: Riyadh cleaning research (illustrative)

Watch me do it. Let's research an illustrative pattern for a Riyadh cleaning company in Search Console. Step one, regex filter on queries: cleaning, تنظيف, or maid, case-insensitive. I export three months. Step two, I scan and see three structures: cleaning company in district, deep cleaning villa, and Arabic queries for home cleaning company in a district name. Step three, in Python I tag each query with service and district, including Arabic district names mapped to the same IDs as English ones, so Al Malqa and الملقا count together. Step four, the grid: eight services by thirty districts. Two hundred and ten cells have impressions, heavily concentrated in north Riyadh. Step five, intent checks: for ten cells I search both languages. English results show directories and company pages; Arabic results show more company pages and a map pack. Both match a listing-style page. Step six, one surprise: queries with the word monthly show a different intent, recurring maid services, which needs its own pattern. The output is a validated grid and two patterns, ready for data sourcing.

7:45 Recap and next step

Recap. Find patterns, not keywords. Mine Search Console with regex and your own data, cluster modifiers into a demand grid, validate intent against real results, aggregate demand across the pattern, and localize natively. Your next step: find one pattern in your own Search Console with a regex filter, build a head by modifier grid of impressions, and check the results for ten modifier values.

From keywords to patterns

Traditional keyword research finds individual keywords. Programmatic research finds patterns: a head term combined with modifiers that follow a consistent structure.

Pattern:   [service] in [area]
Head:      "AC repair", "deep cleaning", "pest control"
Modifier:  "Dubai Marina", "JLT", "Al Barsha", ...
Pattern:   [tool A] [tool B] integration
Pattern:   [job title] salary in [city]
Pattern:   [product] vs [product]

Your job is to find patterns where (1) many modifier values have real demand, (2) the intent is consistent across values, and (3) you have data to answer each one.

Sources for pattern discovery

Your own Search Console: queries already reaching you reveal patterns (filter by regex).
Keyword tools (Google Keyword Planner, and third-party SEO suites): expand head terms and export modifiers.
Autocomplete and "People also ask": reveal modifier types (cost, near me, best, vs, for beginners).
Your product data: every entity in your database (locations, products, integrations, categories) is a potential modifier.
Competitor URL structures: sitemaps and URL folders of successful sites reveal their patterns (analyze, do not copy content).
Internal site search logs: what users type on your site.

Mining patterns from Search Console with regex

In Search Console's Performance report, filter queries with a custom regex (RE2 syntax), for example:

(?i)\b(vs|versus|compare|comparison)\b
(?i)\bin (dubai|abu dhabi|sharjah|riyadh|jeddah|karachi|lahore|islamabad|london|manchester)\b
(?i)\b(integration|integrate|connect|sync)\b

Export via the Search Console API for larger datasets.

Clustering modifiers and intents with Python

import re
import pandas as pd

df = pd.read_csv("gsc_queries.csv")  # columns: query, clicks, impressions
areas = ["dubai marina", "jlt", "al barsha", "downtown", "jumeirah", "business bay"]
services = ["ac repair", "ac service", "deep cleaning", "pest control"]

def parse(q):
    ql = q.lower()
    svc = next((s for s in services if s in ql), None)
    area = next((a for a in areas if a in ql), None)
    return pd.Series({"service": svc, "area": area})

df[["service", "area"]] = df["query"].apply(parse)
grid = (df.dropna(subset=["service", "area"])
          .groupby(["service", "area"])["impressions"].sum()
          .unstack(fill_value=0))
print(grid)

The resulting grid shows which service × area combinations have demand. Blank cells are either no demand or no visibility yet — check with keyword tools before assuming.

Validating intent per pattern

For a sample of 10–20 modifier values per pattern, check the search results:

Result type: listings, local pack, guides, tools, product pages? Your page type must match.
Consistency: do results look similar across modifier values? If some values show different intents (e.g., "pest control Business Bay" shows government notices), handle them separately.
SERP features: map packs, AI Overviews, shopping, video — affects click potential.
Competitor quality: are top results rich data pages or thin pages? Thin incumbents are an opportunity.

Estimating demand realistically

Keyword tools give estimates with wide error bars, especially for long-tail and non-English queries (Arabic and Urdu queries are often under-reported, and many users in Pakistan and the Gulf search in transliterated "Roman Urdu" or mixed Arabic-English). Aggregate demand across the pattern rather than trusting single-keyword numbers, and treat long-tail volume as upside.

Language and localization

Arabic pages for Gulf markets should be written natively, with right-to-left layout and Arabic modifiers ("شقق للإيجار في دبي مارينا"), not only translated from English.
For Pakistan, consider English, Urdu and Roman Urdu query forms; check which the search results favor.
Use hreflang correctly when you have language/region variants.

Worked example: a Riyadh home-services platform

Search Console regex filters surfaced patterns like "[service] [district]" in Arabic and English. The team built a grid of 12 services × 40 districts; 180 combinations showed impressions. SERP checks showed map packs dominating some combinations, so pages focused on data the map pack lacks: verified providers, price ranges from completed jobs, response times, and Arabic-first content.

Prioritizing patterns for a pilot

Do not build every pattern at once. Pick a pilot that has: clear intent, data you already hold, moderate competition, and a direct path to conversion. Launch 50–200 pages for that pattern, measure indexing and engagement for 6–8 weeks, then expand the winners. A pilot also tests your pipeline — data refresh, rendering, internal links and QA — before you multiply mistakes across thousands of URLs.

Pitfalls

Pattern research in English only for Arabic- or Urdu-speaking markets.
Assuming zero-volume modifiers have no demand.
Ignoring intent differences across modifier values.

How to measure success

A validated pattern list with demand estimates, intent notes, SERP features, and the data fields required per page — ready for the data-sourcing step.

Programmatic research finds patterns (head term × modifiers) with consistent intent and answerable data.
Mine Search Console with regex, your own product data, autocomplete, competitor URL structures and site search.
Validate intent by checking results for a sample of modifier values; match page type to SERP.
Aggregate demand across the pattern; long-tail and non-English volumes are under-reported.
Localize natively: Arabic RTL, Urdu/Roman Urdu variants, correct hreflang.

Use Search Console regex filters to find one pattern in your data. Build a head × modifier grid of impressions and check search results for ten modifier values.

Enrol for free to save your progress

Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.

Keyword pattern research: finding modifiers, head terms and intents