Allied Bank: Half a Content Cohort into the Top 20 in 4 Weeks

Allied Bank is one of Pakistan's largest banks. Its website ranked well for its own name and very little else, which is the normal condition for an incumbent brand: the product pages carry the domain, and every question a customer asks before they are ready to open an account gets answered somewhere else.

We were engaged to fix the second half of that. This is what the first cohort did in its first four weeks.

The problem

A bank's search footprint is usually shaped like a barbell. Enormous brand volume at one end, product pages at the other, and almost nothing in the middle where the actual decision happens. Someone asking how to register for mobile banking, whether an investment is halal, or what a bank statement is used for is a customer in the making. Those questions were being answered by forums, aggregators and competitors.

The commercial problem is that this traffic is cheap to earn and expensive to buy. The strategic problem is that the answers being read were not the bank's.

What we did

Mapped the question space, not the keyword list. We built the plan around what a customer asks in sequence rather than around search volume alone, which is what produces a cluster that ranks together instead of ten posts competing with each other.

Wrote to a defined structure. Every post opens with a self-contained answer, uses the question as the heading, and carries one verifiable specific in the first paragraph. This is the same structure that makes a passage quotable by an answer engine, so the work serves classic search and AI search at once.

Handed execution to the client's team. We produced the plan, the briefs and the standard. Allied Bank's own team published, which is why the cohort shipped at roughly six posts a week without an agency bottleneck.

Watched for self-competition. Several target terms were already held by the bank's own product pages. Those were deliberately left alone rather than attacked with a blog post, because two of your own pages arguing for one query is how both lose.

What happened

Within four weeks of the first cohort going live, half the posts had reached the top 20 for their primary keyword and a third were in the top 10, two of them at position 2. The cohort's average position settled at 5.8.

The engagement numbers were more interesting than the ranking numbers. The deepest explainers, on SME banking and on halal investment, held readers for roughly twice the site average. That matters more than it sounds: a bank's blog usually bounces, and dwell time on a pre-purchase question is the closest available signal that the page did its job.

Bing moved too, with clicks up around a third month on month and impressions up around a quarter, though that channel remains mostly brand-driven and we would not claim the content produced all of it.

What we would do differently

Start the highest-volume terms sooner. The largest single opportunity in the plan, a product term with five-figure monthly volume, was scheduled late and is still held by a page ranking in the twenties. It should have been in the first cohort.

Get analytics access on day one. We had Search Console but not the client's analytics for most of the engagement, which meant reporting on rankings and engagement while the conversion half of the story stayed invisible. Ask for it before the first post ships, not after.

Plan for the pause. Publishing stopped at 18 of 75 planned posts. Cohorts lose momentum when they stop, because freshness and internal-link accumulation both compound. A slower but continuous cadence beats a fast burst followed by silence.

Where this goes next

The pattern holds beyond banking. Any incumbent with strong brand search and weak question coverage has the same barbell, and the same fix: find the questions your customers ask before they are ready to buy, answer them better than the aggregators, and make sure your own pages are not competing with each other while you do it.