Whereby SEO Audit

Whereby is a browser-based video meeting platform that lets businesses embed meeting rooms directly into their own website using a native web component — making it the video tool most likely to introduce Core Web Vitals considerations via third-party embed JavaScript on your service and booking pages. When a Whereby room is embedded on a page, the widget\'s JavaScript, iframes, and media assets affect LCP, INP, and CLS in ways that standard video call links do not. DeepSEOAnalysis measures CrUX p75 Core Web Vitals from real Chrome users on your pages, audits structured data on service and booking pages that reference virtual meeting delivery, validates your Organization or ProfessionalService schema for entity consolidation, and checks canonical configuration for sites using Whereby\'s custom subdomain feature.

What DeepSEOAnalysis checks for Whereby

Virtual Meeting Room Embed SEO

  • Whereby <whereby-embed> or <iframe> loaded below the fold with lazy loading
  • Embed facade (static CTA) replacing live widget until user interaction
  • Descriptive anchor text on links to meet.yourbrand.com or app.whereby.com
  • Booking and contact pages include indexable text describing virtual meeting workflow

Core Web Vitals for Embedded Video Call Widgets

  • LCP ≤2.5s on pages embedding a Whereby room — widget must not be LCP element
  • INP ≤200ms — Whereby JS deferred until user interaction to reduce event listener overhead
  • CLS ≤0.1 — explicit width and height attributes on Whereby iframe to prevent layout shift
  • CrUX p75 field data from real Chrome users measuring actual embed impact

Custom Subdomain and Canonical

  • Custom Whereby subdomain (meet.yourbrand.com) included in Organization schema sameAs
  • Canonical tags on main site pages link to canonical version, not Whereby room URLs
  • No accidental indexation of Whereby room URLs via internal links in navigation
  • robots.txt on main domain does not inadvertently block booking flow pages

Professional Brand Entity SEO

  • Organization or Person schema on homepage with sameAs for all brand profiles
  • Service pages describe virtual consultation delivery method with Whereby named explicitly
  • Contact page structured data includes virtual meeting availability as service channel
  • Google Business Profile attributes include "Online appointments" or "Virtual meetings"

Structured Data for Service Businesses

  • Service or ProfessionalService schema with virtual serviceDeliveryMethod noted
  • FAQPage schema on booking/contact page answering "how do virtual sessions work?"
  • Event schema with OnlineEventAttendanceMode for webinars or group sessions via Whereby
  • JSON-LD delivery in <head> — not inline or Microdata — for full Google eligibility

Website Contact and Booking Page Optimisation

  • Booking page indexed and in XML sitemap — Googlebot must be able to crawl it
  • Contact page includes written description of virtual meeting process for indexable content
  • Page title and meta description for booking page include service type and virtual keyword
  • Internal links from service pages to booking/contact page with descriptive anchor text

Frequently asked questions

