Weekly updates on your sites are helpful, but what if you want to jump on an opportunity as soon as it arises – or fix a problem before it has a chance to affect your SEO standing? What if, instead of in a crowded email inbox, you get your to-do lists directly in your Slack – or have them logged in a spreadsheet?
Introducing: SiteGuru webhooks for automation!
It’s time to take your automated SEO to the next level!
How Do Webhooks Work for Automation?
Think of webhooks as a notification system that sends information from one app (e.g., SiteGuru) to another (e.g., Zapier) whenever something happens. This happens in real time, so you don’t have to check for updates.
In SiteGuru’s case, you have access to two types of events within those webhooks:
- Performance updates (triggered every Monday, containing the stats from last week)
- Website audit completed (triggered whenever a site check is completed, sending you the health score and the to-do list)
Since Zapier, Make.com, and N88 work as “portals” for connecting two different apps – for example, SiteGuru and Slack – you can set up virtually any kind of automation, allowing you to spend even less time managing processes manually and focus only on the fixes that deliver value to your (clients’) SEO.
Use Cases
Some of the most popular use cases we’ve seen include:
- Getting notifications directly to your team’s Slack
- Sending notification information to your tech team’s ticketing system
- Keeping the more high-touch clients in the loop by auto-forwarding the information to them
- Logging the information in a spreadsheet for automated and constant performance tracking
But your use case is up to you!
How to Set up SiteGuru Webhooks for Automation in Zapier, Make.com, or N8N
Since all these automation connectors work similarly, we’ll show you the example in Zapier!
Step 1: Add the Webhook URL to SiteGuru
Start setting up the automation process in Zapier, Make.com, or N8N.
In Zapier, you’ll start to create a Zap.
In the App event search bar, choose “Webhooks by Zapier”.
Choose “Catch Hook” as the trigger event. (Skip the “Pick off a child key” and continue.)
This should give you a webhook URL:
Then, when you get the webhook URL, add it in SiteGuru’s notifications settings.
Click “Add webhook” under the “Webhooks” section.
Then, paste the webhook URL:
Step 2. Choose Your Notification Type
Next up, choose what kind of automation you want to set up. As we mentioned, you get two options (for now – but let us know which others you need!):
- Performance updates (Triggered every Monday, containing the stats from last week)
- Website audit completed (Triggered whenever a site check is completed, containing the health score and the to-do list)
Note: You can set up these webhooks for all the sites in your account, or a few specific ones.
Simply toggle the “Set notifications per site” to customize them for different sites.
Step 3. Set up a New Zap (or Automation)
If you’re in Zapier, start creating a new Zap and select “Webhook” as the Zapier trigger.
Then, go back to your SiteGuru account and click “Test” to see if the webhook is passing data as it should:
Step 4. Testing Data in Zapier, Make.com, or N8N
If the test is successful on both SiteGuru and Zapier’s ends, you’ll see all the data in Zapier:
The green check marks are a good signal! 😉
Inspecting and Replaying Webhook Calls
Setting up webhooks is one thing – but what if something looks off, or your endpoint isn’t receiving what you expected? SiteGuru now keeps a log of every webhook call we send on your behalf, so you can see exactly what went out, what came back, and re-send any past call with a single click.
You’ll find the new Recent calls section right under each of your webhooks in your notification settings.
What’s in the Call Log
For every call SiteGuru fires to your webhook, we store:
- The timestamp and event type (performance update or website audit completed)
- The full request payload we sent – the exact same JSON your endpoint received
- The HTTP status code your endpoint returned
- The full response body – nothing truncated, so error messages and stack traces stay readable
We keep the last 30 days of calls per webhook. Older calls are automatically cleaned up.
Replaying a Past Call
Open any call in the log and you’ll see a “Resend” button. Clicking it tells SiteGuru to re-send the exact same payload to your webhook URL, just like the original call. The replay shows up as a new entry in the log, so you can compare the original response with the new one.
This is useful when:
- You’re building or debugging your endpoint and want to iterate against a real payload without waiting for next Monday’s performance update or the next site check
- Your endpoint was down for a moment and you want to retry a specific call instead of waiting for the next event
- You updated your Zap, Make scenario, or n8n workflow and want to verify it handles the same data correctly
Heads up: Resend always sends to your webhook’s current URL. If you’ve updated the URL since the original call was made, the replay will go to the new endpoint – not the old one. This matches how tools like Stripe handle replays, and it’s usually what you want when you’re debugging.
Step 5. Where to Next?
That’s up to you! Since Zapier connects to over 7,000 apps, you get virtually limitless options. N8N and Make.com also offer plenty of integrations!
With that in mind, we’ll leave you to play around with the automations. However, keep us posted on X or LinkedIn – we’d love to see how you’ve made your life easier! 🚀
