Systems and methods for single page application server side renderer

Patent metadata

Field	Value
Publication number	US-10747828-B2
Application number	US-201815937242-A
Country	US
Kind code	B2
Filing date	Mar 27, 2018
Priority date	Mar 27, 2018
Publication date	Aug 18, 2020
Grant date	Aug 18, 2020

Abstract

This system and method relate generally to search engine optimization, and more particularly to systems and methods for single page application server side renderers. In one embodiment, a computer-implemented method for single page application server-side rendering is disclosed. In this method embodiment, a web server receives a request via a computer network. The web server determines that the request is a crawler request, and that the request includes a uniform resource locator for a single page web application. The web server then executes, after determining that the request is a crawler request, a single page application server side renderer. The web server generates a crawler response using the single page application server side renderer, and provides the crawler response in response to the received request.

First claim

What is claimed is:

1. A computer-implemented method for single-page application server-side rendering, comprising:
receiving, via one or more hardware processors, a request via a computer network;
determining, via the one or more hardware processors, if the request is a crawler request or a web browser request by extracting header information from the request, and that the request includes a uniform resource locator for a single-page web application;
executing, via the one or more hardware processors, after determining that the request is a crawler request, a single-page application server-side renderer;
implementing, via the one or more hardware processors, the single-page application server-side renderer, wherein the single-page application server-side renderer executes a script to render a static page;
generating, via the one or more hardware processors, a crawler response containing the rendered static page using the single-page application server-side renderer;
providing, via the one or more hardware processors, the crawler response in real-time in response to the received request;
providing, after determining that the request is a web browser request, a static file to a single page application running in the web browser when the request is for a static asset;
providing, after determining that the request is a web browser request, an API response when the request is an API call; and
providing, after determining that the request is a web browser request, a standard start page when the request is not an API call or a request for a static asset.

2. The method of claim 1 , further comprising:
executing, via the one or more hardware processors, a single-page application service;
requesting, via the one or more hardware processors, by the single-page application server-side renderer via an API call, one or more web resources from the single-page application service; and
wherein the single-page application server-side renderer uses the one or more web resources to render the static page, to generate the crawler response.

3. The method of claim 1 , further comprising:
determining, via the one or more hardware processors, whether the single-pace application server-side renderer has issued a page-loaded JavaScript event; and
determining, via the one or more hardware processors, after determining that the single-page application server-side renderer has issued a page-loaded JavaScript event, that the single-pace application server-side renderer has completed rendering the static page.

4. The method of claim 1 , further comprising:
caching, via the one or more hardware processors, the rendered static page in a page cache;
determining, via the one or more hardware processors, after receiving a second crawler request, that a second crawler response is cached in the page cache; and
providing, via the one or more hardware processors, the second crawler response from the page cache after receiving the second crawler request.

5. The method of claim 1 , further comprising:
determining, via the one or more hardware processors, that the rendered static page should not be cached; and
providing, via the one or more hardware processors, the rendered static page as the crawler response.

6. A system, comprising:
a processor; and
a memory device storing instructions executable by the processor to:
receive a request via a computer network;
determine if the request is a crawler request or a web browser request by extracting header information from the request, and that the request includes a uniform resource locator for a single-page web application;
execute, after determining that the request is a crawler request, a single-page application server-side renderer;
implement, via the processor, the single-page application server-side renderer, wherein the single-page application server-side renderer executes one or more scripts to render a static page;
generate a crawler response containing the rendered static page using the single-page application server-side renderer;
provide the crawler response in real-time in response to the received request;
provide, after determining that the request is a web browser request, a static file to a single page application running in the web browser when the request is for a static asset;
provide, after determining that the request is a web browser request, an API response when the request is an API call; and
provide, after determining that the request is a web browser request, a standard start page when the request is not an API call or a request for a static asset.

7. The system of claim 6 , the memory device further storing instructions executable by the processor to:
execute a single-page application service;
request, by the single-page application server-side renderer via an API call, one or more web resources from the single-page application service; and
wherein the single-page application server-side renderer uses the one or more web resources to render the static page, to generate the crawler response.

8. The system of claim 6 , the memory device further storing instructions executable by the processor to:
determine whether the single-page application server-side renderer has issued a page-loaded JavaScript event; and
determine, after determining that the single-page application server-side renderer has issued page-loaded JavaScript event, that the single-page application server-side renderer has completed rendering the static page.

9. The system of claim 6 , the memory device further storing instructions executable by the processor to:
cache the rendered static page in a page cache;
determine, after receiving a second crawler request, that a second crawler response is cached in the page cache; and
provide the second crawler response from the page cache after receiving the second crawler request.

10. The system of claim 6 , the memory device further storing instructions executable by the processor to:
determine that the rendered static page should not be cached; and
provide the rendered static page as the crawler response.

11. A non-transitory computer-readable medium storing instructions, the instructions executable by at least one processor to:
receive a request via a computer network;
determine if the request is a crawler request or a web browser request by extracting header information from the request, and that the request includes a uniform resource locator for a single-page web application;
execute, after determining that the request is a crawler request, a single-page application server-side renderer;
implement, via the at least one processor, the single-page application server-side renderer, wherein the single-page application server-side renderer executes one or more scripts to render a static page;
generate a crawler response containing the rendered static page using the single-page application server-side renderer;
provide the crawler response in real-time in response to the received request;
provide, after determining that the request is a web browser request, a static file to a single page application running in the web browser when the request is for a static asset;
provide, after determining that the request is a web browser request, an API response when the request is an API call; and
provide, after determining that the request is a web browser request, a standard start page when the request is not an API call or a request for a static asset.

12. The medium of claim 11 , further storing instructions executable by the at least one processor to:
execute a single-page application service;
request, by the single-page application server-side renderer via an API call, on

Assignees

• Capital One Services Llc

Inventors

• Mathews Liju

Classifications

• G06F16/9566

  URL specific, e.g. using aliases, detecting broken or misspelled links · CPC title

• G06F16/9577

  Optimising the visualization of content, e.g. distillation of HTML documents · CPC title

• G06F16/951 Primary

  Indexing; Web crawling techniques · CPC title