Howto replace pagination "refresh" with 301 redirect?

[Daniel_Muller]

When building a site, the summary shows “52 Aliases” created. This 52 aliases are all pagination (page 1) http-equiv=“refresh” type of aliases.

I am unable to disable them with “disableAliases”. I am unable to list them with .Site.Pages.Aliases

Is there another way to get a list of this type of aliases? For now, I am fetching them with the help of
“grep -r” in bash.

My goal is to identify them and add them to a 301 redirect list

Thanks,
Daniel

[maiki]

INFO Alias messages, but I'm not using Aliases

We create an alias for page 1 to enable “endless scrolling” via javascript.

I’m not sure if it picks up paginated aliases, but you can try to shortcode at:

Aliases listed in output, but not used in project

Yeah, I got that from the topic. What I’m suggesting is a way to directly see what they are, to help you debug. In case others find their aliases ponderous, here’s a shortcode for ya; copy to layouts/shortcodes/whatthealiases.html: {{ range $p := .Site.Pages -}} <pre> <code> {{ range .Aliases }} {{ . | printf "%-35s" }} {{ $p.RelPermalink -}} {{ end -}} </code> </pre> {{- end -}} That’s the code from https://gohugo.io/news/http2-server-push-in-hugo/, with some formatting for …

[Daniel_Muller]

I tried looping through .Site.Pages. Only Kinds of pages, taxonomy, taxonomyTerm and section are populated in .Site.Pages.

It seems that paginated lists aren’t pages per-say, and more specially aren’t really considered aliases (except during the build summary output).

Unless there is a .Site.AllPagers variables, I don’t think I can achieve what I want.

Using http-equiv=“refresh” isn’t that bad, I just prefer a 301 than a 200. Running a script before deploy isn’t an issue either, just an annoying extra step.

If someone has another idea, suggestions welcome

Thanks