For your developer

A section or two. One rule each. About an hour.

Everything your team needs to know before saying yes: what we touch, what we do not, and how to undo it.

What we ask for: One or more sections or pages on your domain, for example yourdomain.com/guides. Nothing else on your site changes. No CMS login, no access to your codebase, no customer data.
The rule your developer adds: A single reverse proxy rule that forwards requests for those sections or pages to our server and returns the page under your domain. It works with Cloudflare, Vercel, Netlify, Nginx, Apache and most CDNs. It usually takes about an hour, and we send the exact rule for your stack.
How Google sees it: As native pages on your domain. Every page carries a canonical tag pointing to its own URL in your section, a sitemap you can submit in Search Console, and breadcrumbs that link back into your existing pages.
Speed and caching: Pages are static and served from a CDN, so they load fast and add no load to your servers. When we update a page, the cache refreshes on its own.
Who owns the pages: You do. The words, images and code are yours from day one. If you stop working with us, we hand over the files and you can host them yourself or remove the rule. Turning it off is deleting one line.
Prefer we work in your codebase?: That works too. We open a pull request with the new pages and the internal links, and your team reviews it like any other change.

What the rule looks like

# Nginx example
location /guides/ {
  proxy_pass https://pages.offpagetwo.com/yourdomain/;
  proxy_set_header Host pages.offpagetwo.com;
}