Skip to main content

Pages with Profile Page Structured Data Warnings

Priority: None

Impact: Neutral

What issues it may cause

Review the warnings listed for each page and consider adding the recommended properties. Including sameAs links to verified social profiles, interactionStatistic data, and a clear description can strengthen the entity signals in your markup. Warnings reflect optional optimisations rather than implementation errors, so prioritise these alongside other SEO work.

How do you fix it

Addressing Profile Page warnings by adding recommended properties gives Google a more complete picture of your creators and brand entities. Stronger entity signals can improve accuracy of knowledge panels, author attribution, and how your content is understood across Google Search.

What is the positive impact

Pages with Profile Page warnings are still readable by Google, but may provide a less complete picture of the creator or organisation behind the content. Missing recommended properties such as social profile links or follower counts can reduce the strength of entity signals Google uses to represent your authors or brand.

How to fetch the data for this report template

You will need to run a crawl for report template to generate report. When report has been generated and you have crawl id you can fetch data for the report using the following query:

Operation: query GetReportStatForCrawl( $crawlId: ObjectID! $reportTemplateCode: String! $after: String ) { getReportStat( input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode} ) { crawlStructuredDataBlocks(after: $after, reportType: Basic) { nodes { url schemaType issuesSummary blockCount errorCount warningCount validationResult issues } totalCount pageInfo { endCursor hasNextPage } } } }Variables: {"crawlId":"TjAwNUNyYXdsNDAwMA","reportTemplateCode":"pages_with_profile_page_schema_warnings"}
GetReportStatForCrawlTry in Explorer
GraphQL
query GetReportStatForCrawl(
$crawlId: ObjectID!
$reportTemplateCode: String!
$after: String
) {
getReportStat(
input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode}
) {
crawlStructuredDataBlocks(after: $after, reportType: Basic) {
nodes {
url
schemaType
issuesSummary
blockCount
errorCount
warningCount
validationResult
issues
}
totalCount
pageInfo {
endCursor
hasNextPage
}
}
}
}