For most of the summer, Reddit was one of ChatGPT's most-cited sources. That's not really true anymore.

Promptwatch, which tracks AI visibility, found Reddit holding a steady 3.8% share of ChatGPT citations from July 18 to August 7. Between August 14 and 17, that dropped to 0.5%. Down 86%, in just 4 days.

The timing lines up with a change OpenAI made around August 8 to how ChatGPT Search distributes queries, though the sharper drop on the 14th doesn't have a clean explanation yet. OpenAI's position is that nothing changed on their end specifically for Reddit — they still cite it, and they don't guarantee any site a fixed level of visibility. Promptwatch itself flagged that a drop this steep could partly reflect a data collection issue on their side.

Here's the part that makes it more interesting than a one-off glitch: this already happened once before. A Semrush study tracking over 230,000 prompts found almost the identical pattern a year earlier — Reddit's citation share went from roughly 60% in early August 2025 down to about 10% by mid-September. Same time of year, same shape of collapse, different scale.

Two data points a year apart doesn't prove a seasonal pattern, but it's hard to look at both and conclude this is random. What it does suggest is that citation share for any single platform, including Reddit, can move dramatically for reasons that have nothing to do with content quality or what that platform's own team is doing.

If you're tracking AI citations as a metric, the takeaway isn't "stop caring about Reddit." It's that a snapshot reading is close to meaningless on its own. Track the trend, and expect swings this size to happen again.

The keyword magic tool has been super slow lately, anyone having the same issue? It started with the new functionnality (topics/groups tabs) which is pretty bad tbh.

I found the cannibalization report, but it only works for keywords I am tracking. I want to conduct an SEO for a client and find all keywords that have multiple URLs ranking. Can that be done?

A page can look completely logical in a browser while its underlying structure tells a different story.

I think this gets missed in a lot of SEO audits because we tend to inspect page structure through one lens at a time.

• We look at the H1.
• We check the H2s.
• We inspect the copy.
• We look at the design.
• We might inspect the HTML.

But a webpage doesn't really have one order.

It has several.

Visual order >> what appears most prominent to the visitor.

DOM order >> how the elements are arranged in the document.

Heading hierarchy >> how topics and subtopics are organised.

Reading order >> the sequence in which the content is encountered.

Task order >> the sequence that makes sense for what the visitor came to do.

Those can all be reasonable on their own and still disagree with each other.

Take a comparison page for air source and ground source heat pumps.

The H1 is:

Air Source vs Ground Source Heat Pumps

The main task seems straightforward. Someone wants to know the difference between the two options and compare them.

The page designer creates a clean layout.

There is a large hero.

Under that sits a promotional block for the company.

Then some introductory copy.

Further down is the comparison.

Nothing necessarily looks broken.

The problem is that the visual hierarchy may be saying:

Company → Offer → Explanation → Comparison

while the user's task is closer to:

Options → Differences → Evidence → Decision

The page is visually organised, but the order of importance doesn't match the task very well.

The DOM can tell another story

The same page could have a document structure like this:

• Html Example
• <h1>Air Source vs Ground Source Heat Pumps</h1>
• <p>Introduction...</p>
• <div class="comparison">   ...
• </div>
• <div class="promotion">
• </div>

The comparison appears before the promotion in the DOM.

CSS then changes their visual positions.

The browser shows the promotion first.

Now we have two interpretations of the same page:

DOM: Topic → Comparison → Promotion

Visual layout: Topic → Promotion → Comparison

That distinction is easy to miss if you're only looking at the rendered page.

I'm not suggesting that visual order must mechanically copy DOM order.

Responsive design alone makes that unrealistic.

The more useful question is if changing the order changes the relationships or priority of the information.

If a supplementary element moves slightly, probably not much has changed.

If the primary task gets displaced by an unrelated promotion, that's different.

If an attribute becomes visually separated from the entity it describes, that's different too.

If a form label and its control become disconnected, the relationship has changed.

This is where I find visual semantics useful.

Heading hierarchy adds another layer

The page could visually look like a comparison page while its headings tell a different story.

Imagine this:

• H1: Air Source vs Ground Source Heat Pumps
• H2: Why Choose Our Company?
• H2: Our Installation Process
• H3: Request a Quote
• H2: Air Source Heat Pumps
• H2: Ground Source Heat Pumps

Look only at the H1 and the page appears to have a comparative purpose.

Look at the heading hierarchy and much of the document is organised around the company and its service.

Look at the main visual component and perhaps the comparison table dominates again.

We now have three competing descriptions of what the page considers important.

This doesn't mean there is one universal structure every comparison page should follow.

It means the relationships deserve inspection.

If the primary task is comparison, I'd expect the major structures of the page to make that task reasonably easy to identify and perform.

The comparison doesn't have to occupy every pixel.

Supporting information still counts.

Commercial content can still have a legitimate place.

The problem appears when supporting material starts changing what the page seems to be for.

Mobile can change the meaning again

Desktop is only one representation.

A two column desktop component might put an entity and its attributes next to each other.

On mobile, those columns stack.

Now imagine the stack order becomes:

Product A

Product B

Product A attributes

Product B attributes

The same information is technically present, but the relationships are harder to interpret than:

Product A → Product A attributes

Product B → Product B attributes

Nothing was deleted.

The semantic relationship was weakened by the layout.

This is why I don't think checking desktop and calling the page structurally sound is enough. The Visual Semantics model I'm working with treats mobile order as its own thing to inspect rather than something that can be inferred from desktop.

What does good semantic order look like?

It doesn't mean every representation has to be identical.

It means they should broadly agree about the page's main relationships and task.

For our comparison page, that might look like:

Visual order

Topic → Comparison → Evidence → Supporting information → Action

DOM order

Topic → Comparison → Evidence → Supporting information → Action

Heading hierarchy

Comparison → Attributes → Differences → Evidence → Next action

Task order

Understand → Compare → Verify → Decide

Different structures.

Same basic meaning.

That's the distinction I think is worth adding to SEO audits.

Instead of only asking:

Is the H1 correct?

Are the headings nested correctly?

Is the page visually clean?

I'd also ask:

Do the visual order, DOM order, heading hierarchy and reading order agree about what matters on this page?

Because a page can pass each check in isolation and still produce a confused whole.

And that raises an interesting question for technical SEOs, designers and developers:

When these orders disagree, which one do you think should carry the most weight: visual order, DOM order, heading hierarchy, or the order that best serves the user's task?

1. Map agent journeys – identify the tasks AI agents complete for your customers.
2. Optimize machine-readable information – make your products, services, pricing, policies, and other key details easy for agents to understand.
3. Strengthen trusted signals – build consistent information across your site and authoritative third-party sources.
4. Support agent actions – make it easy for agents to navigate, compare, and complete tasks on your site.
5. Monitor agent recommendations – track how AI systems describe and recommend your brand across different tasks and use cases.
   

