Instruction
Every Monday at 8 AM audit the pages in our sitemap for broken links, title and description problems, noindex tags and slow responses, and add new and fixed issues to our SEO audit sheet.
Steps in each run
- 1 Read the sitemap and list pages
- 2 Fetch each page for status code and response time
- 3 Extract title, description, headings, canonical and links
- 4 Group issues and suggest fixes
- 5 Mark issues as new, open or fixed
- 6 Append results to the audit sheet Google Sheets
Memory. Stores the set of open issues keyed by page and issue type so each week shows only new and fixed problems.
SEO audit changes this week
Sample output| Page | Issue | Status | Suggested fix |
|---|---|---|---|
| /pricing | Title longer than 65 characters | New | Shorten title and keep the main phrase first |
| /blog/onboarding-checklist | Broken internal link to /guides/setup | New | Point link to /guides/getting-started |
| /features/reports | Page carries a noindex tag | New | Remove noindex from the page template |
| /about | Missing meta description | Still open | Write a 150 character description |
| /blog/team-rituals | Redirect chain with 3 hops | Fixed | No action needed |
| /integrations | Response time 2.8 seconds | Still open | Cache the integrations list |
-
/pricing
- Issue
- Title longer than 65 characters
- Status
- New
- Suggested fix
- Shorten title and keep the main phrase first
-
/blog/onboarding-checklist
- Issue
- Broken internal link to /guides/setup
- Status
- New
- Suggested fix
- Point link to /guides/getting-started
-
/features/reports
- Issue
- Page carries a noindex tag
- Status
- New
- Suggested fix
- Remove noindex from the page template
-
/about
- Issue
- Missing meta description
- Status
- Still open
- Suggested fix
- Write a 150 character description
-
/blog/team-rituals
- Issue
- Redirect chain with 3 hops
- Status
- Fixed
- Suggested fix
- No action needed
-
/integrations
- Issue
- Response time 2.8 seconds
- Status
- Still open
- Suggested fix
- Cache the integrations list
Starts as a paused draft in your workspace. You review every step before the first run.
What the SEO audit template checks
The agent starts from your sitemap, fetches each page and records the status code, title, meta description, main heading, canonical tag, robots directives, internal links and image alt text. An AI step then reviews the findings the way an experienced marketer would: it flags titles that are too long or duplicated, pages with thin content, redirect chains, broken internal links and pages that accidentally carry a noindex tag.
Because the audit runs every week, the useful part is the change. The sheet shows which issues are new this week, which were fixed and which are still open, so your team can work through a short list instead of a full report each time. More ideas for marketing teams are on the marketing use cases page.
Why it runs on Monday morning
The default schedule is every Monday at 08:00 in America/New_York, written as 0 8 * * 1. Releases from the previous week are live by then, and the marketing team can plan fixes in the Monday meeting. You can change the sentence to "every day at 05:00" during a site migration, or "first Monday of the month" for a smaller site.
Each step of the audit
- 1Read the sitemap. A web fetch step loads your sitemap and builds the list of pages to check.
- 2Fetch each page. An HTTP step records status code, response time and headers.
- 3Read on page elements. A web fetch step extracts title, description, headings, canonical, robots and links.
- 4Review the findings. An AI step groups problems by type and writes a short fix suggestion for each.
- 5Compare with last week. A memory step marks each issue as new, still open or fixed.
- 6Write to Google Sheets. The integration step adds this week's rows to the audit sheet.
All steps are read only on your website, so no approval gate is needed. If you add a step that opens tickets in another tool, you can put an approval before it.
How memory tracks issues across weeks
Each issue gets a stable key made of the page address and the issue type. After every run the agent stores the set of open keys. Next Monday it compares the new set with the stored one, so an issue that was already reported is marked as still open rather than new, and an issue that disappeared is marked as fixed. This avoids the familiar problem of weekly audit reports that repeat the same 200 warnings until nobody reads them.
Customising the audit
- Limit the crawl to one folder, such as the blog or product pages.
- Set your own rules, for example a title length range or required schema on product pages.
- Post a Slack message when a page returns an error, in addition to the weekly sheet.
- Check a staging site before release with a manual Run now.
- Add competitor pages to compare titles and headings with your own.
Large sites can split the audit into several crons by section so each run stays quick. Read how scheduling works in AI cron jobs.
Who it is for
The template suits in house marketers, small agencies that manage several client sites and founders who want to know when a release breaks something important. If someone spends an hour each week running a crawler and cleaning the export, the agent gives that hour back and delivers a shorter, clearer list.
Frequently asked questions
How many pages can one audit check?
There is no fixed page limit. Each AI review step counts as AI calls, so very large sites are best split into sections. A few hundred pages per run is typical.
Does the audit change anything on my site?
No. Every step only reads your pages. Results go to Google Sheets and, if you add it, Slack.
Can I audit client sites in one account?
Yes. Create one cron per site from the same template. Starter allows 10 active crons, Pro 50 and Teams unlimited under fair use.
Does it check page speed?
It records server response time for every page and flags slow responses. You can add an HTTP step that calls a speed testing service you already use.
Can I run the audit right after a release?
Yes. Use Run now at any time, or trigger the cron from your deployment pipeline through an inbound webhook on Pro and Teams.