Company Domain to YouTube Channel Resolver

Pricing

Rating

Developer

Actor stats

Categories

Share

Resolve company domains and websites to official YouTube channel URLs, handles, and evidence fields for B2B enrichment workflows.

What does Company Domain to YouTube Channel Resolver do?

Company Domain to YouTube Channel Resolver takes a list of company domains, website URLs, or company names and returns one enrichment row per input.

It checks public company websites for YouTube links in footers, headers, HTML, meta content, and JSON-like page data.

It then ranks the best channel candidate and returns the evidence source, matched text, confidence level, alternatives, and pages checked.

Who is it for?

• 🧩 RevOps teams enriching account lists before outreach.
• 🧲 Clay users who need a stable company-to-YouTube column.
• 🤝 Partnership teams matching brands with video channels.
• 📣 Marketing teams auditing owned social profiles.
• 🧪 Data teams validating social enrichment vendors.

Why use this actor?

Many enrichment tools miss public YouTube channels because the link is hidden in a footer, About page, Contact page, or JSON metadata.

This actor is intentionally narrow: it resolves official YouTube channel URLs from company websites and keeps the evidence visible.

Typical use cases

• Add official YouTube channel URLs to a lead list.
• Find brands with video presence before partnership outreach.
• Audit whether a company website exposes the correct YouTube profile.
• Build a repeatable Clay enrichment step without writing custom crawlers.
• Compare official-site matches against search-only guesses.

Data returned

How much does it cost to resolve company domains to YouTube channels?

This actor uses pay-per-event pricing.

• A small start event covers run initialization.
• A per-item event is charged for each output row.
• Each input produces one output row, including not_found rows, so your export can be joined back to your source list.

Final production prices are shown on the Apify Store pricing tab and in the actor input form.

Input options

domainsOrCompanyNames

Add one company per line.

Best results come from domains or website URLs, for example:

["apify.com","stripe.com","https://www.microsoft.com/en-us/"]

Name-only inputs are supported primarily when search fallback is enabled.

maxPagesPerDomain

Controls how many public pages are checked per domain.

The actor always starts with the homepage and then tries likely company pages such as About, Contact, Company, and Social pages.

searchFallback

When enabled, the actor tries a public search fallback after official-site crawling finds no YouTube link.

Search fallback results are marked low confidence because they do not come directly from the company's website.

language and country

Optional hints for search fallback.

requestTimeoutSecs

HTTP timeout per page.

Keep the default unless you are checking slow enterprise websites.

Output example

{
"input":"apify.com",
"normalizedDomain":"apify.com",
"status":"resolved",
"resolvedYoutubeUrl":"https://www.youtube.com/apify",
"confidence":"high",
"evidenceSource":"homepage",
"evidenceUrl":"https://apify.com/",
"pagesChecked":["https://apify.com/"],
"crawledAt":"2026-06-24T06:55:29.423Z"
}

How to run

1. Open the actor on Apify.
2. Paste domains, website URLs, or company names.
3. Keep maxPagesPerDomain at 3 for a quick first run.
4. Enable search fallback only when you want lower-confidence guesses.
5. Start the run.
6. Export the dataset to CSV, JSON, Excel, or connect it to your workflow.

Confidence scoring

High confidence means the link was found on the homepage of the official domain.

Medium confidence means the link was found on an official subpage such as About, Contact, Company, or Social.

Low confidence means the link came from search fallback.

None means no usable channel candidate was found.

What counts as a YouTube channel?

The actor prioritizes profile-like YouTube URLs:

• youtube.com/@handle
• youtube.com/channel/...
• youtube.com/c/...
• youtube.com/user/...
• brand YouTube profile URLs linked from a company site

It filters common low-value video, embed, shorts, playlist, and iframe API URLs so a random embedded video is less likely to become the main result.

Tips for best results

• Use domains instead of company names whenever possible.
• Keep search fallback off for compliance-sensitive enrichment.
• Use confidence = high or medium when you only want official-site evidence.
• Review alternativeCandidates when a brand has regional or product-specific channels.
• Increase maxPagesPerDomain for large enterprise sites.

Clay workflow

1. Add a column with company domains.
2. Run this actor with the domain column as domainsOrCompanyNames.
3. Import the dataset back into Clay.
4. Join on input or normalizedDomain.
5. Filter out rows where status is not resolved.
6. Use resolvedYoutubeUrl in downstream creator, ad, or partnership workflows.

Lead enrichment workflow

