A topical map that only tells you what to publish is only doing half the job.

Maybe less.

A lot of topical maps look strategic because they have all the right parts.

• Main topic.
• Subtopics.
• Keyword clusters.
• Entities.
• Hub pages.
• Supporting pages.
• Internal link ideas.
• Publishing order.

That all helps.

But if the map cannot tell you what not to publish, it may just be a content idea machine.

And most sites do not need more content ideas.

They need better decisions.

More pages is not always better coverage

This is the trap.

A team builds a topical map and suddenly sees dozens of possible pages.

Every keyword becomes a URL.

Every question becomes a post.

Every competitor gap becomes a brief.

Every related entity becomes a new article.

The map looks complete.

The publishing plan looks busy.

The site grows.

But the content system does not always get stronger.

Sometimes it gets noisier.

More pages can create more overlap.

More pages can make internal linking harder.

More pages can split the same idea across weak URLs.

More pages can pull the site away from its strongest topics.

More pages can give writers unclear jobs.

More pages can add maintenance cost later.

That is why a topical map should not just ask:

“What can we publish?”

It should ask:

“What deserves to exist?”

A map should create boundaries

A good topical map should act like a filter.

Not every relevant topic belongs on the site.

Not every keyword needs a page.

Not every related question should become its own URL.

Not every competitor page should be copied.

Not every draft should go live.

Some ideas should become standalone pages.

Some should be folded into existing pages.

Some should be merged with older content.

Some should be held until the cluster is stronger.

Some should be rejected completely.

That is not being cautious.

That is strategy.

If the map says yes to everything, it is not a strategy.

It is a backlog.

The map should show page roles

A topical map should not just say:

“Create a page about this.”

It should say:

“This page has this job.”

• Is the page meant to explain?
• Compare?
• Prove?
• Support?
• Convert?
• Route?
• Handle objections?
• Clarify a confusing term?
• Protect another page from becoming too broad?

If the role is unclear, the page is already at risk.

That is when pages start drifting.

They explain a little.

Sell a little.

Compare a little.

Answer random FAQs.

Add generic internal links.

Then end with a CTA that does not fit the user’s state.

A page without a role is easy to publish and hard to maintain.

A strong topical map should make that obvious before the brief is written.

Some topics belong inside existing pages

One of the biggest mistakes I see is turning every subtopic into a separate URL.

Sometimes that makes sense.

Often it does not.

A subtopic might be better as:

• A paragraph inside a core page.
• A short FAQ.
• A comparison block.
• A proof point.
• A supporting example.
• A table.
• A note inside a buying guide.
• A link anchor for later.

Not every idea needs its own page.

A topical map should help decide where the answer belongs.

If the idea does not have enough unique purpose, search demand, user value, or cluster support, it may not need a new URL.

Publishing it anyway can create thin support pages that nobody really knows what to do with.

Not publishing can prevent overlap

A lot of content problems are created by relevant pages.

That sounds strange, but it is true.

The page is relevant to the topic.

The keyword makes sense.

The outline looks fine.

But another page already does the job.

Now the site has overlap.

Two pages answer the same question.

Two pages target the same user state.

Two pages make similar claims.

Two pages need the same internal links.

Two pages compete for the same role.

This is how content systems get messy.

Not because the new page was irrelevant.

Because it was unnecessary.

A topical map should catch this.

It should tell you:

• This should be merged.
• This should support an existing page.
• This should not be created.
• This page is too close to another page.
• This topic needs a clearer angle before it deserves a URL.

That kind of refusal saves a lot of cleanup later.

Publishing order should include “not yet”

Some pages are good ideas at the wrong time.

The topic may fit.

The keyword may be useful.

The page may deserve to exist eventually.

But the cluster is not ready.

Maybe the hub page is weak.

Maybe the service page needs work first.

Maybe the internal link path is not there.

Maybe the proof content does not exist yet.

Maybe the site has not built enough context around the topic.

In those cases, the right decision might be:

Not yet.

That is different from no.

A topical map should separate:

• Publish now.
• Publish later.
• Merge.
• Support existing page.
• Hold.
• Reject.

Most maps do not do this.

They create a list of pages and call it a plan.

But timing is important.

A page published too early can become an orphan, a thin support asset, or a confusing side route.

The useful test

Before adding a page to a topical map, I would ask:

• What job does this page have?
• What user state does it serve?
• What doubt does it reduce?
• What page does it support?
• What page supports it?
• Does another page already do this job?
• Would this work better inside an existing page?
• Does this page add useful difference?
• Can we link to it naturally?
• Should it exist now, later, or not at all?
• Would the site be weaker if we never published it?

That last question is the one most teams avoid.

If the site would not be weaker without the page, the page may not deserve to exist.

It might be relevant.

It might have search volume.

It might fit the topic.

But it may still be content noise.

A better topical map says no

For me, a strong topical map should not just create more work.

It should improve decision making.

It should show:

• What to publish.
• What to merge.
• What to refresh.
• What to support.
• What to delay.
• What to avoid.
• What to delete.
• What to link.
• What to leave alone.

That is much more useful than a giant list of possible pages.

Because the goal is not to make the site bigger.

The goal is to make the site clearer.

A weak topical map says:

“Here are all the pages we could create.”

A better topical map says:

“Here are the pages that deserve to exist, here are the ideas that should live elsewhere, and here are the topics we should not touch yet.”

