Medical tourism content calendar: reading seasonal demand
Building a medical tourism content calendar without a volume table: reading seasonal demand with Search Console, Google Trends and source-market calendars.
By Roozbeh Nazari · CEO
When people say "content calendar" in medical tourism, what they expect is a table of "which treatment is searched for in which month". Publishing such a table honestly requires a verifiable search-volume dataset, broken down by market and by month; we did not have access to that dataset in the environment where this article was prepared. So we are not writing a month and a volume per treatment here. Instead, we explain how each clinic can read seasonal demand from its own data and public sources, and how to turn that reading into a twelve-month calendar. The method does not change when you have access to a tool with volume data; the tool only adds a third verification layer.
Which data you can read seasonality from
You have four sources, and each has a different limit. The first is the Search Console performance report: month-by-month impressions and clicks for the queries bringing people to your own site, going back up to sixteen months. This is the most reliable source for seeing seasonality, because it is real users and real queries; its limit is that it only shows queries you are already visible for. The second is Google Trends: in Google's own words, a largely unfiltered, anonymised sample of actual search requests. Trends gives not absolute volume but an interest index normalised to the highest point in the selected range; it is suitable for reading a source market's year by selecting country and language, but it is not an answer to "how many people searched". The third is your own enquiry records: the log of enquiries arriving via WhatsApp and forms, kept with date, country and treatment. This shows what search data does not, namely when a query turned into an enquiry. If you have no such record, start today; a year from now it will be the most valuable input to the method in this article. The fourth is the Google Ads search terms report: if you run ads, the actual searches that triggered them and their distribution across months.
Source-market calendars: the dates that shape demand
There is one more layer that shapes seasonal demand independently of search data: the calendar of the source markets. These are not forecasts; they are calendar facts. In the Gulf countries, Ramadan and the two Eids move about eleven days earlier every year; during Ramadan, travel and planned treatment enquiries drop in practice and recover after Eid. The Gulf's school holidays and extreme-heat period fall in the summer months, and long trips pile up in that window. In the Iranian market the year begins with Nowruz, around 21 March, and the Nowruz holiday lasts close to two weeks. In European markets, the summer holidays and the year-end holidays are decisive. You need to confirm the direction and size of these dates' effect on demand in your own Search Console and enquiry data; here we only give the calendar, and you are the one measuring the effect. The reading method in our article on patient flow from MENA to Türkiye makes sense when used together with this calendar.
Building the calendar: a twelve-month grid
Place the four data sources and the market calendar in a single grid: treatments in the rows, months in the columns. Write three things in each cell: the share of impressions that treatment's queries had in that month in Search Console, the level of the Trends index in that month, and the number of enquiries that arrived in that month last year. If all three signals point the same way, mark the cell "high"; if two do, "medium"; if one or none does, "low". This three-level marking makes priority visible without writing a volume figure, and because there is no figure it does not produce false precision either. Keep the grid separate per language: the same treatment can rise in different months in Arabic queries and in Persian queries, and a single grid erases that difference. Then place the content types: treatment guides, which are valid all year and go into the update schedule; season and travel-logistics articles, which are placed ahead of the target month; and articles that match recovery time with holiday length, which are placed ahead of the holiday calendar.
Publication timing: getting ahead of demand
Publishing content in the month it starts being searched for is late. A new page takes time to be crawled, indexed and settle in the rankings; in practice we publish seasonal content at least eight to twelve weeks before the target month and update it at least once before the target month arrives. That is an observation, not a rule; measure in Search Console when a page on your own site received its first impressions after publication and adjust the lead time accordingly. On multilingual sites the timing also changes by language: for the same treatment, Arabic content is brought forward according to the Gulf calendar, Persian content according to the Iranian calendar and English content according to the European calendar. On the keyword side, our four-language research method builds each language's query set separately; the calendar is applied to those sets separately too.
The compliance boundary: what seasonal content can and cannot say
The temptation of seasonal content is to slide into promise language such as "come during the summer holidays, recover on holiday". Türkiye's regulation on promotion and information in health services restricts promises of treatment outcomes, incentive-style campaign language and expressions aimed at generating demand. Seasonal content can explain the medical content of a treatment, the time the recovery process requires and the travel logistics for informational purposes; it cannot promise a specific result, a time guarantee or a discount. When building the calendar, add a "what this article can say" note to each cell; let the legal boundary be set before the publication date.
Measurement and correcting the calendar
The calendar is a hypothesis; it is tested every month against Search Console and enquiry data. At the end of the month ask three questions: did impressions and enquiries really rise in the cells we marked "high", did unexpected demand appear in the "low" cells, and was the publication timing early enough. At the end of a year you have a season map by treatment and by language, verified with your own data, and the second year's calendar is no longer a guess but a measurement. In the projects we run for clinics, this loop is reviewed quarterly; because the market calendar shifts every year, the calendar cannot stay fixed.
Conclusion
A seasonal demand table is not something you buy; it is something you build from your own data. When the sixteen months of Search Console history, the normalised Trends index, your enquiry records and the source-market calendar come together, a grid emerges that shows which treatment to bring forward in which month without writing a volume figure. We gave no month and no volume in this article; they will be in your grid, and there they will be verified.