Skip to main content

Site Pages Library

Common Use Cases

  • Homepage storage: holds the default homepage created when a new site is provisioned
  • Intranet content management: stores informational, departmental, and landing pages
  • News publishing: news posts are stored here since news posts are also pages
  • Page templates: stores reusable page templates for consistent page creation
  • Multilingual content: manages language-specific page variations in dedicated folders
  • Page lifecycle management: review, update, archive, or delete pages as content evolves

Benefits

  • Automatic creation: every SharePoint site includes a Site Pages library by default
  • Single source for pages: pages, news posts, templates, and translations live in one place
  • Version history support: track page changes and restore previous versions when needed
  • Metadata and views: use columns, sorting, and views to organize pages
  • Permission inheritance: pages follow site-level permissions by default
  • Modern publishing support: fully supports modern pages, news, and multilingual publishing

Key Considerations

  • Pages are files: each page (including news posts) is stored as a file in the Site Pages library
  • Homepage lives here: the site’s homepage is just another page in this library
  • Templates folder exists: page templates are stored in a dedicated folder within the library
  • Multilingual folders created automatically: language-specific folders are created when multilingual features are enabled
  • Member permissions apply: anyone in the Site Members group can add, edit, or delete pages by default
  • Deletion impact: dleting a page from this library removes it from navigation and links