-
Notifications
You must be signed in to change notification settings - Fork 684
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
[FEATURE] Added default Rendertron support #3058
Conversation
LogERROR ON TASK: eslintCheck
|
290339f
to
023d3a3
Compare
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.
Very nice; thanks for your contribution, Lewis. Seems very straightforward, so I'd love to try this out.
023d3a3
to
57d4f25
Compare
@jimbo did you had time to check this PR? |
@magento create issue from PR |
@lewisvoncken thank you for submitting a PR! It took us a while to review it internally as we recognize the value Rendition can add to the product, but at the same time we want to make sure the pre-rendering mechanism added to the product works across all deployment models (on-prem and cloud). We start investigating the options internally and welcome you to contribute. Let me know if you are interested |
Description
Many frontend frameworks rely on JavaScript to show content. This can mean Google might take some time to index your content or update the indexed content. One workaround option is to implement dynamic rendering. Dynamic rendering means switching between client-side rendered and pre-rendered content for specific user agents. This codelab will walk you through implementing dynamic rendering using Rendertron, which is an open source solution based on headless Chromium.
source: https://codelabs.developers.google.com/codelabs/dynamic-rendering#0
With 3 new environment variables you can easily setup Server Side Rendering with Rendertron.
Specify the Base URL of the Rendertron proxy service.
Regular expression to match user agent to proxy. Defaults to a set of bots that do not perform well with pages that require JavaScript.
Regular expression used to exclude request URL paths. Defaults to a set of typical static asset file extensions.
It is possible to self-host Rendertron or even refer to SeoSnap (https://seosnap.io/)
Acceptance
Verification Stakeholders
Specification
Verification Steps
closeBrowser
in the rendertron configuration to trueChecklist
Resolved issues: