It'd be great if the process could add the canonical URLs to the dev.to posts automatically.
This would allow org devs to post on dev.to and then generate a standalone site which appears to have the orig content, with the dev posts pointing to it. Is that currently possible (without adding the canonical urls manually)?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Absolutely! But did he have a canonical URL front matter in his dev.to blog post?
I'm going to experiment a bit.
No, but it means that the original content is assumed to be from dev.to and not from anywhere else.
Whereas when Google will crawl the Netlify website, it will likely treat the content as duplicate from the dev.to blog
We’re working on better support for canonical URLs. It’s a matter of settling on how the configuration will work on the DEV side.
It’s been discussed, but we pushed it until post-release because we wanted some broader usability feedback.
Thank you for this answer!
It'd be great if the process could add the canonical URLs to the dev.to posts automatically.
This would allow org devs to post on dev.to and then generate a standalone site which appears to have the orig content, with the dev posts pointing to it. Is that currently possible (without adding the canonical urls manually)?