Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Documentation inclusion of rel=prev & rel=next into page head when using pagination.
See original GitHub issueFeature request to include documentation on having InstantSearch include rel="prev" and rel="next" into the <head> of the page when using the pagination module.
I read the documentation and found brief information on this, but there was no demo or documentation on how to actually achieve this.
Although Google have stated they don’t use this as a factor anymore, we have found their indexing gets confused on large sites. We’ve also heard from Google that they highly recommend keeping this as they do still use it, as do Bing.
Do you have any suggestions on how best to achieve this?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I see, I glanced over
metaInfo. Thanks a lot! for now this issue can be closed I think@Haroenv What do you mean by the rendering part? Vue-meta handles all the management of the <link rel=""> fields in the page <head>.
The
metaInfo()method is read by Vue-meta (as you probs know already) and handles the changes on the page, so I wouldn’t have thought render is needed.