Site Pages Explorer Coming soon
View, change layout, download, upload
Every modern page on one site in one list: its layout, whether it is published, a draft or checked out, whether it is news, its languages and who changed it last. Change the layout of many pages at once, publish them, promote them to news, check them in, make one the home page, or download them as page packages and upload them to another site. The same list is a Pages tab in List Explorer (on the Site Pages library) and Tenant Explorer (on a site's Site Pages).
What it does
- Which pages are published, which are drafts, and which are checked out and to whom.
- Which pages are news posts, and which page is the home page.
- Each page's layout, sections and number of web parts.
- Which pages have translations, and in which languages.
- Who changed each page last, and when.
How it runs
- Sign in. One tenant, asked when you click the tile. Any of the three credentials works here.
- Choose a site. The shared site picker, or paste a URL. Then Open.
- Choose pages. Tick the pages to change, or click one. Search and the filter chips narrow the list.
- Act. Change layout, Publish, Promote to news, Make home page, Check in or Move to recycle bin. Each page's result is listed under the grid.
- Move pages between sites. Download them as page packages (.smpage), then Upload them on the other site. Links and images are pointed at the new site, and the images come with the package.
How it works
Opening a site reads its Site Pages library once; a page's sections are read only when you click it. Every action works on the ticked pages, or on the page you are on when none is ticked, one page at a time. Each page gets its own result, done, skipped with the reason, or failed with SharePoint's words, and after a change the library is read again so the grid shows what is really there. Stop finishes the page in progress and lists the rest as not reached.
A layout change is written into the page's current version, so a published page stays published and no new draft appears, and Modified and Modified by are put back in the same write unless you untick that. Each page is read back: one still showing its old layout is a failure, and one whose Modified stamps did not hold is marked done with that warning. A page already on the chosen layout is skipped.
Publish skips pages checked out to someone else, and on a library that needs approval reports the page as sent for approval. Check in uses a minor version where the library keeps them, and checking in someone else's page asks first and keeps their saved changes. Promote to news uses SharePoint's own promotion rather than setting a flag on the page. Make home page takes one page that has been published and reads the site back to confirm it. Move to recycle bin always recycles, never deletes, and skips the home page.
A page package holds the page's content, its layout and, if you choose, the images it uses; an image that cannot be fetched is noted and the page still downloads. Upload checks each package against the site before writing: a name already taken is skipped, renamed or saved as a new version of that page, as you choose. Links, images and site references are pointed at the new site, and the images are put beside it but never over a file already there. The page is created as a modern page, published or checked in so it is never left checked out, and read back. Original authorship is applied only to a new page, not to a new version of an existing one.
What you need
- Edit permission on the Site Pages library for changes; Read for the list and downloads. Making a page the home page needs the site's Manage Web Site permission (site owner). No tenant-level role and no admin consent: everything runs on SharePoint's own APIs.
What it will not do
- One site at a time.
- Classic wiki and web part pages are listed but cannot change layout, become news or be packaged: they have no modern canvas.
- Single web part app page is only applied to pages with exactly one web part; others are skipped and listed, because the rest of their content would disappear from view.
- A page's .aspx file holds none of its content, so downloads are page packages or an Excel list, never the bare .aspx.
- Web parts that show a list or library from the original site need pointing at one on the new site after an upload. The upload check tells you which pages have them.