Are Whereby meeting room pages indexed by Google?
Whereby meeting room pages hosted at app.whereby.com or on a custom subdomain (e.g. meet.yourbrand.com) are publicly accessible URLs, but they are not meaningful pages for Google to index — they render a video call interface that requires authentication or a room link, not content. Google may crawl them but they carry no SEO value for your brand. The SEO-relevant surface is your own website: the pages that embed a Whereby room, the booking pages that link to Whereby meetings, and the service pages that describe the virtual consultation or meeting service. These are the pages to optimise for structured data, Core Web Vitals, and entity signals — not the Whereby room URLs themselves.
How does using Whereby for client calls affect a brand\'s digital presence?
Whereby does not directly affect your website\'s organic search rankings — it is a video calling tool, not a content or link signal. However, it affects your digital presence in three indirect ways: (1) If you embed Whereby rooms on your website\'s contact or booking pages, the embedded widget adds third-party JavaScript that can increase page weight and affect INP and LCP — measurable Core Web Vitals regressions that Google uses as Page Experience signals. (2) Using Whereby for client consultations is a service delivery method that should be described in your service pages and FAQ content ("virtual consultations available via Whereby") — adding indexable content about your service delivery model. (3) If you use a custom Whereby subdomain (meet.yourbrand.com), it becomes part of your brand\'s domain footprint and should be included in your entity consolidation strategy via sameAs schema on your main site.
What structured data should businesses using Whereby for virtual meetings add?
Businesses using Whereby for virtual client meetings should add structured data to communicate the virtual service delivery context to Google. Recommended schema types: (1) Service or ProfessionalService schema with a ServiceDeliveryMethod or serviceType property noting virtual/online delivery — this signals to Google that you offer remote consultations, which can appear in local service-type rich results. (2) FAQPage schema on your booking or contact page answering common questions about your virtual meeting setup ("How do virtual sessions work?", "What platform do you use for calls?") — FAQPage schema is eligible for FAQ rich results in Google Search. (3) Event schema if you run webinars or group sessions via Whereby, with a eventAttendanceMode of OnlineEventAttendanceMode and a url pointing to the Whereby room or booking page. Add all schema as JSON-LD in the page <head>, not inline or via Microdata.
How does embedding Whereby rooms on a website affect Core Web Vitals?
Embedding a Whereby room on a page using the <whereby-embed> web component or an <iframe> introduces third-party resources — JavaScript, CSS, and potentially video/media assets loaded from whereby.com or Whereby\'s CDN — that can affect all three Core Web Vitals. LCP (Largest Contentful Paint): if the Whereby embed is above the fold and its iframe or hero image is the largest element, it can delay LCP. Mitigation: load the embed below the fold with lazy loading, or use a facade (static image or "click to join" button) that replaces the live embed until the user interacts. INP (Interaction to Next Paint): Whereby\'s JavaScript, once loaded, adds event listener overhead that can increase INP — particularly on mobile. Mitigation: defer Whereby JS loading until user interaction. CLS (Cumulative Layout Shift): an unsized Whereby iframe that loads asynchronously can shift page layout. Mitigation: always set explicit width and height attributes on the iframe. DeepSEOAnalysis measures CrUX p75 CWV from real Chrome users, giving you the field data impact of any embed on your page experience score.
Does Whereby\'s custom subdomain affect SEO?
Whereby allows businesses on paid plans to use a custom subdomain (e.g. meet.yourbrand.com) instead of the default app.whereby.com URL. The custom subdomain does not directly pass link equity to your main domain — subdomains are treated by Google as related but distinct from the root domain, and a Whereby meeting room at meet.yourbrand.com does not boost rankings for yourbrand.com. However, the custom subdomain affects your brand entity signals in two ways: (1) It adds a subdomain to your brand\'s domain footprint, which should be included in your Organization schema\'s sameAs array or url properties to associate it with your entity. (2) The canonical handling of the custom subdomain matters — Whereby\'s platform sets its own canonical tags on the room pages, which you do not control. Ensure that any pages on your main site linking to meet.yourbrand.com use descriptive anchor text and that the link is in context (booking flow, contact page) rather than in navigation, to avoid diluting crawl budget on non-content URLs.
How does Whereby compare to Zoom and Teams for embedded meeting SEO?
From an SEO impact perspective, the key differences between Whereby, Zoom, and Microsoft Teams for embedded meeting use cases are: (1) Whereby is the only major video platform that offers a native embeddable web component (<whereby-embed>) designed for embedding directly into your own website pages — Zoom and Teams do not offer a first-party embed that runs in your site context. This makes Whereby the most relevant tool for the "embed a meeting room on your website" use case, but also the one most likely to introduce Core Web Vitals considerations via third-party embed JavaScript. (2) Zoom and Teams generate their own landing pages at zoom.us and teams.microsoft.com respectively — meetings take users off your site entirely, so there is no embed CWV impact on your pages. (3) All three platforms create a similar entity signal opportunity: mention the platform in your service pages and FAQ schema ("virtual sessions via Whereby/Zoom/Teams"), add it to your FAQ structured data, and ensure your booking page describes the virtual meeting workflow. DeepSEOAnalysis audits your site\'s pages — the structured data, CWV, and entity signals on pages that reference or embed your meeting platform — rather than the platform itself.