Category: Guides

There’s a big difference between embedding a YouTube video and importing it as a custom post type in WordPress. One is a temporary window to YouTube; the other is a permanent, indexable page you own. If you’re building a video library, the post type matters more than you’d think — it shapes your SEO, your site structure, and what you can actually do with the content.

What a “custom post type” actually buys you

A dedicated “video” custom post type (CPT) gives each imported video its own single page, its own archive, its own permalink slug, and a place in your taxonomies. That means real URLs search engines can crawl, comments your audience can leave, and a structure you can browse and filter — none of which a bare embed provides. An embed is just a player dropped into someone else’s page; a CPT is a first-class piece of content on your domain. See how that compares to embed-only plugins.

Better SEO: every video becomes a page that can rank

This is the biggest reason to import rather than embed. When a video is a real post, it gets a unique, crawlable URL with its own title, description and body text — the on-page signals Google needs to understand and rank it. Each page can carry schema.org VideoObject microdata, works with Yoast Video SEO, and is included in your XML sitemap and RSS feed, so search engines discover every video automatically.

Because the content lives on your domain, the traffic, the rankings and the next click stay with you instead of being handed to YouTube. You can target long-tail search terms in each video’s title and description, earn video rich-result thumbnails in the SERPs, and build internal links between related videos — compounding authority across your whole library. Read more on video SEO done right.

A cleaner site structure

A custom post type keeps your video content organised as it scales from a handful of clips to hundreds or thousands. Videos get their own archive page, separate from your blog, plus categories, tags and custom taxonomies you can use to group and filter them — by topic, series, season or guest. Clean permalinks make every video shareable and memorable, and you can add the video archive straight into your navigation menu.

That structure powers browsable, paginated playlist layouts, “related videos” sections, and taxonomy-driven pages that are great for both visitors and search engines. Your blog stays a blog, your videos stay a tidy, self-contained library — and the two can still cross-link wherever it helps.

Ways to use a video CPT on your site

• Mirror your channel — give every YouTube upload a home on a site you own, so you rank and monetise on your own terms.
• Course & membership libraries — organise lessons into taxonomies and themed, paginated playlists members can browse.
• News & niche publishing — auto-curate topical video by keyword or channel and keep a section fresh on autopilot.
• Product, tutorial & support videos — attach how-tos to a knowledge base or product pages with their own searchable URLs.
• Podcast or episode archives — turn each episode into an indexable page with show notes and schema.

Explore more scenarios on the use cases page.

Posts or a video CPT — your choice

Video Hub can import videos as regular posts (so they flow into your blog, categories and homepage) or as a separate “video” custom post type with its own archive and single pages. You pick the model that fits your site — and you can combine both. See the publishing options.

To import YouTube videos into WordPress with OAuth, you need two credentials from Google: a Client ID and a Client Secret. They come from a free Google Cloud project and tell YouTube that your site is allowed to read video data. Here’s how to get them.

What you’re creating

• A Google Cloud project (free)
• The YouTube Data API v3, enabled on that project
• An OAuth Client ID and Client Secret for a web application

Step 1 — Create a project & enable the API

In the Google Cloud Console, create a new project, then open APIs & Services → Library, search for YouTube Data API v3 and enable it. This is the API your Client ID will be authorized to call.

Step 2 — Configure the OAuth consent screen

Under APIs & Services → OAuth consent screen, set the app name, your support email and the authorized domain. You can keep it in testing mode and add your own Google account as a test user.

Step 3 — Create the Client ID & Secret

Go to APIs & Services → Credentials → Create credentials → OAuth client ID, choose Web application, and add the redirect URI that Video Hub shows you. Google then displays your Client ID and Client Secret — copy both.

Step 4 — Paste them into WordPress

In Video Hub, paste the Client ID and Client Secret into the authentication settings and complete the OAuth connection. You can now import any public video plus your own playlists and unlisted videos. More on OAuth vs. a plain API key.

A note on quotas

The YouTube Data API gives each project a daily quota. Video Hub shows a daily quota estimate so heavy imports don’t hit the ceiling. See the FAQ for more on keys and quotas.