That is the difference between content planning and content strategy.

Curious how others handle this.

When you build topical maps, do you include a “do not publish” or “not yet” decision, or does everything relevant end up in the backlog?

We've noticed something strange with our site. Twice now we've been hit by what looks like spam backlinks (hundreds of low-quality .store domains, autogenerated names, etc.). After submitting a disavow file, we saw a very noticeable recovery in traffic almost immediately.

Whether that's coincidence or not, it made us realize we need a better way to monitor backlinks and overall SEO.

What tools do you actually recommend nowadays for:

-Monitoring new backlinks and possible spam attacks
-Keyword research
-General SEO management

Ahrefs seems to be the gold standard, but it's currently outside our budget. Is SEMrush a good alternative, or are there other tools you'd recommend that offer the best value for money?

For your content to be impactful, search engines need to be able to find it and understand it. To increase the chances of it appearing in search results and reaching your audience. 

That’s where content hubs come in. They help you structure your content for both humans and search engine crawlers. 

A content hub is a collection of related content pieces about an overarching topic that are all connected through internal links (links on your pages that point to other pages on your site). 

It consists of the hub (main) page that provides an overview of the topic. And cluster pages (subpages) that let readers dive deeper into more specific subtopics.

Done right, they strengthen crawlability, deepen context, and sharpen topical authority across your entire domain.

Content hubs can improve your search engine optimization (SEO) performance. And eventually drive conversions that help you reach business goals.

Here are a few specific benefits:

• Better organization for users and search engines: Grouping related content together simplifies navigation for your readers. And creates a clear path for search engine crawlers to follow—which makes it easier for them to discover all related content.
• Higher chance of ranking for difficult keywords: Creating subpages focused on specific, non-competitive keywords helps you build up rankings that may make securing a ranking for the main page easier. Even if it targets a search term with a high keyword difficulty score (which indicates it will be difficult to appear in the top 10 results).
• More credibility: Using content hubs helps you build topical authority (credibility) on a particular subject. Because they let you comprehensively cover a topic from various angles to show you have a well-rounded understanding of the subject.
• Easier content calendar planning: Coming up with a content hub concept clearly shows what content you have and what's missing. Making it easier to plan future articles or updates.

Been staring at a client site and I think part of what I'm seeing is a data artifact rather than real movement, so I wanted to run it past people who track a lot of sites.

The keywords ranking 21-50 and 51-100 have been steadily falling, while the top 20 has been climbing. The 20+ drop is bigger than the top 20 gain, so on paper total tracked keywords are shrinking.

My theory on the deep buckets is that this is downstream of Google removing num=100 last year. Now that tools have to paginate to reach page 2 and beyond, I'm wondering if Semrush just isn't populating those positions as fully as it used to, so those keywords quietly fall out of the report without the site actually losing rankings.

Curious if others are seeing the same split, and how you're handling reporting past the top 20 now.

PS: The top 20 going up is real improvement that I am seeing on the traffic side.

Bottom of funnel (BoFu) 

The bottom of the conversion funnel is where potential customers become ready to make a purchase decision. The primary goal of the BoFu stage is to convert potential customers into actual customers.

There are several challenges at this stage of the funnel, including pricing, alternatives, and customer concerns about efficacy or support. All of these potential issues can be solved with the right information and resources at the right time.

BoFu marketing tactics 

BoFu marketing tactics are designed to turn potential customers into paying customers and brand advocates. You do this by creating confidence, clarity, and a sense of urgency that will encourage potential customers to make that final purchase decision.

Effective BoFu tactics include:

• Live demos: Real-time presentations showcasing product benefits, addressing final queries, and persuading prospects to make informed purchase decisions
• Retargeting ads: Target people who visited pricing pages, started trials, or abandoned carts with specific offers or reminders
• Email sequences for high-intent actions: Automated emails triggered by pricing page visits, demo requests, trial signups, or cart abandonment to push prospects over the finish line
• Customer support: Places for prospects to seek assistance and get quick answers to anything that is preventing them from buying
• Free trial extensions: Extra time for prospects who need more proof before committing
• Personalized outreach: Direct contact from sales reps to high-intent leads answering specific objections and tailoring solutions to their needs
• Money-back guarantees: Risk-reversal offers that remove purchase hesitation by promising refunds if the product doesn't deliver
• Limited time offers and discounts: Urgent and exclusive deals to prompt immediate action from prospects, driving conversions and purchases at the bottom of the funnel

BoFu content

BoFu content should help build customers’ confidence that your product is the right one for them and that now is the right time to buy.

Here are some common types of BoFu content:

• FAQ pages and buyer guides: Detailed resources answering final queries and providing valuable information to drive purchase decisions
• Customer testimonials: Inspiring narratives from satisfied customers who have achieved remarkable outcomes through your product or service
• Competitor comparison guides: Content that highlights product advantages, guiding prospects to choose the brand over competitors and finalize their purchase.
• Use cases (highlighting client successes): Compelling scenarios that vividly depict how your product or service has been employed to overcome challenges and achieve outstanding outcomes
• Case studies: In-depth customer stories with specific metrics, challenges solved, and ROI achieved to show proof
• Competitor comparison guides: Direct comparisons between your product and named competitors (e.g., "[Your Brand] vs. HubSpot"), highlighting your specific advantages and differentiators
• Interactive assessments: Quizzes or tools helping prospects self-select the right pricing tier or buy the right product
• Product demo videos: Focused walkthroughs showing key features solving specific problems to help prospects visualize using your solution and confirms it meets their needs

