-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Trailing slash on schema @id despite trailingSlash: false #433
Comments
The node ids are just for a unique id of the node, the trailing slash in them will have no effect on the content of the nodes. The format for the IDs comes from Yoast SEO, see here https://developer.yoast.com/features/schema/functional-specification/ |
I noticed that google try to crawl url from id. When canonical has no trailing slash, google can spend crawl budget for url with trailing slash. |
This is not something that is documented or I've ever seen. Can you provide some more details? |
In Google Search Console for my site appear redirected page http://mysite.com/pathurl/ and this url is referenced by https://mysite.com/pathurl. But the only link that looks like this was in schema node id |
Unless you're seeing Google trying to access your URLs such as |
Environment
unhead 1.11.13
ufo 1.5.4
Node v20.15.0
Reproduction
Use parameter trailingSlash: false and function useSchemaOrg without custom node id.
Describe the bug
Function that create id for schema use withBase, that always add trailing slash, because it doesn't recognize fragments or query and join fragments using slash, so parameter trailingSlash doesn't work properly.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: