Google Launches Video Series Tackling Unusual Technical SEO Questions

Google has introduced "The Non-Canonical Cabinet," a sitcom-style Search Central YouTube series addressing edge-case technical SEO questions — starting with what domain names and URL paths can actually contain.

The series arrives at a time when SEO professionals frequently encounter client questions that fall outside standard documentation. By putting Google's own engineers on camera to answer these fringe queries, the search giant is offering practitioners something arguably more valuable than a help article: on-record answers from the people who build the systems. For anyone working through the most persistent and complex SEO challenges facing practitioners today, having an authoritative, quotable source directly from Google carries significant practical value.

What "The Non-Canonical Cabinet" Is and Who Hosts It

Google announced the series with a teaser video published on October 6, 2026, describing the show as a sitcom-style comedy built around specific questions submitted by website owners and the broader SEO industry. The first full episode followed on October 14, 2026.

Hosting duties fall to Google's Gary Illyes and Cherry Prommawin. The episode description frames the show's purpose plainly: "These are questions that don't belong on a standard FAQ page but are still useful for Search and generative AI features."

Illyes is no stranger to this format. In 2024 he hosted "How Search Works," a five-part Search Central series walking viewers through crawling, indexing, and serving. "The Non-Canonical Cabinet" takes a different approach — rather than starting with fundamentals, it begins with questions the audience is already asking. Google has invited viewers to submit their own edge-case questions in the comments section of each video.

Why This Format Matters for SEO Professionals

The shift from written documentation to on-camera responses from Google engineers is worth noting. A help article can be updated or quietly revised; a recorded statement from an engineer creates a more durable, citable reference point. When clients push back on technical recommendations, practitioners now have something more concrete to point to than a blog post or forum discussion. The format also signals that Google is aware these fringe questions exist in volume — enough to justify a dedicated series.

Domains and URL Paths Follow Different Technical Rules

The first episode draws a clear line between what is permitted in a domain name versus a URL path — a distinction that trips up many practitioners. Understanding these boundaries sits at the foundation of sound technical SEO practice and site architecture decision-making.

Domain Name Rules and Internationalized Characters

Domain names are governed by technical standards set by ICANN and the Internet Engineering Task Force (IETF). Under RFC 1035 and RFC 1123, domain names may contain letters, numbers, and hyphens. Prommawin confirmed that Google follows these same standards. Languages using non-Roman scripts — such as Chinese or Arabic — are supported through Internationalized Domain Names (IDNs), which browsers translate into Punycode strings beginning with "xn--" while displaying the native script to users.

Illyes flagged one complication with IDNs: certain scripts contain characters that closely resemble letters in other languages. A Cyrillic character, for example, can look nearly identical to an English "p," creating potential confusion for both users and browsers. This is not a minor cosmetic concern — it has implications for brand safety and phishing vulnerability, and site owners managing multilingual or international domains should be aware of it when evaluating their URL structure.

Emoji in Domain Names vs. URL Paths

On the question of emoji in domain names, the answer is straightforward. A 2017 ICANN Board Resolution explicitly states that emoji are "disallowed by the current technical standards for Internationalized Domain Names." Illyes confirmed this position. The resolution does note that emoji characters may still be registered at the second level within certain country-code top-level domains (ccTLDs).

URL paths operate under fewer restrictions. Illyes said Googlebot will crawl a path containing an emoji and that "our system will actually process it." Browsers percent-encode those characters — the episode's example chicken emoji becomes %F0%9F%90%94 in the path. He cautioned that not every browser or social media application will display the emoji correctly, with some rendering "a string of gibberish" instead.

Google's existing URL structure documentation already recommends percent encoding for non-ASCII characters and uses emoji in one of its own examples — a useful reference point when advising clients on path construction.

Keywords in URLs Carry Almost No Ranking Weight

Perhaps the most practically useful segment of the episode addresses whether loading a URL with keywords provides any meaningful ranking advantage.

Illyes called keywords in a URL "an incredibly small signal." He elaborated: "It only matters when we have absolutely nothing else to go on" — citing a brand-new site with no content as an example. Once Google has content to evaluate, keywords in the domain or URL path "become basically irrelevant," he said.

This is consistent with prior statements from Google. John Mueller described URL keywords as a "very small ranking factor" in 2016 and a "very lightweight factor" in 2021 — a position that has remained stable across the years. For practitioners who regularly field client requests around URL naming conventions, this trajectory of consistent statements strengthens the case considerably.

Word Separators and the Hyphen vs. Underscore Question

On word separators, Illyes confirmed that Google treats words joined by underscores in a URL path as a single long word. He noted this is not always catastrophic since Google may still parse the individual words, but the recommendation remains to use hyphens. Google's documentation attributes this guidance to "historical reasons," noting that underscores traditionally signal concepts meant to stay joined — such as function names in programming code.

The episode's closing recap delivers a direct message to anyone tempted to game rankings through keyword-stuffed URLs: stop. The marginal value Illyes described applies only in the narrowest of circumstances.

What Comes Next in the Series

Looking ahead, the next episode of "The Non-Canonical Cabinet" is confirmed to cover robots.txt. No formal release schedule has been announced — the teaser and first episode were published eight days apart. Given that robots.txt misconfigurations remain one of the more consequential and frequently misunderstood areas of site management, that episode is likely to generate significant interest. Practitioners working across Google's broader suite of tools for search visibility and site management will find it worth monitoring.

---

How SEO Professionals Can Use This Information

• Use Illyes' on-record statement as client-facing evidence when pushing back against requests for keyword-heavy URL structures — his comments carry more weight in client conversations than a blog post opinion.
• Audit your URL paths for non-ASCII characters and ensure percent encoding is implemented correctly to avoid rendering issues across browsers and social platforms.
• Submit edge-case questions in the video comments to potentially have your specific technical scenario addressed in a future episode with an official Google response on record.