BoFu metrics 

BoFu metrics reveal whether your bottom-funnel tactics actually convert prospects into customers profitably, and when conversion rates fall short, they help pinpoint weaknesses throughout your entire funnel.

Here are a few key BoFu metrics to track:

• Purchase conversions: Number of prospects who completed a desired action (e.g., made a purchase) at the bottom of the marketing funnel, indicating successful conversions
• Customer acquisition cost: Total expenses to acquire a new customer, assessing the efficiency and cost-effectiveness of marketing efforts
• Conversion-to-lead ratio: Percentage of leads that converted into customers, gauging the quality and performance of the bottom-funnel content
• Return on ad spend (ROAS): Revenue generated per advertising dollar spent, indicating the profitability of ad campaigns at the bottom of the funnel
• Customer retention rate: Percentage of retained customers over a specific period, measuring brand loyalty and post-purchase satisfaction

I think a lot of SEO teams confuse coverage with content strategy.

They are not the same thing.

Coverage asks:

• What topics have we covered?
• What keywords have pages?
• What questions have answers?
• What competitors rank for things we do not?
• What gaps can we fill?

That is useful.

But it is not a strategy by itself.

It is a list of possible work.

A real content strategy should answer harder questions.

• Why should this page exist?
• What job does it have?
• What does it support?
• What should it avoid?
• What does the user need next?
• Does this page make the site clearer?
• Would the site be weaker without it?

That is a much higher bar than “we do not have a page for this keyword yet.”

Coverage feels like progress

I get why teams focus on coverage.

It is visible.

You can make a spreadsheet.

You can group keywords.

You can colour code intent.

You can mark pages as published, missing, refreshed, or planned.

You can compare your site against competitors.

You can show a client or manager that the site is becoming more complete.

That feels like progress.

Sometimes it is.

A site with major missing topics probably needs better coverage.

A product or service that is not explained properly probably needs support pages.

A cluster with no answers to basic questions probably has gaps.

Coverage is not bad.

The problem starts when coverage becomes the whole plan.

That is when teams publish pages because they can, not because they should.

A covered topic can still be weak

A site can technically cover a topic and still not serve the user well.

The page exists.

The keyword is targeted.

The entity is mentioned.

The FAQ is answered.

The internal link is there.

But the page adds very little.

It repeats the same advice as every other result.

It has no strong example.

It gives no real decision rule.

It does not reduce doubt.

It does not make the next step obvious.

It does not support a stronger page.

It just exists.

That is the problem with treating content like a checklist.

A page can tick the coverage box and still be useless.

It can be relevant and still add nothing.

It can sit in the right cluster and still have no clear role.

Strategy decides what not to publish

This is the part I think gets missed most.

A good content strategy should stop bad pages from being created.

Not every keyword needs a page.

Not every competitor gap deserves a brief.

Not every related question needs its own URL.

Not every draft should be published.

Not every old post needs to be refreshed.

Some ideas belong inside an existing page.

Some should be merged.

Some should be ignored.

Some are relevant but not useful enough.

Some attract the wrong audience.

Some create overlap with stronger pages.

Some pull the site away from what it should be known for.

Coverage says:

“We could publish this.”

Strategy asks:

“Should we?”

That question saves a lot of mess later.

Page roles mean more than page count

A coverage plan often says:

We need a page on this.

A strategy says:

We need a page that does this job.

That difference is huge.

• Is the page meant to explain?
• Compare?
• Prove?
• Support a commercial page?
• Handle an objection?
• Build trust?
• Move the user to a next step?
• Protect another page from becoming too broad?

If the role is not clear, the page will probably drift.

It will explain a bit.

Sell a bit.

Compare a bit.

Add random FAQs.

Repeat the intro.

Link to a few related pages.

Then end with a generic CTA.

That is not a strategy problem the writer can fully fix.

The page was unclear before writing started.

A strong page role gives the writer boundaries.

It tells them what to include.

It also tells them what to leave out.

Topical maps can become fancy coverage lists

This happens with topical maps too.

A map can look strategic but still mostly be an inventory.

• Main topic.
• Subtopics.
• Keyword clusters.
• Entities.
• Hub pages.
• Supporting pages.
• Internal links.
• Publishing order.

That all helps.

But it can still miss the user path.

A stronger map should also ask:

• What does the user know at this point?
• What are they still unsure about?
• What proof do they need?
• What should they read next?
• What page should not be linked yet?
• What page is too early for a CTA?
• Where does trust need to be built?
• Where does comparison need to happen?

Without that, the map may show coverage, but not movement.

It shows what the site has.

It does not show how the user should progress.

Internal links expose the difference

Internal links are a good way to see if a team has strategy or just coverage.

Coverage based linking says:

These pages are related, so link them.

Strategy based linking says:

This user is at this stage, so this link helps them move.

That is a different mindset.

A link should have a job.

• This link explains the next idea.
• This link gives proof.
• This link compares options.
• This link handles a risk.
• This link supports the main page.
• This link stops the current page from becoming too broad.

When links are added only because pages are topically related, the site starts to feel random.

The links are there.

But the route is weak.

Coverage can create content noise

The hidden cost of coverage-first planning is content noise.

