If you are an agency, this guide will help you:

  • Onboard client sites to Pressidium EDGE in a repeatable way
  • Prepare DNS, SSL, cache, and security checks before launch
  • Review site behavior after DNS changes
  • Organize client site information internally
  • Monitor traffic, cache behavior, and security events across multiple sites
  • Troubleshoot one client site without affecting others
  • Prepare simple handoff notes for clients

Use it as an agency workflow checklist and link to the relevant setup or troubleshooting guide when you need the full procedure.

Use this recommended workflow for each client site:

  1. Gather site, DNS, origin, and WordPress access details.
  2. Add the client website to Pressidium EDGE.
  3. Verify domain ownership.
  4. Route DNS through EDGE.
  5. Confirm SSL is active.
  6. Connect the Pressidium Performance Plugin, if used.
  7. Test the site as a visitor.
  8. Review cache and security behavior.
  9. Document the site configuration internally.
  10. Monitor traffic, cache behavior, and security events after launch.

Using the same flow for every site helps your team avoid missed DNS, SSL, cache, or security checks.

Before adding a client site

Before you add a new site, collect the information your team needs to configure and support it.

Gather:

  • Primary domain
  • www or non-www preference
  • DNS provider access
  • WordPress admin access
  • Hosting provider or origin details
  • Whether the site uses WooCommerce, LMS, membership, or logged-in user features
  • Current CDN, firewall, caching, and performance plugins
  • Known paths that must not be cached
  • Existing security rules, IP restrictions, or geo-blocking requirements
  • Planned migration or DNS change window
  • Client approval and rollback contact

Confirm who controls DNS before starting. DNS access is required to route traffic through EDGE.

Add a client site to EDGE

Use the main site setup flow to add the client site, configure the origin, verify the domain, route DNS, configure SSL, and connect WordPress.

For the full procedure, see Adding a WordPress site to EDGE.

Agency checks before you start:

  • Confirm the site is being added to the correct EDGE account.
  • Confirm the domain spelling and hostname.
  • Confirm whether the root domain, www, or both should be active.
  • Confirm the origin hostname or IP address.
  • Confirm whether the origin requires HTTPS, a specific TLS mode, or SNI handling.
  • Confirm whether the client expects redirects between root and www.

Expected result: The client site is added to EDGE and ready for DNS, SSL, cache, security, and WordPress integration checks.

Prepare DNS changes

Before changing DNS for a client site, confirm the migration window and rollback plan.

Check:

  • Current DNS records
  • Required EDGE records shown in the Dashboard
  • Current TTL values
  • Existing CDN or proxy configuration
  • Email-related records, such as MX, SPF, DKIM, and DMARC
  • Subdomains that should not route through EDGE
  • Whether the client uses the root domain, www, or both
  • Whether Cloudflare records need to be set to DNS only

Do not remove unrelated DNS records. EDGE DNS changes should only affect the records needed to route web traffic.

Verify the site after DNS changes

After DNS points to EDGE, test the site before considering onboarding complete.

Check:

  1. Open the homepage.
  2. Open an internal page.
  3. Open a blog post or content page.
  4. Test both https://example.com and https://www.example.com, if both are used.
  5. Confirm HTTPS works without browser warnings.
  6. Confirm redirects behave as expected.
  7. Confirm images, CSS, JavaScript, fonts, and embedded assets load correctly.
  8. Confirm forms submit correctly.
  9. Confirm WordPress admin remains accessible.
  10. Confirm the origin is not blocking EDGE traffic.

Expected result: Visitors can access the site through EDGE, and the site behaves normally.

For a full post-setup review, use Verify Your Setup.

Review cache behavior

After the site is live through EDGE, review cache behavior before handoff.

Check:

  • Public pages are cacheable where appropriate.
  • Logged-in pages behave correctly.
  • Cart, checkout, account, and admin pages bypass public cache.
  • Search, filtering, and forms work correctly.
  • Query strings and cookies do not create unnecessary cache variations.
  • Cache purges update content as expected.
  • Any custom cache rules match the client’s site behavior.

For WooCommerce sites, test:

  • Product pages
  • Product categories
  • Add to cart
  • Cart page
  • Checkout page
  • Coupon flow
  • Order confirmation flow
  • My Account page
  • Payment callbacks, if applicable

Review security behavior

Review security behavior before handing the site back to the client.

Check:

  • Firewall protection is active.
  • Any custom IP Blocklist entries are intentional.
  • Any IP Allowlist entries are still valid.
  • Geo-blocking rules match the client’s requirements.
  • Login, form, API, and admin actions are not blocked.
  • Known agency, client, and developer IPs are not accidentally restricted.
  • Payment providers, webhook endpoints, and third-party integrations are not blocked.

If legitimate traffic is blocked, collect the affected IP address, URL, timestamp, country, and action before adjusting rules or contacting Support.

Connect the Performance Plugin

Use the Pressidium Performance Plugin when the client site needs WordPress-level integration with EDGE.

The plugin can help with cache sync and optimization features, depending on how the site is configured.

Agency checks:

  • Install and activate the Pressidium Performance Plugin in WordPress.
  • Connect the plugin to the correct EDGE site.
  • Confirm the plugin status shows as connected.
  • Test cache purge behavior from WordPress.
  • Confirm published changes appear as expected.
  • Store connection notes securely for your team.

Important: Do not share client secrets, API keys, or access tokens in plain text.

For the full procedure, see Performance Plugin EDGE Integration.

Organize client sites internally

For agencies, internal organization matters as much as technical setup.

For each site, keep a simple internal record with:

  • Client name
  • Domain
  • EDGE account or workspace
  • DNS provider
  • Hosting provider or origin
  • WordPress admin owner
  • Cache notes
  • Security notes
  • Known bypass paths
  • WooCommerce, LMS, or membership status
  • Date added to EDGE
  • Last configuration review date
  • Emergency contact or escalation owner