Use this actor before outreach to identify brands that actively publish video content.

A matched YouTube channel can help segment accounts by content maturity, creator strategy, brand education, or audience engagement.

Partnership research workflow

Partnership teams can use the output to find official brand channels and then review content fit manually.

The evidence fields reduce false positives because analysts can see whether the match came from the company website or a fallback search page.

Data quality workflow

Run this actor against a vendor-enriched list to audit missing or incorrect YouTube URLs.

Compare your existing channel URL against resolvedYoutubeUrl and inspect confidence and evidenceUrl for disagreements.

Integrations

• Apify datasets for CSV, JSON, XML, RSS, and Excel exports.
• Clay for enrichment tables.
• Google Sheets through Apify integrations or Make/Zapier.
• CRMs and data warehouses through the Apify API.
• Internal lead-scoring pipelines through scheduled actor runs.

API usage with Node.js

import{ ApifyClient }from'apify-client';
const client =newApifyClient({token: process.env.APIFY_TOKEN});
const run =await client.actor('automation-lab/company-domain-to-youtube-channel-resolver').call({
domainsOrCompanyNames:['apify.com','stripe.com'],
maxPagesPerDomain:3,
searchFallback:false,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/company-domain-to-youtube-channel-resolver').call(run_input={
'domainsOrCompanyNames':['apify.com','stripe.com'],
'maxPagesPerDomain':3,
'searchFallback':False,
})
print(run['defaultDatasetId'])

API usage with cURL

curl-X POST "https://api.apify.com/v2/acts/automation-lab~company-domain-to-youtube-channel-resolver/runs?token=$APIFY_TOKEN"\
-H'Content-Type: application/json'\
-d'{"domainsOrCompanyNames":["apify.com","stripe.com"],"maxPagesPerDomain":3}'

MCP: use from Claude Code or Claude Desktop

You can expose this actor to AI agents through Apify MCP.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/company-domain-to-youtube-channel-resolver

Claude Code setup:

$claude mcp add apify-company-youtube-resolver "https://mcp.apify.com/?tools=automation-lab/company-domain-to-youtube-channel-resolver"

Claude Desktop JSON configuration:

{
"mcpServers":{
"apify-company-youtube-resolver":{
"url":"https://mcp.apify.com/?tools=automation-lab/company-domain-to-youtube-channel-resolver"
}
}
}

Example prompts:

• "Resolve these 50 company domains to official YouTube channels and return only high-confidence matches."
• "Check whether the attached account list has official YouTube profiles and include evidence URLs."
• "Find alternative YouTube candidates for brands where the main result is missing."

Scheduling and monitoring

Schedule the actor weekly or monthly for account lists that change over time.

Because the output keeps one row per input, you can diff results between runs and detect newly added social links.

Limitations

• Some websites hide social links behind JavaScript that is not present in the initial HTML.
• Some companies do not link YouTube from their public website.
• Search fallback can return false positives and is therefore marked low confidence.
• The actor does not access private YouTube APIs, login-only data, or paid enrichment databases.

Legality and compliance

This actor reads public company websites and public search-result pages when fallback is enabled.

You should use the output responsibly, respect applicable laws, and verify low-confidence matches before high-impact decisions.

FAQ and troubleshooting

Why did a company return not_found?

The official site may not expose a YouTube link in public HTML, or the channel may be linked only through JavaScript, a cookie banner, or a regional site.

Try increasing maxPagesPerDomain or enabling search fallback.

Why is the result low confidence?

Low confidence means the candidate came from search fallback instead of the official company website.

Use official-site matches when precision matters.

Why do I see alternatives?

Some brands link several YouTube URLs for global, product, support, or regional channels.

The actor picks the top-ranked candidate and keeps the rest in alternativeCandidates.

Related scrapers and actors

• https://apify.com/automation-lab/website-contact-finder
• https://apify.com/automation-lab/google-maps-lead-finder
• https://apify.com/automation-lab/youtube-channel-email-extractor

Changelog

0.1

Initial version for domain-to-YouTube channel resolution with official-site evidence, confidence scoring, alternatives, and optional search fallback.

Support

Open an Apify issue on the actor page if a public website links a YouTube channel that the actor misses.

Include the input domain, expected channel URL, and whether search fallback was enabled.

Summary

Company Domain to YouTube Channel Resolver is a focused enrichment actor for turning company domains into official YouTube profile URLs.

It is designed for repeatable B2B workflows where evidence, confidence, and stable one-row-per-input output matter.