Blog / Web management /

Saying no to SEO requests that won’t help

“Can we add this keyword to every page?”

I get why people ask. They want more visibility, not a worse website. But a blunt “no” starts an argument, and an easy “yes” leaves you with confusing pages and extra upkeep.

In my role at Nivonix, I try to do three things: understand the goal, explain what the request would change, and show the trade-off. If the idea won’t help, I say so plainly and suggest something better. Saying no is part of managing client sites, but it needs reasoning the other person can follow.

Find the goal behind the request

My first question is always what they hope to achieve. A specific ranking? Better product discovery? A new offer to announce? A reaction to a competitor? The tactic they’ve asked for is often just a guess at how to get there.

Clarify the audience and the evidence. Is there a query, customer question, technical issue or business priority behind the request? If the request is based on a screenshot or a competitor’s page, check the context before agreeing that it applies to this site.

Don’t make them defend themselves. They may know something you don’t. A calm question can surface a product change, a customer complaint or a management priority that should shape the plan.

Explain the trade-off in plain language

Describe what the request would do to the site. The same keyword in every title makes them awkward and less useful. A page for a location you don’t serve misleads visitors. Another app may duplicate a feature and add scripts. Be specific about the effect, rather than waving it away as “bad for SEO”.

Separate facts from predictions. Duplicate page purposes or an unavailable service are concrete problems. Be more careful about saying a change will make rankings rise or fall. Say what you can verify and what’s still uncertain.

Use examples from the site only when they are safe to share and relevant. Do not reveal other clients’ data or imply a result that has not been confirmed. A hypothetical example can make a trade-off clear without turning it into a client story.

Offer a route forward

A refusal works better when the project keeps moving. Suggest a smaller test, a page audit, some customer research, or another route to the same goal. If there’s no useful substitute, say what evidence would change your mind.

For example, instead of creating several near-identical pages, you might review whether an existing page answers the intended query. Instead of adding a tracking script, verify whether the event is already measured. Instead of changing every title, test the pages with the clearest mismatch first.

Keep the proposal proportionate. Do not respond to a small request with a large consulting framework if a short check will answer it. State who needs to approve the work and what information you need to proceed.

Make priorities visible

Teams have limited time. Explain how the request compares with other work, such as fixing a broken journey, improving important product information or resolving an indexation issue. A prioritisation list helps clients see that “not now” is a resource decision, not a refusal to help.

Record the agreed scope and the reason for a decision. This is especially useful when several people are involved or when the same request comes back later. If the recommendation changes because new evidence appears, update the note rather than treating the original decision as permanent.

Don’t hide behind jargon. “It could cause cannibalisation” helps less than “these two pages answer the same search and would compete to be the result.” Use the term if it helps, then explain it.

Know when to escalate

Some requests involve legal claims, privacy, security, product safety or commercial promises. SEO staff should not approve those details alone. Ask the responsible person to verify the claim before publishing, and pause the page if the uncertainty could mislead visitors.

If a request changes a technical system, check whether it affects DNS, checkout, tracking or access controls. Bring in the person who owns that layer. A fast SEO change can have wider consequences when it touches shared templates or customer data.

When a disagreement persists, return to the goal and evidence. If the decision belongs to the business owner, document the risk and recommendation, then follow the agreed approval process. Do not silently make a change you were asked to avoid, and do not promise a result you cannot control.

Keep the relationship collaborative

Clients and colleagues need to trust that their questions will receive a thoughtful answer. Acknowledge the outcome they want, explain your reasoning and invite them to share information that could change the recommendation. The aim is not to win an argument; it is to make a better decision together.

A short written follow-up can prevent misunderstanding: request, goal, recommendation, reason, agreed action and owner. Keep the language neutral. Avoid recording frustration or private details that are not needed for the work.

For update conversations, see How I talk to clients during a core update and How I report SEO results to clients. For prioritising technical work, read How to audit a Shopify store in an afternoon.

Next time a request feels wrong, ask what result it’s meant to produce before you reject it. What alternative would move that goal forward?