02
OLX Autos.
A scalable, SEO-oriented content platform, designed, built and deployed to sit inside the OLX Autos ecosystem.
- Industry
- Automobile MNC
- Services
- Design · Development · Deployment
- Platform
- Content & blog platform
The project
A content platform inside a marketplace.
A content and blog platform for OLX Autos: a CMS and a category structure the editorial team runs day to day, search and structured data that make every article findable, and caching, CDN and cloud hosting underneath it.
We took it end to end — the design of the reading experience, the engineering of publishing, search and permissions, and the deployment onto infrastructure that fits the wider OLX Autos ecosystem.
The challenge.
Content attached to a marketplace has to perform like the product around it.
Every article has two audiences at once. A reader wants the answer quickly on whatever device is in their hand; a crawler wants structure, metadata and markup it can interpret without guessing. Both have to be served by the same page, without one being bolted on afterwards.
The editorial side sets its own constraint: publishing cannot wait for a release. Writers, editors and reviewers each need their own reach into the system, which turns a blog into a permissions problem as much as a content one. And because a single article can carry unusual traffic, the platform had to be cached, distributed and hosted to absorb that rather than be tuned for it later.
- Two audiencesReaders and crawlers, served by one page.
- Editorial speedPublishing without a deployment.
- TrafficIndividual articles that spike.
Approach
How we approached it.
Structure first: what an article is, how it is categorised and who can publish it, before any of it is designed.
-
01Model the content
Article types, categories and the taxonomy the whole platform would hang off.
-
02Design the read
A reading experience that holds up from a phone on mobile data to a desktop.
-
03Engineer publishing
CMS, roles and on-site search, so editors run the platform without developers.
-
04Deploy for scale
Cloud hosting behind caching and a CDN, deployed by us end to end.
Design & architecture
The architecture.
Four layers between an editor pressing publish and a reader landing from search.
01Experience
- Article pages
- Categories
- On-site search
- Responsive design
02Publishing
- CMS
- Editorial roles
- Taxonomy
03Discovery
- SEO
- Structured data
- Internal linking
04Delivery
- Caching
- CDN
- Cloud hosting
Solution
What we shipped.
Technology
The system.
Publishing, discovery, delivery and experience, engineered as one platform rather than four add-ons.
01Publishing
- CMSEditors create and manage content without developer involvement.
- CategoriesA taxonomy that organises content for readers and for crawlers.
- User permissionsRoles that decide who can write, edit and publish.
02Discovery
- SEOMetadata, page structure and internal linking built in from the start.
- Structured dataSchema markup that describes every article explicitly.
- SearchOn-site search that gets readers to the right piece quickly.
03Delivery
- CachingCached responses that hold up when an article spikes.
- CDNPages and assets served close to the reader.
- Cloud hostingOrigin infrastructure that scales with demand.
04Experience
- Responsive designOne reading experience across phone, tablet and desktop.
Outcome
What it delivers.
-
01
Editorial independence
Content is created, categorised and published by the editorial team, with roles controlling who can do what.
-
02
Built to be found
Structure, metadata and schema markup on every article, with on-site search alongside.
-
03
Ready for traffic
Caching and CDN delivery in front of cloud hosting, deployed as part of the build.
Gallery
Project gallery
-
Article page
-
Structured data
-
Edge delivery
Next project
247 Tech
Start a project
Have something worth building?
Tell us what you’re building. We’ll tell you how we’d approach it, and what it takes to get there.
Let’s talk