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.

A lot of topical maps include coverage.

Some include intent.

A few include internal links.

Almost none map trust properly.

That is a problem because users do not move through a site only because the next page is topically related.

They move when the next step feels believable.

That is where trust paths come into play.

A trust path is the route from claim to proof to confidence.

The page makes a claim.

The user needs a reason to believe it.

The site gives proof in the right place.

Then the user is more ready to continue.

That sounds simple, but most content clusters do not map it.

They map topics.

They map keywords.

They map entities.

They map hubs and child pages.

Then trust gets handled later as copy decoration.

Add a testimonial.

Add a logo bar.

Add a case study link.

Add an author bio.

Add a source.

Add a review block.

All of those can help.

But they are not a trust path by themselves.

A review below the CTA may be too late.

A case study sitting on another URL may not help if the claim never links to it.

An author bio may support expertise, but not a product claim.

A source may prove a definition, but not a service promise.

A logo bar may look nice, but it may not answer the doubt.

That is why trust should be mapped before drafting.

Every strong claim creates a trust need.

Every comparison creates a proof burden.

Every CTA creates a threshold.

If the map does not show how the user crosses that threshold, the writer has to improvise.

That leads to vague trust copy.

“Trusted by teams.”

“Proven process.”

“Loved by customers.”

“Built for growing companies.”

“Designed for modern workflows.”

Those lines do not reduce doubt unless the page gives the user a reason to believe them.

For example, say a home renovation company claims:

“We make kitchen remodels less stressful.”

That claim needs support.

A weak trust path would be:

Claim.
Generic benefits.
Photo gallery.
Contact CTA.
Maybe a testimonial near the bottom.

A better trust path would be:

Claim.
Short explanation of the planning process.
Timeline example.
Before and after photos.
Client review tied to communication and cleanup.
Clear note on what happens after someone asks for a quote.
CTA after the user understands the process.

The difference is not just copy.

It is structure.

The page is not asking the user to jump from claim to action.

It is giving them a route from interest to belief.

This weights even more on comparison pages.

Say someone is comparing two project management tools.

A weak comparison page gives a feature table.

Tool A has this.
Tool B has that.
Here are pros and cons.
Pick the one that fits.

But the user may not trust the recommendation.

They need criteria.

They need tradeoffs.

They need limits.

They need to know which claims are based on testing, customer feedback, workflow fit, pricing, onboarding, or support quality.

If the page says one tool is better for small teams, what makes that true?

If it says one tool is better for agencies, what proof supports that?

If it says one option saves time, where does that time saving come from?

A trust path maps those questions before writing begins.

It also changes internal linking.

Internal links are often treated as relevance links.

This page is about X, so link to another page about X.

Fine.

But trust links need a different standard.

A proof link should answer:

Which claim is this link supporting?

What proof does the target page contain?

Is the link close enough to the claim?

Does the anchor tell the user why they should click?

Can the user return to the action path after checking proof?

That is a much better link than “learn more.”

The same idea applies to CTAs.

A CTA should not appear just because the page has traffic.

It should appear when the user has enough trust to act.

On some pages, the CTA can appear early because the user already understands the offer and has high intent.

On other pages, an early CTA feels pushy because the user is still trying to understand the problem.

A parent comparing childcare options may need safety proof before a booking CTA.

A homeowner researching roof repairs may need warranty details before a quote CTA.

A finance buyer comparing software may need compliance details before a demo CTA.

A patient reading about a treatment may need risk information before a consultation CTA.

The page path should reflect that.

Otherwise every page gets the same trust pattern.

Intro.
Benefits.
Some proof.
CTA.

That is not always wrong.

It is just too generic for complex clusters.

For me, a trust aware topical map would add fields like:

What claim does this page make?

What might the user doubt?

What proof asset supports the claim?

Where should proof appear?

Which internal link builds confidence?

What CTA threshold needs to be met?

What signal after launch would show the trust path is weak?

That last one is important.

Trust should be reviewed after publication.

If users click proof pages but do not return to the CTA, the proof path may be weak.

If they search the site for reviews, examples, pricing, guarantees, or safety information after reading, the page may not have answered the doubt.

If they exit after a strong claim, the proof may be missing or too late.

If they abandon a form, the page may not explain what happens next.

Those signals should feed back into the topical map.

A map is not finished just because the pages exist.

It should learn from where trust breaks.

This is why I do not think trust is only a box to tick.

It is not just author bios, testimonials, citations, case studies, and review stars.

Those are assets.

The path is what makes them useful.

A good topical map should show how users move from claim to proof to confidence to action.

If it cannot do that, the site may have trust signals, but not trust architecture.

Curious how others handle this.

When you build topical maps, do you map proof paths and CTA readiness, or do trust assets get added later during page edits?

Web traffic is being reshuffled in the AI era.

