Domains

Add and configure the websites you manage through SerpWise, including origin server settings and domain aliases.

A domain in SerpWise represents a website you want to proxy and apply SEO modifications to. Each domain has its own origin server configuration, rule set, redirect list, and security settings.

Adding a Domain

Navigate to Domains in your organization dashboard and click Add Domain.

You'll need to provide:

  • Domain hostname — the public-facing hostname (e.g. www.example.com)
  • Origin server configuration — where the gateway should fetch content from

Plan limits

The number of domains you can add depends on your plan. Check your current usage in the Billing section of your dashboard.

Origin Server Configuration

The origin server is the backend your website actually runs on — the server SerpWise fetches content from before modifying it.

SettingDescriptionDefault
HostOrigin server hostname or IP address
Protocolhttps or httphttps
PortTCP port to connect on443 (https) / 80 (http)
SSL VerificationValidate the origin's TLS certificateEnabled
TimeoutMaximum seconds to wait for origin response30

SSL Verification

Leave SSL verification enabled for production origins. Disable it only for staging environments using self-signed certificates — disabling in production exposes you to man-in-the-middle attacks.

Timeout

The timeout controls how long the gateway waits for your origin to respond before returning a 504 error to the visitor. Set this higher than your origin's typical response time, but not so high that slow origin responses cause visitors to wait excessively.

Testing the Connection

After saving origin settings, use the Test Connection button on the domain overview to verify the gateway can reach your origin. This makes an actual HTTP request from the gateway to your origin and reports:

  • Whether the connection succeeded
  • The HTTP status code returned
  • Response time

Proxy Subdomain

Every domain gets a unique proxy subdomain of the form {id}.edge.serpwise.ai. This is the address you point your CDN or DNS CNAME to.

You can test your domain through the proxy subdomain at any time — even before pointing your CDN — to verify the gateway is working correctly.

Domain Status Lifecycle

Domains move through several statuses during setup and operation:

StatusMeaning
pendingDomain created, ownership not yet verified
verifiedOwnership confirmed, CDN routing not yet confirmed
activeTraffic is routing through SerpWise successfully
pausedDomain manually paused; gateway returns 503
errorAn issue requires attention (e.g. origin unreachable)

Domain Aliases

Domain aliases let you serve multiple hostnames from a single domain configuration. This is useful when:

  • Your site is accessible on both www.example.com and example.com
  • You have regional subdomains (en.example.com, de.example.com) that share the same rules

Each alias can optionally override the origin configuration — for example, pointing to a different origin host for regional variants while sharing the same rule set.

Aliases share the parent domain's rules and redirect list. If you need completely independent rules, create a separate domain instead.

DNS Routing Check

The domain overview includes a DNS Check that queries the live DNS records for your domain and shows:

  • Whether it currently resolves to the SerpWise gateway
  • The detected IP addresses or CNAME targets
  • Whether any CDN (Cloudflare, Fastly, etc.) is detected in front of the gateway

Use this to confirm your CDN routing is correct after making DNS changes.

Editing and Deleting Domains

Origin settings can be updated at any time from the domain's settings tab. Changes take effect on the next request after the gateway cache is invalidated (automatically triggered on save).

Deleting a domain removes all associated rules, redirects, and analytics data. This action is irreversible.

Before deleting a domain, update your CDN/DNS records to stop routing traffic through SerpWise. Requests arriving for a deleted domain will receive errors.

On this page