SEO workflow: the weekly rhythm, and the three workflows that prevent damage

What is an SEO workflow?

An SEO workflow is the repeatable set of tasks, owners and checks a team uses to do SEO work consistently: the recurring rhythm of monitoring and review, and the procedures for specific jobs such as publishing a page or releasing a site change. A good workflow means the same thing happens the same way whoever is doing it, and problems are caught before they reach the live site.

An SEO workflow is narrower than content operations, which covers the whole lifecycle of content from planning to retirement; that is set out in the guide to content operations. This guide is about the rhythm of SEO work itself, and the procedures for the changes that put rankings at risk.

The SEO rhythm: daily, weekly, monthly, quarterly

A recurring rhythm catches problems while they are small and makes sure the slower work, audits and replanning, actually happens. The cadence below suits most sites; the point is to have one and keep it.

Cadence	Tasks	Time for a small site
Daily, automated	Alerts for sudden drops in clicks or indexed pages, robots.txt changes, and errors on key pages	None, unless an alert fires
Weekly	Scan alerts and Search Console for anything unusual; check pages published last week are indexed and linked	30 to 60 minutes
Monthly	Performance review against the same month last year; report; update the keyword map; plan the next month’s pages and updates	Half a day to a day
Quarterly	Technical crawl and audit; content audit of a section; review of what worked; replan the quarter	Two to four days
Yearly	Strategy review: topics, clusters, budget and resourcing	A few days

Time estimates are a starting point to adjust, not a measured standard

The weekly check is the one most often skipped and the one that catches the most. A release that accidentally noindexed a section shows up in the next week’s indexing check, not in next quarter’s audit. What to automate in the daily layer is covered in the guide to SEO automation; how to write the monthly report is in the guide to creating an SEO report.

How much time the rhythm takes, and what is left

Recurring SEO tasks have a habit of filling the week: there is always another report to refine or alert to investigate. Budgeting their time explicitly protects the project work, new pages, updates and technical improvements, that grows traffic.

Hypothetical defaults for one person with half their week on SEO. Time your real tasks for a month before trusting the result.

Hours a week available for SEOhoursWeekly checkshoursMonthly review, report and planninghoursQuarterly audit and replanninghoursAd hoc requests a week, on averagehours

Recurring hours a week, averaged

4.7

Hours a week left for project work

12.3

Negative means the rhythm and requests take more than the time available

Share of time on project work

61.5%

Project hours a quarter

160.0

Monthly and quarterly tasks are spread evenly across the weeks here. In practice they cluster, so the weeks with a quarterly audit have little project time.

If project work falls below about half the time, look first at ad hoc requests and the monthly report. Requests are better batched into a weekly slot than handled as they arrive, and a report that takes a day to produce usually needs its data collection automated, not more polish.

Workflow 1: publishing a new page

Every new page goes through the same steps, from checking the keyword map to confirming the page is indexed and linked. Most of these steps belong to content operations; the SEO-specific checks are the ones listed here, before and after publishing.

1. 1MapCheck the target query against the keyword map. If a page already owns the intent, update that page instead.
2. 2BriefBrief includes the target query, internal links in and out, and acceptance criteria.
3. 3Pre-publishTitle and description written; one H1; internal links in the body; structured data valid; page indexable.
4. 4PublishPage live, added to its hub or pillar and linked from the siblings named in the brief.
5. 5Week oneConfirm the page is indexed, using URL Inspection in Search Console, and appears in the sitemap.
6. 6Month threeCheck impressions and target-query position; adjust title, content or links if it is not moving.

The two steps most often missed are the links in, from the pillar and siblings, and the week-one indexing check. Google’s link best practices say every page you care about should have a link from at least one other page on your site, and a page nobody links to is slow to be found. The brief that sets all of this up is covered in the content brief guide, and the schedule it sits in is in the editorial calendar guide.

Workflow 2: shipping a technical change with developers

Template edits, CMS upgrades, new page types and site redesigns are where SEO problems are introduced most quickly, because one change reaches every page built on a template. The fix is a workflow that brings SEO into the change before it ships, not after the traffic drops.

1

Ticket

Every change that touches templates, URLs, navigation, rendering or metadata is tagged for SEO review when it is raised, with the pages affected.

2

Requirements

SEO writes the acceptance criteria into the ticket: what must not change (URLs, titles, canonicals, indexability, internal links, structured data) and what should.

3

Staging check

SEO crawls the staging version and compares it with production: status codes, titles, canonicals, noindex tags, links and rendered content.

4

Release

Released with a rollback plan. Staging protections, such as password protection or noindex, are removed from production config, not left in.

5

Post-release check

Within a day: crawl key templates on production, check robots.txt and a sample of pages in URL Inspection, and watch alerts for the following week.

A working sequence to adapt to your release process

Staging sites need care in both directions: kept out of Google while they are staging, and not leaking that protection into production. Google’s documentation says robots.txt is not a mechanism for keeping a web page out of Google and recommends noindex or password protection instead; and that for noindex to be effective, the page must not be blocked by robots.txt. Password protection on staging is the safest choice, because it cannot be copied into production by accident in the same way a meta tag can.

The tools on this site cover parts of the staging check by hand: the Internal Link Mapper compares internal links and click depth from a crawl export, the Schema Validator checks structured data, and the Meta Title Generator checks titles. Template changes to page families deserve the most care, because one mistake reaches thousands of pages; the governance for those is in the guide to programmatic SEO without thin content.

Workflow 3: migrating a site

