Build and Verify a Confluence Page Properties Report Across a Space

The Problem: Metadata Trapped in Individual Pages

When a Confluence space grows past a dozen pages, tracking status, ownership, or review dates by opening each page becomes unmanageable. A Page Properties Report solves this by pulling metadata from every page that uses the Page Properties macro into a single table. This guide walks through creating that report, verifying it reflects live data, and recovering from the most common configuration failures.

What You Will Build

You will create a standalone report page that lists selected property keys—such as Status or Owner—from all pages in a target space. The report updates automatically when editors change values inside the Page Properties macro on any source page. The end result is an auditable snapshot that does not require custom plugins or external scripts.

Prerequisites and Permissions

• Space permissions: You need permission to create pages in the space where the report will live. The report respects read access; if a user cannot view a source page, that row will not appear for them.
• Source pages: At least two or three pages in the space must already contain a Page Properties macro. The report aggregates data only from pages that use this macro.
• Consistent keys: Every Page Properties macro must use identical property key names. Keys are case-sensitive, so status and Status are treated as different columns.

Step-by-Step: Creating the Report

1. Create a new page in the target space. A title such as Space Overview makes the purpose clear to other editors.
2. While editing the page, insert the Page Properties Report macro. Do not confuse it with the single-page Page Properties macro; the Report variant is the aggregator.
3. In the macro configuration, select the space you want to scan. The report will look only within that space boundary.
4. Add the property keys you want as columns. Use the exact key names defined in your source Page Properties macros. If you want a friendlier column heading, many Confluence versions let you override the display label separately from the raw key.
5. Save the page. The macro renders a table with one row per qualifying page.

Verifying the Report Works

Open the report page and confirm the table shows each intended column and one row per source page. If the table is empty or rows are missing, the most likely causes are covered in the recovery section below.

To confirm the report is live rather than cached, edit a value inside the Page Properties macro on one source page—for example, change Status from Draft to In Review—then refresh the report page. The updated value should appear without reconfiguring the macro.

For a deeper structural check, use the Confluence REST API to inspect the report page's storage format. From a terminal with curl and credentials that have read access to the page, run:

curl -u <username>:<api-token> \
  "https://<base-url>/rest/api/content/<report-page-id>?expand=body.storage"

In the returned storage XHTML, look for the Page Properties Report macro element and confirm that the space parameter and property key parameters match your intended configuration. If the macro parameters are absent or malformed, the report will not populate correctly.

Recovery Options When the Report Fails

Empty table: Verify the macro is targeting the correct space key. Also confirm that the source pages actually contain a saved Page Properties macro; plain text or tables that look like properties are ignored. If the macro configuration appears corrupted, delete the macro from the report page and insert a fresh instance.

Blank columns: This almost always means a property key mismatch. Because keys are case-sensitive, re-enter each key using the exact casing from the source macros. If you renamed a key on a source page after creating the report, update the report configuration to match.

Rendering errors or timeouts: Very large spaces can exceed macro rendering limits. If the page fails to load or the table is truncated, narrow the scope by adding a label filter to the macro or splitting the audit into multiple reports scoped to smaller page trees. Space administrators can also review Confluence logs for macro rendering exceptions if the failure is intermittent.

Missing rows for specific users: The report respects Confluence permissions. If a colleague cannot see a row, check whether they have read access to the underlying source page.

Limitations and Final Checks

The Page Properties Report is a live view, not a historical database. It cannot aggregate data from other spaces, and it will not retain values from pages that are deleted or moved out of the configured space. There is no built-in rollback for the report itself; if you misconfigure the macro, simply edit the page and adjust the parameters.

As a final practical check, view the report page as a standard space member rather than an admin. The table should display the same columns and rows that a typical auditor would see. If the values look correct and the live-edit test passed, the report is ready for use.