How to create content properties report in Confluence
Build a Confluence content properties report by putting a key/value table inside Content properties on each source page, then reporting on their shared label.
This is the native Cloud workflow formerly called Page properties report. For example, collect Owner, Review date and Decision from release reviews without manually maintaining a second summary table.
Step-by-step guide
Standardize one source table
On each release-review page, insert Content properties and create a two-column table inside its body. Put Owner, Review date and Decision in the left column and their values in the right. Use identical key spelling so the report produces consistent columns.
Label the source pages
Give every source page the same label, such as release-review. If each page contains several properties blocks, assign the relevant block an ID such as launch-summary. The label finds pages; the optional ID selects which block to report.
Insert and scope the report
On the overview page, type /contentpropertiesreport. Enter release-review in Labels and, if used, launch-summary as the properties ID under Options. Add a space or ancestor filter when the label is shared beyond the intended branch.
Check the report against two examples
Publish the overview and compare two rows with their original pages. An empty row or missing column should trigger a check of labels, table placement, matching keys and optional ID. Change one source value and verify that the overview reflects the source.
Common mistakes
Building an ordinary table outside the macro
The report extracts structured content properties, not arbitrary tables that happen to use the same headings.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.