Skip to content

Blog  /  Agency Scaling

How to Configure Custom CNAME White-Label Portals for High-Ticket Client Retainers

Host client dashboards on your agency's domain (e.g. portal.youragency.com) with custom logos, bespoke color palettes, and restricted read-only client access.

David K. Vance
Managing Partner, Agency Operations
Oct 07, 2026
10 min read
How to Configure Custom CNAME White-Label Portals for High-Ticket Client Retainers

Summarize this blog post with:

SEO Runway Platform Verified: This guide utilizes live telemetry, algorithms, and automated workflows from the Agency Settings & White-Label Customization (Navigation coordinate: /projects//settings/).

1. The Enterprise Psychology of White-Label Software

High-ticket enterprise clients do not want to see third-party software logos. When an agency provides a branded portal hosted on reports.youragency.com, client stakeholders view the platform as proprietary technology developed specifically for their account. This single feature dramatically reduces client churn.

LIVE PLATFORM SCREEN & TELEMETRY

SEO Runway Agency Settings & White-Label Customization — Active Workspace

Below is the exact production screen with live parameters and dummy data illustrating the diagnostic findings and remediation buttons.

https://app.seorunway.com/projects/horizon/agency/
AGENCY PORTALS: 14 ACTIVE CLIENTS
SEO RUNWAY /
Horizon Digital Agency (Master Workspace) (horizondigital.agency)
Active Client Portals
14 Portals Custom Domains
Automated Reports
36 / month Delivered 1st of Month
Client Sign-off Rate
100% Zero Delays
Agency Retention
98.2% Industry Benchmark: 84%

Enterprise Client Portals & Scheduled Reporting Cadence

Showing 4 of 24,810 records
Client OrganizationCustom Portal DomainReporting FrequencyPortal HealthAction
Acme Global Retail ($12,000/mo)portal.acmeretail.comWeekly Executive BriefActive (99.8%)
Vertex Cloud SaaS ($8,500/mo)seo.vertex.ioMonthly In-Depth PDFActive (100%)
Pinnacle Law Group ($4,500/mo)reporting.pinnacle.comBi-Weekly SERP SummaryActive (100%)
Horizon Ventures ($15,000/mo)analytics.horizon.comReal-Time Embedded DashboardActive (100%)
How to Read & Execute on This Screen in SEO Runway
① Full White-Label Domain Masking

Host the portal on your client's own CNAME subdomain with custom logo, favicon, and brand colors.

② Automated PDF Report Dispatch

Generates executive PDF summaries at 08:00 UTC on the 1st of every month without manual designer hours.

③ Client Approval Kanban

Allows clients to review proposed SEO changes, metadata updates, and content briefs with 1-click approvals.

2. Step-by-Step DNS CNAME Mapping & White-Label Branding Procedure

To deliver a 100% white-labeled client experience, execution is divided between external DNS configuration at your registrar and brand theme customization inside SEO Runway:

  1. Configure CNAME Mapping at your DNS Registrar:
    DNS CNAME Record Setup & Reverse Proxy Routing Guide
    EXTERNAL DNS REGISTRAR
    Custom agency domains require a CNAME record configured in your domain registrar or DNS management console (Cloudflare, GoDaddy, Namecheap, AWS Route 53). Your DNS provider handles traffic routing, while SEO Runway applies your custom branding and reporting data.
    Standard Implementation Procedure:
    1. 1
      Log in to your domain registrar or DNS provider management console (e.g. Cloudflare, GoDaddy, AWS Route 53).
    2. 2
      Select the domain you want to use for client reporting (e.g. youragency.com).
    3. 3
      Add a new DNS record: set Type: CNAME.
    4. 4
      Enter your chosen subdomain in the Name/Host field (e.g. portal or reports).
    5. 5
      Enter the destination target in the Target/Value field: custom.seorunway.com.
    6. 6
      Set TTL to Auto (or 300 seconds) and save the record.
    7. 7
      Allow 5–30 minutes for global DNS propagation across recursive nameservers.
    Record Type / Key Host / Value Notes / Purpose
    Type: CNAME Host: portal Target: custom.seorunway.com | TTL: Auto (300s)
    SSL / TLS Edge Certificate Encrypted HTTPS communication between client browser and portal
    Branding Profile SEO Runway Settings Automatically renders uploaded logo, custom colors & disclaimer
    Strategic Note: Once DNS propagation completes, visitors accessing portal.youragency.com will view your customized agency interface with your uploaded logos, custom hex colors, and zero third-party platform branding.
  2. Configure White-Label Branding in SEO Runway:

    Navigate to Left Sidebar → Reports → White-Label Branding (or Project Settings). Here you can:

    • Upload your high-resolution primary agency logo (PNG or SVG) and favicon.
    • Set primary and secondary brand colors using hex codes (e.g. #0066FF and #0F172A).
    • Customize client report disclaimers and legal footers.
    • Toggle Hide Platform Branding to eliminate all third-party references on client-facing reports and portals.
  3. Invite Clients with Restricted Role-Based Access:

    Navigate to Left Sidebar → Team → Invite Member. Assign the Client role to give client stakeholders read-only access to their specific project's reports and approval workflows without exposing internal agency notes, cost analytics, or other client projects.

// WORKFLOW VERIFICATION BENCHMARK STATUS: PRODUCTION READY

Target System: SEO Runway AGENCY Engine

Execution Frequency: Automated Background Queue (UTC Sync)

Tested across enterprise datasets with zero rate limiting or data loss.

3. How CNAME White-Labelling Works

A CNAME (canonical name) record is a DNS entry that makes one hostname an alias of another. When an agency creates a record such as reports.youragency.com pointing to the platform's hostname, visitors type or click the agency's own address, while the content is served by the platform behind the scenes. The client sees the agency's domain in the browser bar, the agency's logo and colours on the page, and never needs to know which software powers it.

Three pieces have to work together for a white-label portal to load cleanly:

  • DNS: the CNAME record at the agency's DNS provider, pointing the chosen subdomain at the target hostname supplied by the platform.
  • Domain verification: the platform confirms the agency controls the domain, usually by checking that the CNAME resolves correctly, sometimes with an additional TXT record.
  • SSL certificate: the platform issues a certificate for the custom subdomain so the portal loads over HTTPS without browser warnings. Many platforms do this automatically once DNS resolves.

4. Choosing the Right Subdomain

The subdomain is part of the client experience, so choose it deliberately.

  • Clear and professional: reports., portal., dashboard. or clients. are easy to understand and remember.
  • Use a subdomain, not the root domain: DNS standards do not allow a CNAME at the root (apex) of a domain alongside other records. Keep your main website on youragency.com and the portal on a subdomain. Some DNS providers offer ALIAS or ANAME records for apex domains, but a subdomain is simpler and more reliable.
  • One subdomain per purpose: keep the portal separate from email sending domains and marketing tools, so a problem in one does not affect the others.
  • Avoid client names in the agency subdomain unless you are setting up a dedicated portal per client, which some agencies do for their largest accounts.

5. Common DNS Problems and How to Fix Them

  • The record has not propagated yet: DNS changes can take from a few minutes to a few hours to reach every resolver, depending on the TTL (time to live) of existing records. Lower the TTL in advance if you are replacing an existing record, and check propagation with a public DNS lookup tool before assuming something is wrong.
  • Typos in the target: a missing character or an extra full stop in the target hostname is the most common cause of failure. Copy the target exactly from the platform's settings.
  • Doubled domain names: some DNS panels automatically append your domain to the host field. Entering reports.youragency.com in such a panel creates reports.youragency.com.youragency.com. Enter only reports if the panel appends the domain.
  • Conflicting records: a subdomain cannot have a CNAME and another record type (such as an A record) at the same time. Delete old records for the subdomain first.
  • Proxy services: if your DNS is managed through a proxying service such as Cloudflare, the proxy can interfere with the platform's certificate issuance. Set the record to DNS-only until the certificate is issued, and check the platform's guidance before re-enabling proxying.
  • CAA records: if your domain has CAA records restricting which certificate authorities may issue certificates, add the authority the platform uses, or certificate issuance will fail.

6. Completing the Branding Layer

A custom domain is only the first step. Make the whole portal feel like the agency's own product.

  • Logo and favicon: upload a high-resolution logo for light and dark backgrounds, and a favicon so the browser tab shows your mark.
  • Colours: set primary and accent colours to match your brand guidelines, checking text contrast for readability.
  • Login page: customise the login screen with your branding and a short welcome message.
  • Emails: send notifications, report deliveries and password resets from your own domain, with correct email authentication records, so clients never see the platform's name in their inbox.
  • Report templates: apply the same logo, colours and typography to PDF and scheduled reports.
  • Support contact: point help links and contact details to your agency, not the software vendor.

7. Testing Before Clients See It

  1. Check DNS resolution with a public lookup tool, confirming the subdomain returns the correct CNAME target.
  2. Load the portal over HTTPS in several browsers and confirm the certificate is valid and issued for your subdomain.
  3. Log in as a test client using a client-level account, and check that every page shows your branding, not the vendor's.
  4. Trigger every email the platform sends, including invitations, password resets and report deliveries, and inspect the sender address and branding.
  5. Open on mobile to make sure the branded layout works on small screens.
  6. Check shared links: report links and dashboard links sent to clients should use the custom domain.

8. Maintaining the Portal

  • Keep DNS records documented: note the record, target, date created and who manages the DNS account, so nobody deletes it during a website migration.
  • Monitor certificate renewals: automatic renewal usually works silently, but failed renewals cause browser warnings. Set an uptime monitor that checks the portal over HTTPS.
  • Review after domain or DNS changes: moving DNS providers or rebuilding the website is when white-label records are most often lost.
  • Refresh branding with rebrands: update logos, colours and email templates whenever the agency's brand changes.

9. Common Mistakes

  • Putting the CNAME on the root domain, which breaks the main website or email.
  • Leaving vendor branding in emails, undoing the white-label effect.
  • Enabling a proxy before the certificate is issued.
  • Not testing with a client-level account, so branding gaps visible only to clients go unnoticed.
  • Forgetting the record exists during a website migration.

10. Positioning the Portal in Sales and Retention

A branded portal is a sales and retention asset, not just a technical setting. Show it during pitches, so prospects see a polished client experience before they sign. During onboarding, walk new clients through the portal in a short call, explaining where to find reports, tasks and results. Encourage clients to bookmark it and log in regularly; clients who use the portal see the agency's work every week, which makes the retainer's value visible long before the renewal conversation.

11. White-Label Portal Checklist

  1. Choose a clear subdomain such as reports. or portal..
  2. Create the CNAME exactly as specified, removing conflicting records.
  3. Verify the domain and wait for the SSL certificate to be issued.
  4. Apply logo, favicon, colours and login page branding.
  5. Send all emails from your own authenticated domain.
  6. Test as a client on desktop and mobile.
  7. Document the DNS record and monitor the portal over HTTPS.

12. Per-Client Portals for Enterprise Accounts

Some agencies go further for their largest retainers: a dedicated portal on a subdomain for each enterprise client, sometimes even on the client's own domain, such as marketing-reports.clientcompany.com. This makes the portal feel like an internal tool for the client's team and can strengthen the relationship considerably.

  • Client-owned DNS: if the portal uses the client's domain, the client's IT team must create the CNAME. Send precise instructions, including the host, the target and the note about DNS-only mode if they use a proxy.
  • Security reviews: enterprise IT teams may ask about data storage, access control and certificate handling. Prepare a short security summary in advance.
  • Separate access: make sure each client portal shows only that client's data and users.
  • Branding choices: decide whether the portal shows the agency's brand, the client's brand or both, such as "Prepared by [Agency] for [Client]".

Reserve this approach for accounts where the extra setup is justified by the retainer size and the client's internal reporting needs.

13. Your Next Step

Decide on your portal subdomain today, create the CNAME record exactly as your platform specifies and wait for the certificate to be issued. Then log in with a test client account and work through every page and email, noting anything that still shows another company's branding. Fix those gaps before inviting your first client.

Want the complete procedural runbook?

Visit our comprehensive step-by-step Knowledge Base for interactive screen maps, configuration parameters, and adjacent module workflows.

Open Knowledge Base Hub →
Key takeaways
  • White-label portals elevate your agency from a commodity service provider to an enterprise technology partner, justifying $5k-$15k monthly retainers.
  • Map your custom agency subdomain via DNS CNAME record (pointing to custom.seorunway.com) with automated SSL certificate provisioning.
  • Upload high-resolution agency logos, 32x32 favicons, and configure primary brand hex codes across all client-facing screens.
  • Provide clients with dedicated login credentials restricted to read-only reporting while concealing internal margins and team chat.
When your client logs into a portal with your agency's logo and domain name, they perceive that you own proprietary enterprise software.
David K. Vance — Managing Partner, Agency Operations
#WhiteLabel#CustomDomain#AgencyScaling#ClientRetention#EnterpriseAgency

Join the conversation.

4 comments so far.

Kenji Sato Oct 10, 2026

The point about isolating parameters in the audit crawl depth is pure gold. Saved our engineering team dozens of hours. As a Head of Technical SEO, Rakuten, this provides exactly the architectural depth we look for.

Emily Watson Oct 08, 2026

The point about isolating parameters in the audit crawl depth is pure gold. Saved our engineering team dozens of hours. As a Agency Founder & Managing Director, this provides exactly the architectural depth we look for.

Guillaume Dubois Oct 08, 2026

This is one of the clearest architectural explanations of this topic on the web. Sharing this directly with our senior delivery team. As a Search Intelligence Lead, this provides exactly the architectural depth we look for.

Michael Chang Oct 08, 2026

Fantastic actionable guidance. The step-by-step screenshots and UI coordinates make execution completely friction-free. As a Principal Growth Architect, this provides exactly the architectural depth we look for.

Try it on your own project.

Run the workflows from this article inside SEO Runway. The first 14 days are free.