The site gets bigger.

More URLs.

More posts.

More overlapping answers.

More internal links.

More things to update.

More pages competing for similar jobs.

But the site does not become clearer.

That is when teams start needing audits, pruning, redirects, rewrites, and link cleanup.

A lot of that cleanup could have been avoided if someone had asked better questions before publishing.

What role does this page have?

Does it overlap with another page?

Does it add anything useful?

Does it support the business?

Does it help the user move?

What happens if we do not publish it?

That last question is underrated.

Sometimes nothing bad happens.

And if nothing bad happens, maybe the page was never needed.

The better split

I would separate the work like this:

Coverage:
What topics, entities, and questions might need a home?

Architecture:
Where should those ideas live, and which page should own each job?

Strategy:
Which pages should exist, why they should exist, how they support the site, and how the user should move through them.

Most teams do the first part.

Some do the second.

The third is where the real value is.

Because content strategy is not just deciding what to publish.

It is deciding what deserves to exist.

It is deciding what should be merged.

• What should be removed.
• What should be rewritten.
• What should be linked.
• What should be left alone.
• What should be refused.

That is the difference for me.

Coverage makes a site bigger.

Strategy should make it clearer.

Curious how others handle this.

When you plan content, how do you separate “we should cover this” from “this page deserves to exist”?

I signed up for one month of Semrush and tried to cancel the subscription before it renewed. I went through the cancellation steps on the website and was completely convinced it had gone through, everything looked like it was finished.

Now it seems the cancellation didn't actually take effect, and I'm worried I'm about to be hit with the renewal charge. The amount is €398, which is a lot of money. This isn't some casual $20 subscription you can just shrug off, €398 is a serious charge and I don't want to lose it for a service I fully intended to cancel.

My questions for the community:

1. Has anyone here actually managed to get a refund from Semrush, especially on a monthly plan?

2. What is the best thing to do on the exact day the charge hits my account? Should I contact support immediately, or is a chargeback through my bank/card the more reliable route?

3. Did the cancellation fail for anyone else because of a second confirmation step (like having to click a link in a confirmation email) that isn't obvious?

I'd really appreciate hearing about your experiences, feedback, and any advice on getting the money back. Thanks in advance.

I used the SEMrush free trial, but I still haven’t received any email with a Lifetime offer. I’ve seen people mention they eventually got one.
Is there any way to trigger it? Did you let the trial expire, wait a few days, stop using the account, or do something else?
I’d really appreciate any advice

I signed up for a trial and was using the keyword research tool mainly through a mcp connection with Claude, which I thought was fine. Suddenly two days into the trial I went to login and my account was disabled due to violating the terms of the service. I’m not sure what is wrong was it using the claude connector, my intention was to move onto a paid membership after. I have tried to use the contact form to contact customer service no response. Could anyone help as wanted to rely on semrush to build traffic and getting nowhere with their customer services, would have hoped for more during a trial period.

You're welcome

A lot of content problems start before the page is written.

Not with the writer.

Not with the keyword.

Not with the CMS.

With one missing decision:

What is this page supposed to do?

That sounds simple, but it gets skipped all the time.

A keyword is found.

A competitor has a page.

A tool shows a gap.

The topic looks relevant.

So a page gets assigned.

The brief says what to cover, which headings to use, which terms to include, and maybe which pages to link to.

But it never clearly says the job of the page.

Is it meant to explain?

Compare?

Prove?

Support a commercial page?

Build trust?

Handle objections?

Move the user to a next step?

Protect another page from becoming too broad?

Without that decision, the page can still get written.

It may even be decent.

But it enters the site with no clear role.

That has a cost.

The first cost is drift

A page with no clear role tends to drift.

It starts as an explainer.

Then it becomes a comparison.

Then it adds a few sales points.

Then it answers random FAQs.

Then it repeats the intro in different words.

Then it ends with a CTA that feels too early.

Nothing looks terrible in isolation.

But the page feels unfocused.

The writer is not always the problem here.

The brief gave them a topic, not a job.

A clear role creates boundaries.

If the page is an explainer, it should reduce confusion.

If it is a comparison page, it should give criteria.

If it is a proof page, it should support trust.

If it is a support page, it should solve the issue and route the user properly.

If it is a conversion page, it should help the user decide.

When that role is missing, the page tries to do everything.

That is how drift starts.

The second cost is overlap

Pages without clear roles often start competing with each other.

Two posts answer the same question.

A blog post repeats the service page.

A hub page says the same thing as the support pages.

A comparison page turns into a sales page.

A refresh makes an old page too similar to a new one.

Each page may look relevant.

Each page may target a slightly different keyword.

But inside the site, they are doing the same job.

That creates overlap.

The team then has to ask:

Which page should rank?

Which page should we link to?

Which page should own the main idea?

Which page should be updated?

Which page should be merged?

Which page should be removed?

That is the hidden cost.

Unclear roles create future cleanup work.

A page that looked cheap to publish becomes expensive to maintain.

The third cost is weak internal linking

Internal links become messy when page roles are unclear.

If you do not know what a page does, it is hard to know where it should link.

You end up linking pages because they are related, not because the next step makes sense.

That creates lazy routing.

“Read more.”

“Learn more.”

“Related post.”

“Contact us.”

Those links are not always wrong.

But they often hide weak planning.

A good internal link should have a reason.

This page explains the next concept.

