[MGNLGS-18] Mobile sitemap support Created: 30/Sep/13  Updated: 02/Jan/14  Resolved: 29/Oct/13

Status: Closed
Project: Google Sitemap (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.3

Type: New Feature Priority: Major
Reporter: Ming Chen Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLGS-32 Mobile sitemap support for version 2.0 Closed
causality
is causing MGNLGS-71 Review the new mobile support Closed
dependency
depends upon MGNLGS-19 Cannot open Properties due to JavaScr... Closed
relation
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Support
Sprint: 4.5.13

 Description   

Currently there is no way to specify the url for mobile in the plugin. We need to implement a way that we can generate mobile specific site maps. As per Google, this requires adding a new child tag <mobile:mobile/> in the <url> tag as explained in the following url:

https://support.google.com/webmasters/answer/34648?hl=en



 Comments   
Comment by Christoph Meier [ 22/Oct/13 ]

GoogleSiteMap-Template doesn't allow to edit pageproperties.
At first i thought this is a bug; later on it was told that this is "normal" (or was always like that). It would behelpfull if it works, e.g. to hide the sitemap from the nav.

Comment by Christoph Meier [ 25/Oct/13 ]

After some research it came to the decision, that it makes sense to have 2 Sitemaps (if mobile is required, too):

  • one with infos for desktop-optimzed pages (can contains infos for images and vids, too)
  • one for for mobile-pages (can contains infos for images and vids, too)
    because:
    „ A Mobile Sitemap can contain only URLs that serve mobile web content. Any URLs that serve only non-mobile web content will be ignored by the Google crawling mechanisms. If you have non-mobile content, create a separate Sitemap for those URLs. "
    (see https://support.google.com/webmasters/answer/34648?hl=en)

So: We need some kind of "switch" in the Edit-UI of a GoogleSitemap-page to let it render output for desktop-browser- or mobile-pages
=> e.g. sitemap-type

{ „desktopp-browser“ , „mobile-browser" }

it would nake sense to have that "switch" on the PageProps. (which are NOT working)
otherwise it cpuld be another meta-data-content-node

See https://support.google.com/webmasters/answer/183668# for xml-Details.

As mentioned above and written in the concept page (http://wiki.magnolia-cms.com/display/DEV/Concept+Google+SiteMap), too. It would be nice to allow to add urls for images and videos, too.

Comment by Christoph Meier [ 29/Oct/13 ]

I have a version now which works; commited onto branch magnolia-module-google-sitemap-1.2.x-MGNLGS-18.
Added a properties-dialog to choose "standard" or "mobile" sitemap. "standard" is default.
Changed the xml-rendering-template; it should also work, if the sitemapType is not set on older pages. (some ftl-"guru" should check that, please).
After revision i may push that to magnolia-module-google-sitemap-1.2.x, but not yet to master (since google-sitemap currently is changed for migration-stuff, too).
The reviewer or modulew-owner (Eric) should decide, whether i should open a new ticket for this task for the master-branch.

Comment by Christoph Meier [ 29/Oct/13 ]

Labels are still hardcoded (was not able to use i18n, yet). Since the module has no other translation yet, this should not be a problem.
I set the ticket to resolved, since that version could be sufficient for the moment for the customer who asked for at support.

Generated at Mon Feb 12 02:05:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.