SEO implementation across CMS and custom websites
We start by checking where the problem lives: CMS settings, a shared template, routing, rendered HTML or analytics. The agreed access and release process determine which layer we can change.
Discuss your website platformWhere can we work on your current platform?
We can review public results using representative URLs. An approved CMS role, preview or staging access helps trace the change to its actual source. We agree the minimum permissions for the task.
| Platform | Common change or check | Release and acceptance |
|---|---|---|
| WordPress | Template, index setting, plugin output and redirect rules. | Use approved admin or staging access. Recheck status, canonical and content. |
| Shopify | Collection, product and variant templates, with filter URL behavior sampled. | Review a theme preview and coordinate the approved release. Compare live collection and product pages. |
| Webflow | CMS collections, redirects, metadata and navigation. | Use the assigned Editor or publishing role. Verify the live route and content. |
| Custom JavaScript or PHP | Routing, server output, rendered page, sitemap, and shared templates. | Work in the agreed repository or through tickets. Compare raw and rendered output and verify the deployed URL. |
| Hosted tools | Page fields, templates and URL policies the provider exposes. | Confirm permissions and vendor constraints, then recheck the fields available in production. |
What does production evidence look like?
On October 15, 2026, the AllScale Webflow retest documented one 301 followed by a 200 and ten articles on the expected page in the production browser. It also records a separate request that returned the older version. This is why a retest should report its environment, time and the exact URL behavior.
How do we share access and release ownership?
Your developers can retain the repository and deploy from our specification. Where the scope allows, our team can use a named role in the CMS or repository. For a joint release, assign an approver, a release owner, and who reruns the acceptance checks. For portfolios, keep those permissions and contacts by domain.
Discuss your website platform
Send the platform, representative URLs, the layer you can change, and who can approve and publish a release.