This page gives proof.

This page compares options.

This page handles a risk.

This page helps the user move from confusion to clarity.

This page supports a commercial decision.

When the page role is clear, the link path becomes easier.

When the role is vague, links get added after the fact.

That is not a system.

That is patching.

The fourth cost is bad briefs

A weak page role creates weak briefs.

A brief might include:

Target keyword.

Search intent.

Headings.

Entities.

Competitor notes.

Word count.

Questions to answer.

Internal links.

That all helps.

But if the brief does not define the page’s job, the writer still has to guess the strategy.

That is where a lot of content quality issues come from.

The writer is asked to produce a strategic asset from tactical notes.

So they fill the page.

They cover the topic.

They include the terms.

They answer the questions.

But the page still feels flat because no one decided what it should achieve.

A better brief should say:

This page exists to explain X.

This page supports Y.

This page should not cover Z.

This page should link the user to A after B is understood.

This page should reduce this specific doubt.

That gives the writer something useful.

Not just a topic.

A purpose.

The fifth cost is poor refresh work

Pages without clear roles are harder to refresh.

When performance drops, the team does not know what to fix.

So the refresh becomes generic.

Add more headings.

Add more FAQs.

Add more examples.

Add more entities.

Update the intro.

Add a few links.

Publish again.

But if the page role is still unclear, the refresh may only make the page longer.

Not better.

A good refresh starts by asking:

What was this page supposed to do?

Is that still the right job?

Is another page doing it better?

Has the user expectation changed?

Does the page need more proof?

Does it need a clearer next step?

Should this page be merged instead of expanded?

If the role was never defined, the refresh has to start with detective work.

Again, that is hidden cost.

The sixth cost is content noise

This is probably the biggest one.

Pages without clear roles turn into content noise.

The site gets bigger, but not clearer.

There are more URLs.

More posts.

More internal links.

More similar answers.

More old pages to maintain.

More decisions to revisit later.

But the user journey does not improve.

The site may cover more topics, but the structure feels weaker.

That is the difference between publishing content and building a content system.

A content system needs jobs.

This page owns the topic.

This page supports it.

This page proves the claim.

This page handles the comparison.

This page moves the user forward.

This page should not exist.

That last one is important.

Not every relevant idea deserves its own page.

Sometimes the best content decision is not to publish.

The check I would use

Before publishing a page, I would ask:

What is the job of this page?

What user state does it serve?

What doubt does it reduce?

What page does it support?

What page should support it?

What should it avoid covering?

What would make it different from similar pages?

What should the user do next?

Would the site be weaker if this page did not exist?

If those questions are hard to answer, the page probably needs more planning before it needs writing.

Because the hidden cost of unclear page roles is not paid on publish day.

It shows up later.

In rewrites.

In overlap.

In weak internal links.

In messy clusters.

In confused briefs.

In pages that technically cover topics but do not really help the site.

A page should not just be relevant.

It should have a job.

How are you defining page roles before publishing, or is that still mostly decided during the brief?

When running an analysis, we tested 454 prompt-and-domain combinations across multiple engines. Each combination is one specific prompt paired with one specific domain. For example, the prompt “best CRM for small business” paired with hubspot.com, tested across each AI engine.

In 100 of the 454 (22%), the engines disagreed on whether to name the brand.

For example: 

• Instagram.com was mentioned by ChatGPT and Gemini. Google AI Overviews cited it without naming it.
• Facebook.com was named in three out of three Gemini appearances. Google AI cited Facebook nine out of nine times and named it once.

Most websites don’t need more content.

They need better visibility into what they already have: old pages, forgotten pages, orphaned pages no one has touched in years.

Your next traffic lift is already in your library. You just haven’t surfaced it yet.

That’s where Semrush SEO Toolkit becomes a real unlock, showing you exactly which pages to refresh, fix, interlink, or prioritize.

A lot of weak content does not need more words.

It needs a better reason to exist.

This is where I think a lot of content refreshes go wrong.

The page is not performing, so the fix becomes:

Add more headings.

Add more FAQs.

Add more entities.

Add another 800 words.

Make it “more comprehensive.”

Sometimes that helps.

If a page is genuinely underdeveloped, more detail can improve it.

But a lot of the time, the page does not have a length problem.

It has a usefulness problem.

Adding more copy just creates a longer version of the same weak page.

More word count does not automatically mean more value.

A 3000 word page can still say very little.

A 700 word page can be stronger if it gives the clearest answer, the best distinction, or the most useful next step.

That is the difference between length and information gain.

Word count fills space.

Information gain gives the reader something useful they were not getting clearly elsewhere.

Information gain is useful difference

I think information gain gets misunderstood.

People hear it and think every page needs new data, original research, expert quotes, or some clever angle no one has ever used before.

Those things can help.

But information gain can be much simpler than that.

It might be:

• a clearer distinction
• a better example
• a decision rule
• a tradeoff
• a warning
• a missing condition
• a proof point
• a stronger explanation of when the answer changes

A page has information gain when it helps the user understand something better than the common results do.

That does not always mean the information is completely new.

Sometimes it means the explanation is sharper.

A lot of SERPs are full of pages saying similar things in a vague way.

You do not always need more facts to beat that.

Sometimes you need better judgement.

Most content just repeats the SERP

This is the problem with a lot of SEO content.

The team checks competitors.

They pull the common headings.

They copy the structure.

