SEO for a five-person agency in the AI Overviews era

Your blog traffic has been sliding since sometime in 2024 and you can't figure out why. The posts are the same quality as always, and titles like "Top 10 places to visit in Manali" and "Best time to visit Kerala" still show up on page one in Google. But the clicks aren't coming. If you've searched "ai overviews travel website traffic drop" trying to make sense of it, you're not imagining it and it isn't your writing.

Google now answers the question before the reader ever reaches your page. The AI-generated summary at the top of the results, called the AI Overview, reads your content, several competitors' content, and a few forums, then writes its own two-paragraph answer right there on the results page. For a query like "best time to visit Kerala", the reader gets their answer and never scrolls down to your listing.

This isn't a reason to give up on SEO for your travel agency. It's a reason to stop writing content an AI can already answer, and start writing content only you can answer, because you actually run the trips. This post covers what to stop, what to build instead, and how to tell whether it's working when "traffic" stops meaning what it used to.

Why your blog traffic is falling and it's not your writing

The numbers explain the feeling. AI Overviews now appear on roughly 48% of all Google searches, up 58% year-on-year, which means nearly half of all searches now get a synthesized answer above the organic results, as of July 2026.

Travel gets hit harder than most categories. Informational travel queries, the "top 10 places", "best time to visit", "things to do in" style posts most agencies built their blogs on, show an AI Overview roughly 38.7% of the time. If your blog is mostly this kind of content, well over a third of your target queries are being answered without a click, and that share is only growing.

Even when your page still ranks well, the click math has changed underneath you. On queries where an AI Overview appears, average organic click-through rate falls from about 3.97% to 0.64%: a drop of roughly 84% (do the maths: (3.97 − 0.64) ÷ 3.97). Being in position one or two doesn't protect you either; the same research shows 30–50% CTR reductions even for top-3 rankings once an AI Overview appears on the page.

Put together: rank #1 for "best time to visit Ladakh", get an AI Overview on that query (very likely, given the 38.7% rate), and you should expect to lose most of the clicks you used to get for that same ranking. The keyword is still worth ranking for. Building topical authority matters, but it will never again convert like it did in 2022.

The content Google already wrote for you

Here's the uncomfortable filter: if a question can be answered correctly in three sentences from public information, an AI Overview will answer it, and no travel agency blog post is going to out-rank a synthesized summary of the entire internet's answer to that same question.

That kills a specific category of post that many agency blogs are built on:

• "Top 10 places to visit in [destination]"
• "Best time to visit [destination]"
• "Things to do in [destination] in [X] days"
• "Is [destination] safe for solo travellers"
• "Visa-free countries for Indian passport holders"

These aren't bad topics. They're just topics where you have no informational advantage over every other source Google's model has already ingested. Writing more of them is writing content for an audience of one AI crawler, not for a human who might book with you.

Careful: don't confuse "this ranks" with "this converts." A page can still show up on page one for a generic query and drive zero bookings, because the searcher's question got fully answered in the AI Overview box above it. Rankings reports that don't separate AI-Overview-affected queries from clean ones will make your SEO look fine while your enquiries quietly dry up.

What still needs a human: real prices, not "starting from"

What an AI Overview cannot do is quote you a real, current price for a real, specific itinerary that you actually sell. It can tell a searcher the average cost of a Kerala trip in general terms, pulled from aggregated sources. It cannot tell them what a 6-night Kerala package departing from Nagpur, with train travel included, costs this month, because that number lives nowhere on the public internet except in your quotations.

This is the gap worth building pages around: departure-city, package, and real-price combinations that are specific enough that no generic summary can pre-empt them.

Example: Compare two pages targeting roughly the same traveller.

Page A: "Kerala Tour Package: 6 Nights / 7 Days" with a price range of "starting from ₹15,000 per person." Generic, unverifiable, and every competitor's page says almost the same thing. An AI Overview can summarise "Kerala packages typically start around ₹15,000" and the searcher never needs your page.

Page B: "Kerala Package from Nagpur: 6N/7D by Train, ₹18,500 per person (July 2026 batch, 2 sharing)." This includes the actual train name and class, the exact hotels, and a real per-person breakdown (transport ₹4,200, stay ₹9,800, transfers and sightseeing ₹4,500). Nobody else has this specific number for this specific origin city. It answers "how to rank tour package keywords on google" for the long-tail terms that actually convert: destination + departure city + real number.

Build a page per departure city per popular package, not one generic destination page. A five-person agency running departures from Nagpur, Nashik and Pune should have three separate costed pages for the same Kerala itinerary, not one page trying to serve all three with a vague price range. Update the price and batch dates every time you re-cost the trip. A stale number is worse than no number, and it's the freshness that keeps these pages out of reach of a general-purpose AI summary.

The same logic extends to your quotation format: if your quotes already itemise cost per component, turning that into a public page is mostly a copy-paste exercise, not new content work.

Permit and visa logistics: the paperwork an AI would rather not get wrong

The second category that still rewards a human writer is operational logistics with real consequences for getting it wrong: Inner Line Permits for Ladakh, Bhutan's Sustainable Development Fee process, or the current advisory status for travel to sensitive border areas. These change often enough, and carry enough downside if wrong, that a careful searcher, and increasingly the AI model itself, treats a generic summary as insufficient.

This is content where "as of [date], here is exactly what our agency filed and how long it took" beats "generally, permits are required." Write it as a process document, not a listicle:

1. What the permit or fee actually is and who it applies to.
2. Where and how you apply (portal name, office, or agent).
3. Documents required, in the order the counter asks for them.
4. Processing time you've actually experienced, not the official SLA.
5. What goes wrong (offices closed on local holidays, permits that don't cover certain routes, seasonal closures).

This kind of page also tends to earn something an AI Overview can't take from you: a citation. When your write-up is specific, dated, and operationally accurate, it's the kind of source models pull from and sometimes link back to. That's a very different outcome from being one of a hundred interchangeable "top 10 places" posts. If you're already covering the 2026 visa landscape for top client destinations, the permit and logistics angle is the natural next layer under each country.

Careful: don't let an AI tool draft this kind of page for you and publish it unchecked. Permit rules and advisories are exactly the category where AI models get travel details wrong most often, and a wrong permit fee or closed route on your own website is a worse trust signal than not having the page at all.

How to structure a page so the AI engine quotes you, not just Google

If part of the goal is to become a source AI Overviews and chat-based answers actually cite, structure matters as much as content.

• Answer the question in the first 40 words. Don't bury the price, the permit fee, or the departure date under three paragraphs of scene-setting. Models (and impatient readers) weight the opening heavily.
• Use tables for anything comparative or numeric. A price breakdown, a permit-fee table, a departure-date calendar. These all get lifted into summaries more reliably than the same information in prose.
• Date everything. "As of July 2026" on a price or fee is a signal of freshness that both search engines and readers trust more than an undated claim.
• Show your specific numbers, not ranges. "₹18,500 per person, July 2026 batch" is citable. "₹15,000–₹25,000" is not: it reads as a guess, because it is one.
• Write the byline as an operator, not a copywriter. "Twelve years running Ladakh departures" is a trust signal a generic aggregator page can't claim.

None of this is a guarantee of a citation. It's the difference between content that could plausibly be quoted and content that's indistinguishable from a thousand other pages saying the same generic thing.

Measuring what actually moved

Once your top-of-funnel content is mostly answered by AI, "organic sessions" as a headline metric stops meaning what it used to. A page can be doing its job (building trust, getting cited, feeding branded search) while showing declining click numbers in Analytics. Track these instead of mourning the raw traffic number:

Signal	Where to find it	What it tells you
Branded search volume	Search Console, "your agency name" queries	People saw you somewhere (an AI answer, a citation) and searched you by name
Direct/URL-typed visits	GA4, channel = Direct	Same signal: someone remembered your site without clicking a link
Click-through on non-AI-Overview queries	Search Console, filter by query type where possible	Your real organic performance, isolated from queries you were never going to win anyway
Enquiries from "how did you hear about us"	Your enquiry form or WhatsApp intake	The only metric that pays your rent: track it even if the channel is "not sure, I just found you"

A rising trickle of branded searches and direct visits after you published a specific permit guide or a departure-city price page is a reasonable proxy for "an AI engine or a forum somewhere is pointing people at you", even when you can't see the exact citation. It's imperfect, but it's a better read on 2026 SEO than watching a raw sessions graph that AI Overviews have structurally deflated.

Common questions

Should I stop blogging entirely?

No. Stop blogging generic destination content and redirect the same effort into departure-city pricing pages and operational logistics guides. The volume of writing can stay the same; the topic selection needs to change.

How long until an AI engine starts citing my pages?

There's no reliable timeline, and no verified data on this in the sources behind this post. Treat any specific promise of "citations in X weeks" with suspicion. Freshness, specificity, and consistent publishing over months are the only levers you control.

Do I need to keep publishing "best time to visit" content at all?

Only if you can add something an AI Overview can't: your own bookings data by month, your own weather notes from trips you ran, or your own pricing seasonality. A "best time to visit Kerala" post built entirely from public climate data is exactly the content Google's summary already replaces.

What if I genuinely don't have real pricing to publish?

Start with your next costed batch. Every time you finalise a departure's costing sheet for a client, that same breakdown (minus your margin, if you're not comfortable publishing that) can become a public page within a day. It compounds; six months of departures becomes six months of unique priced pages no aggregator has.

The short version

• AI Overviews now show on around 48% of all Google searches, and roughly 38.7% of travel informational queries. Check the source stats and treat this as structural, not a phase.
• Where an AI Overview appears, click-through rate on organic results falls by roughly 84% on average, even at top rankings. Don't judge a page's success by its position alone.
• Stop writing generic "top 10" and "best time to visit" posts; that content is exactly what AI Overviews already answer for free.
• Build departure-city + package + real-price pages with specific, dated numbers: this is the pricing data no aggregator can pre-empt.
• Write permit and visa logistics guides as operational process documents, dated and specific, not generic advisories.
• Structure pages to answer in the first 40 words, use tables for anything numeric, and date every price or fee.
• Track branded search, direct visits, and enquiry source instead of raw organic sessions: the old traffic number no longer tells the whole story.