Rich Content SEO

I start by mapping the user journey for the target query. If someone searches 'how to install a smart thermostat', the first thing they want is a clear walkthrough. On page 1 of the SERPs, 7 out of 10 results include a video from YouTube. That tells me a video should be the primary rich element for that page. But if the query is 'best budget wireless earbuds 2025', the dominant format is a comparison table with prices and ratings. I would use an HTML table with sortable columns, not a video.

Next, I pick one primary rich element per page. Throwing video, infographic, interactive chart and an image carousel onto one page overloads both the user and performance metrics. I have a decision rule: if the media does not answer a specific sub-question that the text cannot handle efficiently, leave it out. For example, on a page about [on page seo](/on-page-seo/), a short screencast showing how to optimise a title tag is useful. An infographic about '10 on-page factors' is not — the text already lists them.

Then I structure the text itself to be rich in the semantic sense. I use descriptive headings (H2 and H3), short paragraphs, and internal links to related topics like [seo copywriting](/seo-copywriting/) or [alt text](/alt-text/). I also include a table for data that needs comparison. For a recent client, I rewrote a page targeting 'best mattresses 2025'. The original had a 600-word paragraph comparing five mattresses. I turned it into a table with columns for price, firmness, trial period and rating. The bounce rate dropped from 72% to 51% and the average time on page increased from 1:12 to 2:47.

Finally, I align the content with search intent using the [aida model](/aida-model/) as a loose guide. For a transactional query, rich content means a product video or 360-degree image. For an informational query, it means a step-by-step diagram or a calculator. I test the chosen element with five real users from my target audience before publishing. If they find it distracting or irrelevant, I cut it. Numbers drive these decisions, not hunches.

The biggest watch-out: rich content is not a ranking factor on its own. Google’s helpful content system looks for usefulness, not media volume. I have seen a plain text page with clear headings and great writing outrank a page with a flashy video but thin copy. Do not add a video just because your competitor has one. Add it only if it helps someone complete their task faster.

Load time is the second trap. A single 1080p video can add 1.5 MB to a page. On a 4G mobile connection that means an extra 3–5 seconds of load time. Google's Core Web Vitals penalise slow pages. My rule: compress videos to H.265, lazy-load all images below the fold, and test on mobile with a throttled 3G connection. If the Largest Contentful Paint (LCP) exceeds 2.5 seconds, I simplify the rich element.

People often confuse rich content with rich results. You need structured data (like FAQ schema or HowTo schema) to get a rich snippet in the SERP. That is separate from embedding a video or an infographic. I have worked with clients who spent hours creating custom graphics but forgot to add product schema. Their pages got zero rich results. Structured data lives in the HTML markup, not in the visual content. For more on that, see [seo and content marketing](/seo-and-content-marketing/) considerations.

Another watch-out: accessibility. A video without captions excludes hearing-impaired users and misses the chance to rank in video search. An infographic without alt text is invisible to screen readers. I now write [alt text examples](/alt-text-examples/) for every image and include a text transcript beneath each video. This also helps Google understand the content of the media.

Finally, avoid interactive tools unless they genuinely save time. A mortgage calculator on a finance page is valuable. A spinning wheel for 'what to have for dinner' is not. I once added a quiz to a blog post thinking it would boost engagement. It increased time on page by 4 seconds but had a 67% exit rate from the quiz page. Users came to read, not to play. Now I ask: does this element reduce the steps to the user’s goal? If no, I remove it.

Early in my SEO career, I embedded a video on every product page. I thought more media meant better rankings. Instead, the video slowed the page down by 2 seconds on mobile and users who just wanted the specifications had to scroll past a player. The conversion rate dropped by 12% compared to the version without video. I now only use video when it answers a specific question that text cannot efficiently answer, like an assembly tutorial or a product demo.

I also assumed infographics always help. I spent £400 commissioning a custom infographic for a blog post comparing 10 email marketing tools. The infographic looked great on desktop but was 2000px wide and impossible to read on mobile. The bounce rate on mobile was 84%. I learned that infographics are only useful when the data is complex enough to warrant a visual, and even then they must be responsive. Now I test every graphic on a 375px viewport before publishing.

Mobile was another blind spot. I created a detailed table with 8 columns comparing laptop specs. On desktop it looked like a New York Times data graphic. On mobile it was a horizontal scroll nightmare. I had to rebuild it as a series of cards with key stats. That experience taught me to design for mobile first and then expand to desktop. Today I use responsive tables that collapse into list views on narrow screens, or I simply use a bullet list if the data set is small.

Another mistake: trying to cram multiple rich elements into one page. I had a page with an embedded video, an image carousel, an interactive chart showing price history, and an audio interview clip. The page was 8 MB and took 12 seconds to load on 3G. The user engagement was terrible. Now I follow the one primary rich element per page rule. I decide which format serves the primary intent and strip everything else. I documented that rule in my [seo content strategy](/seo-content-strategy/) notes.

Finally, I ignored structured data for years, thinking rich content would naturally lead to rich results. It does not. I had a beautifully formatted how-to guide with embedded videos and screenshots, but no HowTo schema. The page showed as a plain blue link in the SERP. After adding the schema, I got a rich result with step-by-step previews and the click-through rate went from 3.1% to 7.8%. That is when I understood: rich content and structured data are separate tools that work best together.