Monthly SEO Audit Checklist: 12 Checks in About 90 Minutes

A monthly SEO audit checklist is a short, repeatable set of checks you run once a month to catch problems before they cost you traffic. It covers indexing, search performance, technical regressions, Core Web Vitals, AI crawler access and security. It isn't a full audit. It's a 60–90 minute health check that tells you what changed since last month.

Key takeaways

• Run the same 12 checks every month, in the same order, and write down the numbers. The trend matters more than any single value.
• Start with indexing and the Search Console Performance report. A drop there is the earliest warning you'll get.
• Crawl the site once a month to catch new 404s, redirect chains, stray noindex tags and changed canonicals, which usually come from deploys and plugin updates.
• Leave content strategy, information architecture and backlink analysis for the quarterly or yearly full audit.
• Every check ends with a decision: fine, watch it, or fix it now.

What is a monthly SEO audit, and how is it different from a full audit?

A monthly SEO audit is a light review that compares this month with last month and flags regressions. A full audit reviews the whole site against best practice and produces a long, prioritized fix list. The monthly check asks "did anything break or slip?" The full audit asks "what could be better?"

Most small and mid-size sites need both, at different frequencies. Our guide on how often to audit your website covers the schedule by site type. As a rule, do a full audit once or twice a year, the monthly check below every month, and add automated alerts for the things that can't wait 30 days. Use the full SEO audit checklist for the deep review. The list here is only the part worth repeating every month.

The monthly SEO audit checklist at a glance

Here are the 12 checks, grouped by where you'll find the data. Each one has a clear red flag, so you don't have to judge every number from scratch.

Step 1: Is Google still indexing your important pages?

Open the Page indexing report in Search Console and compare the indexed count with last month's entry in your log. Then open each "not indexed" reason that grew. A slow, steady count is normal. A sudden change in either direction means something on the site changed.

Don't aim for 100%. Google says plainly that you should not expect all URLs on your site to be indexed, only the canonical pages, and that all your important pages should be indexed. So the monthly question isn't "why are 300 URLs excluded?" It's "is any page I care about among them?" Spot-check your top 10 revenue or lead pages with URL Inspection.

Two more quick checks:

• Sitemaps: confirm the last read date is recent and there are no fetch errors. Our XML sitemap guide explains what each status means.
• robots.txt: open the file and diff it against last month's copy. A staging Disallow: / that ships to production is one of the most expensive one-line mistakes in SEO.

If a reason like "Crawled – currently not indexed" is growing, follow the step-by-step process in how to fix website indexing problems. After you fix an issue, use Validate fix. Google notes that validation usually takes up to two weeks.

Step 2: Did search traffic change, and why?

In the Performance report, compare the last 28 days with the previous 28 days, then with the same period last year. Month-over-month shows sudden breaks. Year-over-year filters out seasonality. Note total clicks, impressions, CTR and average position in your log.

Google's own guide to debugging search traffic drops recommends looking at long date ranges to spot yearly patterns. It groups the causes into algorithm updates, technical issues, security problems, spam policy violations, seasonality and site moves. It also points out that a small position shift (say 2 → 4) means something very different from a large one (4 → 29).

Then go one level deeper:

1. Sort Pages by click difference and look at the 10 biggest losers.
2. Do the same for Queries.
3. For each big loser, ask: did we change this page? Did the result page change (a new AI Overview, more ads, a competitor)? Is it seasonal?

A falling page can be a symptom. To find the cause, use the page-level diagnosis in why pages lose Google rankings. If the whole site fell, start with the website traffic drop checklist instead.

Step 3: What broke since last month? Run a crawl

Most monthly regressions come from routine work: a theme update, a new plugin, a migrated template, a developer pushing a staging setting. A monthly crawl with any site crawler catches them. Compare the results with last month's crawl rather than reading the whole report from scratch.

Focus on what's new:

• 404s and 5xx errors linked from your own pages. Fix the link or redirect the URL to the closest relevant page.
• Redirect chains and loops. Point internal links straight to the final URL.
• Indexable pages that turned noindex. This is often a template or plugin setting.
• Canonical tags that changed target. A product template that suddenly canonicalizes every variant to the homepage will empty the index quietly. See the canonical tag guide for correct patterns.
• New pages without titles or with duplicate titles and meta descriptions.
• Orphan pages: new URLs in the sitemap that nothing links to.

A crawl from your own machine won't always render JavaScript the way a browser does, so check one or two key templates with URL Inspection's rendered HTML too. If you'd rather not run the crawl yourself, the free SEORecheck audit crawls your pages and shows real broken links, redirect, canonical and noindex issues with example URLs.

