Requirements
What a DpCommand deployment needs.
Fit comes first, then a few practical requirements. Your implementation team confirms the details with you during onboarding.
Fit
Repeatable structure is what makes scale worthwhile.
Strong fit
- Many legitimate combinations of services, markets, customer needs and topics
- A WordPress site, or a willingness to build managed areas on WordPress
- An owner willing to define content standards and who approves what
Less benefit
- A small number of highly bespoke pages
- Sites built entirely on page builders or custom structures that cannot accept a managed area
- Other CMS platforms, which are not supported today
What your agency needs
Requirements for your agency.
Your implementation team confirms the details and walks you through setup during onboarding.
Your team
People and equipment
- A Windows computer for each team member who will run DpCommand
- Team members who complete DpCommand training before your account goes live
- Someone responsible for reviewing and approving content before it is published
Client websites
Websites you manage
- Client websites built on WordPress and served securely over HTTPS
- Administrator access, so DpCommand can be connected during onboarding
- Hosting that can handle regular publishing, with backups in place
Accounts and access
Permission to act for your clients
- Authority from each client to manage the content on its website
- Access to each client site in Google Search Console
- Clear agreement with each client on what DpCommand will manage
Getting set up
What we take care of with you
- Your implementation team confirms your setup and connects each website
- A readiness check on each website before publishing begins
- A reliable internet connection at your office
Readiness
How a website is checked before publishing at scale.
Before publishing begins, each website is checked. The checks look at the site without changing its content.
Connection
The website is secure and DpCommand can connect to it.
Permissions
DpCommand has the access it needs to manage the content you have agreed on.
Setup
Everything DpCommand needs on the website is installed and working.
Security
DpCommand’s access is limited to the content it manages.
Health
The website is in good health and visible to search engines.
Responsiveness
The server responds quickly enough to support regular publishing.
Your hosting
Your server, your pace.
- You choose and operate your website hosting.
- You decide how quickly DpCommand may publish to your site, and you can change it at any time.
- If the site slows down or errors appear, DpCommand shows you so the pace can be adjusted.
- Keep current backups of your website before large publishing runs.
Ownership and responsibility
What stays with you.
- Your domain, hosting, theme, navigation, branding and analytics accounts remain yours.
- DpCommand access can be granted and revoked without transferring ownership.
- Strategy, factual accuracy, legal compliance, brand standards, geographic accuracy and final approval stay with the agency and client.
- Publication does not guarantee crawling, indexing, ranking, traffic, leads or revenue.
Adoption path
Scoped first, then scaled.
Establish access
Connect the website and the search properties you have authority over.
Check compatibility
Review the website’s structure and existing content to decide what DpCommand will manage.
Validate
Run the readiness checks and fix anything they find.
Pilot
Publish a scoped set of pages and watch how the site and search respond.
Decide
Record a readiness decision with the evidence behind it.
Scale with observation
Expand coverage while monitoring site health and search state.
Next step