Create a New Site in SharePoint 2013: Beginner-Friendly Setup Guide

SharePoint 2013 still powers critical workflows for countless organizations. I’ve set up dozens of these sites for teams that need simple, reliable collaboration without modern bells and whistles.

The process is straightforward once you understand the hierarchy. You’ll need admin access to your SharePoint farm and a clear purpose for this new site—whether it’s for a department, project, or team.

What you get is a fully functional site with document libraries, lists, and permissions ready to go. The whole setup takes under 20 minutes if you’ve done your prep work.

Works the same whether you’re on-premises or in a hybrid environment. Here’s how to do it right the first time.

What Youll Need

Instructions

Here’s the process I follow to get a new site up and running in this platform.

Log in to the server with an account that has farm administrator privileges. Open the browser and navigate to Central Administration by entering the URL in the format http://[servername]:[port]/_admin. You’ll land on the main dashboard.

Under the Application Management section, click Create site collections. This is the gateway to provisioning any new site. If you don’t see this option, your account lacks the necessary permissions—contact your SharePoint admin.

In the Create Site Collection page, fill in the Title and Description fields. These appear in the site directory and search results, so make them descriptive. For the Web Site Address, choose a unique path under the managed path dropdown—/sites/ is the default.

Select a template that matches your use case. For collaboration, Team Site is the standard. For publishing, Publishing Site offers more features. Set the language and time zone correctly—these can’t be changed later without recreating the site.

Scroll to the Quota section. Assign a storage quota (e.g., 1GB) to prevent unrestricted growth. For a development environment, you might set this higher, but production sites should have defined limits to avoid storage bloat.

Under Primary Site Collection Administrator, assign yourself or the intended owner. Add a Secondary Site Collection Administrator as a backup. Click OK to create the site. The page will refresh and display a confirmation message when complete.

Return to the Site Collections list in Central Administration. Your new site should appear in the list with a status of Active. Click the URL to open it in a new tab. The default home page loads, confirming the site is live.

Check the top navigation bar and quick launch sidebar to ensure the template applied correctly. If the site doesn’t load, verify the IIS bindings and Alternate Access Mappings in Central Administration—these often cause access issues if misconfigured.

From the new site’s home page, click the gear icon and select Site Settings. Here, you can add subsites, configure navigation, or set up lists and libraries tailored to your team’s needs.

For immediate usability, create a Document Library for shared files and a Tasks list for project tracking. Navigate to Site Contents to add these apps. Each addition appears instantly, ready for content.

Tips and Common Mistakes

Small oversights in setup can cause big problems down the line, so here’s what I’ve learned from building dozens of SharePoint sites.

Permission Pitfall: In Step 1, if you don’t see the Create site collections option under Application Management, your account genuinely lacks farm administrator privileges. Don’t waste time troubleshooting the interface—contact your SharePoint admin immediately to request the proper permissions. This is the single most common stumbling block for new users.

Template Selection Strategy: For Step 2, Team Site works perfectly for 90% of collaboration needs, but if you’re building a public-facing portal, the Publishing Site template is worth the extra features. Between us, I’ve seen teams regret choosing Team Site when they later needed publishing capabilities.

Quota Planning: In Step 3, the 1GB storage quota example is just a starting point. For development environments, I recommend 10GB to account for testing, while production sites should align with your organization’s actual storage needs. Skipping this step often leads to unexpected growth that’s hard to manage later.

Verification Pro Tip: During Step 4, if your new site doesn’t appear in the Site Collections list, double-check the URL format in your browser. I’ve seen typos in the [servername] or [port] portions of the http://[servername]:[port]/_admin URL cause confusion, making users think the site creation failed when it was just an access issue.

Frequently Asked Questions

Creating a new site in SharePoint 2013 is a straightforward process that empowers you to organize and collaborate effectively. 🌟 With your site now set up, take the next step by customizing it to fit your team’s needs—explore templates, permissions, and apps to enhance functionality. Happy building!