Skip to content

Latest commit

 

History

History
56 lines (40 loc) · 1.63 KB

README.md

File metadata and controls

56 lines (40 loc) · 1.63 KB
Raw

Example of SEO4Ajax integration using Lambda@Edge functions in AWS CloudFront

This is an example of integrating SEO4Ajax and a SPA in S3 served over Cloudfront.

Instructions

  1. Upload seo4ajax-cloudfront.yaml to Cloudformation as a new stack, that'll setup the example for you. Enter your SEO4Ajax site token when asked.
  2. Upload code.js and index.html to the S3 bucket created by Cloudformation in step 1.
  3. Change the read permissions for code.js and index.html to be publicly readable.

Testing

To see the page as rendered by seo4ajax.com run:

curl -H 'User-Agent: Facebot' https://${CLOUDFRONT_DOMAIN}/over/here

The same page without pre-rendering:

curl https://${CLOUDFRONT_DOMAIN}/over/here

Implementation

Two Lambda@Edge functions are used. The first detects bot requests on requests entering the system, it sets a header which Cloudfront uses to partition the cache. The second function, run after the cache, detects the presence of the header and, if present, routes the request to api.seo4ajax.com

Caching

By default, static resources from the bucket are cached for a long time period. This improves performance but means that the deploy process of any real app will need a Cloudfront purge step. The requests to api.seo4ajax.com are also cached.

Alternative

Amazon describes a more recent procedure for integrating a service like SEO4Ajax, you can find more info here: https://aws.amazon.com/blogs/networking-and-content-delivery/how-to-optimize-content-for-search-engines-with-aws-waf-bot-control-and-amazon-cloudfront/

Notes

This project is a fork of https://github.com/jinty/prerender-cloudfront