- Issue created by @lucky723
- 🇩🇪Germany gbyte Berlin
We can't get your frontage's last modification date if it's not the core entity (implementing the 'changed' property) that is changing. If we tried, we would have to create a lot of exceptions for a lot of cases.
You could hook into the module to update lastmod upon generation, or implement a URL generator for your Frontpage. Or update the embedding entity's changed value upon saving the blocks.
Or you could do nothing seeing that this parameters are seemingly being ignored by google anyway...
Sorry I don't get it.
I think the home page is expected to have a last modification date in sitemap.xml file. Am I right with this ?
If so, how can I do it with standard Drupal and/or module settings ? (I mean not changing the code)The blocks embedded in the home page are setup to be indexed in sitemap. What else should I do ?
Thanks in advance for you help and advises.- 🇩🇪Germany gbyte Berlin
Sorry I don't get it.
Then don't change this issue's Metadata if I explicitly set it please.
If so, how can I do it with standard Drupal and/or module settings ? (I mean not changing the code)
The less technical answer is you can't. Easiest way is to make sure your home page is a node and that you save it after changing the blocks.
Easiest would be no to bother as the lastmod value has little effect anyway.
For other engines there is Index Now that this module also supports (see submodule) but Google doesn't support it...
Sorry for Metadata, I only added a comment, don't know why it changed back the category ans status, seems like it keeps the ones of original request. This time I ensure it remains as you set it up ;)
Well, my home page is the one by default /node
I assume I should use a content instead. I'll explore this way.Thanks a lot for your answers.
Automatically closed - issue fixed for 2 weeks with no activity.