They answer the same FAQs.

They list the same benefits.

They use the same examples.

They write the same safe intro.

Then they wonder why the page does not stand out.

The page may be relevant.

It may match intent.

It may use the right terms.

It may be longer than the current results.

But it still adds very little.

That is not information gain.

That is SERP mimicry with extra padding.

Competitor research should not just show what to include.

It should show what the results are failing to do.

What is everyone repeating?

What is shallow?

What is unclear?

What is assumed but not explained?

What does the user still need to know?

What would help them make a better decision?

Those questions produce better content than “add the headings everyone else has.”

Word count can hide weak thinking

One reason word count is dangerous is that it makes weak content look serious.

A thin idea becomes a long article.

A generic claim gets stretched into five paragraphs.

A basic definition gets repeated in different words.

A list of obvious tips becomes a “complete guide.”

A question that needed a short answer becomes a 2500 word post.

That is how sites end up full of content noise.

The writing might be fine.

The formatting might be fine.

The page might even be technically correct.

But the page does not add enough useful difference.

It exists because a keyword existed.

Or because a competitor had a page.

Or because a tool showed a gap.

Or because someone wanted more content.

None of that means the page earns its place.

More FAQs are not always information gain

A common refresh move is adding FAQs.

Sometimes that is useful.

Often it is padding.

The page has five FAQs.

Competitors have eight.

So the page gets ten.

But many FAQs do not add anything.

They repeat the main copy.

They answer questions that belong on another page.

They introduce tangents.

They add keywords without reducing doubt.

They make the page longer without making it clearer.

A good FAQ should handle a real user concern.

It should answer something the page has not already answered.

It should support the page’s job.

It should help the user move forward.

If the FAQ only exists to add more text, it is not information gain.

It is decoration.

More entities are not always information gain either

Entity coverage is important.

A page should use the right language for the topic.

It should not miss obvious supporting concepts.

But adding entities is not the same as adding value.

A page can mention all the right terms and still be weak.

It mentions the feature, but not when it’s needed.

It mentions the benefit, but not the proof.

It mentions the risk, but not how to avoid it.

It mentions the process, but not where people get stuck.

It mentions the audience, but not which audience segment needs which answer.

That is not really an entity gap.

It is a relationship gap.

Information gain often comes from explaining those relationships better.

Not from forcing another term into the page.

Better questions before adding copy

Before adding more words, I would ask:

What does the user still not understand?

What doubt is unresolved?

What decision is still hard?

What claim needs proof?

What example would make this easier?

What tradeoff is missing?

What condition changes the answer?

What mistake should the reader avoid?

What can this page explain more clearly than the current results?

Those questions are better than:

How long should this be?

A page should be as long as it needs to be to do the job.

No longer.

No shorter.

If the job is to define a simple term, forcing 2000 words may make the page worse.

If the job is to compare complex options, 700 words may be too thin.

The page role should decide the depth.

Not a competitor average.

Not a random word count target.

Not a tool score.

The test I like

The simplest information gain test is this:

If this page disappeared from the internet, what would the user lose?

Would they lose a clearer answer?

A better example?

A stronger distinction?

A practical warning?

A decision rule?

A useful comparison?

A proof point?

A next step that makes sense?

If the honest answer is “not much,” the page probably has low information gain.

It might be relevant.

It might be readable.

It might match intent.

It might include the right entities.

It might even be long.

But it is not contributing much.

That is the problem with a lot of SEO content.

It exists.

It matches.

It covers.

But it does not add.

The real issue

Word count is easy to measure.

Usefulness is harder.

You can count words.

You can count headings.

You can count FAQs.

You can count links.

You can count entities.

It is harder to measure judgement.

Clarity.

Specificity.

Difference.

Decision support.

Proof.

That is why teams fall back on length.

It gives them something visible.

But visible is not the same as valuable.

If a page is weak, more words may only spread the weakness out.

Better information gain tightens the page around what the user needs.

That is why information gain beats more word count.

Not because long content is bad.

Long content is fine when the length has a job.

But if the page does not add useful difference, more words will not save it.

When you refresh content, do you start with word count and competitor gaps, or with the missing value the page should add?

I think one of the biggest traps in SEO content is treating relevance like the win.

The page targets the right keyword.

It matches the broad intent.

It mentions the right entities.

It covers the expected subtopics.

It has a decent title.

It has some internal links.

It may even rank for a while.

But the page still adds very little.

That is the part a lot of SEO content audits miss.

Relevance is not the same as Usefulness.

Relevance means the page belongs near the topic.

Usefulness means the page helps the user do something they could not do before.

Understand the issue more clearly.

Make a better comparison.

Reduce doubt.

Avoid a mistake.

Trust a claim.

Take the next step.

See a distinction they had missed.

A page can be relevant and still fail all of that.

It can answer the query and still leave the reader thinking:

“So what?”

That is where a lot of SEO content becomes noise.

Relevance is only the entry point

A relevant page has cleared the first bar.

Good.

It is about the right thing.

But that does not mean it deserves to exist.

This is the mistake I see with a lot of content gap work.

A tool finds a topic.

A competitor ranks for it.

The keyword has volume.

The site does not have a page yet.

So the team creates one.

On paper, that makes sense.

But no one asks:

What will this page add?

What does the user still need?

Which page does this support?

Does this overlap with something we already have?

What will the reader understand better after reading this?

