Chapter 41: How to Manage SEO Work

A laptop showing charts, a calendar, a flow chart and colorful notes on a desk

Last updated: November 1, 2026.

When we learn SEO, we usually go topic by topic:

  • Technical SEO
  • Content
  • Backlinks
  • Search Console
  • Site speed
  • Keyword research
  • SEO audit
  • Checklists

But in a real project, none of these lives on its own.

The real question is:

In what order, with what priority, with whom and over how long will we manage all of these?

I think this is where the hardest part of learning SEO begins.

Because theory tells you, “Fix the canonical error.” A real project asks:

“Is the canonical error more important, or the falling category pages, the 404 problem, content production, or the site speed issue?”

SEO work is partly the job of choosing the right task at the right time.

1. I don’t start an SEO project by opening tools

When we start a new project, the first reflex can be:

  • Let’s open Semrush.
  • Let’s look at Search Console.
  • Let’s crawl with Screaming Frog.

We’re going to do all of these anyway. But first you need to try to understand this:

What does this business want to achieve?

Because we may not treat the same technical problem with the same priority on two different sites.

For example, for an e-commerce site these may matter:

  • Sales
  • Profitability
  • Category visibility
  • Product traffic

On a B2B site these may matter more:

  • Qualified leads
  • Quote requests
  • Phone calls
  • Specific product queries

On a news site these may come to the front:

  • Fast indexing
  • Discover
  • News queries
  • Real-time traffic

An SEO strategy shouldn’t be built disconnected from the site’s business model.

2. The first question isn’t “what position are we in?”

A question we hear very often when a new client arrives: “What position can you get us to for this keyword?”

I think there are questions to ask before that:

  • Is this keyword actually valuable?
  • Is the user intent right?
  • Can the person coming from this query become a customer?
  • Do we have the right page for this query?
  • Who are the competitors?
  • What does the search result look like?
  • What can this query earn us commercially?

Ranking first for a keyword is not the goal.

Being visible for the right keyword is the goal.

3. You need to define the goal from the start

Starting an SEO project with a very general goal like “Let’s increase traffic” is not enough, in my view. More meaningful goals can be set.

For example:

  • Increasing the number of organic leads
  • Improving visibility in specific categories
  • Getting more traffic from non-branded queries
  • Moving keywords in the top 20 into the top 10
  • Building visibility for a new product group
  • Solving an indexing problem
  • Creating organic traffic in an international market

The clearer the goal, the easier it becomes to prioritize the work.

4. You can’t do everything at once

You did an SEO audit. You found:

  • 300 broken links
  • 50 canonical problems
  • 20 slow pages
  • Missing content
  • Weak category pages
  • Schema issues
  • Gaps in internal linking
  • A need for backlinks

Trying to solve all of them in the same week is usually not possible. This is where prioritization comes in.

I usually look at these three questions:

How big is the impact?

How urgent is it?

How hard is it?

If something has big impact + low effort, it can make sense to do it first. But if there’s a critical technical problem, you may need to go after it first even if the effort is high.

5. Prioritization in SEO is not fixed

You see a task as high priority in January. In February, conditions change. For example:

  • A Google algorithm update comes out.
  • A new category is opened.
  • A competitor starts pushing aggressively.
  • The development team changes the site.
  • Traffic suddenly drops.
  • A new product group launches.

In that case, the roadmap may change too.

I think an SEO roadmap shouldn’t be a document prepared once and hung on the wall. It should be a working plan that is constantly updated.

6. Month one and month six shouldn’t look the same

A question that comes up very often in SEO projects:

“We did everything in the first month, so what will we do in the second month?”

Actually, we don’t do everything in the first month. The first month mostly goes like this:

  • Understanding the system
  • Finding the problems
  • Collecting data
  • Setting priorities
  • Doing the first critical tasks

In the following months, these continue:

  • Implementation
  • Measurement
  • New opportunities
  • Content
  • Technical improvements
  • Competitor tracking
  • New problems
  • Updates

SEO is not a one-time project.