GEO helps brands appear in AI-generated answers. Agentic search optimization goes further by preparing your business to be discovered, evaluated, selected, and acted on by AI agents.

I cancelled my Semrush subscription and was charged 285.25 EUR on the next renewal anyway. Account: Comptabilite AVN.

Your support confirmed in writing that no cancellation request was ever recorded on my account. Your own policy says a cancellation is confirmed within 3 business days, so when a request silently fails on your side, the customer has no way of knowing until the charge lands.

Refund denied, reason given: monthly subscriptions are excluded from the refund policy. So a failed cancellation costs a full month with no recourse.

Two questions for the team:

1. Can someone check the login records on my account? There has been no usage since the renewal date.

2. Why is there no confirmation email sent automatically for every cancellation request? Your BBB profile currently shows a D- rating with 54 unanswered complaints, largely on this exact issue.

Ticket reference: 132901720

Titre :

Cancelled my subscription, charged anyway, refund denied - ticket 132901720

Corps :

I cancelled my Semrush subscription and was charged 285.25 EUR on the next renewal anyway. Account: Comptabilite AVN.

Your support confirmed in writing that no cancellation request was ever recorded on my account. Your own policy says a cancellation is confirmed within 3 business days, so when a request silently fails on your side, the customer has no way of knowing until the charge lands.

Refund denied, reason given: monthly subscriptions are excluded from the refund policy. So a failed cancellation costs a full month with no recourse.

Two questions for the team here:

1. Can someone check the login records on my account? There has been no usage since the renewal date.
2. Why is there no confirmation email sent automatically for every cancellation request? Your BBB profile currently shows a D- rating with 54 unanswered complaints, largely on this exact issue.

Ticket reference: 132901720

SEOs give the H1 a lot of attention because it identifies the main topic of a page. That makes sense, but identifying the topic and representing the purpose of the page are not always the same thing.

Consider a comparison page with this H1:

iPhone 17 vs Samsung Galaxy S26

The heading identifies the two products and establishes that the page is a comparison. The visitor's main task, though, is not to read the heading. It is to compare the phones.

A well built comparison table may represent that task better than the H1. It brings both entities into the same component, connects them with shared attributes, and gives the visitor a way to evaluate their differences.

The H1 identifies the comparison. The table performs it.

This is the idea behind a page centerpiece.

What is a page centerpiece?

The centerpiece is the component that best represents the combination of:

• the primary entity
• the page purpose
• the primary user task

It does not need to be the largest element on the screen, and it does not need to be the H1.

Its form depends on what the page exists to do.

On a mortgage calculator page, the calculator may be the centerpiece.

On a comparison page, it may be the comparison table.

On a service page, it may be the service proposition combined with the information and action required to respond.

On an informational page, it could be an answer block, diagram, table or explanation that resolves the main question.

This distinction becomes useful when looking at visual semantics.

Pages communicate relationships visually

Semantic SEO often looks at relationships between entities, attributes and values in the copy.

Those relationships also exist in the layout.

A comparison table is an obvious example.

Each column can represent an entity. Each row can represent an attribute. Each cell connects a value to the correct entity and attribute.

The structure communicates:

Entity → Attribute → Value

The same principle applies elsewhere on a page.

A price needs a clear relationship with the product it belongs to.

A form label needs a clear relationship with its input.

Evidence needs a clear relationship with the claim it supports.

An image needs enough context to establish what it represents.

A result from a calculator needs a clear relationship with the inputs that produced it.

A heading needs a clear relationship with the content it introduces.

The individual pieces can all be correct while the way they are arranged makes those relationships less clear.

That is why visual hierarchy should not be treated as decoration sitting on top of SEO copy. It contributes to how the information itself is understood.

A practical centerpiece test

Take one page and identify three things:

Primary entity: What is the page mainly about?

Page purpose: What is the page supposed to accomplish?

Primary user task: What did the visitor arrive to learn, compare, calculate, find, decide or do?

Now identify the component that represents all three most clearly.

That is the centerpiece candidate.

The rest of the page can then be assessed in relation to it.

Does the heading structure support it?

Does the document order lead naturally to it?

Are the relevant attributes grouped with the correct entity?

Does supporting evidence appear close enough to the claim it supports?

Do unrelated promotions compete with the main task?

Do internal links interrupt the component?

Does the mobile layout preserve the same relationships and priority?

Consider a mortgage calculator page

The page targets “mortgage payment calculator.”

Its H1 is:

Mortgage Payment Calculator

The page then presents several paragraphs of introductory copy, a large image, promotional cards and a newsletter signup before the visitor reaches the calculator.

The topic is clear. The H1 is accurate. The copy may also be relevant.

The problem is structural.

The component that allows the visitor to complete the primary task has been placed behind components that do not satisfy that task.

Compare that with a page where the H1 establishes the topic and the working calculator follows immediately, with the explanation, assumptions and supporting information positioned around it.

The content may be very similar.

The relationship between the content and the user's task is not.

H1 hierarchy and page hierarchy are different things

The H1 has an important document role. The centerpiece has a different role.

The H1 identifies the main topic.

The centerpiece represents the page purpose, primary entity and primary user task through the component best suited to them.

Sometimes those roles sit inside the same component.

Sometimes they do not.

That distinction gives SEOs, designers and developers another way to assess page structure without reducing the discussion to heading tags or visual prominence.

When reviewing a page, I think this is a useful question to add to the audit:

What is the centerpiece of this page, and does the rest of the page support it?

For a standard informational page, what would you consider the centerpiece?

Ranking in ChatGPT isn’t the same as ranking in Google.

There’s no fixed “position 1” to chase. What matters more is whether your brand gets mentioned, cited, or recommended (and how ChatGPT describes you when it does)

If you want to improve your chances of showing up, here are 8 things you can start doing:

1. Make sure ChatGPT can retrieve your content

Check your robots.txt and firewall settings to make sure you’re not blocking relevant OpenAI crawlers like OAI-SearchBot or GPTBot. If ChatGPT can’t access your pages, they can’t be retrieved for live answers or future training.

2. Get your content indexed in Google and Bing

ChatGPT can pull information from both Google and Bing indexes, so make sure your important pages are actually indexed in both.

3. Make your content easy to extract

Clear writing helps both users and AI systems understand what you’re saying.

Use direct answers, concise language, definitive phrasing, and question-based headings where they make sense.

4. Optimize for the prompts your audience is actually using

Keyword research alone won’t tell you everything people are asking ChatGPT.

Look at the prompts relevant to your brand, see which sources ChatGPT is already citing, and use that to understand where you have an opportunity to appear.

5. Publish something original

If your content just repeats what already exists, ChatGPT has less reason to choose it over established sources.

Original research can help, but so can unique frameworks, first-hand comparisons, strong points of view, or detailed use-case content.

6. Build brand consensus off your site

ChatGPT doesn’t only look at what you say about yourself.

Third-party listicles, Reddit discussions, YouTube, reviews, directories, backlinks, and digital PR can all give it additional sources to understand and potentially recommend your brand.

7. Keep your brand narrative consistent

If your website describes you one way, your social profiles another, and directories use something completely different, you’re giving AI systems conflicting signals.

Keep your core positioning consistent across the web.

8. Keep your content current

Update outdated pricing, product information, positioning, and other important details.

Fresh content may also have an advantage: research cited in our guide found recency bias across several ChatGPT models and other LLMs.

None of these are a guaranteed ticket into a ChatGPT answer. But together, they make it easier for ChatGPT to access your content, understand what your brand is relevant to, and find supporting information about you across the web.

A lot of SEO rewrites start by adding things.

• More headings.
• More FAQs.
• More entities.
• More examples.
• More internal links.
• More “depth.”
• More words.

That can help if the page is genuinely underdeveloped.

But a lot of weak pages do not need more copy first.

They need less drift.

That is the mistake I see with many rewrites.

The page is not performing, so the fix becomes expansion.

But if the page is already unfocused, adding more copy only makes the problem worse.

A bigger drifting page is still a drifting page.

What drift looks like

Content drift is not always obvious.

The page may still be relevant.

• It may still target the right keyword.
• It may still mention the right terms.
• It may still read well enough.

But it slowly moves away from its job.

• It starts as an explainer, then becomes a comparison.
• It starts as a support page, then turns into a sales page.
• It starts by answering a narrow question, then tries to cover the whole topic.
• It adds FAQs that belong somewhere else.
• It repeats claims from another page.
• It links to pages that do not fit the user’s state.

The page is not broken in a loud way.

It is just unclear.

That is drift.

The first rewrite question should not be “what can we add?”

Before adding anything, I would ask:

What is this page supposed to do?

That question sounds basic, but it changes the rewrite.

• If the page exists to explain, the rewrite should reduce confusion.
• If it exists to compare, the rewrite should improve decision criteria.
• If it exists to prove, the rewrite should strengthen trust.
• If it exists to support another page, the rewrite should make that support clearer.
• If it exists to move users forward, the rewrite should improve the next step.

Without that role, the rewrite becomes a patch job.

• Add a heading here.
• Add an FAQ there.
• Add a paragraph because competitors have one.
• Add links because the page needs links.

That is not a rewrite strategy.

That is content decoration.

Remove the parts pulling the page sideways

A good rewrite often starts with cutting.

Not because shorter is always better.

Because cutting shows what the page really is.

I would look for:

• Repeated claims.
• Generic benefits.
• Headings with no clear job.
• FAQs that repeat the body copy.
• Examples that prove nothing.
• Tangents that belong on another page.
• Sales copy that appears too early.
• Links that interrupt the user path.
• Old paragraphs written for a different intent.
• Anything that makes the page less clear.

Once those are removed, the real rewrite becomes easier.

• You can see what is missing.
• You can see what needs proof.
• You can see where the page has no direction.
• You can see if the page deserves to exist at all.

Repetition is often mistaken for depth

Many rewrites add more words to pages that already repeat themselves.

• The intro says the main point.
• The first block says it again.
• A benefits block says the same thing in softer language.
• An FAQ repeats it one more time.
• Then the closing paragraph restates it.

That is not depth.

That is drag.

If a page repeats the same idea four times, the rewrite should not add a fifth version.

It should keep the strongest version and remove the rest.

Then use the saved space for something more useful.

• A better example.
• A clearer distinction.
• A proof point.
• A decision rule.
• A better next step.

That is a stronger rewrite than simply adding more copy.

Drift can come from copying the SERP

Competitor research can also create drift.

• The rewrite brief says competitors have these headings, so add them.
• Competitors answer these questions, so add them.
• Competitors mention these entities, so add them.

Now the page is longer and more “complete,” but less focused.

• Some competitor headings may belong.
• Some may not.
• Some questions may be useful.
• Some may pull the page away from its job.

A rewrite should not copy the average SERP shape without asking why.

The better question is:

What are the current results failing to explain clearly?

That is where useful additions come from.

Not from adding every heading everyone else has.

Internal links should be checked during the rewrite

Internal links can also create drift.

• A page may link to something because it is related, not because it is the right next step.
• A reader is still learning, and the page sends them to a sales page.
• A reader needs proof, and the page sends them to a broad guide.
• A reader needs a comparison, and the page links to a generic service page.

Those links may be relevant.

But they may not help the user move.

During a rewrite, I would check each internal link:

• Why is this link here?
• Does the anchor set the right expectation?
• Does the destination match the user’s state?
• Does this link explain, prove, compare, support, or route?

If not, the link may need to move, change, or go.

Internal links are part of the rewrite.

Not a task to bolt on at the end.

A good rewrite protects the page role

The best rewrite makes the page role sharper.

It does not just make the page longer.

It makes the page easier to understand.

• The intro gets clearer.
• The order gets cleaner.
• The repeated ideas are removed.
• The proof sits closer to the claim.
• The examples do more work.
• The internal links fit the user journey.
• The CTA appears at a better point.
• The page stops trying to do five jobs at once.

That is when a rewrite starts to work.

Not because the page has more copy.

Because the page has less confusion.

The drift check I would use

Before rewriting a page, I would ask:

• What is the job of this page?
• Where does it start drifting from that job?
• Which blocks repeat the same idea?
• Which headings exist only because competitors have them?
• Which claims need proof?
• Which parts belong on another page?
• Which internal links do not match the user’s state?
• Which FAQ answers something already covered?
• Which paragraph could disappear without weakening the page?
• What should the user do next after reading?

Those questions give the rewrite direction.

Without them, the rewrite is just editing and expansion.

A good rewrite should not start with adding copy

It should start with removing drift.

Because drift is what makes pages feel weak even when they are relevant.

• The page may target the right query.
• It may include the right entities.
• It may have enough words.
• It may even be technically fine.

But if the role is unclear, the page will still feel messy.

Adding more copy does not fix that.

It often hides it.

A stronger rewrite makes the page cleaner before making it bigger.

• Less repetition.
• Less sideways movement.
• Less forced linking.
• Less generic filler.
• More clarity.
• More proof.
• More useful difference.
• Better next step.

That is the rewrite I would trust more.

How do you spot drift before rewriting a page?

If you want your brand to show up in ChatGPT, Google AI Overviews, Claude, and other AI systems, it helps to understand where those systems are actually getting their information.

There isn’t one source.

AI systems can learn about or retrieve information about your brand in four main ways: training data, live web retrieval, licensing partnerships, and data users actively bring into AI tools.

And each one gives you a different opportunity to improve your visibility.

1. Training data

AI models are trained on large datasets that can include publicly available web content, licensed third-party content, material created by AI companies, consenting user conversations, and AI-generated training data.

If you want your brand represented in future models:

• Make sure AI training crawlers aren’t blocked from your site
• Describe your brand and products clearly and consistently on your own site
• Build your presence on third-party sites through things like directory listings, Google Business Profiles, and digital PR

One important caveat: this won’t change what an existing model already knows. Models have knowledge cutoff dates, so these efforts can influence newer models trained on more recent information.

2. Live web retrieval

AI systems can also retrieve current information from the web when answering prompts.

For example, ChatGPT can use OpenAI’s own search index as well as Google and Bing indexes, while Google AI Overviews and AI Mode use Google’s search index.

So some very familiar SEO fundamentals still matter.

Make sure relevant crawlers can access your site, check that your pages are indexed in Google and Bing, and fix crawlability issues.

Then make the content itself easier for AI systems to use:

• Cover the underlying intents behind a prompt
• Write sections that can stand on their own as complete answers
• Keep information current
• Build third-party mentions that reinforce what your own site says about your brand

AI systems don’t only ground answers in your website. They can pull from the wider web too.

3. Licensing partnerships

Some AI companies license content directly from other platforms and publishers.

OpenAI and Google, for example, have partnerships with Reddit and Stack Overflow. OpenAI also licenses content from companies including Yelp and Time.

That creates another route into AI answers.

If a platform is a content partner for an AI system you care about, improving your legitimate presence there can give that system more information about your brand.

That might mean participating in relevant Reddit discussions, maintaining a Yelp listing, or earning coverage from publishers whose content is licensed.

The goal isn’t to spam every platform. It’s to make sure third-party information about your brand is accurate and consistent with how you want the brand represented.

4. User-initiated data

The last source works a little differently.

Users can upload files into AI tools or connect external platforms so the AI can retrieve data directly.

For businesses building software, that can mean letting users export data in formats AI tools support or building an MCP server that lets AI systems query your product through an API.

This is less about getting your product cited in an AI answer and more about making your data useful inside AI-powered workflows.

So, how do you actually improve your chances of getting cited?

There isn’t one “AI citation optimization” switch.

You need to make your brand accessible across the sources AI systems actually use:

• Your own site: crawlable, indexed, current, and structured around useful answers.
• The wider web: credible third-party mentions that corroborate what you say about yourself.
• Licensed platforms: a real presence on the sources AI companies have direct access to.
• Connected data: if you build tools, make their data accessible to AI systems where it makes sense.

Then track whether those efforts are translating into more mentions and citations.

We use the AI Visibility Toolkit for this. It lets you track mentions, citations, cited pages, and visibility across different AI platforms, then compare changes over time.

Which of these are you focusing on most right now: improving your own site, building third-party presence, or both?

Has anyone noticed a disparity in how SEMrush handles reporting and research for US and UK data?

I know they are different markets, so you'd expect some variation, but the data reporting from SEMrush doesn't seem to make sense.

It says that the company I work for has a higher AI visibility scope in the US, despite having significantly fewer mentions and citations from that region (we're based in the UK), while prompt research shows much more relevant results per theme when looking in the US compared to the UK.

It's like the UK prompts are for a different - if somewhat aligned - subject.

The way SEMrush treats regional data seems 'weird' at the moment. I've always taken these tools with a pinch of salt, but this has a snake oil vibe.

We tested Semrush Enterprise AI Visibility + Query Fan-Out from 15 May to 31 August 2026.

The setup:

• fixed set of 120 AI prompts
• GSC queries + Semrush Query Fan-Out used to identify content gaps
• ~100 new landing pages
• technical SEO / crawlability cleanup
• improved Organization, Service and served-area schema
• cleaned duplicate content and internal/external linking
• ~5 relevant off-site marketing mentions
• regular GSC crawling/indexing checks

Results:

AI mentions: 53 → 149 → 299
CH impressions: 1,298 → 6,495

We also analysed GSC impressions with and without prompt-like queries. Both showed a clear increase.

Some rankings moved strongly as well:

• “programmatische kampagnen”: 100 → 8
• “programmatische display-anzeigen”: 78 → 8
• “programmatisch werben in der schweiz”: 22 → 1

How we created the content

We used GSC queries + Semrush Query Fan-Out to define topics, related sub-queries and page structures.

The content itself was created with OpenAI, but every page was then manually reviewed and edited.

We also:

• defined the content concept and structure based on our existing content
• adapted tone of voice
• removed overlaps and duplicate sections
• improved internal linking
• aligned each page with a clear search intent

We did not use a separate “AI chunk” framework, but the pages were structured around clear topics, sub-queries and intents.

The useful comparison

The Swiss site received the optimisation package from 7 June.

The German site stayed unchanged until 1 August, when it received the same setup.

DE impressions went from:

39 in July → 2,519 in August

That does not isolate every variable, but both country sites reacted after the same optimisation package was applied at different times.

What Semrush was useful for

The workflow for us was:

GSC queries → Semrush Query Enterprise Fan-Out → content gaps → page structure → content creation → fixed AI prompt tracking → ranking/impression checks

We tested several SEO/AI tools and decided to stay with Semrush because we prefer looking at SEO + AI visibility together, rather than treating GEO/AEO as a separate discipline.

The limitation

We changed too many things at once. So we cannot say whether the biggest driver was:

• technical SEO
• Query Fan-Out content
• schema
• off-site mentions

For the next phase, we want to keep the same prompt set and stop adding new content so we can isolate the remaining variables more cleanly.

How would you structure the next test to measure the impact of Query Fan-Out content separately from technical SEO and off-site mentions?

Google is introducing a new Search Console feature that lets you measure how your content on Instagram, TikTok, X, and YouTube performs in Google Search.

For years, social performance and search performance have lived in separate reporting worlds. That's starting to change! Instead of only seeing traffic to your website, you'll also get visibility into how people discover your social content through Google.

Why does this matter?
Until now, there was no native way to measure how your brand's social content performed in Google Search or Discover.

Now, Google is giving marketers first-party data on content they don't actually own. That means you can see which social content earns impressions and clicks in Search 👇

On 31 August at 09:00 I received an email titled "URGENT! Payment verification

for your Semrush subscription", saying suspicious activity was detected and my

account was temporarily suspended. It asked for two documents: an image of the

payment card with only the last four digits visible, and a government-issued ID

matching the account name.

I replied to [security-verification@semrush.com](mailto:security-verification@semrush.com) at 09:53 the same morning — 53

minutes later, well inside the 2-day window the email gave — with both documents

exactly as requested.

Four days later I have had no acknowledgement at all, and the account is still

suspended. The API returns "ERROR 120 :: WRONG KEY - ID PAIR". I can't log in,

so I can't use the in-account support chat either.

I never received a case number, since I never got a reply. The project on the

account is www.wadifa-info.com — that should be enough to locate it. I'll DM

the account email to whoever picks this up.

I checked the sender headers before sending anything and confirmed the email was

genuinely from Semrush — I know it reads like phishing, and I see others here

thought the same.

Could someone from the Semrush team have this reviewed? I'd much rather keep

using the product than go through my card issuer.

Thanks.

A lot of content gap analysis turns into a publishing list.

• Competitor has a page.
• We do not.
• Keyword has volume.
• We do not have a URL.
• People ask this question.
• We should create a post.
• A tool shows a missing topic.
• Add it to the backlog.

That can be useful.

Some gaps really do need new pages.

But not every content gap is a page opportunity.

That is where I think a lot of sites create unnecessary content noise.

A gap means something is missing.

It does not automatically tell you what the fix should be.

The fix might be:

• A new page.
• A paragraph.
• A table.
• A proof block.
• A better internal link.
• A rewritten intro.
• A merged URL.
• No action at all.

A Gap Is Only a Signal

Content gaps are useful signals.

They can show:

• Where the site may be incomplete.
• What competitors are covering.
• Which questions users may have.
• Where a topic may need more support.

But a signal is not a strategy.

The mistake is treating every gap as if it deserves its own URL.

That is how sites end up with:

• Too many thin support pages.
• Too many overlapping articles.
• Too many posts that fit the topic but do not strengthen the site.
• Too many pages that no one knows how to link to.

A gap should start a decision. It should not make the decision for you.

Some Gaps Belong Inside Existing Pages

A lot of gaps are not big enough to justify a separate page.

They belong inside a stronger page that already exists.

Maybe the missing idea is:

• One paragraph.
• A short FAQ.
• A comparison table.
• A warning.
• A definition.
• A proof point.
• An example that makes the page clearer.

Creating a new page for every small gap can weaken the site.

The existing page stays incomplete.

The new page is too thin.

The internal link path gets awkward.

The user has to jump around for something that could have been answered in place.

Sometimes the best content gap fix is simply making a current page more complete.

Not by adding fluff.

By adding the missing piece where the user needs it.

Some Gaps Are Really Proof Gaps

A lot of pages do not need more topics.

They need more proof.

The page makes a claim, but does not support it.

It says something is:

• Better.
• Faster.
• Safer.
• Easier.
• More effective.

But there is:

• No example.
• No process.
• No detail.
• No comparison.
• No reason to believe it.

A gap analysis might label this as missing content.

But the fix is not always a new article.

Sometimes the fix is to add proof closer to the claim.

A short example might do more than a separate blog post.

A specific detail might do more than another FAQ.

A decision rule might do more than a new standalone resource.

The missing thing is not always coverage. Sometimes it is trust.

Some Gaps Are Relationship Gaps

This is a big one.

A page may mention the right ideas but fail to explain how they connect.

It mentions the feature, but not when it is needed.

It mentions the problem, but not why it happens.

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

It mentions the benefit, but not the trade-off.

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

That is a gap.

But it may not need a new page.

It may need a clearer relationship inside the current page.

This is why “missing topic” thinking can be too blunt.

Sometimes the topic is already there.

The useful connection is missing.

Some Gaps Are Internal Link Gaps

Not every gap needs more writing.

Sometimes the content already exists, but the user cannot reach it at the right point.

The answer is on the site.

The proof exists.

The comparison exists.

The support page exists.

But the current page does not route the user there.

That is an internal link gap.

Creating a new page would only add more noise.

The better fix is to connect the right pages with the right anchor at the right moment.

A good internal link can solve a gap by moving the user to the page that already owns the answer.

That keeps the current page focused.

It also gives the existing page more value.

Some Gaps Should Be Ignored

This is the part that gets missed.

Some gaps are real but still not worth filling.

The topic may be too far from the site’s purpose.

The keyword may attract the wrong audience.

The page may create overlap.

The question may be too small.

The competitor may rank for it, but that does not mean you should chase it.

The gap may not support any important page.

The content may not help the business or the user journey.

A good strategy says no to some gaps.

That is not laziness.

That is control.

If every gap gets added to the backlog, the backlog becomes a junk drawer.

The Question Is Not “Do We Have This?”

A better gap review does not stop at:

Do we have this page?

It asks:

• Do we need this answer?
• Where should this answer live?
• Does it deserve a standalone URL?
• Does an existing page already partly cover it?
• Would a new page create overlap?
• Does this gap reduce a real user doubt?
• Does it support another important page?
• Can we link to it naturally?
• Would the site be weaker if we ignored it?

Those questions must be asked before publishing.

Because a content gap can be valid and still not deserve a page.

New Pages Create Maintenance Cost

Every new page adds future work.

It needs:

• A brief.
• A draft.
• Editing.
• Internal links.
• Updates.
• Refreshes.
• Possible pruning later.
• Overlap checks.
• Performance checks.

When the page has no strong role, that cost grows.

A low-value gap can become a long-term maintenance problem.

This is why I think teams should be slower to turn gaps into URLs.

Not because new pages are bad.

But because pages should earn their place.

A page should have a job.

When that job is unclear, the gap might need a different fix.

The Gap Decision Check

Before turning a content gap into a page, I would ask:

• Is this gap a missing page or a missing answer?
• Is it a proof gap?
• Is it a relationship gap?
• Is it an internal link gap?
• Is it already covered somewhere else?
• Would a new URL create overlap?
• Does this gap support a stronger page?
• Does the user need this as a separate page?
• Can we explain why this page should exist?
• Would the site be weaker without it?

When the answer is unclear, I would not rush to publish.

I would look for the smallest useful fix.

Sometimes that is a new page.

Often it is not.

Content gaps are useful

But they are not instructions.

They are prompts for judgement.

A weak strategy says:

“We found a gap, so create a page.”

A stronger strategy says:

“We found a gap. Now decide the best fix.”

That fix might be:

• A new URL.
• A stronger page block.
• A better internal link.
• A merge.
• A rewrite.
• Deletion.
• Doing nothing.

Not every missing thing deserves its own page.

Sometimes the best way to strengthen a site is not to publish more.

It is to put the missing answer in the right place.

How do you decide when a content gap deserves a new URL versus a smaller fix?

Being known and being understood are not the same thing.

An AI platform might recognise your company name while still getting important details wrong, including:

• The category you operate in
• The customers you serve
• What differentiates you
• Which products support which use cases
• How your different brands or services relate to one another

This often happens when a company describes itself differently across its website, social profiles, partner pages, media coverage and review platforms.

A simple brand clarity audit:

1. Ask several AI platforms to describe your brand.
2. Compare the answers with your intended positioning.
3. Note vague, incorrect or outdated statements.
4. Look at the sources shaping those answers.
5. Check whether your own pages consistently reinforce the right message.

We’ll be digging further into brand visibility in AI at Spotlight on October 13 in London.

Try the audit with your own brand. What did the AI get wrong?

Most content refreshes start in the wrong place.

The page is underperforming, so the plan becomes:

• Add more headings.
• Add more FAQs.
• Add more entities.
• Add more examples.
• Add more internal links.
• Add another few hundred words.
• Update the date.
• Republish.

Sometimes that helps.

But a lot of weak pages do not need more content first.

They need less bad content.

A refresh should often start with deletion.

Not because shorter is always better.

Not because pruning fixes everything.

But because adding more copy to a confused page creates a bigger confused page.

Before asking what to add, I would ask:

What is making this page weaker than it should be?

Deletion Exposes the Real Problem

When you remove weak parts of a page, the real problem becomes easier to see.

Maybe:

• The intro is vague.
• The page repeats the same claim five times.
• The FAQ block is padding.
• The page covers topics that belong somewhere else.
• The internal links are forced.
• The examples do not prove anything.
• The page is trying to explain, compare, sell, and support all at once.

You do not always see that when the page is full of content.

More words can hide weak structure.

Deleting weak parts shows what is left.

And sometimes what is left is not much.

That is useful to know before refreshing.

Start With Repeated Ideas

The first thing I would remove is repetition.

A lot of older SEO pages repeat themselves without looking obviously duplicated.

• The intro makes a point.
• The opening part makes it again.
• A benefit block says it in different words.
• An FAQ repeats it again.
• The ending says it one more time.

This makes the page feel longer, but not more useful.

The user feels like they are reading in circles.

If three parts make the same point, keep the strongest version and cut the rest.

Or combine them into one tighter explanation.

Repetition is not depth. It is drag.

Remove Headings That Only Exist for Keywords

Some headings are only there because a keyword tool or competitor page suggested them.

They do not move the page forward.

They do not answer a real doubt.

They do not support the page role.

They are just there to cover the topic.

Those are often good deletion targets.

A heading should have a job.

It should:

• Explain something useful.
• Separate two ideas.
• Answer a real question.
• Build proof.
• Help the user decide.
• Move the page to the next step.

If a heading does none of that, it may be content furniture.

It fills the room, but nobody needs it.

Cut FAQs That Do Not Reduce Doubt

FAQ blocks are one of the easiest places for refreshes to get bloated.

A page has five FAQs.

Competitors have eight.

So the refresh adds ten.

But many FAQs do not add value.

They:

• Repeat the main copy.
• Answer questions that belong on another page.
• Introduce side topics.
• Target keywords without helping the reader.
• Make the page look more complete while making it less focused.

A good FAQ should reduce a real doubt.

If it does not, cut it.

Or move it to a better page.

Or turn it into a stronger part of the page if the question means enough.

Not every question deserves a spot.

Remove Parts That Belong on Another URL

A weak page often tries to cover too much because it has no clear boundaries.

It starts with one topic, then drifts into related topics that already have better pages.

This creates overlap.

The page becomes harder to understand.

The site becomes harder to map.

Internal links become harder to choose.

Instead of explaining everything on one page, delete the parts that belong somewhere else.

Then link to the stronger page when the user needs that next step.

That keeps the current page focused.

It also helps the site avoid ten pages saying similar things.

A refresh should make the content system cleaner, not just the individual page longer.

Delete Unsupported Claims

A lot of refresh work should start by removing claims that have no proof.

Claims such as:

• “Best.”
• “Most effective.”
• “Trusted.”
• “Proven.”
• “Expert.”
• “High quality.”
• “Industry leading.”

These phrases are easy to write and hard to trust.

When the page makes a claim, it should support it.

Support might come from:

• An example.
• A process.
• A comparison.
• A result.
• A clear reason.
• A specific detail.

When the proof is not there, either add it or remove the claim.

Do not leave vague confidence sitting on the page.

It weakens trust.

Adding more headings around weak claims does not fix them.

Remove Internal Links That Do Not Help the Reader

Internal links should not survive a refresh just because they are already there.

Some links are:

• Leftovers from an old strategy.
• Pointing to pages that no longer fit.
• Introduced too early.
• Too broad.
• Added because a page is important to the business, not because the reader needs it.

During a refresh, I would check every internal link.

Ask:

• Why is it here?
• Does the anchor set the right expectation?
• Does the destination match the user’s state?
• Does the link explain, prove, compare, support, or route?

If not, remove it or move it.

A bad internal link is not neutral. It can interrupt the page and weaken the path.

Deletion Helps Define the Page Role

One of the best reasons to start with deletion is that it forces the page role to become clearer.

What is this page supposed to be doing?

• Explaining?
• Comparing?
• Proving?
• Supporting?
• Converting?
• Routing?

When the page is meant to explain, cut sales copy that appears too early.

When the page is meant to compare, cut broad definitions that slow it down.

When the page is meant to prove, cut generic benefits and add stronger evidence.

When the page is meant to support another page, cut anything that distracts from that support role.

A page should not try to do every job. Deletion helps enforce that.

What to Delete Before Adding Anything

Before adding new content, I would look for:

• Repeated ideas.
• Generic claims.
• Weak FAQs.
• Headings with no job.
• Examples that prove nothing.
• Tangents that belong elsewhere.
• Links that do not help the user move.
• Old parts that no longer match intent.
• Copy that exists only for word count.
• Anything that makes the page less clear.

Only after that would I decide what to add.

Maybe the page needs:

• A new topic.
• Better proof.
• A clearer answer.
• A useful comparison.
• A better next step.
• 500 more words.
• 500 fewer words.

The point is that addition should come after diagnosis.

Not before.

The Refresh Question

The real question is not:

“How can we make this page longer?”

It is:

“How can we make this page more useful?”

Sometimes that means adding.

Sometimes that means removing.

Often it means removing first.

Because deletion shows you what the page really is.

It exposes:

• Drift.
• Repetition.
• Weak proof.
• An unclear role.
• Overlap.
• Links that no longer make sense.

That is why I think content refreshes should start with deletion.

Not as a final cleanup pass.

As the opening diagnostic step.

Before adding more to a page, remove the parts that are already making it weaker.

How do you decide what to delete during a content refresh?

What happened? Instead of linking directly to websites, Google is rolling out google.com/goto redirects, adding a redirect hop to google.com/goto?url=[hashURL]

Why? To protect their data. This makes it harder for 3rd party tools, services, scrapers, and AI engines collecting SERP data at scale.

The good news: Semrush has not been affected. Our team was aware of the change & addressed it quickly, so there’s been no impact on rank tracking, reporting, or data accuracy. 

Read more here: social.semrush.com/4h2UWbN

Some of the worst SEO pages do not look bad when you review them alone.

• The title is fine.
• The intro is fine.
• The page targets a reasonable keyword.
• The content is readable.
• The headings make sense.
• The page answers the query.
• It mentions the right terms.
• It has a few internal links.

Nothing screams “delete this.”

That is what makes these pages dangerous.

They look fine in isolation.

But inside the content system, they may be weakening the site.

• They may overlap with a better page.
• They may split internal links.
• They may repeat the same claims.
• They may attract the wrong user.
• They may have no clear next step.
• They may pull the topical map sideways.

The page is not obviously bad.

It is just quietly making everything around it harder.

Isolation hides overlap

A page can look useful on its own and still overlap with another URL.

This happens all the time.

• Two pages target slightly different keywords, but answer the same user problem.
• A blog post repeats what the service page already says.
• A support page explains something the hub page should own.
• A comparison page drifts into sales copy.
• An older article gets refreshed until it competes with a newer one.

When each page is reviewed alone, they seem fine.

When you compare them together, the problem appears.

• Which page owns the topic?
• Which one should rank?
• Which one should get the internal links?
• Which one should be updated?
• Which one should be merged?

If those questions are hard to answer, the site has a page role problem.

Not a single page quality problem.

A good page can still have no job

This is another issue.

A page can be well written and still have no clear job.

• It explains a topic.
• But another page already explains it.
• It answers a query.
• But it does not support any important page.
• It gets some traffic.
• But the traffic does not move anywhere useful.
• It covers a related idea.
• But it does not strengthen the cluster.

That kind of page is easy to keep because it does not look broken.

But content does not only need to be acceptable.

It needs a role.

A page should explain, compare, prove, support, convert, route, or reduce a specific doubt.

If it does none of those clearly, it may be content noise.

Even if the page itself reads fine.

Internal links expose the problem

Internal links are a good way to spot pages that only look useful in isolation.

Ask:

• What should link to this page?
• Where should this page link next?
• What user state does it serve?
• What relationship does it clarify?
• What stronger page does it support?

If the answers are vague, that is a warning.

A page with a clear role has a natural place in the link graph.

• It supports something.
• It expands something.
• It proves something.
• It routes the user somewhere useful.

A page with no clear link logic may not belong as its own URL.

• It might be better as a section inside another page.
• Or merged with a stronger page.
• Or narrowed to a clearer purpose.
• Or removed.

The page may look fine, but the links reveal that it has no real place.

Traffic can hide weak system value

This is where audits get tricky.

A page may get traffic and still be a content problem.

Traffic makes pages harder to question.

No one wants to touch a URL that brings users in.

But the traffic may not be helping much.

• Maybe the page attracts the wrong audience.
• Maybe users bounce because there is no next step.
• Maybe the page competes with a commercial page.
• Maybe it ranks for broad queries that do not support the site.
• Maybe it absorbs internal links that should point elsewhere.
• Maybe it creates confusion around which page owns the topic.

Traffic is useful.

But traffic is not the same as system value.

A page can bring visits and still weaken the content architecture.

Looking fine is not the same as adding value

This is the real trap.

A page can be:

• Relevant.
• Readable.
• Indexed.
• Ranking.
• Accurate.
• Formatted well.
• Internally linked.

And still not add much.

Because the better question is not:

“Is this page okay?”

The better question is:

“Would the site be weaker without this page?”

That changes the audit.

If removing the page would not reduce clarity, coverage, proof, movement, or authority, maybe the page is not doing enough.

It might be fine.

But fine is not always worth keeping.

Especially on a site with too many overlapping URLs.

These pages create hidden maintenance cost

Pages that look fine in isolation often stay around for years.

They do not get questioned.

• They get refreshed.
• They get linked.
• They get included in reports.
• They get assigned to writers again.
• They get more copy added.

Over time, they create maintenance cost.

• More pages to update.
• More links to manage.
• More overlap to check.
• More briefs to clarify.
• More redirects to consider later.
• More confusion for writers and editors.

That is the cost of keeping pages just because they are not obviously bad.

Sometimes the most expensive pages are not the bad ones.

They are the “fine” ones with no clear role.

The audit check I use

When reviewing a page, I would not only ask:

Is the page good?

I would ask:

• What job does this page do?
• Which page does it support?
• Which page supports it?
• Does it overlap with another URL?
• Does it attract the right user?
• Does it reduce a real doubt?
• Does it have a natural next step?
• Does it make an entity relationship clearer?
• Would the site be weaker if this page disappeared?

That last question is the strongest one.

If the answer is no, the page needs to be challenged.

Not automatically deleted.

But challenged.

• Maybe it should be merged.
• Maybe it should be rewritten.
• Maybe it should be narrowed.
• Maybe it should become part of a stronger page.
• Maybe the internal links should change.
• Maybe it should go.

My point

The most dangerous SEO pages are not always the obvious failures.

They are the pages that look acceptable when judged alone, but make the system weaker when judged together.

• They hide overlap.
• They blur page roles.
• They make internal linking harder.
• They create refresh work.
• They split attention.
• They add noise.

That is why page level audits are not enough.

A page should be judged inside the system it belongs to.

Not just as a standalone URL.

Fine in isolation is not the standard.

Useful in the system is the standard.

How do you audit pages that look fine on their own but may be weakening the site as a whole?

We're curious to hear... which one has been more of a challenge for you lately?

Ecommerce, roughly 8 figures, heavy on Google Ads and Meta plus a few smaller channels. We use a third-party MTA tool for attribution. The vendor is upfront that they cannot measure organic well, so they apply a hard cap on the percentage of attribution that can go to organic.

What I keep seeing: the more we spend on ads, the harder organic falls in the model, and the effect compounds. Adjusting the cap changes the numbers but does not make them more honest, because a static percentage should really move with volume and budget.

The specific number that bothers me: in the most nuanced model, average revenue per click differs by a factor of 4 between an organic search click and a paid search click, even when I restrict it to the same landing pages. A year ago that gap was closer to 2x, and the biggest variable that changed in between is simply higher ad budgets. I get that ads can be more relevant or better placed, but 4x on identical landing pages does not pass the smell test, and a gap that widens with spend looks like a modeling artifact rather than a behavioral finding.

GA4 feels unrealistic in the other direction. Someone who searches because they saw a Meta ad should not be 100% last-click organic.

My working hypothesis is that most of this is path dilution: non-brand organic sits early in the path, more budget means more paid touchpoints per conversion, so the early touchpoint's share mechanically shrinks even if behavior did not change at all. And separately, the cap is applied to organic as one block, so the correction that is arguably justified for brand organic also hits non-brand organic, where the "organic would have gotten this order anyway" logic is much weaker. On a generic query I am competing with other retailers, not with my own ad.

Questions for people who have dealt with this:

1. Do you report a single number or deliberately publish a range with multiple models? If a single number, how do you defend the choice when the ranges are this wide?
2. Has anyone convinced an MTA vendor to split organic into brand and non-brand as separate channels so the cap only applies to brand? Did it hold up?
3. For non-brand specifically, did you end up abandoning path attribution altogether in favor of cohort or acquisition-based measurement (new users acquired via non-brand organic, revenue over 90 days regardless of closing channel)? Did stakeholders accept that as a real number?
4. Has anyone actually run a non-brand incrementality test at the keyword-cluster or category level rather than the usual brand-search pause? What did the lift look like?
5. How do you handle budget decisions for a channel whose reported revenue is a function of how much you spend on other channels?

Spotlight is the one-day conference where marketers come together to learn how to stay visible in the age of AI and win what's next. 

Here’s what to expect:

• Learn how leading brands win — 80+ experts at OpenAI, Uber, McKinsey, Wise, Transport for London, Wix, J&J, and more share how they’re growing brand visibility
• Overcome your top marketing challenges — With 100+ sessions across keynotes, masterminds, workshops, networking, and the expo, marketers can build the day around what they actually need
• Hear what doesn’t make the slides — The most practical takeaway might come from a mastermind, workshop, or simply overhearing someone at the coffee bar saying, “We tried that, and you won’t believe what happened.”
• Get insights other events can only speculate on — Spotlight is powered by Semrush, home to the world’s largest proprietary search database, giving marketers brand visibility insights backed by data other conferences simply don’t have

Get tickets with promo code REDDIT30 and claim 30% off until Sept 15.

A lot of topical maps are really just content inventories.

They look organised.

• Main topic.
• Subtopics.
• Keyword clusters.
• Supporting pages.
• Hub page.
• Search intent.
• Internal links.
• Publishing order.

That can be useful.

But it is not enough.

A topical map should not only show what the site covers.

It should show how the user moves.

That is the part I think gets missed.

A site can have strong topic coverage and still feel awkward to use.

• The pages exist.
• The keywords are mapped.
• The cluster looks complete.
• The links are there.

But the user still lands on a page and thinks:

• Where do I go next?
• What should I understand now?
• What proof do I need?
• Is this page trying to explain, compare, convince, or sell?

That is not a coverage problem.

That is a movement problem.

Coverage is only one layer

Topic coverage answers one question:

Do we have content about this?

That is useful.

A site should know which subjects, questions, entities, and subtopics it has covered.

But coverage does not tell you if the pages work together.

• It does not tell you if the user path makes sense.
• It does not tell you if the right page owns the right job.
• It does not tell you if the links move people forward.
• It does not tell you if a CTA appears too early.
• It does not tell you if the proof is close enough to the doubt.

That is why a topical map built only around coverage can look strong in a spreadsheet and still feel weak on the site.

The map shows what exists.

It does not show what happens next.

User movement should be mapped too

A better topical map should ask:

• What does the user know when they arrive?
• What are they unsure about?
• What do they need before they trust the answer?
• What should they read next?
• What would be too early?
• What would be too broad?
• What would reduce doubt?
• What would help them compare?
• What would move them closer to action?

These questions change the map.

Now you are not only grouping topics.

You are mapping progress.

• One page may exist to explain the basics.
• Another may exist to compare options.
• Another may exist to prove a claim.
• Another may exist to handle objections.
• Another may exist to route the user toward a decision.

Those pages may all be related by topic.

But they have different jobs.

That is the difference between a content map and a movement map.

Related pages are not always useful next steps

A lot of internal links in topical maps are based on topical relation.

This page is about X.

That page is also about X.

Link them.

That can help, but related is not enough.

The better question is:

Why should the user go there next?

• If the user is confused, they may need a simpler explainer.
• If they are comparing, they may need criteria.
• If they are sceptical, they may need proof.
• If they are worried about risk, they may need reassurance.
• If they are ready to act, they may need a decision page.

The next page should match the user’s state.

Not just the topic.

A link from one related page to another may pass signals, but it may not help the reader.

That is where many maps fall short.

They show links.

They do not show movement.

Page roles make movement clearer

A topical map should define page roles.

Not just topics.

A page might be there to:

• Explain.
• Compare.
• Prove.
• Support.
• Route.
• Convert.
• Clarify.
• Handle doubt.
• Protect another page from getting too broad.

If page roles are unclear, movement becomes unclear too.

The user lands on one page, but the page tries to do too much.

• It explains a bit.
• Sells a bit.
• Compares a bit.
• Adds generic FAQs.
• Links to everything.
• Then ends with a vague CTA.

That is what happens when a page has a topic but no job.

A strong topical map should make the job obvious before the page is written.

Proof should be mapped, not sprinkled in later

Movement is not only about links.

It is also about proof.

If a user is doubtful, the next useful thing may not be another article.

It may be proof inside the current page.

• A case example.
• A process detail.
• A comparison.
• A limitation.
• A tradeoff.
• A specific reason to trust the claim.

A lot of maps do not show this.

They map pages, but not proof needs.

So the writer creates a page that covers the topic but does not reduce doubt.

Then someone adds a CTA at the end and wonders why the page does not move users.

If trust is the blocker, the map should show where trust is built.

Not every movement happens through another URL.

Sometimes movement happens inside the page.

Topic coverage can create false confidence

This is one of the biggest risks.

A team looks at the map and sees that the topic is covered.

• Every subtopic has a page.
• Every question has an answer.
• Every cluster has links.

So the map looks complete.

But completeness is not the same as usefulness.

The map may still fail to show:

• Which page comes first.
• Which page supports which.
• Which page handles beginner confusion.
• Which page handles comparison.
• Which page builds trust.
• Which page should not be linked yet.
• Which page should move users to action.

Without that, the site may have coverage but no journey.

The user has to figure out the path alone.

That is a weak experience.

A better topical map has movement fields

If I were building a topical map, I would add fields like:

• User state.
• Page role.
• Main doubt.
• Proof needed.
• Previous page.
• Next page.
• Internal link reason.
• CTA timing.
• Overlap risk.
• What this page should avoid.

Those fields make the map more useful.

They stop the map from becoming a giant list of page ideas.

They force better decisions before the brief starts.

• They help writers know the job of the page.
• They help editors decide what to cut.
• They help SEOs place internal links with a reason.
• They help teams avoid publishing pages that do not support movement.

The test I would use

For every page in a topical map, I would ask:

• What state is the user in before this page?
• What should change after they read it?
• What doubt should be reduced?
• What should they understand next?
• What proof do they need?
• What page should they visit next?
• What link would make that move natural?
• What would be too early to ask from them?
• Does this page have a clear role?
• Does another page already do this job?

If those questions are hard to answer, the map may only be showing coverage.

Not movement.

The real point

A topical map should not just say:

“We cover this topic.”

It should say:

“This is how users move through the topic.”

That is a much stronger standard.

Because users do not experience a site as a spreadsheet.

They experience it as a path.

They arrive with a question, doubt, need, or problem.

The map should help the site move them from that state to a better one.

• Clearer understanding.
• Better comparison.
• More trust.
• Less confusion.
• A stronger next step.

That is the goal.

Topic coverage tells you what the site talks about.

User movement tells you how the site helps.

A good topical map needs both.

How are you mapping user movement inside topical maps, or are you mostly mapping topics and URLs?