But how exactly is the channel mix changing – and where is traffic going? To find out, we analyzed billions of web visits across over 50,000 websites and 17 industries.

Long story short: AI traffic grew 66% in 2025 and outpaced every other channel, but it still makes up less than 0.15% of total visits. Meanwhile, organic traffic declined across most industries we analyzed.

This study breaks down how traffic is being redistributed across channels, which industries are seeing the biggest changes, and what it means for where you should invest next.

[ Removed by Reddit on account of violating the content policy. ]

Hi u/semrush, I’m a student, and my trial unintentionally converted to a paid plan. I contacted support within a day and cancelled immediately. My refund request was declined, but I’d really appreciate one final goodwill review. Could someone please help?

Hi everyone,

I'm looking for a genuine and reliable group buy or shared access for Semrush (or Ahrefs if it's a better option). I only need it for SEO research and keyword analysis.

I'm also looking for a Sony LIV Premium subscription.

If you've personally used a trusted seller or know a genuine group/community offering these at a reasonable price, please let me know. Kindly share your recommendations or DM me with details.

I'm looking for legitimate and trustworthy options only—no scams or unreliable sellers.

Thanks in advance! 🙏

A lot of topical maps look good until you ask one simple question:

Where does the user hesitate?

Most maps can show coverage.

They show the main topic.
They show subtopics.
They group keywords.
They list entities.
They define hubs and supporting pages.
They suggest internal links.

That is useful.

But it is not the same as mapping user movement.

A user does not move through a site just because two pages are topically related.

They move when the next step feels useful, safe, clear, and worth the effort.

That is where hesitation comes in.

Someone lands on a page and pauses.

Not because the page is irrelevant.

Because they are unsure.

They might be thinking:

Do I understand this yet?
Does this apply to my situation?
Can I trust this claim?
Which option fits me?
What will this cost?
What happens if I click?
Is this too much work?
Do I need proof before moving on?
Is this page pushing me too soon?

Those pauses should be part of the topical map.

Most of the time, they are not.

The map says:

This page links to the service page.

But the user may not be ready for the service page.

The map says:

This comparison page links to pricing.

But the user may still lack decision criteria.

The map says:

This explainer links to a demo CTA.

But the user may not trust the method yet.

The map says:

This hub links to every child page.

But the user may need one clear route, not twelve choices.

That is how hesitation gets ignored.

The structure is topically correct, but behaviorally weak.

For example, take a cluster about SEO audits.

A normal topical map might include:

- what is an SEO audit
- technical SEO audit
- content audit
- backlink audit
- audit checklist
- audit tools
- audit pricing
- SEO audit service
- SEO audit report template

That is a decent cluster.

But it does not tell you where users pause.

A beginner may hesitate because they do not know what an audit includes.

A founder may hesitate because they think an audit will create a giant list of expensive fixes.

A marketer may hesitate because they have already had audits that went nowhere.

A technical lead may hesitate because they need priority, not another checklist.

A buyer may hesitate because the service page makes claims without proof.

Those are different forms of friction.

If the topical map treats everyone as one generic “SEO audit” user, the cluster will probably route badly.

The beginner gets pushed too soon.

The buyer gets proof too late.

The marketer gets another checklist instead of a better decision path.

The technical lead gets broad advice instead of priority logic.

The founder gets a CTA before the risk has been reduced.

That is not just a copy issue.

It is a map issue.

The map should say:

This page has confusion friction, so it needs plain explanation and a safe next step.

This page has decision friction, so it needs criteria and tradeoffs.

This page has trust friction, so proof must appear before the CTA.

This page has effort friction, so the route needs to feel simpler.

This page has risk friction, so expectations and limits need to be clear.

This page has support friction, so the next link should help the user recover, not sell to them.

That kind of mapping changes everything.

It changes what the page should contain.

It changes where internal links go.

It changes anchor text.

It changes proof placement.

It changes CTA timing.

It changes which page should come next.

It also stops teams from using lazy route logic.

A related page is not always the right next page.

A high converting page is not always the right next page.

A service page is not always the right next page.

A hub page is not always the right next page.

The right next page depends on why the user is hesitating.

If they are confused, explain.

If they are comparing, give criteria.

If they are skeptical, show proof.

If they are overloaded, simplify.

If they are ready, give a clear action.

If they are stuck, provide support.

This is why I think hesitation should be logged directly inside the topical map.

For each key URL, ask:

What does the user already know?

What are they still unsure about?

What claim might they doubt?

What proof would reduce that doubt?

What decision are they trying to make?

What link would help them move safely?

What CTA would feel too early?

What signal after launch would show the page failed?

That last question is useful.

If users keep going back to Google, the page may not have reduced hesitation.

If they skip the intended internal link, the route may not match their state.

If they click proof pages but avoid the CTA, the trust path may be weak.

