Every fix waited on engineering
The old blog was hand-coded, so any change sat in the engineering queue behind the actual product. Improvements we knew would work couldn't ship — and we watched rankings slip while we waited.
e-GMAT Blogs —
a content system, not a pile of posts
e-GMAT ranked well but couldn't move: every blog change waited on the engineering queue. I led a full rebuild on WordPress with the Extra theme — turning a flat list of posts into a system with real hierarchy, a conversion-minded article page, and a custom-built sidebar, extended with code wherever the theme fell short.
Ranking well, converting nothing
Strong content pulled readers onto article pages. The pages then did nothing with them — no recommendations, no path onward, no reason to sign up. Three gaps on every page:
- Where do I go after this article?
- What else here is worth reading?
- Why would I sign up?
Cut the engineering dependency
A setup anyone could edit — no code, no queue, no bottleneck.
Make every article a path forward
Each page had to recommend, cross-sell, and convert — not dead-end the reader it earned.
Give the blog a real spine
A true structure — home to category to subcategory to article — readers and search both follow.
The article page is the front door. People search a problem, not "e-GMAT blogs" — so they land mid-site, on an article. I designed everything around that page earning the next click.
I led this end-to-end on WordPress with Elegant Themes' Extra — coordinating with SEO, architecting the flows, and driving the junior designers. Where the theme couldn't reach, I took the code route rather than settle.
Two problems in one: how a reader finds the right page, and what that page does once they are on it. The decisions follow that split — and a few places where I had to out-build the theme.
3.1Chose the engine on purpose
I researched ten well-rated blog themes, shortlisted three, and picked Extra on three tests: how easily a non-coder could update it, whether it shipped the pieces a blog needs, and how far it could be customised.
Jannah.
Hestia
Kadence WP
OceanWP
Neve
BlocksyOur pick
Extraby Elegant Themes
Extraby Elegant Themes- Easy updates
- Blog capability
- Customization
3.2Treated the article page as the front door
Search visitors land on articles, not the home page — so that is where the work went. A register-free hook, sibling-category cross-links, and visual in-content link blocks turn a single answer into a reason to stay.
The article page does the converting — hooks and cross-links built into the template.
3.3Built a custom sidebar app
The theme's sidebar was too thin for the job, so I built my own. It adapts to the article — relevant reads, parallel categories, and the platform resources that match what the visitor came for.
A sidebar I coded from scratch — it changes with the article it sits beside.
3.4Closed every dead end
Three featured reads from the same category at the foot of each article, author pages to follow a writer, and breadcrumbs plus a secondary nav so a reader can always go up, across, or onward.
End of article: three featured reads from the same category.
3.5Gave the blog a spine
Home to category to subcategory to article, each level earning its place. The home page leads with featured and recent picks then fans into category chips; category and subcategory pages do the same one rung down.
A four-level hierarchy where a flat list of posts used to be.
3.6Out-built the theme where it mattered
A prescribed theme gets you most of the way, then resists the last stretch. Rather than settle for "good enough," I extended it with custom CSS and injected code — the sidebar app, the in-content modules, the spacing — so the design served the content, not the other way round.
| Before | After |
|---|---|
| Every update waited on the engineering queue | The content team publishes and edits on its own |
| A flat, reverse-chron list of posts | Home to category to subcategory to article |
| Articles dead-ended the reader | Related reads, author pages, and links onward |
| No reason or route to sign up | Register hooks woven into the template |
| A thin, generic theme sidebar | A custom sidebar that adapts to each article |