It’s continuous improvement.

7. An SEO audit isn’t done just once

On our projects, we don’t just do an SEO audit at the start and leave it. We recheck from scratch at regular intervals. Because the site changes.

While a developer is working on something else:

  • The canonical can break.
  • The analytics code can disappear.
  • The sitemap can change.
  • noindex can get turned on.
  • A redirect chain can form.

With one client, we had solved a canonical problem. Then after another development, the same problem came back. With another client, we found that the Analytics code had completely disappeared from the site.

These aren’t things you can call done with “We fixed it once, it’s fine now.”

8. Some checks can be monthly, some can’t

For example, a full SEO audit can be done monthly. But we can’t say “We’ll check next month” for uptime.

With one client, the site was down for about an hour. Noticing that in a monthly check would be pointless.

That’s why these should be monitored in real time or much more often:

  • Site availability
  • Server problems
  • Critical errors

With services like UptimeRobot, you can get email, SMS or push alerts.

I think the basic rule is:

First the site has to work. Then we grow it.

9. Checklists should be at the center of SEO management

We talked about SEO checklists in Chapter 34. In project management, they become much more meaningful.

For example:

Daily

  • Is the site up?
  • Is there a critical traffic drop?
  • Is anything abnormal in Search Console?

Weekly

  • Has new content been indexed?
  • How have important queries moved?
  • Are there new technical errors?
  • Has anything significant changed at competitors?

Monthly

  • SEO audit
  • Traffic analysis
  • Conversions
  • Content performance
  • Backlinks
  • Core Web Vitals
  • Index status
  • Roadmap

But keeping these in someone’s memory is not right.

A checklist should live inside the system, not in someone’s memory.

10. ClickUp, Asana, Trello or Jira, it doesn’t matter

Which project management tool you use is secondary. What matters is that every task has:

  • An owner
  • A due date
  • A priority
  • A status
  • Evidence
  • A history

For example, instead of “The canonical will be fixed,” these should be clear:

  • Which URL type?
  • Who will do it?
  • When?
  • How will it be checked?
  • Who will verify it after it’s done?

SEO work shouldn’t be left hanging as “to be done.”

11. “Done” and “verified” are not the same thing

I think this is one of the most important distinctions on the operations side.

The developer says, “I set up the redirects.” Fine. But are they actually right?

The SEO team should check:

  • Is the status code correct?
  • Is the target URL correct?
  • Has a chain formed?
  • What happened to the canonical?
  • Is the sitemap up to date?

So the workflow can look like this:

Requested → Done → Checked → Verified

It shouldn’t end with just “The developer said it’s done.”

12. Keeping a dated record of changes is very important

One day traffic drops. Everyone is talking about the Google core update. But three days ago on the site:

  • The menu changed.
  • The URL structure changed.
  • The cache plugin was updated.
  • The internal link structure broke.

If there’s no record of these, diagnosis gets harder. That’s why it’s very useful to log important changes with dates.

For example:

October 12 - category template changed
October 18 - canonical fixed
October 22 - new content structure went live

Then you can put them side by side with the chart. Sometimes what you thought was an algorithm update turns out to be a change you made yourself.

13. When traffic drops, the first move shouldn’t be panic

For example, organic traffic dropped 30%. The first question shouldn’t be “Did Google penalize us?”

First you need to break the problem down:

  • Did the whole site drop?
  • A specific folder?
  • Mobile?
  • Desktop?
  • A single country?
  • Branded?
  • Non-branded?
  • Specific queries?
  • Specific pages?
  • Did impressions drop?
  • Click-through rate (CTR)?
  • Average position?

The smaller you make the problem, the easier it is to find the cause.

14. You need to separate an algorithm update from your own mistake

Google rolled out an update. Traffic dropped in the same period. Just because these two things happened at the same time, it’s easy to say “The core update hit us.”

But maybe:

  • robots.txt changed.
  • noindex got turned on.
  • Analytics broke.
  • There was a server problem.
  • Content was removed.

