Add inline CTA images to next 50 blog posts by traffic - #5607
Merged
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
JoycePlaysFootball
approved these changes
Aug 15, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Description
Adds the ::cta-image inline shortcode to the next 50 highest-traffic blog posts (based on Search Console clicks) that didn’t already have one, continuing from the top 20 + 3 recent posts covered previously. Each post uses the CTA image most relevant to its content, with CTAs placed roughly 25–30% into the article body after a complete paragraph and outside code fences, lists, and other shortcodes.
src/blog/2024/06/dashboard-1-deprecated.mdwenco-book-demo.pngsrc/blog/2026/01/opcua-vs-mqtt.mdaperia-book-demo.pngsrc/blog/2025/12/node-red-buffer-parser-industrial-data.mdaperia-book-demo.pngsrc/blog/2023/07/how-to-deploy-a-basic-opc-ua-server-in-node-red.mdaperia-book-demo.pngsrc/blog/2025/02/node-red-academy-announcement.mdbook-a-demo.pngsrc/blog/2026/04/modbus-polling-best-practices.mdaperia-book-demo.pngsrc/blog/2024/12/publishing-modbus-data-to-uns.mdarch-systems-book-demo.pngsrc/blog/2025/09/poka-yoke-mistake-proofing.mdarch-systems-book-demo.pngsrc/blog/2023/07/how-to-build-a-opc-client-dashboard-in-node-red.mdwenco-book-demo.pngsrc/blog/2026/04/diagnosing-modbus-degradation.mdaperia-book-demo.pngsrc/blog/2025/12/read-s7-optimized-datablocks-flowfuse.mdaperia-book-demo.pngsrc/blog/2026/02/modbus-tcp-vs-modbus-rtu.mdaperia-book-demo.pngsrc/blog/2024/05/exploring-node-red-dashboard-2-widgets.mdwenco-book-demo.pngsrc/blog/2024/08/customise-theming-in-your-dashboards.mdwenco-book-demo.pngsrc/blog/2025/06/what-is-mes.mdarch-systems-book-demo.pngsrc/blog/2024/08/comparing-dashboard-2-with-uibuilder.mdwenco-book-demo.pngsrc/blog/2025/12/kafka-vs-mqtt.mdpower-workplace-book-demo.pngsrc/blog/2025/10/plc-to-mqtt-using-flowfuse.mdaperia-book-demo.pngsrc/blog/2024/09/how-to-scrape-web-data-with-node-red.mdbook-a-demo.pngsrc/blog/2024/04/displaying-logged-in-users-on-dashboard.mdwenco-book-demo.pngsrc/blog/2025/05/how-to-generate-pdf-reports-using-node-red.mdbook-a-demo.pngsrc/blog/2023/06/import-modules.mdbook-a-demo.pngsrc/blog/2025/09/what-is-takt-time.mdarch-systems-book-demo.pngsrc/blog/2025/05/designing-flexible-cron-schedules-in-flowfuse-with-node-red.mdbook-a-demo.pngsrc/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.mdaperia-book-demo.pngsrc/blog/2024/09/how-to-use-subflow-in-node-red.mdbook-a-demo.pngsrc/blog/2025/10/node-red-vs-flowfuse.mdbook-a-demo.pngsrc/blog/2025/02/interacting-with-arduino-using-node-red.mdbook-a-demo.pngsrc/blog/2025/10/building-mcp-server-using-flowfuse.mdbook-a-demo.pngsrc/blog/2024/05/mapping-location-on-dashboard-2.mdwenco-book-demo.pngsrc/blog/2024/08/opc-ua-to-mqtt-with-node-red.mdaperia-book-demo.pngsrc/blog/2023/03/comparing-node-red-dashboards.mdwenco-book-demo.pngsrc/blog/2025/12/what-is-teep.mdarch-systems-book-demo.pngsrc/blog/2025/12/node-red-timer.mdbook-a-demo.pngsrc/blog/2026/03/why-opcua-is-not-replacing-modbus-yet.mdaperia-book-demo.pngsrc/blog/2025/11/building-hmi-for-equipment-control.mdwenco-book-demo.pngsrc/blog/2026/06/node-red-5-on-flowfuse.mdbook-a-demo.pngsrc/blog/2024/03/dashboard-getting-started.mdwenco-book-demo.pngsrc/blog/2024/01/dashboard-2-multi-user.mdwenco-book-demo.pngsrc/blog/2024/12/flowfuse-release-2-12.mdbook-a-demo.pngsrc/blog/2026/01/why-modbus-still-exist.mdaperia-book-demo.pngsrc/blog/2023/01/environment-variables-in-node-red.mdbook-a-demo.pngsrc/blog/2024/03/using-kafka-with-node-red.mdpower-workplace-book-demo.pngsrc/blog/2023/08/flowforge-is-now-flowfuse.mdbook-a-demo.pngsrc/blog/2025/10/using-ethernet-ip-with-flowfuse.mdaperia-book-demo.pngsrc/blog/2023/07/influxdb-historical-data.mdpower-workplace-book-demo.pngsrc/blog/2024/02/connect-node-red-to-kepware-opc.mdaperia-book-demo.pngsrc/blog/2023/12/device-agent-as-a-windows-service.mdpower-workplace-book-demo.pngsrc/blog/2023/03/3-quick-node-red-tips-4.mdbook-a-demo.pngsrc/blog/2024/08/opentelemetry-with-node-red.mdpower-workplace-book-demo.pngRelated Issue(s)
Checklist