I am about to migrate a client away from using a static collection and static collection page to a dynamic version. In order to mitigate the negative impact this will have on their SEO, I would like to implement the Cloudflare solution outlined here.
As I will be making updates to a production application I would like to understand better what will happen behind the scenes. I think I will be able to follow the tutorial but I want to understand what it is I am doing.
Would it be possible for someone from the dev team to create a diagram to support the information given in the tutorial? Ideally, this would start at the point of a user navigating to the collection page and end with the metadata being updated.
I was trying to put this together myself and it highlighted how little I know about what will actually be happening behind the scenes. My current understanding is something like this:
- User request collection page
- Magic happens
- The page is loaded
- The collection item is loaded
- The header is updated.
Perhaps it’s something like this in reality?
- User request collection page
- The URL is looked up on a DNS which maybe has to be on Cloudflare
- The URL is resolved to an IP address that points to coudlfare or maybe WeWeb or Xano
- Cloudflare forwards the request to WeWeb… maybe
- WeWeb serves the page
- But then where does the metadata header come in?
Help!