You need to rule these out first. In SEO diagnosis, it’s important not to confuse correlation with cause.

15. A drop isn’t always a failure

In Chapter 31 I described a real client example. The client had worked with another SEO agency for a long time.

In the first month after we started, organic traffic dropped about 10%. But revenue rose about 180%.

Why? The previous setup was producing high traffic, but from queries that weren’t very meaningful commercially.

For example, volleyball content was getting high traffic. But the site didn’t sell volleyball shoes. On the basketball shoe side there was commercial potential, but the content and CTAs weren’t strong enough.

We changed the strategy. Irrelevant traffic went down. Sales went up.

Then the client naturally asked:

“Why did traffic drop? :)”

In SEO management, you need to explain not just the chart, but what the chart is telling you.

16. An SEO report is not a list of tasks done

Sometimes a report looks like this:

  • 10 pieces of content published.
  • 20 backlinks acquired.
  • 30 titles edited.
  • 50 errors fixed.

These are activities. But not results.

I think a report should tell you:

  • What did we do?
  • Why did we do it?
  • What changed?
  • What was the result?
  • What will we do next?

The client doesn’t need to understand every technical task the SEO specialist did. But they should be able to understand the answer to “What changed this month?”

17. A report should be prepared for its audience

What the CEO wants to see and what the developer wants to see may not be the same.

The CEO may want to see:

  • Traffic
  • Leads
  • Sales
  • Revenue
  • Growth

The developer may want to see:

  • 404s
  • Canonical
  • Sitemap
  • Core Web Vitals
  • Logs

The content team may look at these questions:

  • Which articles are growing?
  • Which queries are opportunities?
  • Which content should be updated?

We don’t have to present the same data the same way to everyone.

18. You need to manage client expectations right from the start

One of the most dangerous sentences in SEO: “We’ll get you to number one in 3 months.”

It’s impossible to guarantee that. Competition:

  • Can change.
  • Google can change.
  • A competitor can push harder.
  • A site problem can come up.

I think the healthier approach is to explain these from the start:

  • What we will do
  • What we can measure
  • A rough time expectation
  • The risks

In SEO, instead of guaranteeing a specific position, you should commit to the right process.

19. There’s no single answer for how long SEO takes

There were two examples I used to give in my training sessions.

On one of our students’ sites, we made small on-site changes. Competition was low. It rose about 10 positions within roughly 4 hours.

On another project, we worked for about 6 months. The site was moving like the Ottoman Mehter band’s march, two steps forward and one step back. Then, after changes at Google, it made a big jump.

Both are SEO.

That’s why there’s no single answer to “How many months does SEO take to show results?”

20. But just because it takes time doesn’t mean you wait forever

SEO requires patience. But not blind patience.

For 6 months:

  • Impressions don’t increase.
  • No new queries come in.
  • Rankings don’t change.
  • No leads come in.
  • Content doesn’t perform.

And if we’re still saying “SEO takes time,” there may be a problem.

Before results arrive, we need to see some leading signals. For example:

  • An increase in impressions
  • New queries
  • Keywords moving from 30 to 15
  • More crawling
  • Indexing
  • Traffic to commercial pages

While waiting for SEO results, we also need to measure whether we’re on the right track.

21. You may need to admit the strategy isn’t working

We prepared a strategy. We applied it for 3 months. The signal we expected didn’t come.

Sometimes what needs to happen isn’t “Let’s wait a bit longer,” but asking “What did we assume wrong?”

Maybe:

  • We chose the wrong keyword.
  • The search intent is wrong.
  • The content isn’t good enough.
  • The competitor analysis was flawed.
  • There’s a technical problem.
  • The CTA is wrong.
  • There’s no demand for the product.

Changing your SEO strategy isn’t failure. It’s making decisions based on data.

22. You don’t have to produce new content every month

Just because we provide SEO services doesn’t mean we have to sell the client “20 blog posts a month.”

In some months, the right work may be:

  • Improving old content
  • Reorganizing categories
  • Improving internal links
  • Solving a technical problem
  • Improving product pages

