What 166K Clicks Taught Me About Using AI for SEO

Over three months, my static website generated 166K Google clicks from 1.39M impressions, with an 11.9% CTR and 7.5 average position.

The graph also shows traffic declining after its peak. That is important: AI did not create automatic, permanent growth. What helped was using AI inside a measurable SEO workflow—and reverting ideas when the data disagreed.

Here is the loop I now use.

1. Use Keyword Planner for discovery, not decisions

I start with broad product terms in Google Keyword Planner and export the results.

Search volume and competition help me find possible clusters, but a high-volume keyword is not automatically a reason to create a page.

Before choosing one, I ask:

• Does it match my product?
• Is its intent different from pages I already have?
• Does an existing URL already rank for it?
• Can I create something genuinely useful for the searcher?

This prevents keyword research from becoming a factory for thin pages.

2. Check keyword ownership with GSC MCP

I use a Google Search Console MCP connection to pull query-and-page data directly into my workflow.

This is more useful than looking only at a keyword report. A keyword may appear to be an opportunity while an existing page already ranks in positions 1–3.

Creating another page could split its signals and cause keyword cannibalization.

My basic decision record contains five fields:

Query: target keyword

Current URL: ranking page or none

Evidence: clicks and position from a settled GSC window

Intent: informational, local, comparison or action

Decision: improve, create or reject

If the intent already belongs to an existing page, I improve that page instead of creating another URL.

3. Use Claude skills as reviewers, not autopilot

I use Claude SEO-audit and keyword-research skills to inspect proposed changes.

They help me check:

• Duplicate keyword targets
• Titles, descriptions, H1s and canonicals
• Indexability and internal links
• Thin or repetitive content
• Unsupported product and pricing claims
• Possible performance regressions

AI can investigate, compare and draft—but it cannot replace evidence or editorial judgment.

I reject templated pages that only swap a keyword or city name.

4. Fix what Search Console actually flags

When clicks fall, I do not immediately rewrite the entire site.

I first separate incomplete recent Search Console data from settled data. Then I decompose the loss:

1. Compare equivalent date ranges.
2. Find which page lost clicks.
3. Pull that page’s query-level changes.
4. Check its indexing, canonical and crawl status.
5. Review the commits made before the decline.
6. Revert only when the evidence supports it.

This has saved me from treating every ranking fluctuation as a technical emergency.

5. Audit before and after deployment

Before every SEO commit and deployment, I run the repository SEO audit.

After deployment, I inspect the live HTML—not just the local source file—to verify:

• Title
• Meta description
• Canonical
• Robots directive
• H1
• Sitemap entry

Only after the production page passes those checks do I submit it through Search Console and begin its validation window.

The main lesson

My best results did not come from asking AI to “write SEO content.”

They came from giving AI access to structured evidence and enforcing a release process:

Keyword Planner → GSC ownership check → human intent decision → SEO audit → deploy → live verification → measure or revert

That is the process I use on Flingo, a product website with hundreds of static pages.

AI makes research and diagnosis faster.

Search data decides whether an idea deserves to ship.

How are you using AI in SEO without handing it the steering wheel?

Comments

[Codearea]

This is a great example of using AI as an SEO assistant rather than an SEO autopilot. The focus on GSC data, keyword ownership, and validating changes after deployment is especially valuable. I also like the point about reverting changes when the data disagrees—SEO needs measurement, not just AI-generated content.

[Mofidul Islam]

Exactly—AI is most useful when it accelerates investigation, not when it makes the final decision. GSC provides the evidence, keyword ownership prevents cannibalization, and post-deployment validation closes the loop. Being willing to revert a weak experiment has been just as valuable as finding a successful one.

[Fouad El Mourabit]

The strongest point is the feedback loop: use AI to inspect hypotheses, but let settled Search Console data decide. Segmenting changes by query intent and page type also helps distinguish a ranking loss from a SERP-feature or snippet change.

[Mofidul Islam]

Exactly. That’s the approach I did— AI proposes the hypothesis, but Search Console gets the final vote.

[Mark2Phillips9]

The data from 166K clicks underscores the necessity of adapting SEO strategies to accommodate AI-driven search algorithms. Understanding user intent and optimizing for these shifts can enhance brand visibility significantly.

[Mofidul Islam]

Absolutely. One lesson for me was that adapting doesn’t mean publishing more AI-generated content—it means using real query and page-level data to understand intent. I use GSC to verify which URL already owns a query, then improve or create content only when the intent is genuinely different. That has helped protect existing visibility while testing new opportunities.