Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for canonical URL #23

Closed
yonatankarp opened this issue Dec 4, 2022 · 1 comment · Fixed by #25
Closed

Add support for canonical URL #23

yonatankarp opened this issue Dec 4, 2022 · 1 comment · Fixed by #25

Comments

@yonatankarp
Copy link

yonatankarp commented Dec 4, 2022

Description

As we're handling cross-posting here there is an SEO penalty that we have to pay, to avoid one (or both) of the published articles should have the canonical URL from the main published site.

Describe the solution you'd like

There should be a new optional flag with the canonical URL, and an option to set it to either one of both of the blogging systems (e.g. in my case my main system is hashnode)

A better option would be to select the main account, so if in the future there are more blog systems you can automatically set the canonical URL to all non-main accounts

Describe alternatives you've considered

At this moment the only alternative is to run the action in draft mode and manually alter the outcome after each post-publication

Additional context

@protiumx
Copy link
Owner

protiumx commented Dec 6, 2022

Hi @yonatankarp,
I have introduced a new canonicalUrl config in https://github.com/protiumx/blogpub/releases/tag/v0.8.0.

A better option would be to select the main account, so if in the future there are more blog systems you can automatically set the canonical URL to all non-main accounts

It would be nice to support any forem based blog, but that would require a mayor change and I don't really have the time for it. Would love to see a PR for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants