Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →To create a new WordPress site in an agency hosting account, first identify which hosting dashboard you actually use. The workflow documented here is for WordPress.com: sign in, open the Hosting Dashboard, choose Add new site, select a creation route, choose a domain and plan, then open the new site’s WP Admin area. The resulting site is independent, with its own design, domain, subscribers, settings and subscription.
“Agency hosting” is not a single WordPress product name. If your agency uses another provider, its panel labels and provisioning steps may differ; do not assume that a WordPress.com instruction applies to that host. This guide also explains when a separate site is the right architecture instead of a WordPress Multisite network.
As an Amazon Associate I earn from qualifying purchases.
What you are creating
On WordPress.com, adding a site creates another independently managed WordPress.com site under the account you use. WordPress.com Support states that “Each site will be completely independent of each other, with different designs, domains, subscribers, and settings.” A site created for one client does not inherit the theme, users, subscribers or content of another site.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe account that creates the site becomes its owner and administrator. That matters in agency work: ownership, billing and day-to-day access can involve different people, so decide whose account should perform the initial creation before you begin. A subscription can also have an owner who is different from the site owner, so document both relationships in your client hand-off records.
Before you start: choose the right architecture
Use a separate site for an independent client project
Choose a separate site when each client needs its own domain, design, subscribers, privacy settings, administrators or billing decision. Each site receives its own site settings and plan. A plan attached to one site is not shared automatically with other sites in the same WordPress.com account.
Use Multisite only for a deliberately shared network
WordPress.org Multisite is a network of sites inside one WordPress installation. It is not the same as clicking Add new site in a hosting account dashboard. Enabling Multisite requires server and configuration work, including defining WP_ALLOW_MULTISITE in wp-config.php. WordPress.org warns that some hosts do not support the feature, so confirm support with the host before enabling it.
A network can make sense when one organization needs centralized administration and a coordinated set of subsites. It introduces network-level configuration and support considerations that do not apply to independent WordPress.com sites. If the agency brief simply says “add another client website,” create a separate site unless the client has explicitly chosen a Multisite architecture.
| Decision | Independent WordPress.com site | WordPress Multisite network |
|---|---|---|
| Where it is created | Hosting Dashboard with Add new site | Inside one WordPress installation after Multisite is configured |
| Domains and design | Each site has its own domain and design choices | Sites share a network installation; domain and theme arrangements depend on the network setup |
| Plans and billing | Each site needs its own WordPress.com plan | Not the WordPress.com independent-site workflow; hosting and licensing depend on the network host |
| Prerequisites | WordPress.com account and a selected creation route | Configuration access, host support and a network design decision |
| Best fit | Separate client or brand projects | One organization intentionally operating a connected group of sites |
WordPress.com requirements and decisions
- Account: Sign in to the WordPress.com account that should own and manage the new site.
- Creation route: Decide whether you are starting from scratch, using the AI-assisted creator, migrating an existing site or connecting through Jetpack.
- Domain: You can register a new domain, use a domain you already own or connected, or start with a free WordPress.com address. Buying a domain before setup is not required.
- Plan: Select a WordPress.com plan for this site. Plans are assigned per site, not pooled across all sites in the account.
- Client ownership: Confirm who should own the site and who will pay for or administer its subscription. The creating account becomes the owner and administrator.
- Launch content: Prepare the initial pages, navigation, contact details and intended primary domain before making the site public.
Step-by-step: add the new site in WordPress.com
1. Sign in to the managing account
Open WordPress.com and sign in with the account that should control the project. For an agency, avoid creating the site from a temporary employee account unless your ownership and transfer process is already defined. The initial creator becomes the site owner and administrator.
2. Open the Hosting Dashboard
After signing in, select the WordPress W icon in the upper-left corner. This opens the Hosting Dashboard, where the account’s sites are listed and managed. If you do not see the expected sites, verify that you are in the correct WordPress.com account before creating anything.
3. Select “Add new site”
In the Hosting Dashboard, choose Add new site. This begins the site-provisioning flow without changing the existing sites in the account.
4. Choose the creation path
WordPress.com presents four routes. Select the one that matches the project rather than choosing the first option by habit.
| Route | Choose it when | What to prepare |
|---|---|---|
| Start a fresh site | The client needs a new installation and you will build its pages, design and settings yourself. | Brand assets, site name, initial content and a domain decision. |
| Create with AI | You want assisted setup and a generated starting structure, then plan to review and edit it. | Clear description of the business, audience, services and desired tone; treat generated content as a draft. |
| Migrate an existing site | The project is moving an existing WordPress site into WordPress.com. | Access to the source site, a migration plan, backups and a cutover window. |
| Connect via Jetpack | You are connecting an existing WordPress installation through Jetpack rather than creating a purely new build. | Administrative access to the source installation and the connection credentials requested by the flow. |
For a genuinely new client project, choose the fresh-site route. Use migration or Jetpack only when an existing installation is part of the scope. AI assistance can accelerate a first draft, but the agency remains responsible for checking accuracy, accessibility, branding and legal text before launch.
5. Select a domain option
During setup, choose one of the available address routes:
- New domain: Register a new domain as part of the setup flow.
- Domain you already own: Use or connect an existing domain, following the requested DNS or connection instructions.
- Free WordPress.com address: Begin with the supplied WordPress.com address if the client is not ready to register or connect a custom domain.
The free address lets you build before a custom domain is ready. If the client plans to use a domain later, record the intended spelling and ownership now so the temporary address does not become the accidental public identity.
6. Select the plan for this site
Choose the WordPress.com plan that meets this project’s requirements. The plan applies to the site being created; it is not shared automatically with the other sites in the account. Confirm whether the client or agency will own the subscription and who will receive renewal notices.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute7. Wait for provisioning, then open WP Admin
When setup finishes, return to the Hosting Dashboard, select the new site and choose WP Admin. This opens the site’s WordPress dashboard, where you can configure the theme, pages, menus, users, plugins or other features available to the selected plan.
Open the site in a separate browser tab and verify that the dashboard title, domain and site identity match the intended client. This simple check prevents editing the wrong site when an agency account contains several similar projects.
Configure the site before launch
Review content and navigation
Check the home page, page titles, headings, calls to action, contact details, footer links and primary menu. Test every navigation item and form in a logged-out browser window. Remove placeholder copy and unused pages before inviting the client to review.
Confirm the site email address
Verify the administrative and contact email address shown in the site settings. It should belong to the person or team responsible for approvals, security notifications and account recovery, not an abandoned project mailbox.
Set the intended primary domain
If you connected or registered a custom domain, set it as the site’s primary address after confirming that it resolves to the correct site. Keep the temporary WordPress.com address documented for administration and recovery, but use the client’s chosen domain as the public identity.
Check privacy and visibility
New sites are not public until you launch them. While the site is private or in Coming Soon mode, send reviewers the appropriate preview access rather than assuming the public domain is live. Confirm that search-engine visibility and any privacy controls match the client’s launch plan.
How to make the site live
- Sign in to the site’s WordPress.com account and open the site in WP Admin.
- Go to Settings → Reading → Site Visibility.
- Review the available visibility choice and select the launch/public option when the content, domain and approval checks are complete.
- Save the setting, then open the primary domain in a logged-out browser or private window.
- Test the home page, navigation, forms and key links from the public view.
Launching changes the site from its private or Coming Soon state to its public state. Do not use the visibility control as a substitute for content approval: it makes the site reachable, but it does not validate copy, legal notices, forms or DNS configuration.
Domain activation and DNS timing
WordPress.com Support’s launch guidance, last reviewed September 17, 2026, says that a recently registered or connected domain can take 24–72 hours to become fully active. The exact delay depends on the domain connection and DNS propagation. During that window, the site may work at its temporary WordPress.com address while the custom domain still shows a setup message or an older destination.
Recommended Free Tools
If the domain is not active after the stated window, check that the domain was connected to the intended site, that required DNS records were entered exactly as instructed, and that no old hosting record is still directing visitors elsewhere. Contact the domain registrar or WordPress.com support with the domain name and the connection status rather than repeatedly changing records.
Agency ownership, access and hand-off
Record the owner and subscription owner
Write down the WordPress.com account that owns the site, the person responsible for the subscription, the billing contact and the client’s approved administrators. These may be different people. A clear record prevents a client from losing access when an employee leaves or an agency contract ends.
Grant the minimum necessary access
Give collaborators the role they need for their work. Keep ownership and billing privileges with the agreed owner, and remove temporary access after launch or migration. Store recovery information in the agency’s approved password-management process rather than in a project document.
Maintain a launch record
For each client site, record the creation date, selected plan, temporary and primary domains, launch date, DNS changes, approved administrators and the final public URL. This is especially important when one account manages multiple independent sites.
Troubleshooting common setup problems
“Add new site” is missing
Confirm that you are signed in to WordPress.com and have opened the Hosting Dashboard through the upper-left W icon. If the account is managed by an organization, ask the account owner whether your role can create sites. Do not create a duplicate site in another account until ownership is resolved.
The new site appears under the wrong account
The creating account becomes the owner. If the wrong account created the site, stop adding content, document the intended owner and use the supported ownership or transfer process rather than trying to solve the problem by changing only the administrator email.
The custom domain shows the wrong site
Check the primary-domain setting in the selected site and compare the domain’s connection records with the instructions from the registrar or WordPress.com. Confirm that you are editing the intended site in WP Admin. Allow up to 24–72 hours for a recent connection to become fully active.
The site is still private after approval
Open Settings → Reading → Site Visibility and confirm that the public launch option was saved. Then test from a logged-out window. A cached browser session can make a visibility change appear incomplete, so test from another browser or network before changing settings again.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A client asks for “another site” inside the existing installation
Clarify whether they want an independent WordPress.com site or a Multisite network. Independent sites have separate plans and settings. Multisite requires host support and configuration, including WP_ALLOW_MULTISITE; it should be designed and approved as an architecture project, not treated as a shortcut for adding a client site.
Practical decision checklist
- Is the hosting platform actually WordPress.com, or does the agency use another provider with different controls?
- Should this project be an independent site rather than a Multisite subsite?
- Which account should own the site?
- Will the project start fresh, use AI assistance, migrate an existing site or connect through Jetpack?
- Will the site use a new domain, an already-owned domain or a free WordPress.com address?
- Has a separate plan been selected for this site?
- Are the site email, client administrators and subscription owner documented?
- Have content, navigation, forms and the primary domain been checked?
- Has the site been deliberately switched from private/Coming Soon to public in Settings → Reading → Site Visibility?
- Has the public domain been tested after launch, allowing 24–72 hours for a recent domain connection to activate?
When this workflow does not apply
If “agency hosting” means a third-party host rather than WordPress.com, the concepts still help—choose the site architecture, provision the site, attach a domain, configure WordPress and launch it—but the exact buttons, plan model and DNS instructions must come from that provider. Do not present the WordPress.com Hosting Dashboard path as a universal agency-hosting procedure.
Likewise, this guide does not replace a migration runbook for a production site, a Multisite design document or a registrar-specific DNS guide. Those projects require their own backups, access checks, testing and rollback plans.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
