Discussion
  • Enterprise SEO

Legal or brand teams reject title and copy changes. How do you put a revenue cost on the rejection in a way they accept?

Published 1 reply

Discussion starter: an enterprise SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.

Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.

1 reply

  • admin
    Admin
    Original poster

    The short answer is that a single “this rejection cost us $X” figure rarely lands, because legal and brand teams are trained to discount numbers built by the person who wants the change. What gets accepted is a range built from the company’s own data, with assumptions they can inspect and change, expressed as gross margin per month of delay, set beside the specific risk they are protecting against. Pair it with a limited, reversible test they can approve without accepting the full risk.

    The goal is not to beat legal. It is to move the decision to the person who owns both the revenue and the risk, usually a commercial or category lead, with an honest estimate on the table. Sometimes that estimate will show the change is not worth fighting for, and saying so is what makes the next estimate credible.

    Why the usual SEO forecast gets rejected

    Most rejected business cases share three weaknesses. They use industry CTR curves that do not match the company’s own search results pages, which now vary with ads, AI Overviews, shopping units and brand versus non-brand intent. They show only upside, which reads as advocacy. And they ask the reviewer to accept a personal, concrete risk (a misleading claim, a trademark issue, an off-brand title) in exchange for a diffuse, probabilistic gain that someone else gets credit for.

    That asymmetry is the real problem. A lawyer who approves a claim that draws a regulator complaint owns that outcome. A lawyer who blocks a title change that might have produced more clicks owns nothing, because the lost clicks are invisible. Your job is to make the second cost visible and owned, without overstating it.

    Two facts that change the conversation

    Title changes can lose. SearchPilot’s published title tag tests include clear wins and clear losses: in one test, organic traffic to the variant pages “dropped by 16 percent at the 95 percent confidence level”, while other title changes produced gains. Their summary is that “Even the smallest changes to a title can move the needle significantly, and the only way to know for sure is to test”. Those figures belong to those sites and tests, and they will not transfer to yours. The useful point for legal is that your forecast should include a downside scenario, because leaving it out is what makes SEO forecasts look like sales pitches.

    Google may not show the approved title anyway. Google’s title link documentation says title link generation “is completely automated” and draws on the title element, headings, prominent on-page text, anchor text and links pointing to the page. It lists boilerplate, inaccurate and outdated titles among the issues that lead Google to adjust a title link, and warns against keyword stuffing. Mandatory disclaimers and repeated legal boilerplate in titles are exactly the patterns that invite a rewrite. Check the live results: if Google is already replacing the legally approved title with an H1 or anchor text, the compliance control legal thinks it has does not exist in search results, and that is a risk argument they will listen to.

    Build the number in layers they can audit

    1. Affected pages and non-brand queries, last 3 to 12 months
    ↓
    2. Uplift range: low (including a loss), expected, high
    ↓
    3. Value per click: conversion rate × order or deal value × gross margin
    ↓
    4. Gross margin per month of delay, as a range
    ↓
    Is the expected value material next to the risk and the cost of the work?

    Layer 1: scope. Pull impressions, clicks and CTR from Search Console for only the affected pages, using the branded queries filter to exclude brand demand. People searching your brand will click whatever the title says. Use a recent baseline, because AI features have shifted CTR on many query types and AI Mode activity is counted in Search Console’s web totals.

    Layer 2: uplift. This is where credibility is won or lost. Take the assumption from the strongest evidence you have, state which tier it came from, and let the reviewer argue with it.

    Layer 3: value per click. Use the organic conversion rate for those pages, average order or deal value, and the gross margin figure finance already uses. Revenue overstates the cost of a rejection; margin is the number a CFO recognises.

    Layer 4: time. Express the result per month of delay. “This costs between a small loss and AUD 7,800 a month, most likely around AUD 3,100” invites a decision. “This cost us AUD 93,000 last year” invites a defence.

    Hypothetical example:

    A fashion retailer’s brand team requires category pages to use campaign names (“The Coastal Edit”) instead of product terms (“Women’s linen dresses”). The affected pages get about 2,000,000 non-brand impressions a month at 2% CTR, so about 40,000 clicks. Organic conversion is 1.8%, average order AUD 120, gross margin 45%, so each click is worth about AUD 0.97 in gross margin. Scenarios for descriptive titles and headings: low, a 5% loss in clicks (about minus AUD 1,900 a month); expected, an 8% gain (about AUD 3,100 a month); high, a 20% gain (about AUD 7,800 a month). The expected case is roughly AUD 37,000 a year in gross margin, with a real chance of a small loss. That is a number a brand director can weigh against the value of the campaign naming, and it is small enough that nobody feels ambushed.

    Where the uplift assumption comes from matters more than its size

    Evidence for the uplift Strength How a sceptical reviewer will read it
    Your own past split test on similar templates Strongest Hard to dismiss: same site, same audience, a control group
    Your own before and after on comparable pages Moderate Acceptable if seasonality and updates are accounted for
    Pages on your site that already use the proposed pattern, compared at similar positions Moderate to weak Useful for direction, open to “those pages are different”
    Published split tests from other sites Weak for size, useful for direction and downside Shows the change can win or lose; does not size your effect
    Industry CTR-by-position curves Weakest Likely rejected, and rightly so

    Put it in their format, not an SEO report

    Legal teams think in likelihood and severity. Brand teams think in consistency and long-term equity. Neither reads traffic dashboards. A one-page decision record works better than a deck:

    Field What goes in it
    Change requested Exact current and proposed wording, and the pages affected
    Reason for rejection The specific rule or risk: claim substantiation, trademark, regulator guidance, or a named brand guideline
    Compliant alternatives tried Two or three variants written to avoid that risk
    Estimated cost of rejecting Gross margin per month as a range, with the evidence tier
    Estimated cost of approving Legal or brand’s own assessment of likelihood and severity
    Proposed test Scope, duration, metrics, stop rule, rollback plan
    Decision owner and review date The commercial lead who accepts the trade-off, and when it is revisited

    The “reason for rejection” field does most of the work. Asking “which specific claim or rule is the problem?” often turns a blanket no into a narrow objection. A regulated-industry lawyer may object to “cheapest” or “guaranteed” but have no issue with the product term the SEO case actually depends on. Consumer law on misleading claims is a real constraint; a vague sense that SEO copy is risky is not, and the record separates the two.

    Offer a bounded test instead of a permanent change

    1. Scope. A randomised subset of similar templated pages (categories, locations, products) gets the new wording, and a comparable subset stays as it is. This only works with enough pages and traffic for the difference to be detectable; a handful of pages will not produce a trustworthy result.
    2. Wording. Legal approves the variant wording in advance. The test is not a loophole; it is a way to limit exposure while producing evidence.
    3. Metrics. Primary: non-brand organic clicks to the variant group against the control. Secondary: organic conversions, and whether Google displays the new title or rewrites it.
    4. Duration and stop rule. Set a fixed window in advance, typically several weeks, and agree the rollback trigger before launch. Record the launch with Search Console annotations and note any core update in the window.
    5. What changes the decision. A clear gain moves the change to the decision owner with evidence. No detectable effect or a loss means you drop the request and record why.

    Where pages are not templated (a handful of flagship pages), a time-based comparison against a seasonal forecast is the fallback. Say plainly that it is weaker evidence.

    Watch for this:

    The fastest ways to lose the room: using revenue instead of margin, including brand clicks, presenting the high case as the forecast, annualising a guess as if it were booked, and framing the document as “legal cost us money”. Any one of these gives the reviewer a legitimate reason to dismiss the whole estimate.

    A practical position

    If I were making this case, I would pick the one rejected change with the most non-brand impressions behind it, build the four-layer range with finance’s margin figure, include a loss scenario, and bring it to legal or brand as a question: which specific risk is the blocker, and would you approve a limited test with wording you sign off? Then I would let the commercial owner decide with both costs on one page. If the expected value is small next to the risk, I would drop it and say so. A team that sees you walk away from weak cases is far more likely to accept your number on the strong ones.

    Need help with this on your own site?

    Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.

    See SEO services

Add a reply

Replies are open to approved members. Log in or apply to join.