The task list should be built around needs, not a package.

23. Old content is sometimes a bigger opportunity than new content

In Search Console, these queries can be very valuable:

  • Ranking between 8 and 20
  • Getting high impressions
  • With a weak click-through rate

Instead of producing a new article, improving the existing page like this can bring faster results:

  • Going deeper
  • Developing it around search intent
  • Fixing the headings
  • Adding internal links
  • Adding a CTA

In SEO management:

Seeing the existing opportunity matters as much as producing new work.

24. It helps to evaluate tasks by impact / effort

For example, there are two tasks.

Task A: Requires 3 months of development. Estimated impact is medium.

Task B: Takes 2 hours. Estimated impact is high.

Doing B first can make sense.

But doing everything just because it’s easy isn’t right either. Some big technical tasks can take months but still need to be done.

What matters is:

Setting priorities deliberately.

25. The SEO team shouldn’t just throw problems at developers

The SEO specialist says, “The canonical is wrong, fix it.” The developer asks, “How?”

I think a good SEO request should be as clear as possible. For example:

  • What is the problem?
  • On which URLs?
  • What is the expected behavior?
  • What is an example of a correct URL?
  • What is the test criterion?

A clear ticket makes the developer’s job easier too.

SEO and development teams aren’t on opposite sides. They’re solving the same problem.

26. Developers shouldn’t make SEO decisions alone either

A developer might say, “These are duplicates, so I pointed the canonical to the main category.” It may look technically sensible. But maybe that filter page is getting serious traffic for the query “red prom dress.”

That’s why there are areas that need to be evaluated together:

  • Technical decisions
  • SEO decisions
  • Product decisions

This is especially important on large sites.

27. The content team shouldn’t be left alone without an SEO brief

We talked about the content brief in Chapter 22. We’ve seen the same piece of content rewritten 4-5 times because of a bad brief.

A good brief should guide on:

  • Target user
  • Search intent
  • Main topic
  • Supporting headings
  • What competitors are missing
  • CTA
  • Internal link opportunities

But a brief shouldn’t turn the writer into a robot.

28. You may need to question the client’s brief too

The client says, “We’re a luxury brand.” But these may be saying something completely different:

  • The site
  • Prices
  • Images
  • Product presentation
  • Social media

The SEO specialist’s job isn’t to carry out what the client says without questioning it. Sometimes we need to ask politely, “Do users really see the brand this way?”

The right strategy can’t be built on a wrong assumption.

29. Bringing the sales team into SEO meetings is very useful

Especially on B2B projects. The sales team knows:

  • What do customers ask?
  • Why don’t they buy?
  • Which product gets attention?
  • Which competitor are we compared to?
  • Which objection keeps coming up?

All of this is SEO data.

Sometimes the best keyword research can come out of a 30-minute meeting with the sales team.

30. Sharing data with the Google Ads team is also very valuable

Google Ads doesn’t directly raise organic rankings. But the Ads team can have very valuable data. For example:

  • Which query converts?
  • Which landing page works?
  • Which product is in demand?
  • Which copy gets clicks?

You can get some learnings on the Ads side much faster than the months they might take in SEO.

I think SEO and Ads working completely disconnected from each other is a serious loss of data.

31. Test SEO changes where you can

The outcome of no SEO decision is guaranteed.

For example, we change a title. Will CTR go up? We change the content structure. Will rankings go up? We add price information to a category. How will Google evaluate it?

On some large sites, controlled SEO tests can be run. For example, a test group and a control group can be created from similar groups of pages.

In SEO, instead of “I think it’s better this way,” it’s very valuable to verify with data whenever possible.

32. Hypothesis thinking works on small sites too

You may not have enough pages to run an A/B test. You can still work like this:

Hypothesis: If we add a section on this page that better meets user intent, visibility will increase.

Then you track:

  • Date of the change
  • Before
  • After
  • Impressions
  • Clicks
  • Average position

That way you don’t forget why you did the work.