Step 4: Are Core Web Vitals holding steady?

Open the Core Web Vitals report and note how many URLs are Good, Need improvement and Poor, for mobile and desktop. The thresholds are LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1. Flag any URL group that has moved down a bucket.

Keep in mind how the data works. The report is built on Chrome UX Report field data and groups similar URLs together. Because it's real-user data, a slow page released this week may not show up for a while. Validating a fix also takes longer than for indexing: Google describes a 28-day monitoring period. That's another reason a monthly rhythm suits this report well: you check it, ship a fix, and see the result next month.

If a group got worse, look at what shipped on those templates: a new hero image, a chat widget, a consent banner, an A/B testing script. The Core Web Vitals guide covers fixes for each metric.

Step 5: Can AI search still reach and use your site?

Check monthly that AI search crawlers aren't blocked and that your visibility in AI features isn't falling. These settings often change without anyone noticing: a CDN bot-protection rule, a new robots.txt template or a plugin can block crawlers you want.

Three quick checks:

1. robots.txt rules for AI bots. Search bots and training bots are separate. OpenAI documents that OAI-SearchBot is used to surface websites in ChatGPT's search features, while disallowing GPTBot means your content should not be used for training foundation models. You can allow the first and block the second. Just make sure the file reflects the choice you actually made. The robots.txt guide lists the main user agents.
2. Google's generative AI setting. Google's AI optimization guide states that, beyond the Search technical requirements, a site must be included in Search generative AI features in Search Console to be eligible for AI Overviews and AI Mode. Confirm the setting hasn't changed.
3. Generative AI performance report. The same guide names this Search Console report as the place to measure how content performs in generative AI features. Log impressions month over month next to your classic Search numbers.

Skip the rituals that aren't documented to help. Google says it ignores AI text files such as llms.txt, so there's nothing to "refresh" there. The SEO vs GEO measurement guide covers what else is worth tracking.

Step 6: Any manual actions or security issues?

Open the Manual actions and Security issues reports in Search Console. Both should say no issues detected. This takes 30 seconds, but if anything appears, it goes straight to the top of your list. A hacked page or a spam action can wipe out more traffic than every other item on this checklist combined.

While you're there, check the Crawl stats report (Settings → Crawl stats) for spikes in server errors or response time. A host that slows down at night can hurt crawling without anyone on the team noticing.

How do you log results and decide what to fix?

Write every month's numbers in the same place, whether that's a spreadsheet, a doc or a ticket. The checklist only works if you can compare months. A minimal log entry looks like this:

Month: 2026-10
Indexed pages: 1,284 (Sep: 1,301)  | New "not indexed" reasons: none
Clicks 28d: 9,420 (-6% MoM, +3% YoY) | Biggest loser: /pricing-guide (-210 clicks)
Crawl: 14 new 404s (blog tag pages), 2 redirect chains
CWV mobile: Good 81% (Sep: 88%) – product template LCP regression
AI: OAI-SearchBot allowed, GPTBot blocked (intended); AI impressions stable
Manual actions / security: none
Tasks: fix product hero image LCP; redirect tag 404s; review /pricing-guide

Every finding gets one of three labels: fine, watch (check again next month) or fix now. Rank the "fix now" items by impact and effort. How to prioritize SEO fixes gives a simple scoring model. Most months should end with zero to five tasks. If you keep ending up with 20, the site needs a full audit, not a longer monthly checklist.

What should you leave out of a monthly check?

Some work doesn't change month to month, and reviewing it monthly just wastes time. Move these to a quarterly or yearly full audit:

• Keyword research and content gap analysis
• Site architecture and internal linking strategy
• Backlink profile reviews (unless you suspect spam or a negative campaign)
• Structured data coverage across all templates
• Content pruning and consolidation. The process in finding pages that hurt your SEO works best on a full-site dataset.
• International setup such as hreflang, unless you launched a new language

A full audit with a recheck fits this rhythm well. You fix things for 30–60 days, then compare every issue with the previous audit to see what's fixed, improved, unresolved or new. The sample comparison report shows what that looks like, and pricing depends on your country and site.

How long does a monthly SEO audit take?

For a site with a few hundred pages, plan on 60–90 minutes once your log is set up: about 15 minutes for indexing and sitemaps, 20 for performance, 20–30 for crawl review, 10 for Core Web Vitals, 10 for AI access and 5 for manual actions and security. The first month takes longer because you're creating the baseline.

Large sites, online stores with faceted navigation, and sites that deploy daily should add automated alerts. Weekly monitoring and alerts are covered in SEO monitoring tools and best practices. The monthly checklist is the human review on top: alerts tell you something moved, and the monthly check tells you whether it matters.