Your organic traffic is down, AI answers are appearing across the search journey, and the easiest conclusion is that SEO has stopped working. That conclusion is too broad to guide a useful response. If you react by publishing more generic posts, chasing every new AI optimization tactic, or decorating pages with trust badges, you can spend heavily without fixing the actual loss.
A better response starts by separating visibility loss from click loss, protecting the searches that still produce business value, and creating evidence that people and AI systems have a reason to reference. Here is how to make that shift without abandoning the parts of SEO that still work.
Start with the loss surface, not an AI narrative

Organic search is under pressure, but the pressure is neither uniform nor attributable to one cause. Across a modeled Similarweb sample, organic visits fell 13.2% in the U.S. and 24.4% in France between August 2024 and August 2026. Organic search also declined as a share of total traffic. Those figures describe estimated visits across selected domains, not unique people, revenue, or the entire web, and they do not prove that AI caused the losses.
The distribution matters more than the headline average. In the same sample, 62.5% of U.S. sites and 66.6% of French sites declined, yet roughly 1% of domains accounted for 40.2% and 48.5% of gross lost visits, respectively. The typical smaller site was close to flat, while publishers lost about 42% of organic traffic in both markets. A media business whose product is informational content therefore faces a different problem from a specialist company whose search pages support sales, leads, or product use.
Before changing your strategy, build a diagnosis around comparable periods, query groups, page types, and outcomes:
- Locate the decline. Compare the same pages, countries, devices, and time periods. A sitewide percentage can hide growth in commercial pages and a sharp decline in informational archives.
- Separate discovery from selection. For each query and landing-page group, compare impressions, average position, clicks, and click-through rate. Falling impressions indicate a different problem from stable visibility with fewer clicks.
- Group searches by the job they perform. Separate simple fact-finding, problem exploration, product evaluation, implementation help, and branded navigation. AI answers are more capable of completing some of these jobs without a visit than others.
- Connect the loss to business results. Compare qualified leads, sales, sign-ups, assisted conversions, or another outcome that matters to your organization. Ten thousand lost visits to interchangeable definitions may matter less than a small decline on a high-intent service page.
- Test other explanations. Review rankings, indexing, template changes, seasonality, changing demand, SERP features, brand demand, and channel mix. Timing alone does not establish AI as the cause.
The patterns will tell you where to work. If impressions and rankings fell together, investigate relevance, technical accessibility, internal linking, and authority. If impressions remain stable while click-through rate falls, inspect the result page, the query’s current intent, your title and description, and whether an answer feature is completing the task. If traffic declined but qualified conversions held steady, do not make raw visit restoration your primary goal.
Build pages that deserve a citation or a click
Publishing more versions of information already available everywhere is a weak response to declining traffic. Search systems can recognize substantial overlap, and generative systems can synthesize common knowledge without citing every page that repeats it. Original experience, proprietary data, expert analysis, distinct viewpoints, and real use cases give a page a reason to be retrieved, cited, and opened.
Audit your content by purpose rather than word count. Every important page should have a primary job:
- Answer pages resolve a constrained question. Give the answer early, define the conditions under which it holds, and support it with evidence.
- Evidence pages contribute something the existing results cannot reproduce independently: original data, a documented process, a test, a useful taxonomy, a calculation, or a first-party example.
- Decision pages help a reader choose. Explain tradeoffs, suitability, limitations, switching costs, and the evidence that should change the decision.
- Implementation pages help someone complete a task. Include the sequence, prerequisites, failure modes, validation checks, and the next action after completion.
A page can perform more than one job, but assigning a primary one prevents a common failure: answering a broad keyword while leaving the reader’s actual decision unresolved.
Use a five-part brief before commissioning or refreshing content:
- The reader’s decision: What will the visitor be able to do, choose, or rule out after reading?
- The direct answer: What is the shortest accurate response, including its most important qualification?
- The information gain: Which evidence, example, method, entity, or conclusion is not already interchangeable with the leading results?
- The proof boundary: Which statements are observed facts, which are inferences, and which are recommendations?
- The next useful action: Where should the reader go or what should they check once this page has done its job?
If you cannot identify the information gain, do not solve the problem by making the draft longer. Interview a genuine subject-matter expert, analyze first-party data, document the workflow, add a decision framework, or narrow the question until you can contribute a precise answer. AI can help organize notes, prepare a brief, or transcribe an interview, but it cannot independently supply experience your organization never captured.
Do not automatically delete an old page because its traffic fell. Check its backlinks, conversions, rankings, internal-link role, and historical demand first. Where several pages perform the same job with no distinct value, choose the strongest destination, consolidate carefully, preserve useful material, and redirect retired URLs to a genuinely equivalent page.
Turn E-E-A-T from decoration into observable evidence

