Key takeaways

• SharePoint is designed for internal audiences: document management, team collaboration, and intranet pages behind authenticated access.
• A dedicated CMS (Kentico, Sitefinity, Umbraco, Payload) is designed for public-facing digital experiences: websites, landing pages, and content published to external audiences.
• Most organisations with a public web presence and an internal collaboration requirement use both: SharePoint for internal, CMS for external.
• Trying to run a public website on SharePoint introduces limitations in design control, SEO, performance, and content workflow that a dedicated CMS does not have.

What does SharePoint do well?

SharePoint is Microsoft's internal collaboration and document management platform. It is built for authenticated internal users: staff, contractors, and partners who log in with organisational credentials. Its strengths are document storage and version control, intranet pages and internal communications, team sites and project collaboration spaces, and tight integration with the rest of Microsoft 365.

• Document libraries with version history and approval workflows
• Intranet pages for team communications, policies, and news
• Permission management at the site, library, folder, and file level
• Integration with Teams, OneDrive, Power Platform, and Microsoft Copilot
• Lists for tracking structured internal data without a custom database

What does a dedicated CMS do well?

A dedicated CMS is built for public-facing digital experiences. It is designed for content that anonymous external visitors will see, read, and interact with. Its strengths are flexible page templates and design control, SEO optimisation including metadata, structured data, and URL management, high-performance delivery to external audiences, content publishing workflows for marketing teams, and integrations with marketing technology including analytics, forms, and personalisation.

• Design-led page building with no authentication requirements for visitors
• SEO tools: meta titles, descriptions, canonical URLs, structured data, sitemaps
• High-performance delivery optimised for external web traffic
• Marketing-oriented workflows: staging, approval, scheduled publish
• Multisite and multilingual management for complex web estates

Why does running a public website on SharePoint cause problems?

SharePoint can publish pages to external audiences with some configuration. But it was not designed for that use case, and the limitations become visible quickly. Design flexibility is constrained by SharePoint's web part and template system. SEO control is limited compared to a dedicated CMS. Page performance for external visitors is not optimised in the same way. Content publishing workflows for marketing teams are more complex to configure than in a dedicated CMS.

Organisations that have tried to run their public website on SharePoint often end up with sites that are difficult for marketing teams to manage, hard to customise visually, and underperforming in search rankings.

Should you use both?

For most Australian organisations with both an internal collaboration requirement and a public web presence, the right answer is to use both platforms for what they are each designed for.

SharePoint handles the intranet, document libraries, and internal team collaboration. A dedicated CMS handles the public website, campaign landing pages, and external-facing content. The two platforms serve different audiences with different requirements. Keeping them separate keeps each one fit for its purpose.

How does this play out in practice?

The pattern we see most is use both. A public website runs on a CMS, and the intranet and document management run on SharePoint. SharePoint is built for staff and shared content. A CMS is built for the public and for publishing.

When should you choose SharePoint over a CMS?

If your organisation has no public web presence and your digital requirement is purely internal, SharePoint may be all you need. Government agencies, internal portals, and organisations that communicate exclusively with authenticated members are examples. In these cases, a dedicated CMS adds unnecessary cost and complexity for no additional benefit.

About Dapth

Dapth is your Perth digital consultancy, building connected digital systems from websites and intranets to applications, software, ERP and AI tools. For more than 15 years we have helped WA businesses, government agencies and organisations unlock advantages like streamlined workflows, increased efficiency, cost savings, new revenue and more powerful marketing.

We start with your organisation, not the technology: your users, your operations and your objectives. Then we connect everything across four areas:

• Digital Consultancy: Digital strategy, service design and UI and UX design that map how your customers, people and systems should work together, before anything is built.
• Customer Experience: Websites and digital experience platforms on Xperience by Kentico (Kentico Gold Partner), Sitefinity, Umbraco and Payload CMS, plus ecommerce.
• Employee Experience: Intranets and employee portals on Microsoft SharePoint, and workflow automation that takes the double handling out of everyday work.
• Operational Systems: ERP with Odoo as our primary platform (we are an Odoo partner), plus custom software, apps and the integrations that connect them.