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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR generates individual integration pages for each integration listed under /integrations. The integration page data is fetched from the npm registry, and it currently generates pages for all FlowFuse-certified nodes as well as the top 50 most downloaded nodes.
Both certified and non-certified node pages display the node’s README along with key details such as author, last updated date, published date, npm link, maintainers, and GitHub stats.
Certified node pages display a FlowFuse Certified mark at the top, along with a banner highlighting the node’s certification status and a link to learn more about certified nodes.
Non-certified node pages also include a banner, but with messaging that encourages node authors to apply for certification, including a link to the certification application form.
Screen.Recording.2026-01-14.at.2.35.41.PM.mov
SEO & Traffic Rationale
The primary goal of generating these pages is to increase organic traffic to the FlowFuse website. Today, when users search for documentation on specific Node-RED nodes, they typically land on the Node-RED node README pages. According to Node-RED search analytics, these pages receive a significant number of clicks daily.
There was an initial concern around duplicate content and the risk of Google penalizing these integration pages. However, this should not be an issue because:
We add certification badges and banners, which provide trust and authority that Google values.
We include additional links and contextual information
These elements meaningfully differentiate our pages from the original Node-RED documentation.
Expected Impact
With this strategy, when users search for any popular node, our integration pages are likely to rank highly in search results, potentially in the second position.
Based on existing data:
Highly downloaded nodes receive ~100 clicks/day on the Node-RED website
Capturing just 10–15 clicks per node would result in approximately:
~500 additional clicks per day
(50 nodes × 10 clicks per node)
Note on Implementation & Design
Note: Claude was used during parts of this PR for content and implementation assistance. The current design is intentionally basic and not final. The structure is in place, and we can iterate and improve the UI/UX in follow-up PRs based on feedback and performance data.
1 paths audited Performance: 63 (🟢 up 1 from production) Accessibility: 80 (no change from production) Best Practices: 100 (🟢 up 8 from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports
1 paths audited Performance: 83 (🟢 up 21 from production) Accessibility: 80 (no change from production) Best Practices: 100 (🟢 up 8 from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports
@sumitshinde-84 as discussed on the call, here are the suggestions we aligned on:
Remove the sticky behavior from the right panel. When the content is long, it prevents users from seeing the end of the panel without scrolling the entire page.
For the quick links section: those links take users away from our website, so they shouldn’t be styled as buttons. It would be better to de-emphasize them and move them lower on the page.
Button styling: our buttons generally use all caps and no underlining. Please make sure the buttons on these pages are consistent with the rest of the site.
We include additional links and contextual information
Can you expand what value you add here?
On our integrations page, we display GitHub stats for each node, including stars, open issues, and forks. The page also provides links to install the node via the Palette Manager or npm. Additionally, it now features a tab layout with two tabs, Overview and Examples. The Overview tab displays the node’s README, while the Examples tab renders example flows provided by the author. For more information, watch the following video.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sumitshinde-84
requested review from
MichaelBDavis and
knolleary
as code owners
Description
This PR generates individual integration pages for each integration listed under
/integrations. The integration page data is fetched from the npm registry, and it currently generates pages for all FlowFuse-certified nodes as well as the top 50 most downloaded nodes.Both certified and non-certified node pages display the node’s README along with key details such as author, last updated date, published date, npm link, maintainers, and GitHub stats.
Screen.Recording.2026-01-14.at.2.35.41.PM.mov
SEO & Traffic Rationale
The primary goal of generating these pages is to increase organic traffic to the FlowFuse website. Today, when users search for documentation on specific Node-RED nodes, they typically land on the Node-RED node README pages. According to Node-RED search analytics, these pages receive a significant number of clicks daily.
There was an initial concern around duplicate content and the risk of Google penalizing these integration pages. However, this should not be an issue because:
These elements meaningfully differentiate our pages from the original Node-RED documentation.
Expected Impact
With this strategy, when users search for any popular node, our integration pages are likely to rank highly in search results, potentially in the second position.
Based on existing data:
~500 additional clicks per day
(50 nodes × 10 clicks per node)
Note on Implementation & Design
Related Issue(s)
Checklist