There is no public, calculable E-E-A-T score that rises when you lengthen an author biography or add another badge. Experience, expertise, authoritativeness, and trustworthiness belong to Google’s Search Quality Rater Guidelines; they describe qualities Google wants good results to exhibit, not four direct scoring controls available to an SEO team. Human rater feedback is also not itself a direct ranking signal.
That does not make E-E-A-T useless. It makes checklist theater useless. Translate each quality into evidence that a reader, search engine, or referring site can actually observe:
- Experience: Show the process, inputs, constraints, edge cases, outcomes, and artifacts produced by real work. A generic claim about having experience is weaker than one verifiable detail that could only come from doing the task.
- Expertise: Explain the mechanism, use precise terminology, state where the advice applies, and distinguish certainty from judgment. Expert content also knows when a universal answer would be misleading.
- Authoritativeness: Earn relevant links, citations, mentions, and repeat recognition around a coherent subject. Authority depends on how the wider information environment connects to your work, not on what you declare about yourself.
- Trustworthiness: Support consequential claims, disclose methods and affiliations, keep ownership and dates accurate, correct errors, and make the page fulfill the promise that brought the visitor there.
Use real author information where authorship helps the reader evaluate the work. Do not invent a persona, inflate credentials, or add an unsupported claim such as “tested by experts.” Those changes create risk without creating evidence.
Apply the same rule to structured data. JSON-LD should clarify truthful entities, relationships, authorship, and page meaning already supported by the visible content. It cannot turn a recycled claim into original evidence, and markup that contradicts the page weakens clarity rather than improving it.
Treat AI visibility as a distribution problem
Your website is the canonical home for your strongest evidence, but it is not the entire discovery environment. Grok is a particularly clear example: X, Reddit, and YouTube can shape the sources and perspectives that appear in its answers. That platform-specific mix should not be generalized to every AI engine, but it demonstrates why website-only optimization leaves part of the problem untouched.
Build distribution outward from evidence instead of copying the same promotional message across channels:
- Choose a small, fixed set of audience questions. Include the questions people ask before they know your brand, while comparing options, and after they begin implementation.
- Create the canonical evidence. Publish the complete method, data, example, or decision framework on a stable page you control.
- Adapt the insight to each channel. A YouTube demonstration, an X explanation, and a Reddit answer should each be useful in their native context. Do not reduce every contribution to a teaser link.
- Participate transparently. Follow community rules, disclose a relevant affiliation, answer the question directly, and link only when the destination materially helps.
- Keep the entity consistent. Use stable names for the organization, product, people, and concepts so that separate mentions are easier to associate with the same entity.
- Observe what gets carried forward. Record which claims, pages, videos, or community explanations appear in AI answers. Strengthen the evidence behind repeated claims instead of manufacturing more near-duplicate pages.
On the page itself, make the useful passage easy to identify. Put the direct answer under a descriptive heading. Keep the claim and its evidence close together. Define the scope, version, market, or audience that limits the answer. Use tables only when the comparison is genuinely tabular. Label observation, inference, and recommendation distinctly. Keep important URLs stable, and ensure structured data agrees with visible facts.
This is the practical overlap between SEO, answer engine optimization, and generative engine optimization: a retrievable answer, credible evidence, clear entity relationships, and a reason for another system or person to reference the work. None of those requires writing for a robot at the reader’s expense.
Replace the traffic-only report with a visibility-to-value scorecard
Sessions remain useful, but they no longer describe the full search outcome. A page may lose low-value clicks while retaining sales. Another may receive impressions and AI citations without producing a measurable business result. Your reporting needs to keep those cases separate.
| Layer | What to measure | Decision it supports |
|---|---|---|
| Discovery | Impressions, rankings, indexed pages, and visibility by query cohort | Whether the problem is eligibility, relevance, authority, or changing demand |
| Selection | Clicks and click-through rate by query and landing-page type | Whether the result earns a visit when it appears |
| Consumption | Engaged visits, task completion, and useful next-page movement | Whether the page resolves the promise behind the click |
| AI presence | Citation frequency, cited URLs, represented claims, and brand inclusion for a fixed prompt set | Where your evidence is being retrieved and where competitors supply the answer |
| Business value | Qualified leads, sales, sign-ups, retention actions, or assisted outcomes | Which page and query groups deserve investment |
For AI visibility, use a repeatable prompt set tied to real audience questions. Keep the model, market, language, and test conditions as consistent as the platform allows; record the date and cited URL; and look for patterns across repeated observations. A single favorable answer is not a durable benchmark.
Review the scorecard by query cohort and page purpose, not only as a sitewide total. That lets you make different decisions for different losses: defend commercial discovery, improve a weak result snippet, add evidence to a frequently cited topic, consolidate commodity pages, or stop funding traffic that never produced value.
Key takeaways
- Do not label a traffic decline “AI-caused” until you separate impression loss, ranking loss, click loss, page type, market, and business impact.
- Protect pages that support decisions and outcomes; do not spend indiscriminately to restore every lost informational visit.
- Give each important page an identifiable information gain: original evidence, experience, analysis, method, or application.
- Treat E-E-A-T as an editorial standard expressed through observable proof, not a set of ranking switches.
- Measure search as a path from discovery to selection, citation, consumption, and business value.
Start with one declining landing-page group. Classify its query job, determine whether visibility or selection changed, identify the business value that remains, and improve the evidence on the strongest page before commissioning anything new. That first diagnosis will tell you far more than another sitewide traffic forecast.
References
- HiGoodie Blog – How to Rank on Grok: Get Your Brand Cited in X’s AI Search
- Search Engine Land – SEOs, we need to talk about E-E-A-T
- Search Engine Land – Human-first SEO: The risks of optimizing for AI over users
- Search Engine Land – Organic traffic is down, but it’s not all AI


Leave a Reply