How do you make sure you don’t “break” your website’s content?
But why did I need this?

Last week, while restructuring my website’s backend, I realised:

  1. I don’t want to test every single page manually.
  2. I don’t want to just spot-check the website, and risk breaking things.

How could I easily ensure that no content or pages were broken after my changes?

A while back, I built a relatively small n8n process to collect all my website content into a Google Sheet (and PDF).
I did this to provide relevant business information to ChatGPT as my assistant, enriching its understanding of what I do, why and how I do it.
This enabled it to act as a more “sound” business assistant.

I reused that process to create two different versions of the Google Sheet, and then leveraged n8n to check for missing URLs or content differences between production and testing before going live.

I am now sure I did not break anything that could affect SEO or content structure.


Automation isn’t only about streamlining business processes.
It is about iteratively enhancing business resilience, with reusable components.


There you have it. Two ways I use automation to boost efficiency:

  1. Collecting and storing website content for basic training of your LLM models.
  2. Creating a website testing and comparison tool for automated and straightforward testing.

I hope this sparks some ideas for you and your business improvements!