# Plan the website and the work behind it

> Site operations guides for clearer decisions about website builds, ecommerce, integrations, analytics, maintenance, and migrations.

Source: https://scayverstaging.1wp.site/resources/site-operations/

![Person typing at a desk with two monitors displaying code and open site operations guides nearby.](https://scayverstaging.1wp.site/wp-content/uploads/2026/09/sg-resources-146772-hero.webp)

These site operations guides help you define what a website must do, where its information moves, and what your team needs to maintain.

[Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book) [Every resource](https://scayverstaging.1wp.site/resources/)

A website is easier to build when its decisions are visible before anyone chooses a tool or draws a page, and easier to operate when a person owns each handoff after launch. You do not need to read every guide in order. Start with the question closest to the problem you face now. If your checkout is failing, begin with that journey. If a redesign is approaching, begin with the content and URL inventory. If your site runs but nobody knows who handles updates or backups, begin with website care. Each guide gives you a decision framework you can use in a conversation with a developer or internal team.

## Scope a build people can maintain.

Before asking for a price, use the [website requirements checklist](https://scayverstaging.1wp.site/resources/site-operations/website-requirements-checklist/) to name the audience, primary action, content, integrations, and owner. The [CMS selection guide](https://scayverstaging.1wp.site/resources/site-operations/choosing-a-cms/) asks whether editors can manage real records rather than only demo pages. [Plugin or custom development](https://scayverstaging.1wp.site/resources/site-operations/plugin-vs-custom-development/) helps you compare a ready-made feature with a workflow that needs its own build.

If tools must exchange data, start with an [integration data map](https://scayverstaging.1wp.site/resources/site-operations/integration-data-map/). Then use [API vendor due diligence](https://scayverstaging.1wp.site/resources/site-operations/api-vendor-due-diligence/) to question limits, account ownership, costs, failure behavior, and exit options. These are related decisions, but they are not the same. First define what information must move. Then decide whether a vendor can support that movement reliably.

## Make commerce and access rules explicit.

For a store, map the [checkout flow](https://scayverstaging.1wp.site/resources/site-operations/checkout-flow-planning/) from cart through payment and fulfillment. Structure the [product catalog](https://scayverstaging.1wp.site/resources/site-operations/ecommerce-catalog-structure/) so shoppers can compare items and staff can update them. Define [shipping and tax workflows](https://scayverstaging.1wp.site/resources/site-operations/shipping-and-tax-workflow/) from owner-approved business and professional guidance. Connect [returns information](https://scayverstaging.1wp.site/resources/site-operations/returns-content-structure/) to product pages, order messages, and support so a customer can find the right process.

For a gated experience, a [membership access model](https://scayverstaging.1wp.site/resources/site-operations/membership-access-model/) clarifies who can see what when account status changes. [LMS delivery requirements](https://scayverstaging.1wp.site/resources/site-operations/lms-delivery-requirements/) cover enrollment, progression, completion, and staff editing. These pages begin with business rules because a login screen or course template cannot decide them for you.

## Connect inquiries to accountable action.

A booking flow starts with the [fields and states an appointment needs](https://scayverstaging.1wp.site/resources/site-operations/appointment-booking-fields/). A form-to-sales handoff needs [CRM field mapping](https://scayverstaging.1wp.site/resources/site-operations/crm-field-mapping/) so the request lands with its context. Review [form spam and privacy](https://scayverstaging.1wp.site/resources/site-operations/form-spam-and-privacy/) to keep the inquiry route usable without collecting more data than the team needs. When a workflow spans several systems, [automation failure handling](https://scayverstaging.1wp.site/resources/site-operations/automation-failure-handling/) defines alerts, retries, and a person who can recover lost work.

An AI assistant needs narrower rules than a general sales promise. Set [chatbot knowledge boundaries](https://scayverstaging.1wp.site/resources/site-operations/ai-chatbot-knowledge-boundaries/) around approved sources and unknown answers. Design the [human handoff](https://scayverstaging.1wp.site/resources/site-operations/ai-human-handoff/) so a visitor can reach a person without starting over. The useful question is not how many messages the bot can send. It is whether the person gets a correct answer or a clear route to one.

## Measure what the site actually accomplishes.

Use [analytics event naming](https://scayverstaging.1wp.site/resources/site-operations/analytics-event-naming/) to identify meaningful actions before tagging buttons. Follow with [conversion event validation](https://scayverstaging.1wp.site/resources/site-operations/conversion-event-validation/) to test whether the business action and report agree. [Consent and analytics planning](https://scayverstaging.1wp.site/resources/site-operations/consent-and-analytics-planning/) connects owner-approved visitor choices to tag behavior. A report cannot be trusted if the event definition, delivery path, or consent state is unclear.

Set a [website performance budget](https://scayverstaging.1wp.site/resources/site-operations/website-performance-budget/) for media, scripts, fonts, and third-party tools against real page journeys. Keep [accessibility in content operations](https://scayverstaging.1wp.site/resources/site-operations/accessibility-content-operations/) so new headings, images, links, and downloads remain usable after launch. These are ongoing publishing decisions, not one-time design effects.

## Prepare the site to change safely.

Run a [backup restore drill](https://scayverstaging.1wp.site/resources/site-operations/backup-restore-drill/) before an outage forces the question. Give [plugin updates a staging process](https://scayverstaging.1wp.site/resources/site-operations/plugin-update-staging/) tied to the visitor actions each dependency affects. Decide [who responds to monitoring alerts](https://scayverstaging.1wp.site/resources/site-operations/monitoring-ownership/) and compare [website care scope](https://scayverstaging.1wp.site/resources/site-operations/website-care-scope/) by actual responsibilities, exclusions, and recovery terms.

A move needs its own decision set. Map [domain and DNS ownership](https://scayverstaging.1wp.site/resources/site-operations/domain-dns-transfer/) before changing where the site points. Build a [content migration inventory](https://scayverstaging.1wp.site/resources/site-operations/content-migration-inventory/) before replacing the old site. Use [redirect mapping](https://scayverstaging.1wp.site/resources/site-operations/redirect-mapping/) to preserve relevant paths for people following old links. Define a [launch rollback plan](https://scayverstaging.1wp.site/resources/site-operations/website-launch-rollback/) in case the new version breaks a critical flow. None of these tasks is interchangeable with a visual redesign.

## Turn these site operations guides into the next decision.

Pick the guide that describes your immediate problem and write down its unanswered questions. Bring the current site, the systems involved, and the person who owns the outcome into the conversation. A useful scope can be small. It should still explain what the team will build, what it will test, and who will operate it afterward.

Explore [development services](https://scayverstaging.1wp.site/services/development/) for connected site features and [website care](https://scayverstaging.1wp.site/services/maintenance/) for ongoing support. If you want help deciding where the work starts, [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/).

[Return to all resources](https://scayverstaging.1wp.site/resources/).

Guides

## The guides in Site operations.

1. ### [Define the website before you price the build](https://scayverstaging.1wp.site/resources/site-operations/website-requirements-checklist/)
   Site operations · 4 min read
2. ### [Choose a CMS around the work your team does](https://scayverstaging.1wp.site/resources/site-operations/choosing-a-cms/)
   Site operations · 3 min read
3. ### [Use the smallest build that solves the real problem](https://scayverstaging.1wp.site/resources/site-operations/plugin-vs-custom-development/)
4. ### [Map the handoff between tools before you automate it](https://scayverstaging.1wp.site/resources/site-operations/integration-data-map/)
5. ### [Check the dependency before it becomes invisible](https://scayverstaging.1wp.site/resources/site-operations/api-vendor-due-diligence/)
6. ### [Plan checkout as a business process, not a button](https://scayverstaging.1wp.site/resources/site-operations/checkout-flow-planning/)
7. ### [Give the product catalog a structure that can grow](https://scayverstaging.1wp.site/resources/site-operations/ecommerce-catalog-structure/)
8. ### [Decide the order rules before you configure checkout](https://scayverstaging.1wp.site/resources/site-operations/shipping-and-tax-workflow/)
9. ### [Make the return path clear before someone needs it](https://scayverstaging.1wp.site/resources/site-operations/returns-content-structure/)
10. ### [Define access rules before the member dashboard](https://scayverstaging.1wp.site/resources/site-operations/membership-access-model/)
11. ### [Design the learning workflow before choosing the LMS](https://scayverstaging.1wp.site/resources/site-operations/lms-delivery-requirements/)
12. ### [Ask for what the appointment actually needs](https://scayverstaging.1wp.site/resources/site-operations/appointment-booking-fields/)
13. ### [Make website leads usable inside the CRM](https://scayverstaging.1wp.site/resources/site-operations/crm-field-mapping/)
14. ### [Stop form spam without punishing real visitors](https://scayverstaging.1wp.site/resources/site-operations/form-spam-and-privacy/)
15. ### [Every automation needs an owner when it stops](https://scayverstaging.1wp.site/resources/site-operations/automation-failure-handling/)
16. ### [Give the chatbot a smaller, trustworthy job](https://scayverstaging.1wp.site/resources/site-operations/ai-chatbot-knowledge-boundaries/)
17. ### [The handoff is part of the answer](https://scayverstaging.1wp.site/resources/site-operations/ai-human-handoff/)
18. ### [Name the action before you tag the button](https://scayverstaging.1wp.site/resources/site-operations/analytics-event-naming/)
19. ### [Test the conversion, not just the dashboard](https://scayverstaging.1wp.site/resources/site-operations/conversion-event-validation/)
20. ### [Make measurement follow the choice a visitor makes](https://scayverstaging.1wp.site/resources/site-operations/consent-and-analytics-planning/)
21. ### [Spend page weight on things visitors can use](https://scayverstaging.1wp.site/resources/site-operations/website-performance-budget/)
22. ### [Accessibility continues every time someone publishes](https://scayverstaging.1wp.site/resources/site-operations/accessibility-content-operations/)
23. ### [Test the backup before you need it](https://scayverstaging.1wp.site/resources/site-operations/backup-restore-drill/)
24. ### [Update the plugin, then prove the journey still works](https://scayverstaging.1wp.site/resources/site-operations/plugin-update-staging/)
25. ### [An alert needs a person and a next action](https://scayverstaging.1wp.site/resources/site-operations/monitoring-ownership/)
26. ### [Know what ongoing website care actually covers](https://scayverstaging.1wp.site/resources/site-operations/website-care-scope/)
27. ### [Keep the domain and its connected services in view](https://scayverstaging.1wp.site/resources/site-operations/domain-dns-transfer/)
28. ### [Decide what to carry before you rebuild](https://scayverstaging.1wp.site/resources/site-operations/content-migration-inventory/)
29. ### [Give each old link a sensible destination](https://scayverstaging.1wp.site/resources/site-operations/redirect-mapping/)
30. ### [Decide how to reverse a bad launch before launch day](https://scayverstaging.1wp.site/resources/site-operations/website-launch-rollback/)

No guides in this group yet.

Keep reading

## Read after Site operations.

The rest of the resources, newest first.

- [2 July 2026 Customer Persona Worksheet](https://scayverstaging.1wp.site/resources/customer-persona-worksheet/)
- [2 July 2026 The Social Content Sprint Playbook](https://scayverstaging.1wp.site/resources/the-social-content-sprint-playbook/)
- [2 July 2026 AI Prompt Pack for Blog Post Outlines](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-blog-post-outlines/)
- [2 July 2026 Email Welcome Sequence Template](https://scayverstaging.1wp.site/resources/email-welcome-sequence-template/)
- [2 July 2026 Website Pre Handoff QA Checklist](https://scayverstaging.1wp.site/resources/website-pre-handoff-qa-checklist/)
- [2 July 2026 The SEO Content Audit Guide](https://scayverstaging.1wp.site/resources/the-seo-content-audit-guide/)
- [2 July 2026 Positioning Statement Worksheet](https://scayverstaging.1wp.site/resources/positioning-statement-worksheet/)
- [2 July 2026 The Client Onboarding Playbook](https://scayverstaging.1wp.site/resources/the-client-onboarding-playbook/)
- [2 July 2026 AI Prompt Pack for Ad Headline Variations](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-ad-headline-variations/)
- [2 July 2026 The One Page Creative Brief Template](https://scayverstaging.1wp.site/resources/the-one-page-creative-brief-template/)
- [2 July 2026 Brand Launch Readiness Checklist](https://scayverstaging.1wp.site/resources/brand-launch-readiness-checklist/)
- [2 July 2026 The Landing Page Teardown Guide](https://scayverstaging.1wp.site/resources/the-landing-page-teardown-guide/)