SEO checklist: the weekly, monthly and quarterly checks

Most SEO checklists are one long list. That is the wrong shape, because the items are not due at the same time.

Checking whether robots.txt still blocks the site is weekly work. Deciding whether your keyword map still matches what the business sells is quarterly. Put both on one list and the quarterly thinking gets skipped every week.

So this website SEO checklist is grouped by cadence. If you are new to the subject, read our complete guide to SEO first for the concepts — this page assumes you know them and just need the running order.

Audit once, check forever — the split

There are two different documents, and mixing them is why checklists get abandoned.

An audit is a one-off deep diagnostic. You run it when you inherit a site, before a migration, or when something clearly broke. It takes days and produces a backlog. That whole job — method, crawl setup, the order you investigate in — belongs to our SEO audit checklist. Nothing here repeats it.

An operating checklist is short and never ends. Its job is to catch three things: something broke, something drifted, something changed outside your control.

The audit sits outside the cycle.

The weekly checks

Five items. They catch breakage, not opportunities. If all five read clean, close the tab.

That last one saves the most wasted effort. Google publishes ranking updates with start and end dates on the its own documentation for that dashboard. Check it before you rewrite a page in a panic.

The monthly checks

Monthly is where you look for drift — things that are not broken but are quietly getting worse.

On the speed check, use real thresholds rather than a tool's score out of 100. web.dev sets the "good" bar at 2.5 seconds or less for Largest Contentful Paint, 200 milliseconds or less for Interaction to Next Paint, and 0.1 or less for Cumulative Layout Shift — assessed at the 75th percentile of page loads, split by mobile and desktop. Our Core Web Vitals guide explains each metric, and page speed optimisation covers the fixes.

The quarterly checks

Quarterly is the only slot where you are allowed to question the plan instead of the pages.

Checks tied to an event, not a calendar

Two short lists run on a trigger. The first is your on page SEO checklist for anything new. The second runs when developers deploy.

On every new page, before you call it live:

Step five matters more than it used to. Google states there are no additional requirements and no special schema.org markup needed to appear in AI Overviews or AI Mode — but its generative AI guidance does name one gate: the page must be indexed and eligible to be shown with a snippet. That is the actionable item. The same page says you do not need machine-readable files, AI text files, markup or Markdown to appear in Search, and names LLMS.txt directly as fine to keep but not needed. Nothing to add there.

On every release:

Checks that tell you nothing

These appear on most published checklists. They cost time and return no decision. Replace each one.

What we check on this site ourselves

This is Digital Hangover's own cadence on digitalhangover.in, not a template. We run it because we publish often, and publishing often is how sites quietly damage themselves.

Weekly: Page Indexing deltas, 404s with inbound links, and the Search Status Dashboard. Twenty minutes.

Monthly: the Performance report by page, internal links into service pages, and one pass over anything published in the last 60 days to check it was linked from somewhere sensible. Linking a new post is the step teams forget, including ours.

Quarterly: the cannibalisation register. This is the one check we would keep if we could keep only one. It is a plain spreadsheet with one row per target query and one column naming the single URL that owns it. Before anything new is briefed, we check its primary keyword against the register. If a live page already owns that query, the new piece either gets a narrower angle or does not get written.

Every blog brief we write carries a cannibalisation line for this reason — a sentence stating how the new page differs from the live page nearest to it. It is cheaper than untangling two pages that fight for a year.

Where a checklist stops and judgement starts

A checklist is a smoke alarm. It is very good at telling you something is burning and completely unable to design the building.

Rankings move because of content and links, not checkboxes. Every item above can read green on a site that will never rank, because nothing on it answers a question better than the pages already ranking. Fixing a canonical tag does not make a thin page good.

So keep the hierarchy honest: the checklist protects what you have built; content and links build it. Given two hours and a choice, write the better page.

Timelines follow from that. Organic work usually shows meaningful movement in roughly three to six months and compounds after, so a checklist run in week two will not show you much. That is fine. It is insurance, not a growth lever.

One note on reporting. Search Console documentation states that "Clicking a link to an external page in AI Mode counts as a click," so clicks from AI surfaces do reach you and are counted in your ordinary Performance report. Google announced separate Search Generative AI performance reports in a June 2026 Search Central post, and those give impressions-level insight — you can see AI traffic inside your totals, you cannot isolate it. Treat it as context in your SEO reporting, not as a separate scoreboard.

What a year of this cadence changes

After four quarters, the checklist stops finding emergencies. That is the point.

Breakage gets caught in the week it happens, not the quarter someone notices the traffic. New pages launch linked and indexable instead of being rescued later. The register stops you writing pages that compete with your own. The compounding is not in the checks — it is in the time they free up for work that moves rankings.