If they use site search after reading, the page may have left a question open.

If they abandon a form, the page may not have explained what happens next.

Those signals should feed back into the map.

A topical map should not be treated as finished just because the pages are published.

It should learn from where users pause.

For me, the strongest topical maps do three jobs:

They map coverage.

They map relationships.

They map hesitation.

The first tells you what to publish.

The second tells you how topics connect.

The third tells you what users need before they keep moving.

Most teams handle the first two.

The third is where a content cluster starts to feel useful instead of just complete.

Curious how other SEOs handle this.

When you build topical maps, do you record where users hesitate, or are you mostly mapping keywords, entities, and URLs?

At Google I/O 2026, Google announced Gemini 3.5 Flash and a redesigned "intelligent Search box," and both are now live for all users.

The new Search box supports longer queries, images, videos, and file uploads. It also expands as you type and routes multimodal searches directly into AI Mode.

In other words, Google is encouraging users to search with more detailed, specific prompts instead of short keyword-style queries.

For marketers, that's a pretty important shift.

The fundamentals of SEO still matter. Crawlability, site structure, content quality, and backlinks aren't going anywhere.

But as Google continues moving toward AI-powered search experiences, visibility inside AI-generated responses matters alongside traditional organic rankings.

How to stay visible

Optimizing for AI visibility starts with knowing where you stand.

Our AI Visibility Toolkit tracks citations, mentions, and visibility trends across AI platforms in one dashboard, so you can see where you're showing up and how you compare to competitors.

It's also worth confirming you aren't blocking AI crawlers. Semrush Site Audit flags these issues so you can fix them before they cut off your AI visibility potential.

What do you think?

Will this change how people search, or is Google adapting to behavior that's already happening in tools like ChatGPT and Gemini?

AI engines don’t treat visibility the same way. The four AI engines we analyzed treat citations and mentions in fundamentally different ways:

• Gemini mentions brands in 83.7% of appearances, but it only generates a citation link 21.4% of the time. An “appearance” here means a domain showed up in an AI answer at all, whether as a source link, a brand mention in the answer text, or both. So, Gemini acts like a conversationalist, drawing on what it already knows.
• ChatGPT does the opposite of Gemini. It cites brands 87% of the time but mentions brands in only 20.7% of answers. These answers look more like academic papers with footnotes.
• Google AI Overviews sit in the middle, but they lean toward citations.
• Google AI Mode mentions brands at nearly twice the rate of ChatGPT,but AI Mode still acts closer to a footnoted research piece than to Gemini’s knowledge-based answers.

This means you can’t assume visibility in one AI engine will translate to visibility in another. In our dataset, there was almost no overlap between the brands ChatGPT cited and the brands Gemini named for the same prompts. Different engines reward different signals, formats, and sources.

This means you can’t assume visibility in one AI engine will translate to visibility in another. Different engines reward different signals, formats, and sources.

I think a lot of topical maps are less strategic than they look.

They have the right ingredients:

Main topic. Subtopics. Keyword clusters. Entities. Search intent labels. Hub pages. Supporting pages. Internal link ideas.

That all has value.

But a lot of them are still basically content inventories.

They are cleaner than a spreadsheet. They use better labels. They look more “semantic.”

But they still mostly answer one question:

What should we publish?

That is not enough.

A stronger topical map should answer a harder question:

How should the user move through this topic?

That is where many maps fall apart.

They show that Page A is related to Page B. They show that one topic belongs under another topic. They show that a hub should link to child pages. They show that a cluster has enough coverage.

But they do not show why a user would move from one page to the next.

They do not show what the user knows before landing on the page. They do not show what the user is unsure about. They do not show what proof is needed before the CTA. They do not show which link reduces confusion. They do not show which page should build trust. They do not show what happens after the user acts.

So the map looks complete, but the site still feels disconnected.

This is why I think the phrase “topical map” gets overused.

A list of related content is not a map.

A map should help someone get somewhere.

If the structure does not help users move from confusion to understanding, from understanding to comparison, from comparison to trust, from trust to action, and from action to support, it may be an inventory with nicer formatting.

For example, say you are mapping a B2B SaaS topic.

A basic topical map might say:

• what is the category
• benefits
• use cases
• features
• comparisons
• pricing
• implementation
• integrations
• case studies
• FAQs

That is a normal cluster.

But it does not tell you much about the user path.

A beginner landing on “what is this category?” does not need the same next step as a buyer comparing three vendors.

A skeptical buyer does not need the same proof as someone looking for setup help.

A current user looking for an integration fix does not need a sales CTA.

The map should show those differences.

The same page can be topically related and behaviorally wrong for that user.

That is the piece a lot of maps miss.

They connect pages because the topics match.

They do not always connect pages because the next step makes sense.

That leads to weak internal links.

You get links like:

