Loom built one of the most effective product-led growth engines in SaaS history.
Shared video links drove traffic. Traffic drove signups. Signups drove more shared videos. Repeat.
By the time Atlassian acquired them in November 2023 for approximately $975 million, they’d accumulated 25 million users and 200,000 company customers—largely without a traditional content marketing operation.
That context matters for everything that follows. Loom’s content strategy differs from that of a typical SaaS blog because it was never the primary growth driver. The product was.
But post-acquisition, with enterprise ambitions and a shifting competitive landscape, there’s a lot to learn from how they’ve set up their content and SEO efforts.
If you’re a SaaS founder or marketing leader with a great product and a nagging feeling that content could be doing more work for you, this is for you.
In this breakdown (essay, teardown, whatever you’d like to call it), you’ll see:
- Where Loom’s traffic comes from
- How their site is structured and why it works
- Blog UX and content presentation
- How they’ve mapped content across the funnel
- How they show up in AI search
- What I’d suggest they do differently, and what you can learn
Heads up: I’m an independent SaaS SEO consultant who spent way too long in Semrush for this. Loom didn’t ask me to write this, didn’t pay me to write this, and probably didn’t know I was writing this.
Loom’s overall traffic profile
Loom.com attracts around 285K monthly visitors as of April 2026.
While their April 2026 traffic is down 1.48% from March 2026, Loom is experiencing an overall steady increase in traffic, which is impressive, given reported declines across B2B SaaS websites.
For instance, compared to April 2025, Loom’s traffic has grown by over 27%.
178K (around 62.8%) of Loom’s 285K visits are driven by branded or direct search.
I wasn’t too surprised at that number, considering Loom’s popularity and how I personally use the tool. Most of the time, I just type “loom” into Google or use their Chrome plugin whenever I want to record a video.
Let’s now examine what makes up Loom’s top pages.
The homepage naturally gets most of the traffic. From there, it links to key landing pages and individual feature pages rather than a single catch-all features overview.
Each feature or capability gets its own URL and its own copy.
It would have been nice to have the features mentioned in the homepage copy. Right now, you can only find the links in the dropdown menu or the footer area.
The same logic applies to their use case pages. Loom has built out pages for different categories of users—engineering teams, sales, marketing, design—and while the page structure is consistent across all of them, the copy and examples are tailored to each audience.
For example, on the sales teams page, Loom highlights features such as tracking, personalization, and integrations that only salespeople would find useful.
This audience-specific positioning improves SEO and conversion performance. Why? Category-specific pages capture the searches buyers run (“video prospecting tool,” “sales video tools”) rather than relying on a generic product page to rank for all of them.
The keyword data backs this up. Outside the homepage, the terms driving the most traffic to loom.com are category keywords. People are finding Loom by searching for what they’re trying to do and the terms used to describe Loom’s product offerings.
Category keywords are searches for a type of tool rather than a specific one—“screen recording software,” “async video tool,” “video messaging platform.” These attract buyers who know the solution category they want but haven’t chosen a product yet.
Where is Loom’s blog?
So far, I’ve analyzed traffic for “loom.com.” But what about Loom’s blog? Is all their traffic going to the home page, feature, and use case pages?
The blog situation is more interesting than it first appears—because the Loom blog doesn’t live on loom.com anymore.
Post-acquisition, Loom’s editorial content moved to atlassian.com/blog/loom/. That subfolder ranks for over 20,700 keywords, pulls in 82,300 monthly visitors, and carries an estimated traffic value of $291,400. Those are strong numbers. But the more important detail is why I think they’re strong.
Atlassian’s domain authority is 79. Loom’s is 63.
By hosting the blog on the parent domain, every piece of Loom content is borrowing Atlassian’s authority. A post published on atlassian.com/blog/loom/ starts with a structural advantage that a standalone loom.com/blog post simply doesn’t have.
Now look at who’s landing on that content. Only 49 of the blog’s ranking keywords are branded—a sharp contrast from the people landing on loom.com.
That means the overwhelming majority of people visiting Loom’s blog have probably never heard of Loom before they clicked. The blog is doing acquisition work, not just serving people who already use the product.
What are the keywords driving that traffic?
Two kinds:
- Jobs-to-be-done (JTBD) keywords
- Tool listicles (Best X software)
JTBD keywords (“jobs to be done”) are searches built around a task someone is trying to complete — “how to record a screen on Mac,” “how to send a video update to a client.” The person isn’t looking for a product yet. They’re looking for a way to get something done. Good JTBD content meets them at the task and introduces the product as the solution.
“Productivity tools,” “how to screen record on Mac,” “how to record your screen.” That’s the pattern.
When I filtered by traffic value rather than raw visit counts, the listicles and more JTBD content carry the most commercial weight.
The highest-traffic posts aren’t always the most valuable ones. The ones with purchase intent behind them are.
Search intent describes what someone wants when they type a query.
There are four types of search intent. Informational (they want to learn something), commercial (they’re comparing options before buying), transactional (they’re ready to sign up or purchase), and navigational (they’re looking for a specific website or page).
Matching content to the right intent is what separates traffic that converts from traffic that bounces.
There’s an AI search layer on top of this, too.
Around 1,700 of their keywords are triggering AI overviews, sending roughly 11,000 visitors with an estimated traffic value of $21,800.
Those are JTBD keywords doing double duty—ranking in traditional search and getting picked up in AI-generated answers.
What businesses can take from this: If you have access to a higher-authority parent domain, using it to host your blog is a head start most companies never think to take.
If you don’t, the content mix still applies. Create JTBD content and tool listicles, as these have commercial intent metrics that target what buyers are searching for.
💡The atlassian.com/blog/loom/ subfolder has no alternatives or review content to speak of. Aside from three comparison pages on loom.com itself, that entire content type is absent from their blog.
Alternatives and review content target buyers who are actively evaluating, as well as people who’ve already decided they want a tool in this category and are now narrowing the field. That’s one of the highest-intent traffic available in organic search, and right now, third-party sites are capturing all of it.
If I were advising the Loom content team, I’d start here. A “best [competitor] alternatives” post, a handful of “Loom vs [competitor]” comparisons, and a few reviews of competitor tools would cover the entire bottom of the funnel.
Blog UX and content presentation
Loom’s blog is clean and consistent.
You can tell there’s a template behind it, and I don’t mean that in a bad way. Consistency at scale is hard, and they’ve pulled it off.
The titles are simple and descriptive. No clever wordplay, no bait-and-switch headlines.
They tell you exactly what the article covers, which is exactly what search engines reward.
Each post includes an author bio and publish date—small trust signals that demonstrate E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness).
The author bio is clickable, too, so that readers can browse other articles by the same writer. That’s a smart way to build internal linking and keep readers moving through the blog.
Speaking of authors, Jeong writes most of Loom’s blog content, and his intro style is worth studying.
For most articles, he leads with a feeling rather than a fact. In his article on creating GIFs, he opens by describing the specific moment that makes someone want to share a GIF in the first place.
In his explainer video piece, he paints a picture of an employee hunting for a PM tool, completely lost, who could really use a two-minute walkthrough. You’ve been that person. I’ve been that person. That’s the point.
It’s a story-driven approach that earns the reader’s attention before asking for it—and it works because it mirrors the exact emotional state that triggered the search.
Structure-wise, the articles lean heavily on images. Most posts have five or more, which does two things: breaks up long blocks of text and gives readers visual anchors to orient themselves while scanning.
Another thing I like about their “how-to” articles is that they include incline CTAs. These offer multiple conversion opportunities, even if readers don’t reach the end of the page.
For the “best X tools” listicles, there’s a clear structural pattern across most of the articles:
Intro → context paragraph (why the category matters and the different types of tools available) → tool name → image → description → key features → pros → cons → pricing → conclusion.
Some posts also include a “how to evaluate [category tool]” section toward the end. That’s a smart addition because it helps undecided readers make a decision instead of bouncing back to Google.
Most of the articles fall between 2,500 and 3,000 words—long enough to feel comprehensive, but focused enough to stay readable.
One thing I noticed, though, is that Loom rarely uses TL;DRs, table of contents sections, or FAQs in these posts. For a blog pulling in more than 82,000 monthly visitors, that feels like a missed opportunity.
A table of contents would make longer articles easier to navigate. FAQs could help capture more People Also Ask visibility. TL;DRs would help retain scanners who want quick takeaways before committing to the full article.
None of these improvements requires creating new content. They simply add more structure and usability to existing content.
Internal linking strategy
Loom’s internal linking strategy is straightforward: keep readers inside the Atlassian ecosystem.
Every article links back to Loom properties first, such as product pages, feature pages, and other blog posts.
Most of the articles I checked had at least four links to other Atlassian or Loom pages. That deliberate choice to pass authority between pages reduces exits to competitor sites and keeps readers moving through content that eventually leads to a signup.
External links go to reputable third-party sources—the kind of citations that signal credibility without sending readers somewhere they’d rather stay. Think industry publications, research sources, and established reference material. Nothing that competes with Loom for the same buyer.
The lesson here is simple but easy to overlook. A lot of SaaS blogs link generously to external sources and barely at all to their own product. Loom does the opposite. Every article is quietly doing pipeline work—pulling readers deeper into the ecosystem rather than releasing them back to Google.
What Loom isn’t doing and what you can learn from that, too
Every teardown has two lessons: what to copy, and what to do that they haven’t.
No alternatives or review content on the blog
This was the most obvious gap I noticed. Third-party sites are ranking for keywords such as “Loom alternative,” “Loom vs Vidyard,” and others, capturing buyers who are one step away from a purchase decision.
Loom isn’t competing for that traffic at all. If you’re building content in any SaaS category, alternatives and comparison content is where you start, not where you get around to eventually.
No TL; DRs, FAQs, or table of contents
I mentioned this in the blog UX section, but it’s worth flagging again here because it’s so fixable. Although AI search is still unpredictable, most content teams that add features such as TL; DRs and FAQs see increased citations and visibility.
Case studies and proof content aren’t doing enough commercial work
Loom has compelling proof points. 93 million videos recorded in 2025. 245 million meetings replaced. These are striking numbers that don’t appear to have dedicated landing pages or BOFU case study content built around them.
The data lives in a year-in-review blog post. It should be living in sales enablement content, on comparison pages, and in the kind of ROI-oriented case studies that enterprise buyers need before they sign a contract.
Feature pages aren’t surfaced in the homepage copy
Loom’s individual feature and use case pages are doing real SEO work, but you can only find them through the dropdown menu or the footer.
A visitor who lands on the homepage and reads the copy won’t naturally discover them. That’s a missed opportunity to funnel homepage traffic into pages with more specific commercial intent.
What this means for you
Reading about Loom is useful. Knowing what to do with it is the point. Here’s how each major finding from this teardown translates into something you can apply.
1. Product-led distribution beats content-led distribution when the product allows for it
What Loom does: Every shared video URL is a marketing asset. A non-user clicks a link, lands on a Loom-branded page, and gets pulled into the funnel without Loom spending a cent on acquisition for that visit. That loop is what built 25 million users.
What you could do: Before you invest heavily in content, audit your product for sharing mechanisms that put your brand in front of non-users. If mechanisms such as shared outputs, embeddable widgets, public reports, and referral links exist, build content to amplify them. If they don’t, content has to do more of the heavy lifting, and you’ll need to plan accordingly.
2. Borrowed authority compounds faster than earned authority
What Loom does: Loom’s blog lives on atlassian.com, a DA 79 domain. Every post starts with a structural advantage that a standalone loom.com/blog post wouldn’t have. The result is 82,300 monthly visitors and 20,700 ranking keywords, with very little branded search behind those numbers.
What you could do: You probably don’t have a DA 79 parent domain to lean on, but the principle still applies.
Guest post on high-authority publications in your category. Earn links from established industry sites. Build topical authority in a focused niche before expanding into adjacent topics.
Publish where authority already exists, then earn your own.
3. JTBD content is the most durable traffic you can build
What Loom does: Loom’s highest-traffic blog posts are jobs-to-be-done queries like “how to record your screen” and “how to screen record on Mac.” These searches don’t go stale. They’ll exist as long as people have screens and need to share what’s on them.
What you could do: Identify the tasks your buyers are trying to complete before they know which product they want. Write content that meets them at the task and introduces your product as the solution. Task-based content attracts buyers earlier than category content does, and it ages well.
4. Listicles and comparisons do the heaviest commercial work
What Loom does: When you sort Loom’s blog by traffic value rather than raw visits, the highest-value pages are tool listicles and comparisons. The traffic and revenue numbers don’t always match, and listicles are where commercial intent is concentrated.
What you could do: If you’re starting a content program from scratch, your first ten articles should be JTBD guides, “best [category] tools” listicles, and comparison content. These are the pages that capture buyers in evaluation mode, when they’re closest to a purchase decision.
5. Blog UX is a conversion lever you can pull this week
What Loom does: Loom’s blog has clean templates, consistent author bios, and strong intros, but it’s missing TL;DRs, tables of contents, and FAQs. For a blog at their scale, those gaps are leaving placements and on-page engagement on the table.
What you could do: Add a table of contents to long-form posts. Add a TL;DR after the intro. Add an FAQ section that targets People Also Ask queries. None of this requires new content. It’s an afternoon of structural work on your highest-traffic posts that compounds for as long as those posts rank.
6. Internal linking is pipeline work, not housekeeping
What Loom does: Every Loom article links to product pages, feature pages, and other blog posts first. External links go to credible third-party sources that don’t compete for the same buyer. The pattern is deliberate—keep readers inside the ecosystem.
What you could do: Open your five most recent blog posts and count the links to your own product or service pages. If the average is under three, add more. Treat every blog post as a chance to move the reader one step closer to a conversion, not a destination in itself.
Your implementation checklist
If you’ve read this far, you’re probably thinking about your own content program. Here’s the order to work through it:
Pull your top ten organic pages in Semrush or Ahrefs. Map each one by intent (JTBD, category, comparison, branded). If the majority are informational with no path to a signup, you have a funnel problem that needs to be fixed.
Identify the content type you’re missing. Most SaaS blogs over-invest in TOFU and under-invest in alternatives, comparisons, and BOFU pages. Whichever stage is empty, that’s where the next ten articles go.
Audit your blog UX. Add a table of contents, TL;DR, and FAQ section to your ten highest-traffic posts this week.
Count the internal links in your five most recent posts. If the average is under three links to product or feature pages, fix that before you publish anything new.
List the JTBD queries your buyers run before they know your product exists. Build content around those tasks, not just around your category.
If you have a parent company, partner, or established publication you can publish under, use that authority. If not, plan a guest posting strategy for the next quarter.
Work with me
If reading through this review surfaced gaps, questions, or opportunities in your content strategy, I can help.
I work with B2B software companies to uncover SEO opportunities, improve content performance, and build content programs focused on driving pipeline.
