You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will support all major meta tags both on the index and static 404. Ideally, they will share the same meta.
We also need to support complex HTML inside noscript tags. We'll do it this way (if it's good for SEO, not 100% sure about that yet):
Have a crawlers.html at the root which will have its body extracted into the <noscript> of the index
Maybe we should also implement static meta tags such that static html would be generated based on some sort of meta tag object exported by the JSX of the page. Maybe also implement a static html exported object as well (or at least an object for <noscript> tags)?
To worry about later: Basically, plan is to have some exported content from pages that goes into noscript tags. each page has a corresponding index.html without prerendering, itll just link back to the react app and users can load the app. should work with RR. not sure though. the prerendered bit is the noscript tag and custom meta tags for noscript users and bots which dont support spas. since we're code splitting the JS should have enough time to load up for bots.
The text was updated successfully, but these errors were encountered:
We will support all major meta tags both on the index and static 404. Ideally, they will share the same meta.
We also need to support complex HTML inside noscript tags. We'll do it this way (if it's good for SEO, not 100% sure about that yet):
crawlers.html
at the root which will have its body extracted into the<noscript>
of the indexMaybe we should also implement static meta tags such that static html would be generated based on some sort of meta tag object exported by the JSX of the page. Maybe also implement a static html exported object as well (or at least an object for
<noscript>
tags)?To worry about later: Basically, plan is to have some exported content from pages that goes into noscript tags. each page has a corresponding index.html without prerendering, itll just link back to the react app and users can load the app. should work with RR. not sure though. the prerendered bit is the noscript tag and custom meta tags for noscript users and bots which dont support spas. since we're code splitting the JS should have enough time to load up for bots.
The text was updated successfully, but these errors were encountered: