Affiliate disclosure: This article contains affiliate links to Semrush. If you sign up through them, Creaitz may earn a commission at no extra cost to you.
Making a page easier for AI systems to summarise sounds like an obvious improvement. Add a concise comparison, highlight your strengths and make important information easier to extract.
But how do you know whether the change helps your website overall—not just its appearance in AI answers?
That is the practical GEO vs SEO question.
Generative engine optimization (GEO) aims to improve visibility in AI-generated answers, while SEO supports discovery through traditional search.
The same page can serve both, but an improvement in one does not automatically establish success in the other.
When you change a page to improve its visibility in AI answers, include its existing search performance in your review.
A service comparison, pricing explanation or summary can affect several outcomes: what visitors understand, which sources AI systems cite and whether prospective customers enquire.
GEO vs SEO testing helps you examine those outcomes together. Define the change, record your starting position and decide which business measures you will monitor before publishing.
You can apply this approach to a single service page, course landing page or resource hub.
Table of Contents
ToggleWhat Omio Learned From Testing Two Page Changes
Travel-booking platform Omio tested this challenge with SearchPilot by measuring how specific page changes affected both LLM-referred visits and Google organic sessions.
One experiment added a section explaining the brand’s unique selling points. LLM-referred sessions increased by 18%, while the Google organic result was inconclusive: the test did not establish a clear benefit or harm in that channel.
A separate experiment added quantitative and comparative bullet points above an existing summary table. LLM traffic improved, but the test indicated a likely 6.5% decline in Google organic sessions. Because Google organic was Omio’s largest traffic source, the team decided against rolling out that version.
These results apply to the specific implementations tested on Omio’s pages. Use them to inform your testing method: define the edit and measure its effects across relevant channels.
On a smaller website, you can begin with one reversible change and a documented observation plan.
Plan Your GEO vs SEO Test
1. Test one change at a time
Imagine you are a freelance web designer. Prospective clients regularly ask whether they need a landing page or a full website.
You could add a concise comparison to your service page, explaining the differences in scope, deliverables and suitable use cases. That would address a real customer question while giving AI systems clearer information to reference.
Your hypothesis might be:
Adding a service-comparison section will help visitors choose the right option and may improve relevant AI visibility, without reducing qualified organic enquiries.
Now you have something specific to evaluate.
Add the comparison, but avoid changing the page title, pricing, internal links and enquiry form at the same time. Otherwise, any movement becomes harder to interpret.
Save the original version and record the affected URL, publication date and exact edit. Then decide what you will monitor—and what deterioration would make you reconsider the change.
That turns “make it AI-friendly” from a vague instruction into a manageable experiment.
2. Decide what must not get worse
Before editing, identify the page’s business purpose.
If you sell web-design services, you might define success as enquiries that match your scope, budget and availability.
Before publishing the comparison section, decide what you will monitor:
- Business Outcome: Enquiries that match the services you offer.
- SEO Guardrails: Google clicks to the page and rankings for relevant service keywords.
- AI Indicators: Appearances in relevant answers, citations and identifiable referral visits.
Use a consistent definition of a qualified enquiry before and after the change.
There is no universal acceptable percentage decline. You should set expectations using your traffic volume, normal fluctuations and business priorities.
An AI citation and a qualified enquiry are different units. Adding them together does not produce a meaningful “net win.”
3. Monitor the same pages and conditions
Keep the comparison focused on the edited service page.
Track relevant searches, such as “landing page designer,” alongside AI questions about choosing between a landing page and a full website.
Select your actual tracking terms from customer enquiries, Search Console data and audience research.
Use Semrush’s Position Tracking to monitor relevant Google keywords with a consistent location, device and keyword set.

Record ranking movements alongside search clicks, sessions and qualified enquiries. Investigate changes across those measures before drawing a conclusion.
Alongside that, review relevant prompts, mentions and cited pages in Visibility Overview.

Keep the platform, market and reporting period consistent where those controls are available. Record the report’s scope rather than treating it as a complete record of every AI answer.
Use your own Search Console and analytics data for observed search clicks, sessions and business actions.
Semrush One combines SEO and AI visibility tools in one subscription. Use the reports to document observations within your testing plan.
Our guide to AI search reporting explains how to interpret visibility measures and record their limitations.

4. Match the method to your website’s size
Omio’s testing approach used statistically similar groups drawn from thousands of comparable pages.
A small portfolio or community website may not have that scale.
You can still make a limited, reversible change and observe it carefully.
If you have genuinely comparable service pages, leave some unchanged as a reference.
Choose reference pages with similar purposes, audiences and demand patterns. Document the differences that could affect your comparison.
Describe a small before-and-after review as an observational test. A statistically reliable A/B test requires an appropriate design and sufficient data.
Record other developments: campaigns, technical changes, seasonal demand and search updates.
Low traffic may leave the result inconclusive. That is a valid outcome too.
5. Choose: keep, revise, reverse or wait
At the review point, consider the evidence together.
- Keep: the change helps users and business outcomes, with no material deterioration observed in the guardrails.
- Revise: one channel improves while another shows a concerning decline.
- Reverse: there is credible evidence of material harm and a practical rollback is available.
- Wait: the observation period or data volume is insufficient.
If your AI mentions increase while qualified enquiries fall, investigate the affected pages, traffic sources and enquiry quality. If enquiries improve and search performance remains stable, record that encouraging pattern and continue monitoring other possible explanations.
If performance falls, inspect technical issues too. Site Audit can surface broken links, crawlability problems and other implementation issues that deserve investigation. It cannot determine by itself that a GEO change caused the decline.

Our zero-click attribution guide explains how to combine recorded website activity with customer-reported discovery and confirmed sales.
Make the Next Rollout an Informed Decision
Keep a record of the original page, your hypothesis, the exact edit and the measures you will review. At the agreed checkpoint, decide whether to keep, revise, reverse or continue observing the change.
Use what you learn to improve the next experiment. A result can remain inconclusive, particularly on a low-traffic website; preserve that uncertainty in your report.
You can try Semrush One free for seven days to establish your SEO and AI visibility baselines. Give the next rewrite a test run before handing it the whole website.