33. You need to give each change enough time

We changed a title today. Saying “It didn’t work” tomorrow is usually too early.

These can take time:

  • Google recrawling the page
  • Processing the change
  • User data building up

But the opposite is also true. Defending a change made 6 months ago with “Let’s wait a bit longer” can be pointless too.

In SEO, how you read timing is very important.

34. Track competitors, but don’t copy them

Just because a competitor publishes 5,000 pieces of content, opens a page for every city and gets backlinks every day doesn’t mean we have to do the same.

Maybe:

  • Their site is 15 years old.
  • Their team is 30 people.
  • Our budget is different.
  • Our user intent is different.

Competitor analysis isn’t “They did it, so let’s do it too.” It’s the question “Why does it work, and what does it mean for us?”

35. You need to turn Google updates into action too

Google released a core update. Everyone is talking about it on X. But what will we do for the client? I think that’s the real question.

You don’t need to change the site after every Google announcement. First you need to look at:

  • Were we affected?
  • Which area was affected?
  • What happened across the industry?
  • Is there enough data?

SEO management isn’t following the news.

It’s turning the news into the right action.

36. When a problem is solved, you also need to find the root cause

noindex was accidentally added to the site. We removed it. Problem solved. But why did it happen?

  • A theme update?
  • A plugin?
  • The deploy process?
  • A manual error?

If we don’t fix the root cause, the same problem will come back.

That’s why instead of just saying “Fixed,” you also need to ask “What will we do so it doesn’t happen again?”

37. That’s why SEO checklists should be living documents

We had a new problem. For example, the Analytics code disappeared. We solved it. Then we can add it to the checklist.

On another project we had a sitemap cache problem. We can add that too.

Over time, the checklist grows from real experience.

I think a good SEO operation:

Turns every mistake into a new rule for the system.

38. You also need to tell the client you don’t have to do everything

The audit found 100 problems. Solving all of them may not make sense.

For example, if there’s a problem that takes 100 hours to fix but has almost no effect on SEO, you can put it on hold.

The SEO specialist’s job isn’t just finding errors.

It’s saying which errors are worth fixing.

39. Budget is part of the strategy too

The client has no development team, a low content budget and no backlink budget. But we prepared a 40-item roadmap. That’s nice in theory. In practice it’s useless.

An SEO strategy should be doable with the resources available.

With a smaller budget, we can focus on:

  • The highest-impact areas
  • Existing content
  • Critical technical issues
  • Low-effort opportunities

40. On large teams, SEO’s job is partly coordination

On large projects, the SEO specialist doesn’t do every task themselves.

  • The developer writes code.
  • The editor publishes content.
  • The designer prepares visuals.
  • The PR team gets news out.
  • The data team produces reports.
  • The product team builds features.

SEO’s job is to understand how each of these affects organic visibility and to bring the right people together around the same goal.

That’s why, as the project grows, SEO turns into technical expertise + coordination.

41. Good SEO management is a continuous cycle

I think we can sum up SEO work in its simplest form like this:

Measure → Find the problem → Prioritize → Implement → Verify → Measure → Repeat

There’s no end to it. Because:

  • The site changes.
  • Google changes.
  • Competitors change.
  • Users change.
  • The product changes.

SEO has to change too.

In short

Managing SEO work well isn’t:

  • Producing the most content
  • Getting the most backlinks
  • Preparing the longest to-do list

It’s finding the right problem and doing the right work at the right time.

Sometimes the most important task may be producing new content. Sometimes fixing a canonical. Sometimes reducing the wrong traffic. Sometimes getting the site back up. And sometimes collecting a bit more data without changing anything.

There are lots of tools in SEO. There’s even more work you could do.

The hard part is:

Deciding which one to do today.

I think that’s exactly the essence of SEO management.

Previous: Chapter 40: SEO for Marketplaces, Classifieds and Large Database Sites · Contents · Next: Chapter 42: A Holistic View of SEO

This chapter was first published in Turkish on X (October 21, 2026).