I thought publishing more useful content would automatically give my website more opportunities to rank.
Then I noticed something uncomfortable.
Two articles on my site were covering almost the same subject.
Both were useful.
Both were properly indexed.
Both answered similar questions.
And both were competing for overlapping search intent.
I had accidentally created a small SEO architecture problem inside my own blog.
I'm building "SabrTime.in" (https://sabrtime.in/), a small Islamic companion app focused on practical digital tools for everyday worship. As a solo developer, I also manage the website, content, SEO, and product development myself.
While working on the site's content, I published two articles around Tasbeeh:
- How to Do Tasbeeh — A Complete Guide
- Digital Tasbeeh Counter: How It Works & Why Muslims Are Switching
The first article is about the practice itself.
The second is supposed to be about the technology and use case of digital Tasbeeh counters.
Sounds different enough, right?
At first, I thought so too.
But when I looked at the actual content and search intent, the overlap became obvious.
The Problem Wasn't Duplicate Content
This is where SEO gets misunderstood.
Keyword cannibalization doesn't necessarily mean you have two pages containing identical paragraphs.
The more interesting problem is intent overlap.
If two URLs are trying to satisfy essentially the same searcher's question, a search engine has less information about which page should be the primary result.
For example, imagine these two pages:
/page-a
"How to Do Tasbeeh"
/page-b
"Digital Tasbeeh Counter"
Their titles are different.
But if both pages explain:
- what Tasbeeh means
- how many times to recite it
- common Tasbeeh counts
- the same hadith
- how to count Tasbeeh
- why Muslims use a counter
- FAQs about Tasbeeh
...then the distinction between the pages starts becoming blurry.
That was happening on my site.
The two articles were not technically duplicates.
But parts of their search intent were duplicates.
And that distinction matters.
How I Found It
I didn't start by running an expensive SEO crawler.
I started with the simplest question:
«"Why do I have two pages that could answer the same searcher's question?"»
I compared the pages manually.
Then I looked at the queries and pages appearing in Google Search Console.
The useful report here is:
Search Console → Performance → Search results → Queries → Pages
If you investigate a particular query and discover multiple URLs receiving impressions for it, that's worth investigating.
It doesn't automatically prove cannibalization.
Google can legitimately rank multiple pages from the same site for one query.
But when those pages also have highly overlapping content and intent, you've got a stronger signal that your information architecture needs work.
The Two Pages Had Different Jobs — But I Hadn't Made That Clear Enough
This was the key realization.
The solution wasn't simply:
«"Delete one article."»
The solution was:
«Give each article a clearly different job.»
I defined the two pages like this.
Page 1 — The Practice
Primary intent:
«How do I perform Tasbeeh correctly?»
This page should answer questions about the Islamic practice itself.
It can cover:
- Meaning of Tasbeeh
- Correct method
- Common counts
- Tasbeeh after Salah
- Tasbeeh Fatima
- Common mistakes
- Relevant Islamic references
- Building a consistent dhikr habit
This is the educational/pillar page.
Page 2 — The Tool
Primary intent:
«How does a digital Tasbeeh counter work, and should I use one?»
Now the content becomes more product and technology oriented.
It can cover:
- What a digital Tasbeeh counter is
- Physical vs digital counters
- How a phone counter works
- Advantages and limitations
- Offline functionality
- Privacy considerations
- Tracking repetitions
- When a digital counter is useful
- How SabrTime implements the feature
The article still needs enough Islamic context to be useful.
But it shouldn't become another complete guide to Tasbeeh.
That's the important distinction.
I Removed Unnecessary Overlap
This was probably the most useful part of the exercise.
I went through the overlapping sections and asked:
«"Does this information belong here because it helps this page's primary intent, or am I including it because it's another keyword opportunity?"»
Those are very different reasons.
If a section existed only because I thought:
«"This keyword might help the page rank."»
I questioned it.
For example, the digital counter article doesn't need a massive standalone explanation of every aspect of performing Tasbeeh.
That's already the job of the Tasbeeh guide.
Instead, I can briefly explain the relevant concept and link to the detailed guide.
Conceptually:
Tasbeeh Guide
│
│ explains the practice
▼
Digital Tasbeeh Counter
│
│ explains the technology
▼
SabrTime Counter
Now the pages support each other instead of competing with each other.
Internal Linking Became More Important
Once I had separated the intent, internal links became much more meaningful.
Instead of randomly linking between articles, I could establish a relationship.
Tasbeeh guide → Digital counter
«If you prefer counting dhikr digitally, here's how digital Tasbeeh counters work.»
And:
Digital counter → Tasbeeh guide
«Before using a digital counter, learn the traditional method and recommended Tasbeeh practices.»
Now the relationship is obvious.
One page explains the practice.
The other explains the tool.
That's much cleaner than having two pages both trying to be the complete answer.
I Didn't Immediately Canonicalize One Page
Canonicalization was one of the first technical solutions I considered.
But I didn't want to use a canonical tag as a shortcut for a content architecture problem.
If two pages have genuinely different purposes, blindly canonicalizing one to the other can throw away useful search opportunities.
So my approach was:
- Identify overlapping intent.
- Decide which page owns the broader topic.
- Give the second page a narrower purpose.
- Remove unnecessary overlap.
- Improve internal linking.
- Monitor Search Console.
- Only consider stronger consolidation if the pages still don't have a meaningful distinction.
In other words:
Fix the information architecture before reaching for a technical directive.
The Interesting Part: This Is Basically Refactoring
As a developer, this way of thinking made the problem much easier.
Imagine I had two functions:
function tasbeehGuide() {
// explains Tasbeeh
// explains counts
// explains methods
// explains how to count
}
function digitalTasbeehCounter() {
// explains Tasbeeh
// explains counts
// explains methods
// explains how to count
// explains digital counting
}
That's a code smell.
The functions have overlapping responsibilities.
You'd probably refactor them.
SEO content can have the same problem.
Instead of thinking:
«"I need another article targeting another keyword."»
Think:
«"What responsibility does this URL own?"»
That mental model changed how I approached my blog.
My New Rule for Creating Content
Before publishing another article, I now ask five questions.
- What exact question does this page answer?
Not:
«"What keyword am I targeting?"»
But:
«"What does the searcher actually want?"»
- Do I already have a URL answering this?
Search the existing site before creating a new article.
- If I already have one, what is genuinely different here?
If the answer is just:
«"The title is different."»
That's probably not enough.
- Can I describe the difference in one sentence?
For example:
«"This article explains Tasbeeh."»
versus:
«"This article explains digital Tasbeeh counters."»
If I can't clearly articulate the distinction, the pages probably aren't differentiated enough.
- Where should the new article fit in my site's information architecture?
A blog shouldn't just be a collection of URLs.
It should behave more like a knowledge graph.
Related pages should have relationships.
What I'm Watching Now
I don't consider the problem "fixed" simply because I edited the pages.
SEO changes need to be measured.
I'm watching:
- Which URL receives impressions for broader Tasbeeh queries
- Whether the digital-counter page gains visibility for tool-related searches
- Whether the Tasbeeh guide retains its educational queries
- CTR changes
- Average position
- New queries appearing for each page
- Whether impressions become less fragmented between the two URLs
The important thing is that I'm not expecting an overnight result.
The goal isn't:
«"Make one URL rank #1."»
The goal is:
«Make it obvious which URL should rank for which intent.»
That's a much more sustainable strategy.
What I Learned as a Solo Developer
The biggest lesson wasn't actually about SEO.
It was about content architecture.
When you're building alone, it's incredibly easy to think about every article independently:
«"This seems like a useful topic. I'll write it."»
Then six months later, you have 30 articles that individually look fine but collectively overlap.
That's exactly like accumulating technical debt.
A little duplication doesn't look dangerous.
But eventually:
Article A ──┐
├── overlapping intent
Article B ──┘
becomes a problem you have to untangle.
So now I'm treating SEO content more like software architecture.
Every URL needs a responsibility.
Every important topic needs a clear primary page.
Related pages should support each other rather than competing unnecessarily.
The Bigger Lesson
If you have a small website and your rankings aren't behaving the way you expect, don't immediately assume you need more backlinks, more articles, or more keywords.
Sometimes the problem is simpler:
You may have already written the answer — twice.
Before publishing your next article, search your own website.
Look at the existing URLs.
Compare their titles, headings, FAQs, and search intent.
Then ask:
«"If I were Google, which of these two pages would I consider the better answer?"»
If the answer isn't obvious, that's probably your next SEO task.
I'm still experimenting with this on "SabrTime.in" (https://sabrtime.in/), but this change has already altered how I plan content.
I don't want to build a blog with hundreds of pages.
I want to build a site where every page has a reason to exist.
And, like good code, good content architecture should make the system easier to understand — not harder.
The pages behind this experiment
- "SabrTime.in" (https://sabrtime.in/) — the Islamic app I'm building
- "Digital Tasbeeh Counter" (https://sabrtime.in/blog/digital-tasbeeh-counter.html) — the technology/tool-focused article
- "Tasbeeh Guides" (https://sabrtime.in/blog/tasbeeh-guides.html) — the practice/educational side
If you're also building a content-heavy product as a solo developer, I'd be interested to know:
Have you ever discovered two of your own pages competing for the same search intent?
Top comments (0)