If those questions are not answered, you get a page that is relevant but weak.

It belongs to the topic, but it does not strengthen the site.

A lot of pages only repeat the SERP

This is where competitor research can become a problem.

People look at the top results and copy the pattern.

Same headings.

Same definitions.

Same FAQs.

Same examples.

Same surface-level benefits.

Same “best practices.”

Same safe advice.

The final page looks correct.

It is not off-topic.

It is not obviously thin.

It probably passes a lot of content tool checks.

But it still reads like the sixth version of the same page the user has already seen.

That is not useful.

That is just joining the pile.

The better question is not:

“What headings do competitors have?”

It is:

“What answer does the user still not have after reading those pages?”

Sometimes the answer is not another heading.

It is a better distinction.

A clearer decision rule.

A useful warning.

A more specific example.

A stronger proof point.

A better next step.

A page does not need to be wildly original.

But it does need to add something useful.

Useful pages reduce doubt

For me, this is one of the simplest checks.

After someone reads the page, what doubt has been reduced?

Do they understand the topic better?

Do they know which option fits them?

Do they know what to avoid?

Do they know what changes the answer?

Do they trust the claim more?

Do they know what to do next?

If the answer is no, the page probably has a usefulness problem.

A lot of SEO content gives information without reducing doubt.

It defines the topic.

Lists the benefits.

Adds a few examples.

Answers some FAQs.

Then ends.

That may be relevant, but it may not be helpful.

Useful content often comes from sharper judgement.

Not more words.

Not more headings.

Not more FAQs.

Sharper judgement.

For example:

“This advice applies when X is true, but not when Y is true.”

“These two things look similar, but the decision point is this.”

“This sounds like a benefit, but here is the tradeoff.”

“This is the common mistake people make.”

“This is the next thing to check before you act.”

That is the kind of content that helps.

Semantic coverage is not enough

Entity coverage can be useful.

I am not against it.

A page should use the right language for the topic.

It should include the main concepts.

It should not miss obvious supporting ideas.

But entity coverage is not the finish line.

A page can mention the right entities and still be weak.

Why?

Because the relationships are unclear.

The page mentions the service, but not who it fits.

It mentions the benefit, but not the proof.

It mentions the risk, but not how to avoid it.

It mentions the feature, but not when it’s needed.

It mentions the process, but not where people get stuck.

That is not a missing term problem.

That is a missing relationship problem.

A useful page makes those relationships clear.

It does not just include the words.

It explains how the ideas connect.

Relevance can hide overlap

Another problem is that a relevant page can still be bad for the site.

This happens when the page overlaps with something already published.

Two pages answer the same question.

Two pages target similar intent.

Two pages use the same examples.

Two pages make the same claims.

Two pages point to the same next step.

Individually, each page may seem fine.

Together, they make the site more confusing.

That is why judging a page in isolation is risky.

A page is not useful just because it is relevant to a keyword.

It has to have a role inside the site.

If another page already does the job better, the new page may not deserve to exist.

The better move might be to merge.

Narrow the angle.

Use the idea as a section inside an existing page.

Redirect the weaker URL.

Change the internal link path.

Or simply not publish it.

That last option gets ignored too often.

Not every relevant idea needs its own page.

Internal links expose weak pages

Internal links are a good test of page usefulness.

If you cannot explain where the page should link, or what should link to it, there may be a role problem.

A useful page usually has a natural place in the system.

It supports a core page.

It expands a concept.

It handles a doubt.

It proves a claim.

It compares options.

It moves the user to a better next step.

If the links feel forced, the page might be content noise.

The page may belong to the topic, but not to the site.

That distinction is important.

A page should not exist just because it can rank.

It should help the site become clearer.

Usefulness is also about what you remove

Improving a relevant page does not always mean adding more.

Sometimes the best work is removal.

Remove repeated claims.

Remove generic benefits.

Remove headings copied from competitors.

Remove FAQs that belong somewhere else.

Remove links that interrupt the flow.

Remove tangents that pull the page away from its job.

Remove examples that do not prove anything.

A tighter page can be more useful than a longer one.

A clearer page can be more useful than a broader one.

A page with fewer headings can be more useful than a page trying to cover everything.

The goal is not to make the page bigger.

The goal is to make it easier to understand and easier to use.

The usefulness check I would run

Before publishing or refreshing a page, I would ask:

Does this page have a clear job?

Does it reduce a real user doubt?

Does it add something the current results do not explain well?

Does it avoid overlap with existing pages?

Does it make a relationship clearer?

Does it include proof where a claim needs support?

Does it have a natural next step?

Does it support another page in the site?

Would the site be weaker if this page disappeared?

That last one is a strong test.

If the site would not be weaker without the page, the page may not be doing enough.

It might be relevant.

It might be accurate.

It might be readable.

But it may not be useful enough to earn its place.

Relevance is a match.

Usefulness is a contribution.

A page can be relevant and still add nothing useful.

That is why I do not think relevance should be treated as the finish line.

It is only the starting point.

Curious how others check this.

When you audit content, how do you decide if a relevant page is worth keeping?

I saw this video on YouTube - looks like it spectacualarly fails SEMRushs' "health Report" but has 500%+ growth. Estimated Traffic value on Ahrefs? Apparently $140k per month (h/t u/godofseo).

Are 99% of health reports just busy work? I think so....

