Latest / 5 Minute UX / Making Images and Video Findable in Search
Transcript
- 0:08This lesson is Making Images and Video Findable in Search. Let's
- 0:12get started.
- 0:19A search engine cannot inherently identify the content
- 0:21of a video file, a PDF, or an image without explicit pointers
- 0:24embedded directly in the page code. This fundamental
- 0:26limitation means that primary search results often return
- 0:28links to new stories, but they rarely surface video assets
- 0:31unless specific optimization has been performed. The core issue
- 0:33is that these non-text assets remain invisible to the indexing
- 0:36process until textual cues are placed strategically within the
- 0:39site structure. Optimization relies on ensuring the right
- 0:41words are in the right places throughout the engine’s analysis
- 0:44of your site. When a user searches for a horse race, the
- 0:46engine needs to see a link with anchor text that explicitly
- 0:48reads “video of a horse race” to make that asset findable.
- 0:51Without this specific textual pointer, the engine simply
- 0:53cannot determine what the file contains, and it remains hidden
- 0:56from results. This dependency on text creates a clear
- 0:58requirement for how you structure your content. You must
- 1:00place these descriptive links near other relevant page text so
- 1:03the engine can properly index the asset. The entire system
- 1:05hinges on making these textual pointers visible to the search
- 1:08engine, which sets the stage for the specific anchor text
- 1:10requirements you will apply next.
- 1:17The first move is creating a link pointing directly to the
- 1:20asset, such as a video file. The anchor text for this link must
- 1:22explicitly describe the asset's content. You need to place this
- 1:25link near other text on the page that is relevant to the asset's
- 1:27subject matter. This context helps the search engine
- 1:29understand what the asset actually is. Consider a horse-
- 1:32race video. To make it findable, the link anchor text must read
- 1:34“video of a horse race.” This specific phrase acts as the
- 1:37textual pointer. Without this descriptive anchor text near
- 1:39relevant text, the search engine cannot determine the asset is a
- 1:41horse-race video. The engine relies on these explicit words
- 1:44to index the file. This requirement applies to any non-
- 1:46text asset you want to surface in search results. The anchor
- 1:48text does the heavy lifting of identification. It bridges the
- 1:51gap between the binary file and the human query. Ensure your
- 1:53anchor text is precise and descriptive. Vague links offer
- 1:56no value to the crawler. The search engine needs clear,
- 1:58explicit instructions on what the asset contains. This
- 2:00specific placement and wording creates the necessary
- 2:02connection. It allows the asset to be indexed alongside related
- 2:05content. The anchor text becomes the primary identifier for the
- 2:07video.
- 2:13The `alt` attribute provides the textual pointer that allows the
- 2:16engine to index non-text assets. When you place an image or video
- 2:20on the page, the search engine reads this code to understand
- 2:22what the asset is. It serves the same function as the descriptive
- 2:26anchor text you just reviewed, but it lives directly inside the
- 2:29asset’s tag. This ensures the content is identified accurately
- 2:32during the crawl. Beyond search visibility, adding `alt` text is
- 2:35always a good idea for usability and accessibility. Screen
- 2:38readers rely on this description to convey meaning to users who
- 2:41cannot see the visual content. So, you are solving two problems
- 2:44with one small piece of code. The engine gets the data it
- 2:46needs to index the asset, and the user gets the context they
- 2:49need to understand the page. Keep the text concise and
- 2:52descriptive, just like your anchor text. Avoid vague phrases
- 2:55that don't tell the engine what it is looking at. The specific
- 2:58words you choose become the searchable data. This direct
- 3:00textual link is what bridges the gap between the non-text file
- 3:03and the search index.
- 3:11Consider the structural failure that traps your content. If a
- 3:14page at the very bottom of your site structure lacks links back
- 3:17into the main site, you have created a dead end. Search
- 3:20engine spiders hit this wall and stop, preventing them from
- 3:23crawling further or properly indexing the asset you just
- 3:26optimized. You must ensure that even the deepest level of your
- 3:29hierarchy connects back to the core, so the crawler never gets
- 3:32stuck. Next, weigh the risk of duplicate content. It often
- 3:35hides in seemingly innocuous conveniences, like a "printer
- 3:38friendly" version that is an exact duplicate of a page in a
- 3:41PDF. Search engines view these identical copies as redundant,
- 3:44which can dilute your indexing. To prevent this, you can shield
- 3:47these kinds of pages with scripted links or use the
- 3:50`rel="nofollow"` link attribute. This stops the duplicate from
- 3:53being treated as primary content. Before you move to
- 3:56verifying your indexing, pause and audit your site map. Where
- 3:59does your structure end? If a user or a spider reaches a page
- 4:02with no exit, that asset is lost. Check your "printer
- 4:05friendly" templates now. Are they generating exact
- 4:07duplicates? If so, apply the `rel="nofollow"` attribute
- 4:10immediately. This ensures your unique, optimized assets remain
- 4:13the primary targets for search engines.
- 4:23So, when you publish that new horse-race video, you need to
- 4:26verify it is indexed and searchable before, or very
- 4:28shortly after, being publicly available. You check the page
- 4:31code to confirm the textual pointers, specifically the
- 4:34anchor text and alt attributes, are visible to the engine. You
- 4:37also confirm the site structure does not contain dead ends that
- 4:40would trap search engine spiders. This final check
- 4:43ensures the asset doesn't sit in a dead-end content page without
- 4:46links back to the main site. You verify that duplicate pages,
- 4:49like a printer-friendly version of a PDF, are shielded with a
- 4:52rel="nofollow" link attribute or scripted links. This prevents
- 4:56the spider from getting stuck or indexing duplicate content. When
- 4:59you apply descriptive anchor text and alt attributes, you
- 5:02make non-text assets findable in search engines. You identify the
- 5:05two primary textual pointers required for indexing, describe
- 5:08how dead-end structures prevent proper indexing, and apply the
- 5:11requirement that anchor text explicitly describes the asset's
- 5:14content near relevant page text. That is how you make sure the
- 5:18right words are in the right places throughout the site
- 5:20analysis, so the search engine can finally see your video.
- 5:26Welcome to The Take. I'm joined by a fellow practitioner and
- 5:29together we're going to dig into Making Images and Video Findable
- 5:32in Search — what it means in practice and what's worth
- 5:35remembering.
- 5:37[HOST] The bit about the "printer friendly" duplicate
- 5:40really caught my eye. It’s a classic trap where a small
- 5:43convenience feature quietly cannibalizes your indexing.
- 5:46[LEARNER] Exactly. I’ve seen clients lose significant traffic
- 5:49because they treated those duplicates as harmless. The
- 5:52`rel="nofollow"` tag is the only real shield, but most devs
- 5:55ignore it. [HOST] That’s the control issue. You’re deciding
- 5:58whether the engine sees one authoritative asset or a
- 6:01confusing pair of twins. [LEARNER] It’s frustrating
- 6:04because the user experience of a clean print view is so obvious.
- 6:07But the SEO cost is invisible until the rankings drop. [HOST]
- 6:10Right, and that’s where the structural wrappers fail. If the
- 6:14spider hits a dead end without an exit route, it stops crawling
- 6:17entirely. [LEARNER] Yeah, the "orphaned file" concept is
- 6:20terrifying. You think you’ve published the video, but if the
- 6:23context links are weak, it’s effectively gone. [HOST] The
- 6:26descriptive anchor text has to be specific. "Video of a horse
- 6:30race" isn’t just a label, it’s a signal. [LEARNER] I agree, but
- 6:33in practice, designers often use "Click here" or "Watch video."
- 6:36That’s lazy, and it kills the semantic connection. [HOST] It’s
- 6:40a usability trap. We optimize for the human click, but we
- 6:43forget the machine reading the tag. [LEARNER] With AI, this
- 6:46gets even more nuanced. LLMs might parse the alt text to
- 6:49generate summaries, so vague labels create bad data. [HOST]
- 6:52That’s a sharp point. If the alt text is generic, the AI summary
- 6:56will be generic too. [LEARNER] So the quality of our metadata
- 6:59directly impacts the quality of the AI’s understanding. It’s a
- 7:02direct pipeline. [HOST] Absolutely. We’re not just
- 7:05indexing for search, we’re feeding the training data for
- 7:08future assistants. [LEARNER] That changes the stakes. A bad
- 7:11alt tag isn’t just a missed click, it’s a corrupted fact in
- 7:14the model. [HOST] It forces us to be precise. We have to
- 7:17describe the asset with the same rigor we’d use for a database
- 7:21entry. [LEARNER] It’s a high bar, but it’s necessary. The
- 7:24cost of being vague is now paid by the machine, not just the
- 7:27user. [HOST] And that’s the real shift. We’re no longer just
- 7:30optimizing for a crawler, we’re curating the context for
- 7:33intelligent systems.