# Mobile Alternates in Sitemaps URLs which were found within the mobile/AMP rel alt tag of another page, which were found in a sitemap during the crawl. **Priority**: Low **Impact**: Negative ## What issues it may cause [Google recommends only including either desktop or mobile pages](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap) as entries in Sitemaps and generally only the desktop versions are included. If separate mobile pages are not found via a mobile alternate link, they might be considered duplicate pages until the relationship has been understood which may take some time. ## How do you fix it Separate mobile should be included as a link attribute under the desktop URL entry instead of a separate entry. ## What is the positive impact Mobile pages can be identified as an alternate of a desktop page more effectively. ## 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: ```graphql query GetReportStatForCrawl( $crawlId: ObjectID! $reportTemplateCode: String! $after: String ) { getReportStat( input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode} ) { crawlUrls(after: $after, reportType: Basic) { nodes { pageTitle url desktopUrl foundAtSitemap deeprank level sitemapsInCount httpStatusCode separateMobile mobileReciprocate amphtml amphtmlReciprocate noindex foundInGoogleAnalytics foundInGoogleSearchConsole foundInBacklinks foundInList foundInLogSummary foundInWebCrawl foundInSitemap } totalCount pageInfo { endCursor hasNextPage } } } } ``` **Variables:** ```json {"crawlId":"TjAwNUNyYXdsNDAwMA","reportTemplateCode":"mobile_alternates_in_sitemaps"} ```