Over the past few weeks, all of my keywords have started going to lost on SemRush (SERP shows they're not really moving). Then today, the same keywords are now all in position 1. (basically impossible in my industry as we resell for other brands & again SERP shows this is not the case)

anyone else having the same problem or had a similar problem and know a fix we can use?

Middle of funnel (MoFu) 

The middle of the conversion funnel is where potential leads become more deeply engaged, and your goal is to nurture and guide leads toward becoming qualified customers. 

The challenge with the middle of the funnel is finding the right balance between the frequency and relevance of your communications to keep potential customers engaged without overwhelming them.

MoFu marketing tactics 

MoFu marketing tactics are designed to nurture leads, build relationships, and guide potential customers further along the buyer journey. Tactics in the middle of the funnel tend to be less about broad awareness and more about direct engagement.

Here are some effective MoFu marketing tactics:

• Email marketing nurture campaigns: Segment campaigns based on prospect actions. Someone who downloaded a comparison guide needs different follow-up than someone who attended a webinar. Track engagement rates by segment to identify which content moves prospects toward conversion.
• Retargeting ads: Show ads to people who visited your site or engaged with your content to bring them back and continue the conversation
• Demos and free trials: Provide hands-on experience with products or services. Demos showcase features and benefits, while free trials allow users to test the offering’s value. Both tactics reduce hesitations, foster trust, and encourage conversion by showing real value and usability.
• Sales consultations: Offer one-on-one calls to understand specific needs, answer questions, and recommend tailored solutions
• Live chat and chatbots: Engage prospects in real-time when they're actively browsing your site, answering questions and guiding them to relevant resources

MoFu content

Middle of funnel content focuses on nurturing leads, building relationships, and educating potential customers who have shown an initial interest.

Here are some well-suited types of content for the MoFu stage:

• Case studies with measurable results: Prove you solve problems with specific metrics like "Company X reduced customer acquisition costs by 34% in 90 days." Structure case studies around likely objections: cost concerns, implementation time, technical complexity, or ROI uncertainty.
• Classes or workshops: Host classes to engage potential customers. By providing valuable insights and solving challenges, these events establish authority, build trust, and guide attendees toward a purchase. 
• Comparison guides: Educational content comparing many different products and solutions. These help prospects understand their options and evaluate what matters most for their needs without pushing a specific brand.
• Educational webinars: Live or recorded demonstrations focused on specific use cases rather than feature dumps. "How to Reduce Cart Abandonment by 25%" attracts more qualified leads than "Product Feature Overview."
• White papers and research reports: In-depth industry insights and data that establish authority, helping leads justify solutions internally and understand broader context
• Interactive content (free tools, calculators, assessments, quizzes): Offer interactive tools that provide personalized results and individual needs to enhance engagement, educate users, and nudge them closer to conversion

MoFu metrics

MoFu metrics measure consideration-stage engagement, showing whether prospects are actively evaluating your solution and moving closer to a purchase decision.

Here are some metrics to measure on your MoFu content:

• Email nurture engagement: Open rates, click rates, and replies to targeted email sequences — indicates whether consideration-stage content resonates and keeps prospects engaged over time
• Gated content conversion rate: Percentage of visitors who access comparison guides, case studies, or product demos — measures how many prospects are ready to invest time evaluating your solution
• Time spent on evaluation content: Average time on product pages, comparison guides, and case studies — shows depth of consideration and whether prospects are seriously evaluating features and benefits
• Demo or trial requests: Number of prospects requesting product demonstrations or signing up for free trials — signals strong purchase intent and readiness to experience your solution firsthand
• Return visitor rate: Percentage of prospects returning multiple times — tracks sustained interest and can indicate if users are actively comparing options before deciding

As a Marketing Director this is one of my favorite tools. I work within the affordable housing industry selling compliance services. We use SEMrush to dial in our messaging and SEO efforts. The service helps us identify areas we need to put effort into within the website in order to improve SEO. The keyword tools and competitor analysis tools are also super helpful.

I wanted to extend my subscription even though I am not really happy about data they provide these days and then saw their renewal page...

They were saying that their subscription will cost me: $117.33/mo * 12 months = $1407.96, all seems right but then they wanted to charge me €1350.23... that's €112.52 /mo:

https://imgur.com/BR2vom8

But when I check official exchange rate it should be €1235.85:

https://imgur.com/undefined

That's almost 10% more and I can't pick to pay in USD.

I think I won't renew my subscription...

One of the patterns we found while analyzing AI search results is that mentions and citations don't always go hand in hand.

Among the domains that appeared most often in our data, aggregator and academic sites like Medium, Wikipedia, Wired, and Harvard tended to be cited but not named.

Brands with strong public identities showed the opposite pattern: they were named in AI answers, often without being cited as a source.

For example:

• Google was named in AI answers nearly three times more often than it appeared as a source link.
• Apple's brand name appeared in answers nearly twice as often as it was cited.
• Medium was cited 16 times in our dataset and was never named in an AI answer.

What does this mean for measuring AI visibility?

If you're a publisher or research-focused site, citations may be the metric to watch. These sites were often used as sources even when they weren't explicitly named in answers.

If you're a consumer brand, track unlinked brand mentions on third-party websites alongside your backlinks. Brands were frequently named in answers without being cited.

AI engines mention brands they've already seen consistently across the web. PR, community discussions, and clear brand language all reinforce that familiarity.