Illustrative case study

A fictional business. The figures are a modelled scenario, not a client result.

Ilu Pictures · Film production & streaming studio · Lagos

How a Lagos film studio made its catalogue the source search engines quote

An 11-month Content Engine programme for a creative & media studio in Lagos, Nigeria.

Video schema · Entity optimisation · Topic hubs · AI Overviews

★ Now showing ★

Ilu Pictures · 11 months · Middle East & Africa

Opening scene

The challenge

Fan wikis and piracy sites outranked the studio for its own film titles and cast, and AI answers cited unofficial sources.

Ilu Pictures produces and streams its own films, yet a search for any title returned someone else first: a fan wiki for the cast, a piracy mirror for “watch”, a forum thread for the watch order. Every one of those clicks was a fan who never reached the studio's legal stream — and AI answers were learning the story from the same unofficial sources.

The brief: make the studio's own catalogue the canonical source — for search results, knowledge panels and the answer engines that now sit above them.

Search result · month 0Before
harmattan bride cast
  1. 1fanwiki.exampleHarmattan Bride (film) — Cast, plot, trivia | Fan WikiUnofficial
  2. 2freemovz.exampleWatch Harmattan Bride Full Movie Free HDPiracy
  3. 3ilupictures.exampleWatch — Ilu PicturesOfficial
Search result · month 11After
harmattan bride cast
  1. 1ilupictures.exampleHarmattan Bride (2025) — Cast, trailer & where to stream | Ilu PicturesOfficial
  2. 2ilupictures.exampleHarmattan Bride cast: Adaeze Okon, Tunde Bakare & moreOfficial
  3. 3fanwiki.exampleHarmattan Bride (film) — Fan WikiUnofficial

The diagnosis

Audit: the programme of problems

A crawl of the catalogue, a knowledge-graph check on 40 flagship titles and a citation scan of 180 AI prompts. Eight findings set the running order.

  • T-01TechnicalCriticalCatalogue rendered client-side behind one /watch route — 140 films, one indexable URL.
  • T-02TechnicalCriticalNo VideoObject or Movie markup; trailers hosted only on third-party embeds.
  • E-01EntityHighKnowledge panels for 7 flagship titles linked to a fan wiki, not the studio.
  • E-02EntityHighCast names spelled three different ways across listings; release years conflicted.
  • C-01ContentHighSynopses were one-line taglines — nothing an answer engine could quote.
  • C-02ContentMediumZero pages for watch orders, soundtracks or locations — the queries wikis owned.
  • R-01TrustCriticalPiracy mirrors ranked top-3 for “[title] full movie” on 38 titles.
  • R-02TrustMediumNo clear “where to watch legally” signal on any page.

Feature presentation

The strategy, in four reels

Built on our Content Engine plan: Video schema, Entity optimisation, Topic hubs, AI Overviews — each one a reel that builds on the last. Pick a reel to see what shipped.

Now showing · Reel 1 · Months 1–3

Every film gets a real page

The catalogue lived inside one JavaScript player route, so search engines saw a single URL for 140 films. We gave every title its own server-rendered page with Movie, VideoObject and Clip markup, trailers with key moments, and a video sitemap.

  • 140 title pages with Movie + VideoObject schema
  • Trailer chapters as Clip markup (key moments)
  • Video sitemap with thumbnails and durations

Running time · 11 months

Month by month

  1. Month 01

    Crawl audit: 140 films hidden behind one player route.

    idx 104
  2. Month 02

    Server-rendered title pages ship; video sitemap submitted.

    idx 113
  3. Month 03

    VideoObject + Clip markup live; first trailer key moments shown.

    idx 127
  4. Month 04

    Cast & crew pages with Person schema; credits aligned.

    idx 148
  5. Month 05

    Knowledge panels for 4 flagship titles switch to the studio.

    idx 176
  6. Month 06

    First franchise hubs: watch orders and soundtracks.

    idx 211
  7. Month 07

    Lagos filming-locations hub; piracy mirrors fall off page one.

    idx 252
  8. Month 08

    Answer-first synopses rolled across the full catalogue.

    idx 296
  9. Month 09

    Fact boxes with legal stream links; AI citations hit 31.

    idx 341
  10. Month 10

    Genre hubs expand; sign-ups from organic pass +140%.

    idx 384
  11. Month 11

    64 title pages at #1; 52 tracked prompts cite the studio.

    idx 422

Box office

The results

Admit one · Result 1/4

+322%

Organic sessions

Index 100 → 422 against the pre-project baseline month.

1 / 4

Organic sessions: +322%

Modelled scenario for a fictional business — not a client result. Rankings and traffic are never guaranteed; see our Terms.

Organic sessions
+322%
Title pages ranking #1
9 → 64
Streaming sign-ups from organic
+177%
AI answer citations
52 queries
Organic sessions (index)+322%
0211422M01234567891011422
Title pages ranking #19 → 64
032649M010113218324431538645751856961106411
Streaming sign-ups from organic (index)+177%
0139277M01234567891011277
AI answer citations52 queries
02652M0123456789101152

The ranking marquee

Sample of tracked title queries, month 0 vs month 11.

Keyword rankings before and after
QueryHeld by (before)BeforeAfter
harmattan bride castFan wiki61
lagoon kings where to watchPiracy mirror141
the danfo diaries season 2Fan wiki91
yaba sunday soundtrackLyrics site—1
eko nights watch orderForum thread232
nollywood thriller films 2026Listicle413
ilu pictures new releasesAggregator41
third mainland film locationsBlog—1

Coming soon · your title

Get a plan like this

Video schema, entity work, topic hubs and AI-answer readiness — scoped to your catalogue in the Content Engine plan.

← Back to all case studies