-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[docs] add SEO docs #3946
[docs] add SEO docs #3946
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me and I'm happy to close/resolve #1142 when it lands. Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a useful page to have, but we can make it waaaay more concise. I agree with @Conduitry's feedback — this isn't a place to put grandiose marketing claims
Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
Co-authored-by: Rich Harris <richard.a.harris@gmail.com>
I think we should probably leave #1142 open — we could probably do something to e.g. make prerendered pages available to a sitemap generator. It wouldn't be trivial, and it wouldn't cover all cases, but there's room for Kit to provide value |
This is appendixy content, it should probably go near the bottom (after typescript, perhaps?) |
We talk about SEO on the homepage, so should clarify the benefits SvelteKit offers
I think this is enough that we could consider whether we still want to leave #1142 open. It's not exactly clear to me what else we could provide beyond this documentation in terms of site maps