How to Implement Server-Side Rendering (SSR) and Improve Indexing of Public Pages (sp_page) in Servi

[HIPortalP]

Hello, community!

I am working on a project in the ServiceNow Service Portal where Google indexing of public pages and page load performance are critical factors. One of the challenges we have encountered is the lack of native support for Server-Side Rendering (SSR), something that other technologies like React, Vue, and Next.js provide.

We know that the Service Portal dynamically renders content on the client side, but we would like to explore ways to improve the initial load time and facilitate the indexing of public pages created in the sp_page table.

Our Challenges:

1. SSR in Service Portal:

   • Is there any way to pre-render public pages (sp_page) so that content is delivered already processed to the browser, reducing load time?
   • We know it's possible to generate server-side HTML using Script Includes or GlideAjax, but is there a recommended implementation by ServiceNow?

2. Indexing in Google:

   • How can we improve indexing of public pages (sp_page) by Google?
   • Are there any techniques to ensure that Googlebot properly interprets and indexes these pages, considering that they are dynamically loaded via AngularJS?

3. Alternatives and Best Practices:

   • Has anyone in the community faced this issue and found a viable solution within ServiceNow’s best practices?
   • Are there plugins, external integrations, or platform configurations that could help simulate SSR or improve the indexing of public pages?

If anyone has encountered something similar or can share insights, I would greatly appreciate it! Any recommendations can help us define the best strategy.

Thanks in advance! 

[lastreaction122]

---

@HIPortalP wrote:

Hello, community!

I am working on a project in the ServiceNow Service Portal where Google indexing of public pages and page load performance are critical factors. One of the challenges we have encountered is the lack of native support for Server-Side Rendering (SSR), something that other technologies like weight, React, Vue, and Next.js provide.

We know that the Service Portal dynamically renders content on the client side, but we would like to explore ways to improve the initial load time and facilitate the indexing of public pages created in the sp_page table.

Our Challenges:

1. SSR in Service Portal:

   • Is there any way to pre-render public pages (sp_page) so that content is delivered already processed to the browser, reducing load time?
   • We know it's possible to generate server-side HTML using Script Includes or GlideAjax, but is there a recommended implementation by ServiceNow?

2. Indexing in Google:

   • How can we improve indexing of public pages (sp_page) by Google?
   • Are there any techniques to ensure that Googlebot properly interprets and indexes these pages, considering that they are dynamically loaded via AngularJS?

3. Alternatives and Best Practices:

   • Has anyone in the community faced this issue and found a viable solution within ServiceNow’s best practices?
   • Are there plugins, external integrations, or platform configurations that could help simulate SSR or improve the indexing of public pages?

If anyone has encountered something similar or can share insights, I would greatly appreciate it! Any recommendations can help us define the best strategy.

Thanks in advance! 

---

ServiceNow's Service Portal does not natively support Server-Side Rendering (SSR), but you can improve page load performance and Google indexing using alternative methods. First, use server-side scripts in widgets to pre-fetch and process data before it reaches the client, reducing load times. Implement SEO best practices such as meta tags, clean URLs, and mobile optimization to enhance search visibility. Additionally, use server-side pagination for large datasets to improve performance. These strategies help optimize public pages (sp_page) for better indexing and faster loading without requiring native SSR support.