Exact screens change over time — for the current click-by-click walkthrough, see the documentation.

Your YouTube Channel ID is the long string that starts with UC… — and it’s not the same as your @handle or channel name. You’ll need it whenever a tool asks you to identify a channel exactly, including when you import a channel’s uploads into WordPress. Here are three ways to find it.

1. From YouTube advanced settings

Sign in to YouTube, open Settings → Advanced settings (or the channel’s advanced settings in YouTube Studio). Your Channel ID is listed there in full — the most reliable method.

2. From your channel URL

If your channel URL looks like youtube.com/channel/UCxxxxxxxx, the part after /channel/ is your Channel ID. Note that custom URLs (/@handle or /c/Name) hide it — use method 1 or 3 in that case.

3. From the page source

Open the channel page, view the page source, and search for externalId or channel_id — the UC… value next to it is the Channel ID.

Why you need it: importing a channel

Once you have the Channel ID, you can point a YouTube video importer at that channel and pull its uploads into WordPress as real posts — automatically, on a schedule. See how to import a YouTube channel into WordPress.

Channel ID vs. @handle vs. custom URL

It’s easy to mix these up. Your @handle (like @MyChannel) and a custom URL (/c/MyChannel) are friendly, human-readable names you can change. The Channel ID (UC…) is the permanent, unique identifier YouTube assigns — it never changes and is what APIs and import tools actually use. When something “can’t find” your channel from the handle, the Channel ID is almost always what it really wants.

Finding the ID for a channel you don’t own

You can only open advanced settings for your own channel. For any other channel, use method 2 or 3 above — read it from a /channel/UC… URL, or view the page source and search for externalId. Opening one of the channel’s videos and checking its links can also surface the UC… value.

Turn that ID into an automated video site

The Channel ID is the key that unlocks a self-updating library. Feed it to Video Hub, set how many uploads to pull and how often, and each new video becomes a real, indexable WordPress post — building a channel mirror you own, rank for and monetise on your own terms. Explore the possibilities in use cases.

If you want to import a YouTube channel into WordPress — and not babysit it forever — the trick is automation. Pasting embed links one by one doesn’t scale, and it leaves every view and every bit of SEO value on YouTube. A proper importer pulls the channel in once and then keeps it in sync on its own.

Embeds vs. importing a channel

An embed is a window to YouTube; an import is content on your domain. When you import a channel with Video Hub, each upload becomes a real WordPress post — indexable, categorized and styled by your theme — instead of a throwaway iframe.

How automatic channel import works

You point the importer at a channel’s uploads feed (you’ll need the channel’s ID), choose how many videos to pull and how often, and let scheduled, cron-based imports do the rest. New uploads appear on your site automatically, with titles, descriptions, thumbnails, categories and publish dates mapped for you. Because imports run off-request, syncing never slows a visitor’s page load. See all the import options.

Bulk-import the back catalog, too

Starting from an established channel? Bulk-import the existing videos — preview the results and select exactly what you want — then let automation handle everything new from there.

Every detail mapped, not just the video

A channel import is only useful if the data comes with it. Video Hub maps each upload’s title, description, publish date and thumbnail (set as the featured image) into the WordPress post, and can assign categories and tags so videos land in the right part of your site. Choose to import as regular posts — flowing into your blog, categories and homepage — or as a dedicated video custom post type with its own archive and single pages.

Why an owned channel mirror is better for SEO

When uploads become real posts, each one is a crawlable URL carrying schema.org video markup and feeding your XML sitemap and RSS — so search engines can index and rank every video on your domain. Instead of donating views and SEO value to YouTube, you keep visitors, rankings and ad revenue on a site you control, with internal links tying the library together. See video SEO in WordPress.

Set it up to stay light and tidy

Because imports run off-request via cron, even a large channel won’t slow your pages. Images can be fetched on demand, the importer works with the official AMP plugin, and a maintenance routine can retire videos that have been deleted or made non-embeddable — so your library stays current without manual cleanup.

For the exact setup steps, see the documentation.