Schema App's Entity Reports show which entities have been identified by Omni LER on URLs where the tag has been deployed. These reports provide data to support optimizing content strategy, ensuring comprehensive and effective coverage of entities, and improving overall content performance.
IMPORTANT:
- Only projects with active Omni LER tags will be able to run the reports
- Reports show data from the last 12 weeks by default
- URLs cannot currently be accessed from the Schema App menu
TABLE OF CONTENTS
Report List
The list of Entity Reports can be accessed by navigating to https://app.schemaapp.com/entity-hub/report-list
As new reports are requested and made available, they will appear in this list.
The reports currently available are:
Entities grouped by URL
The Entities grouped by URL report lists URLs where specific entities have been identified, providing insights into the richness and detail of the content.
This report contains the following columns:
- URL: A URL with at least one entity identified by Omni LER
- Number of Entities: The count of entities identified on that URL
- Entities: A comma-separated list of the names of the entities identified on that URL
This report provides an overview of the content depth on each individual URL.
Use Cases
The Entities grouped by URL report can be leveraged to answer questions like:
Content Richness and Depth:
- Which URLs have the highest number of identified entities, indicating richer content?
- Are there any URLs with a low number of identified entities that may need content enhancement?
Content Optimization:
- If URLs have a diverse range of entities, should the content be refined to target only the most important entities?
- Are there specific URLs that could benefit from the inclusion of more entities to improve SEO and relevance?
Audience Engagement:
- Which URLs with identified entities are performing best in terms of SEO (e.g. clicks, impressions, click-through rate. query volume)?
- Are there high-performing URLs that could serve as models for optimizing other content?
URLs grouped by Entity
The URLs Grouped by Entity report presents the breadth of coverage for specific entities across a page set.
This report contains the following columns:
- Entity Name: The name of each entity identified by Omni LER on at least one URL
- Entity Type: The type of the entity as defined in the Schema.org vocabulary
- Number of URLs: The count of URLs where the entity has been identified
- URLs: A comma-separated list of the URLs where the entity has been identified
- Same As: A comma-separated list of URIs for the entity in Wikipedia, Wikidata, and/or Google's Knowledge Graph
By reviewing this report, users can understand how widely each entity is covered across their content, helping to identify opportunities for content expansion and ensuring comprehensive coverage of key topics.
Use Cases
The URLs Grouped by Entity report can be leveraged to answer questions like:
Content Coverage:
- How widely is a specific entity covered across the website's content?
- Are there key entities that are consistently represented across multiple URLs?
Content Gaps:
- Are there important entities that are only mentioned on a few URLs, indicating a potential gap in coverage?
- Which entities are underrepresented, and where can additional content be created to improve coverage?
Content Strategy:
- How can the current coverage of entities inform future content creation and optimization strategies?
- Which entities should be prioritized for inclusion in new content to align with audience interests and search trends?
SEO Optimization:
- Are there high-value entities that need better coverage to enhance SEO performance?
- How can the distribution of entities across URLs be optimized to improve search engine rankings?
- Are there specific entities that contribute to the success of high-performing URLs?
Content Redundancy:
- Are there entities that are overly redundant across multiple URLs, possibly diluting content quality?
- How can content be refined to avoid unnecessary repetition of entities?
Additional Resources
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article