You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 5, 2021. It is now read-only.
Hello again. :) Just found another side-effect. Redirects created in config.rb like:
redirect 'tags/peperoni.html', to: 'tags/pepperoni.html'
do get included in sitemap (which is probably fine?), but the Middleman includes a "noindex, follow" metatag in generated HTML code:
<meta name="robots" content="noindex,follow" />
which is being considered as an error by Google Search. Anybody has an opinion on which is better: disable redirects being added to sitemap, or changing the Middleman template HTML-code for redirects? Or create a new config option in middleman-search_engine_sitemap?
The text was updated successfully, but these errors were encountered:
The reason is that dynamically generated redirects have no source_file attributes (proxies do have source_file set to proxy template source file). If you guys think this is enough, then we can close this issue. But maybe it would helpful to think, what's right.
Hey, sorry @komor72. I'm not maintaining this any more. It's been a few years since I used it myself, and I've lost touch with what's happening inside the Middleman codebase.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello again. :) Just found another side-effect. Redirects created in
config.rb
like:do get included in sitemap (which is probably fine?), but the Middleman includes a "noindex, follow" metatag in generated HTML code:
which is being considered as an error by Google Search. Anybody has an opinion on which is better: disable redirects being added to sitemap, or changing the Middleman template HTML-code for redirects? Or create a new config option in middleman-search_engine_sitemap?
The text was updated successfully, but these errors were encountered: