Should you verify `sc-domain:` or separate URL-prefix properties for subdomains?
Google Search Console offers two property types, and choosing the wrong one either blinds you to subdomain traffic or forces you to manage dozens of verification tokens:
| Feature | Domain Property (sc-domain:example.com) |
URL-Prefix Property (https://docs.example.com/) |
|---|---|---|
| Scope of Coverage | All subdomains & protocols: Captures `http://`, `https://`, `www.`, `docs.`, `blog.`, and any newly launched child host automatically. | Exact prefix only: Only captures URLs starting with that exact protocol and hostname string. |
| Verification Method | Requires DNS `TXT` or `CNAME` record at your domain registrar/DNS host. | Supports DNS, HTML file upload, <meta> tag, Google Analytics, or GTM. |
| Main Drawback in GSC Web UI | Aggregates all subdomains together by default; a spike on `docs.` hides a drop on `www.`. | Requires manually adding and verifying a new property for every single subdomain. |
| How Searchbop Handles It | Uses a single `sc-domain:` connection to auto-discover every active subdomain and split their reports by hostname automatically. | Connects directly if you only have access to a specific subdomain or subfolder property. |
Copy-paste RegEx patterns to segment subdomains in Google Search Console
When working directly inside the Google Search Console web UI on a `sc-domain:` property, you can isolate specific subdomains by clicking **+ New → Page → Custom (regex)**. Always remember to escape literal dots (`\.`):
# 1. Match ONLY the apex + www marketing site (exclude all other subdomains)
^https?://(www\.)?example\.com/
# 2. Match ONLY docs and blog subdomains together
^https?://(docs|blog)\.example\.com/
# 3. Match ANY child subdomain except root and www
^https?://(?!www\.)[a-z0-9-]+\.example\.com/
# 4. Exclude app/auth/status subdomains (use with "Doesn't match regex")
^https?://(app|auth|status)\.example\.com/4 technical SEO bugs that only appear when you audit subdomains separately
According to Google’s crawling standards, each hostname (`example.com`, `docs.example.com`, `shop.example.com`) is governed by its own root files and server headers:
- Independent `/robots.txt` per subdomain: A rule in `https://example.com/robots.txt` has **zero effect** on `https://docs.example.com/`. Each subdomain serves its own `/robots.txt` and must be checked independently across all 14 search and AI crawlers.
- Cross-subdomain canonical mistakes: If a shared layout template in a monorepo hardcodes `metadataBase` to the root domain, pages on `docs.example.com` may accidentally output
<link rel="canonical" href="https://example.com/..." />, de-indexing the entire documentation subdomain. - Leaked staging or preview subdomains: Automatic subdomain discovery in Searchbop scans your `sc-domain:` page table and regularly catches forgotten `staging.`, `dev.`, or `old.` subdomains that accidentally got indexed without `X-Robots-Tag: noindex`.
- Separate Core Web Vitals profiles: Your static Astro marketing site on `example.com` may score 99 on PageSpeed Insights while your heavy client-rendered docs or store subdomain fails LCP and INP.
Running SEO audits across 3, 15, or 1,000 websites without per-site SaaS upgrades
Hosted cloud SEO platforms typically restrict their $129/month base plan to 1 to 5 projects, charging extra every month as you add side projects, regional domains, or client properties. Because Searchbop runs locally on your Mac and uses your own Google Search Console Service Account and AI keys, you only pick a one-time workspace capacity once: **Solo ($39 once for 3 sites)**, **Pro ($69 once for 15 sites)**, or **Agency ($299 once for 1,000 sites)**.
Official Search Console API documentation
Reference documentation: See Google Search Console API — searchanalytics.query and Website Property Types in Search Console. Searchbop filters domain-level Search Analytics rows using dimension filter groups on the `page` dimension so each child subdomain receives accurate click, impression, CTR, and position deltas.
Research context & search queries covered on this page Subdomains · P1
Cluster & intent: subdomains (Commercial · P1) · Target queries: SEO audit for multiple websites, subdomain SEO monitoring, multiple website SEO dashboard, Search Console subdomain tracking, monorepo SEO tool.
Benchmark prompt addressed: P08 — How can I monitor several subdomains separately in one SEO workspace?