This helps your team troubleshoot faster and reduces dependency on one person’s memory.

Monitor client sites

After onboarding, review client sites regularly.

During each review, look for:

  • Monthly request usage
  • Traffic spikes
  • Cache behavior
  • Origin request volume
  • Firewall events
  • Blocked requests
  • SSL status
  • DNS status
  • Unusual bandwidth changes
  • Performance changes after WordPress updates
  • New plugin or theme changes that may affect caching or security

For agencies managing many sites, create a recurring review process. Focus first on high-traffic, revenue-critical, WooCommerce, membership, and campaign-driven sites.

Handle client content updates

When a client says their changes are not visible, use a focused cache and content check.

  1. Confirm the exact URL.
  2. Confirm whether the change was published in WordPress.
  3. Test in a private browsing window.
  4. Purge the affected URL or related content.
  5. Test as logged out.
  6. Test as logged in, if the page has user-specific content.
  7. Check whether another cache layer or plugin is active.
  8. Confirm whether the content is controlled by a page builder, theme, plugin, or external feed.

Expected result: Public content updates should appear after the relevant cache is purged.

If the change is still not visible, check whether the issue is caused by WordPress, the theme, a page builder, another cache layer, or the origin.

Troubleshoot one site without affecting others

When an issue affects one client site, avoid making account-wide changes unless needed.

Start with site-specific checks:

  • Affected domain
  • Affected URL
  • Recent site-specific changes
  • Site-specific cache rules
  • Site-specific firewall rules
  • WordPress plugins
  • Theme changes
  • Origin logs
  • DNS records for that domain
  • SSL status for that hostname

Avoid broad changes that affect all client sites unless the issue is confirmed to be account-wide.

Common agency use cases

New client onboarding

Use EDGE when taking over a client site that already has several performance or security tools.

Recommended approach:

  1. Audit the existing stack.
  2. Identify current CDN, firewall, and cache plugins.
  3. Decide which tools should remain, be disabled, or be removed.
  4. Add the site to EDGE.
  5. Route DNS.
  6. Test cache, SSL, forms, login, and checkout.
  7. Document the final setup.

Remove or disable overlapping tools only when it is safe to do so.

Campaign or launch preparation

Before a campaign, product launch, or traffic spike:

  1. Confirm DNS and SSL status.
  2. Review cacheability of landing pages.
  3. Purge critical pages if needed.
  4. Confirm forms, checkout, and tracking work.
  5. Review firewall rules.
  6. Confirm client and agency emergency contacts.
  7. Monitor traffic during the campaign.

Focus on pages that receive paid traffic, email traffic, social traffic, or launch traffic.

WooCommerce client management

For WooCommerce clients:

  • Keep product and category pages cacheable where safe.
  • Keep cart, checkout, account, and order pages out of public cache.
  • Test payment flows after major changes.
  • Review plugin cookies and sessions.
  • Watch origin load during sales events.
  • Confirm security rules do not block payment callbacks or checkout actions.

Test WooCommerce flows after DNS, cache, security, plugin, or theme changes.

Membership, LMS, or logged-in sites

For membership and LMS clients:

  • Separate public marketing pages from private user areas.
  • Avoid caching private dashboards or progress pages as public content.
  • Test as logged out, member, admin, and any important user role.
  • Review rules after adding LMS, membership, or access-control plugins.

Logged-in experiences need more careful testing than simple public marketing sites.

Multi-site management checklist

Use this checklist when managing several client sites.

  • Client and domain recorded
  • DNS provider recorded
  • Origin or hosting provider recorded
  • Site added to EDGE
  • Domain verified
  • DNS updated
  • SSL confirmed
  • Homepage tested
  • Key internal pages tested
  • WordPress admin tested
  • Forms tested
  • WooCommerce checkout tested, if relevant
  • Membership or LMS flows tested, if relevant
  • Cache behavior reviewed
  • Firewall behavior reviewed
  • Performance Plugin connected, if used
  • Conflicting cache, CDN, or security tools reviewed
  • Known bypass paths documented
  • Client handoff notes completed
  • Monitoring process assigned

Client handoff notes

After onboarding a site, give the client a short summary of what changed and what they should expect.

Include:

  • The domain added to EDGE
  • Date DNS was updated
  • What EDGE now handles
  • Which tools were removed, replaced, or kept active
  • Any paths intentionally excluded from cache
  • Any important Firewall, IP Allowlist, IP Blocklist, or Geo-blocking rules
  • What the client should do when publishing major updates
  • Who to contact if something looks wrong

Keep the handoff short. Clients usually need to know what changed, what is now handled by EDGE, and when to contact your team.

Need help?

Contact Support if you cannot safely confirm whether the issue is caused by EDGE, the origin, WordPress, DNS, SSL, cache rules, Firewall rules, or another active tool.

Contact Support especially if:

  • A client site is unavailable after DNS changes
  • SSL does not activate correctly
  • Domain verification remains pending
  • Legitimate traffic is blocked
  • Cache behavior looks unsafe
  • WooCommerce, membership, LMS, or logged-in flows behave incorrectly
  • Performance problems continue after cache and origin checks
  • A change may affect more than one client site

Include:

  • Client domain
  • Affected URL
  • Timestamp and timezone
  • Recent changes
  • Expected result
  • Actual result
  • Screenshots
  • Visitor IP address, if relevant
  • Relevant DNS, SSL, cache, Firewall, or Performance Plugin settings

Important: Avoid account-wide cache, Firewall, DNS, or security changes unless the issue is confirmed to affect multiple sites.

Where to go next