What Videojam is
Videojam is our own platform for music videos, DJ sets and short films, live at videojam.live. As of November 2026 it carries about 300 short films and eight festivals and series with their own hubs, plus Videojam Fest 2026. We built the platform, film for it and run it, so every number in this article is from a property we control and can show.
That size is the SEO problem. A catalogue of videos, artists, genres and events can generate thousands of URLs, most of them thin: a title, an embed and a few words. Put all of them in the index and you dilute the pages that deserve to rank. So the work was built around restraint: decide what deserves to be indexed, then make that content readable by search engines and AI crawlers.
What we built
The SEO work is part of the platform, not a plugin on top of it:
- An indexation gate: a stored flag for video pages and noindex rules for hub pages keep thin pages out of the sitemap and the index.
- llms.txt generated from the same gate, and IndexNow pings when pages are published.
- A robots.txt that names Googlebot, Bingbot, OAI-SearchBot, GPTBot, PerplexityBot, ClaudeBot and Google-Extended.
- JSON-LD for VideoObject, checked against Google’s required fields, plus FAQPage, ItemList, CollectionPage and BreadcrumbList.
- Programmatic per-genre text, only for genres with enough source material, assembled from existing editorial notes, glossary entries and comparison tables.
- A genre taxonomy of hub pages, with server-rendered links to the current chart and playlists from the home and DJ-sets pages.
- A Wikidata entity in the Organization sameAs, visible curator bylines, and a DOM-based checker that reads the rendered HTML the way a crawler does.
What the exports show
The web search figures are from the Search Console chart export of 15 November 2026, which runs from 1 August to 13 November. Over those 15 weeks web search shows 17,469 impressions and 342 clicks, a click-through rate of 1.96%, at an average position of 21.2. That is the “17.5k in 15 weeks” in the title: the total for the window, including the quiet weeks at its start. Three other sets of figures come from exports of 2 November 2026 that have not been refreshed: the coverage report, the query and page rows for 4 to 31 October, and the AI-features report. Each is dated where it appears.
Month by month, from the same export:
- August 2026: 597 impressions, 17 clicks.
- September 2026: 1,864 impressions, 48 clicks.
- October 2026: 10,025 impressions, 207 clicks.
- 1 to 13 November 2026: 4,983 impressions, 70 clicks, in 13 days.
ImpressionsClicks
Every day in the chart
| Date | Impressions | Clicks |
|---|---|---|
| 2026-08-01 | 19 | 0 |
| 2026-08-02 | 24 | 0 |
| 2026-08-03 | 14 | 0 |
| 2026-08-04 | 10 | 0 |
| 2026-08-05 | 7 | 0 |
| 2026-08-06 | 14 | 0 |
| 2026-08-07 | 7 | 0 |
| 2026-08-08 | 6 | 0 |
| 2026-08-09 | 29 | 3 |
| 2026-08-10 | 19 | 1 |
| 2026-08-11 | 21 | 0 |
| 2026-08-12 | 12 | 0 |
| 2026-08-13 | 20 | 1 |
| 2026-08-14 | 14 | 4 |
| 2026-08-15 | 19 | 0 |
| 2026-08-16 | 22 | 0 |
| 2026-08-17 | 13 | 0 |
| 2026-08-18 | 20 | 0 |
| 2026-08-19 | 11 | 0 |
| 2026-08-20 | 15 | 1 |
| 2026-08-21 | 12 | 3 |
| 2026-08-22 | 18 | 0 |
| 2026-08-23 | 22 | 0 |
| 2026-08-24 | 19 | 3 |
| 2026-08-25 | 27 | 0 |
| 2026-08-26 | 26 | 0 |
| 2026-08-27 | 29 | 0 |
| 2026-08-28 | 34 | 0 |
| 2026-08-29 | 31 | 0 |
| 2026-08-30 | 34 | 1 |
| 2026-08-31 | 29 | 0 |
| 2026-09-01 | 13 | 0 |
| 2026-09-02 | 18 | 2 |
| 2026-09-03 | 13 | 1 |
| 2026-09-04 | 16 | 1 |
| 2026-09-05 | 14 | 1 |
| 2026-09-06 | 24 | 0 |
| 2026-09-07 | 20 | 0 |
| 2026-09-08 | 16 | 0 |
| 2026-09-09 | 27 | 0 |
| 2026-09-10 | 23 | 0 |
| 2026-09-11 | 26 | 0 |
| 2026-09-12 | 26 | 1 |
| 2026-09-13 | 22 | 1 |
| 2026-09-14 | 26 | 1 |
| 2026-09-15 | 21 | 0 |
| 2026-09-16 | 24 | 0 |
| 2026-09-17 | 12 | 1 |
| 2026-09-18 | 13 | 0 |
| 2026-09-19 | 13 | 0 |
| 2026-09-20 | 11 | 1 |
| 2026-09-21 | 10 | 0 |
| 2026-09-22 | 13 | 0 |
| 2026-09-23 | 133 | 4 |
| 2026-09-24 | 185 | 2 |
| 2026-09-25 | 206 | 6 |
| 2026-09-26 | 194 | 4 |
| 2026-09-27 | 163 | 4 |
| 2026-09-28 | 167 | 4 |
| 2026-09-29 | 222 | 7 |
| 2026-09-30 | 193 | 7 |
| 2026-10-01 | 196 | 5 |
| 2026-10-02 | 218 | 8 |
| 2026-10-03 | 214 | 4 |
| 2026-10-04 | 255 | 1 |
| 2026-10-05 | 223 | 3 |
| 2026-10-06 | 237 | 5 |
| 2026-10-07 | 244 | 3 |
| 2026-10-08 | 232 | 2 |
| 2026-10-09 | 253 | 7 |
| 2026-10-10 | 231 | 1 |
| 2026-10-11 | 248 | 3 |
| 2026-10-12 | 269 | 4 |
| 2026-10-13 | 306 | 5 |
| 2026-10-14 | 359 | 7 |
| 2026-10-15 | 387 | 8 |
| 2026-10-16 | 441 | 4 |
| 2026-10-17 | 389 | 5 |
| 2026-10-18 | 357 | 6 |
| 2026-10-19 | 408 | 7 |
| 2026-10-20 | 332 | 8 |
| 2026-10-21 | 404 | 7 |
| 2026-10-22 | 456 | 15 |
| 2026-10-23 | 508 | 24 |
| 2026-10-24 | 458 | 15 |
| 2026-10-25 | 356 | 7 |
| 2026-10-26 | 348 | 10 |
| 2026-10-27 | 375 | 6 |
| 2026-10-28 | 335 | 9 |
| 2026-10-29 | 344 | 3 |
| 2026-10-30 | 316 | 10 |
| 2026-10-31 | 326 | 5 |
| 2026-11-01 | 344 | 7 |
| 2026-11-02 | 317 | 4 |
| 2026-11-03 | 359 | 7 |
| 2026-11-04 | 343 | 6 |
| 2026-11-05 | 335 | 6 |
| 2026-11-06 | 332 | 4 |
| 2026-11-07 | 356 | 2 |
| 2026-11-08 | 328 | 3 |
| 2026-11-09 | 307 | 8 |
| 2026-11-10 | 327 | 7 |
| 2026-11-11 | 347 | 6 |
| 2026-11-12 | 397 | 0 |
| 2026-11-13 | 891 | 10 |
The latest 28 days
In the latest 28 days, 17 October to 13 November, the property had 10,695 impressions and 207 clicks at an average position of 20.7. In the 28 days before, 19 September to 16 October, it had 5,823 impressions and 109 clicks at 18.1. Clicks grew 1.90 times and impressions 1.84 times, so the two moved almost together. The average position got worse, from 18.1 to 20.7: more queries are now entering at page two and three, which adds impressions faster than it adds visits.
The first half of November held at October’s level, between 307 and 397 impressions a day. Then 13 November recorded 891 impressions and 10 clicks, the highest day in the series. Search Console’s first figure for 14 November, still provisional when we exported, is 777. Two days are not a trend, and we have not tied the jump to a change on the site, so we report it with its dates and nothing more.
What is indexed
The coverage report of 23 October 2026 shows where the catalogue stands: 970 pages indexed and 1,475 not, of which 367 are excluded by noindex on purpose, 632 crawled but not indexed, 377 discovered but not indexed, 92 alternates with a canonical elsewhere, 6 not found and 1 redirect. Read as a funnel: 2,445 pages known to Google, 2,068 crawled, 970 indexed, 810 shown in search and 77 clicked in the 28 days from 4 to 31 October. The first three steps are a one-day snapshot and the last two a 28-day window, so the step from indexed to shown compares two periods.
Which queries carried it
Search Console lists only queries that are not anonymised. In the 4–31 October export those rows add up to 3,139 of the 9,397 impressions, grouped like this: genre names 955, artists and DJs 785, “what is…” questions 774, live and DJ sets 322, Videojam by name 166, and other listed queries 137. Most of the visibility is for the subject, not the brand.
The page-row view of the same days says which kinds of page earned it: glossary pages 2,202 impressions, events 1,476 (festivals 954 and series 522), genre hubs 1,354 and DJ-set subgenre pages 797. Page rows exceed the property total because one search can count on more than one URL, so these are compared with each other, never added to the 9,397.
The glossary result is the clearest lesson. Definition queries reward a page that states the definition in its first sentence, which is how those pages are written.
AI features, reported separately
The AI-features export for 1 August to 31 October 2026 is a different file from web search. It shows 749 impressions, with no click column and no queries. 729 of those impressions are dated from 23 September onward. Its daily rows add up to 778 rather than 749; we quote the export’s total and point out the gap rather than pick the bigger number.
We do not treat the 749 as part of the 12,486 web search impressions for the same three months, 1 August to 31 October 2026, and we do not subtract one from the other. They are different reports, and an AI impression is not a visit.
How to get your site cited by ChatGPT, Perplexity and Gemini
Correlation, not causation
Crawl-path and event-hub work shipped around 22 September 2026. On that day the property recorded 0 clicks and 13 impressions. On 23 September it recorded 4 clicks and 133 impressions, and the series stays higher from there. The AI-features report moves from the same date.
That is a correlation. Search Console cannot attribute a change in impressions to a deploy, and other things can change at the same time: Google’s own crawling schedule, new pages being published, interest in a particular event. We draw the date on the chart because it is honest to show it, and we stop short of saying the deploy caused the jump.
What we can say with confidence is narrower and still useful. The pages that carry the impressions now are the kinds of page the work was aimed at: glossary definitions, event hubs and genre hubs. The indexation gate kept 367 thin pages out on purpose. And the export starts on 1 August, so we make no claim about where impressions stood before then.
What to take from it for your own site
Most sites do not have Videojam’s catalogue, but the approach transfers. Start from your own coverage export and name every not-indexed reason before writing anything new. Decide which pages deserve the index and keep the rest out deliberately, with noindex and a sitemap that matches. Link to the pages that matter from the body of related pages, not only from the menu. Write the first sentence of each important page as the answer to its query. Then read the same reports again after Google has recrawled, and report the result with its dates, including when nothing moved.