A migration, whether a new domain, a new CMS, a redesign that changes URLs, or a move to HTTPS, is the highest-risk event in SEO. It deserves its own workflow, started weeks before the move.

Phase	What to do	Owner
Inventory	Export every URL that has traffic, links or rankings, from Search Console, analytics, a crawl and a backlink tool	SEO
Map	Map every old URL to its best new equivalent, one to one where possible; avoid redirecting everything to the homepage	SEO with content owners
Build	Implement permanent redirects; keep titles, content and internal links equivalent unless the change is deliberate	Developers
Test	Crawl the redirect map on staging: every old URL returns a single redirect to a working page	SEO
Launch	Release, update the sitemap and internal links to new URLs, and for a domain move use Search Console’s Change of Address tool	Developers and SEO
Monitor	Daily for two weeks, then weekly: indexing, crawl errors, rankings and traffic for key pages against the old site	SEO
Keep	Leave redirects in place long term and keep the old domain registered	Developers and finance

Google gives two pieces of guidance on how long to keep redirects. Its Change of Address documentation for domain moves says to maintain the redirects for at least 180 days, longer if they still receive traffic from Google Search, and to keep paying for the old domain for at least a year. John Mueller has said that, to be certain a redirect has been seen a few times, Google recommends keeping it in place for at least one year, as Search Engine Journal reported. In practice, there is rarely a reason to remove a working redirect.

Handoffs: who does what

SEO workflows cross teams: content, developers, product and sometimes legal or brand. Most failures happen at the handoff, when each team assumes the other checked. Writing down who is responsible, who approves and who needs to know prevents that.

Task	Responsible	Approves	Informed
Keyword map check before a brief	SEO or content lead	Content lead	Writer
Pre-publish SEO checks	Editor	SEO	Writer
SEO acceptance criteria on technical tickets	SEO	Product or engineering lead	Developers
Staging crawl and sign-off	SEO	SEO	Developers
Release with rollback plan	Developers	Engineering lead	SEO
Migration redirect map	SEO	Engineering lead	Content owners
Post-release and post-migration monitoring	SEO	SEO	Engineering and marketing leads

The most valuable single agreement is with engineering: that any ticket touching templates, URLs, navigation, rendering or metadata is tagged for SEO review when it is raised. That one rule, written into the ticket template, puts SEO in front of the changes most likely to cause a release-related drop. It is the kind of process fix the SEO audit guide argues for: change the system that keeps creating the defects.

When something goes wrong: the incident workflow

Even with good workflows, traffic sometimes drops suddenly. A short incident workflow turns panic into a sequence of checks.

Did anything ship to the site in the days before the drop?

Yes, a release or migration

Check the release first: robots.txt, noindex tags, canonicals, redirects, status codes and rendering on the affected templates. Roll back if the cause is clear and the fix is not quick.

No, or not that we know of

Is the drop across the whole site, or limited to some pages or queries?

Whole site

Check tracking first, then Search Console for manual actions and indexing changes, then Google’s Search Status Dashboard for confirmed updates on the dates in question.

Some pages or queries

Compare those pages’ rankings and the results pages for their queries. Look for competitors, results-page changes such as AI Overviews, and decay in the pages themselves.

Write down what you checked and when; it shortens the next incident

Google lists confirmed ranking updates and incidents on its Search Status Dashboard, which is the place to check dates. Whatever the cause, write a short note afterwards: what happened, how it was found, how long it took, and what change to the workflow would have caught it sooner.

Making workflows stick

A workflow that lives in one person’s head stops when they go on holiday. seoClarity’s guide to SEO workflows describes a workflow as a set of scalable, repeatable activities for completing a task; the word that matters is repeatable, and that needs it written down.

• Keep each workflow to one page. A checklist people use beats a manual nobody reads.
• Put it where the work happens. The SEO checklist inside the ticket template or the CMS, not in a separate document.
• One owner per workflow. The person who updates it when something goes wrong.
• Review after incidents. Every problem that reached the live site is a missing step in a workflow.
• Automate the mechanical steps. Checks that never need judgement should run on their own.

Common SEO workflow mistakes

Each mistake below is common, and each has the check that catches it.

• No weekly check. Check: would a release that noindexed a section be noticed within a week?
• SEO reviews releases after they ship. Check: are template, URL and metadata changes tagged for SEO when the ticket is raised?
• Staging protection leaking to production. Check: is staging password-protected, and is production checked for noindex after every release?
• robots.txt used to hide staging. Check: are pages kept out of Google with noindex or a password, not only robots.txt?
• Migrations without a redirect map. Check: does every old URL with traffic or links map to a specific new one?
• Redirects removed early. Check: are redirects kept for at least a year?
• Recurring work crowding out projects. Check: what share of the week goes to project work?
• Workflows in one person’s head. Check: could someone else run each workflow from its checklist?

Rhythm

Daily alerts automated Weekly check scheduled and owned Monthly review and report, quarterly audit and replanning on the calendar Time for project work protected

Workflows

New page workflow with pre-publish and week-one checks Technical change workflow with SEO acceptance criteria and staging crawl Migration workflow with inventory, redirect map and monitoring Incident workflow for sudden drops

Handoffs

Template, URL and metadata tickets tagged for SEO when raised Responsibilities written down for each workflow Each workflow on one page, kept where the work happens

Ticks are saved in your browser.

Setting up the rhythm, workflows and handoffs so a small team can run SEO without problems reaching the live site is part of an SEO systems engagement.