Improve canonical path for vision in Google#748
Merged
ivan-nginx merged 3 commits intomasterfrom Mar 28, 2019
Merged
Conversation
From now all links will be not only without 'index.html', but without `.html` too.
stevenjoezhang
approved these changes
Mar 28, 2019
Member
|
For links contain html like https://1v9.im/post/theme-next-added-today's-poetry.html My conf: permalink: post/:uniq.html
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
title: {{ title }}
date: {{ date }}
tags: []
uniq:
categories:
comments: true
quicklink: false
--- |
Member
Author
I just updated readme, reread it. |
stevenjoezhang
suggested changes
Mar 28, 2019
ivan-nginx
added a commit
to theme-next/theme-next.org
that referenced
this pull request
Mar 28, 2019
stevenjoezhang
approved these changes
Mar 28, 2019
Contributor
stevenjoezhang
left a comment
stevenjoezhang
left a comment
There was a problem hiding this comment.
Oh, yes, netlify did the redirect on the server side... It's OK to do so
ivan-nginx
added a commit
to theme-next/theme-next.org
that referenced
this pull request
Mar 28, 2019
Closed
liolok
changed the title
11 tasks
tongluyang
pushed a commit
to tongluyang/hexo-theme-next
that referenced
this pull request
Nov 19, 2019
* Improved canonical path for vision in Google. From now all links will be not only without 'index.html', but without `.html` too. * Changed links in tag plugins. * Changed links in config.
whyliam
pushed a commit
to whyliam/hexo-theme-next
that referenced
this pull request
Apr 19, 2025
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Pages must placed in subdirectories with
index.htmlnames, e.g.source/docs/troubleshooting/index.mdfor pretty path withcanonicaloption enabled:But if we want to use pages in root directories and named as is with
*.htmlsuffix,source/docs/advanced-settings.md, canonical path will contain*.htmlsuffix:What is the new behavior?
From now all links will be not only without
index.html, but without.htmltoo for pretty path withcanonicaloption enabled. And not need to setpermalinkin each page for that.Pages now can placed in root directories and named as is with
*.htmlsuffix, e.g.source/docs/advanced-settings.md:(with theme-next/theme-next.org@de8fffc and theme-next/theme-next.org@ac9141c changes)
How to use?
In local servers
*.htmlsuffix will be exists. For remove they in Production, need to create redirects (for Nginx) or use advanced settings in deployment services (like «Pretty URLs» in Netlify):Does this PR introduce a breaking change?