Meet Pages: My Command Center for Content Performance

Dark-mode Pages dashboard for relay.com listing URLs, tags, citation share, AI citations, and AI indexing metrics with gains and losses.
Pages in Profound content performance command center

I’m introducing Pages in Profound—my single command center for monitoring content citations, tracking bot activity, and understanding page health.

Dark Profound content analysis dashboard reviewing a Relay vs Ledgerly startup ERP article, with a 65% overall score and quality metrics.
Profound’s content command center puts page analysis beside the article itself, surfacing a 65% score and signals for freshness, structure, readability, and information density.
Dark Profound dashboard comparing bot and human-readable content, showing 25% bot readability and an Unhealthy status.
A side-by-side content audit reveals a stark visibility gap: bots can read just 25% of the page, while the JavaScript-rendered human view exposes far more content.

Inspired by this post on Try Profound Blog.


crushpress.ai community screenshot

FAQs

What is Pages in Profound?

Pages in Profound is a single command center for monitoring content citations, tracking bot activity, and understanding page health. It brings those signals together in a page-level view.

Which content performance metrics appear in the Pages dashboard?

The dashboard shows page-level citation share, AI citations, AI indexing, and trend gains or losses. It also surfaces signals for freshness, structure, readability, and information density.

How does Pages assess content quality?

Pages places its analysis beside the article and presents an overall score with supporting quality signals. The example shown has a 65% score and evaluates freshness, structure, readability, and information density.

Can Pages compare what bots and people can read?

Yes. The illustrated side-by-side audit compares bot-readable content with the JavaScript-rendered human view, exposing visibility gaps between them.

What can Pages reveal about JavaScript-rendered content?

A side-by-side audit can reveal when bots see far less than human visitors because the human view relies on JavaScript-rendered content. In the example, bots can read just 25% and the page is labeled Unhealthy.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *