Page view
Shows you what GOV.UK's own APIs know about a page that the page itself doesn't tell you.
Try an example
-
Who actually writes this page?
The Government Digital Service holds the pen, while HMCTS is named on the page. -
What pages are hiding inside this one?
One entry in search, four separate pages a user can land on. -
How old is this page really?
Last updated in 2014, with three different policy owners.
Estate view
Pick an organisation to see what it publishes, broken down by content type, before loading the full list of pages.
Try an example
-
What does HM Courts & Tribunals Service publish?
98.6% of what it publishes is tribunal decisions. Filtering by content type is what makes an estate readable.
Total items in the index
—
Projected rows for current selection
0
Tick content types below.
Content types
Show bar chart of items per content type
Results
Items by year of last update
court fee, tribunal.Map view
Map the content ecosystem around a service. Starting from a page you choose, it follows the links written into each GOV.UK page and draws them as a map, so you can see how the content connects and which shared pages it sends people to.
Use the page a user starts on, for example
/make-court-claim-for-money.Try an example
-
Map the Civil Money Claims service.
Traced from its start page, following links across GDS and HMCTS: the claim forms, the fee help, the enforcement steps.
About
A tool for looking at GOV.UK content through its own public APIs.
Three ways in:
- Page view inspects a single page: who owns it, how stale it is, what pages hide inside it, whether there's a Welsh version, and what it links out to.
- Estate view shows what a department publishes, broken down by content type and age, as a filterable table you can export.
- Map view traces a service from a starting page and draws its content as a map: how the pages link to each other through their text and their "Related content" links, the parts of guides and publications grouped together, and the shared pages they send people to. You can also show the external sites it signposts to, such as Citizens Advice.
Where the data comes from
Everything is fetched live, read-only, from two public GOV.UK APIs:
- Content API, to read each page in full: its ownership, dates, the pages inside it and its links (used by Page view and Map view).
- Search API, for the search index, used for the Estate view breakdown and title search.
What it does not cover
- It only reads GOV.UK pages. The map can show links out to other sites, including other government services, but it does not read those sites.
- No in-service content: the pages inside transactional services are not in these APIs.
- Attached files such as PDFs are not read.
- Only live, published content. Drafts and unpublished updates do not appear.
- Read-only. It never changes anything on GOV.UK.
Editorial owner vs policy owner
The least obvious thing the tool surfaces. The editorial owner (the page's primary_publishing_organisation) is who actually holds the pen and publishes the page. The policy owner (the associated organisations) is the department responsible for the policy it describes. They are often different: a mainstream guide may be editorially owned by the Government Digital Service while the policy belongs to HMCTS. The page itself only shows the policy owner, so the editorial owner is invisible unless you look here.
Feedback
Found a bug, or got an idea? Post it on the feedback board, where you can report problems, suggest features, and vote on what others have asked for.