saurabhd / hk_realestate

GNU General Public License v2.0
1 stars 0 forks source link

xmlsitemap change frequency not changeable #85

Open heliogabal opened 7 years ago

heliogabal commented 7 years ago

I'm not sure if this could cause a problem, but it seems the change frequency in the sitemap.xml is set quite randomly and is often 1 year or 1 month.

I searched for a way to change that, and as so often with Drupal the fix has been worked on in the issue queue since 2012... and is not yet fully functional: https://www.drupal.org/node/1811692

Not sure if there is a simpler way to change the frequency of all pages to weekly, and what the consequences of the change frequency actually are, but I fear this might lead to lots of pages in the Google index becoming stale (404 or 403).

Could you please verify this is actually a problem, and if so, look into either setting the change frequency default to weekly, or try to apply the patch (but I would rather avoid that)?

darshi-shah commented 7 years ago

Hi Rainer,

Changing frequency is basically informing google about how often the content is being modified. If we do not modify content after adding it, frequency do not matter much. New URLs will be added in sitemap. Changing frequency to weekly would indicate that content is being modified on weekly basis. More details here: https://www.sitemaps.org/protocol.html

Let me know if this is the case with HK content. In this case, we should set frequency to weekly.

Thanks

heliogabal commented 7 years ago

ok, thanks for looking that up. So as I thought, this is rather considered a hint, and won't mean the yearly pages are only crawled once a year. That's already comforting.

Nonetheless, we should make sure that the frequency is rather weekly, as at least objects and apartments do change frequently, and disappear if they are taken from the market. The static pages could be set to monthly, as they rarely change (apart from hopefully being redesigned soon...).

So could you check on dev if the mentioned patch #56 from the issue queue is working without problems, so we could have control over that (Or if you find a quicker way to set the default to weekly, rather do that. We don't really need page-by-page manual control over that). If that is confirmed, you could also set the issue to RTBC, as 4 people before already said it's working.

darshi-shah commented 7 years ago

Hi Rainer,

The patch worked fine in local. We need to run update once pull is done. I set weekly frequency for object and apartments. Upon rebuilding links, changes are shown on sitemap.

Please take pull and let me know.

Thanks

heliogabal commented 7 years ago

ok, once it is pushed to live, can you also change the priority of the object nodes to 0.7 or 0.8, so these are prioritized over the static pages?

Thanks.