✨ feat(header): add support for canonical URLs #168
Merged
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.
Description
This PR enhances tabi's SEO capabilities by introducing a flexible system for setting canonical URLs.
The feature allows for setting canonical URLs at individual page or section levels, with a fallback to a dynamically generated global
base_canonical_url
, if specified.Resolves #151.
Changes
canonical_url
as an optional front matter attribute in both pages and sections under the[extra]
section.$base_url
in the current URL with thebase_canonical_url
specified inconfig.toml
.<link rel="canonical">
and<meta property="og:url">
based on the newly introduced logic.How to Test
canonical_url
to the[extra]
section of a page or section's front matter.base_canonical_url
inconfig.toml
.Additional Information
This feature is beneficial for those running multiple domains with the same content. By setting
base_canonical_url
dynamically, it will automatically adapt the canonical URLs based on the current URL's$base_url
. For example, for a page with URL$base_url/blog/post1
, and abase_canonical_url
set to "https://example.com", the generated canonical URL will be "https://example.com/blog/post1".