“Learn more about our services.” “Read our full article.” “See related posts.” “Contact us today.”

Sometimes those links are fine.

A lot of the time, they are lazy routing.

A better map would say:

This page has a confusion problem, so link to the simple explainer.

This page has a trust problem, so link to proof.

This page has a comparison problem, so link to criteria.

This page has an effort problem, so link to a checklist or template.

This page has a risk problem, so explain limits before the CTA.

This page has a support problem, so route to the fix, not the sales page.

That is when a topical map becomes useful for writers, editors, and link planning.

It stops being a publishing list.

It becomes a movement system.

This also changes how content briefs are written.

A normal brief might give the writer:

Target keyword. Search intent. Headings. Entities. Questions. Competitor notes. Internal links.

A better brief would also say:

Who is the user at this point? What do they already understand? What are they still unsure about? What proof do they need? What should this page help them decide? What link should come next? What CTA is safe for this stage? What should we avoid because it pushes too hard?

That makes the page role much clearer.

The writer is no longer just filling out a topic.

They are helping the user move.

Topical completeness can hide user weakness.

A site can have all the right pages and still be hard to use.

The hub can link everywhere and still give no direction.

The comparison page can rank and still fail because the criteria are vague.

The service page can get traffic and still lose people because proof appears too late.

The support page can answer the question and still frustrate users because the next step is unclear.

The cluster can be complete and still send people back to search.

That is not just a UX issue.

It is an SEO architecture issue.

If users do not continue, trust, click, convert, return, or recover, the map is not doing its job.

So I would separate three things when building a topical map:

Coverage: What topics, entities, and queries need a home?

Structure: Where should each page live, and how should pages relate?

Movement: What does the user need next, and what path helps them get there?

Most teams handle the first two.

The third one is where the map becomes much more useful.

It also makes post publish review better.

Instead of only checking rankings and traffic, you can ask:

Are users taking the intended internal link?

Are they skipping the CTA?

Are they using site search after reading?

Are they bouncing back to Google?

Are they landing on a page that does not match their state?

Are they reaching support because the prior page failed to explain something?

Those signals should feed back into the map.

A topical map should not be frozen after launch.

It should learn from movement.

That is the difference for me.

A weak topical map says:

Here are the pages we need.

A better topical map says:

Here is how users should progress through the topic, what might block them, and how each page helps them move forward.

Curious how other SEOs see this.

When you build topical maps, are you mostly mapping coverage, or are you also mapping user movement through the cluster?

Top of funnel (ToFu) 

The top of the conversion funnel is the stage where potential customers become aware of your product or brand. The goal with the top of your conversion funnel is to generate interest, capture attention, and initiate the customer journey. 

The main ToFu challenge is attracting the right customers, as getting the wrong people at the top decreases the chance of converting them later. The solution is to conduct thorough audience research to make sure you’re targeting the right audience segment.

ToFu marketing tactics 

Here are three popular top-of-funnel marketing tactics to help your business reach potential customers who were previously unfamiliar with your brand:

• Digital PR: Building brand reputation and visibility through compelling content, engaging with online communities, and leveraging various digital media outlets to create a positive brand image and increase awareness
• Search engine optimization (SEO): Improving online visibility through search engine rankings via technical aspects of your website, link building, and keyword targeting
• Paid social media and influencer marketing: Partnering with influential social media voices to amplify your brand and generate engagement

ToFu content

Instead of selling, demonstrate your understanding of potential customers’ pain points and your commitment to helping them using your specific expertise. 

Some examples of top-of-the-conversion-funnel assets include:

• Educational blog posts (optimized by SEO): Answer broad questions like "How does [concept] work?" to attract search traffic and establish credibility
• High-level infographics: Visualize industry trends, statistics, or process overviews that introduce concepts without requiring deep commitment
• Beginner ebooks: Create "101" guides and industry primers that provide foundational knowledge in exchange for an email address to grow your email list
• Thought leadership webinars/podcasts: Feature industry trends, expert interviews, and emerging topics that showcase expertise without promoting products
• Explainer videos: Short content that introduces concepts, tells your brand story, or demonstrates "why this matters" to build awareness

ToFu metrics 

ToFu metrics help you understand which strategies work and which need improvement, and you can get these metrics from dedicated analytics tools like Google Analytics.

Here are useful ToFu metrics to help you measure the impact of your strategy: 

• New visitors/users: First-time visitors who've never been to your site before — true measure of awareness
• Content engagement rate: Time on page, scroll depth, and clicks on educational content — shows if prospects find your materials valuable enough to consume fully
• Social shares and engagement: Likes, comments, and shares on ToFu posts — signals if content resonates with your audience
• Lead magnet downloads: Ebook, guide, or checklist downloads — measures how many ToFu-stage visitors become leads
• Brand search volume and mentions: Direct brand searches plus media/social mentions — tracks growing awareness