Language schools and tutoring centres sell against a calendar their customers already carry in their heads. Term dates, exam seasons and enrolment windows open and close on schedule, whether or not anybody has done any marketing that month.
That makes the timing of visibility unusually decisive. A school that is invisible in June is not slightly behind — it has missed the window in which September’s students chose where to go. By the time the intake starts, the decision was made weeks ago, quietly, by a parent comparing three websites on a phone.
This guide covers the way to stay present through that cycle without hiring anyone to run social accounts: letting the school’s own website do the posting.
Most language school and tutoring websites contain more postable material than their owners realise:
Each of these can be its own feed, and each can go somewhere different. That separation matters more here than in most sectors, because current students and prospective ones want completely different things.
An RSS feed is a plain, machine-readable list of the newest items a website has published. Your site almost certainly produces one already. On WordPress it sits at your domain followed by /feed/, and every category has its own — /category/courses/feed/, for instance.
An auto-posting service watches that feed. When a new item appears it builds a post and publishes it to the accounts you connected. Nothing is scheduled by hand. Publishing on the website becomes the trigger.
For a school the effect is that adding the autumn timetable to the site — which you do anyway so people can enrol — is the same action as announcing it across your accounts. This is the ordinary shape of RSS automation, and it fits education well because the content is dated, planned in advance, and genuinely useful to read.
The post carries the item’s title and a link back to your site. The network builds its preview card from the page’s open-graph tags — the image, title and description your site already declares. So your website controls how the posts look.
For schools this is worth one deliberate decision. Course pages published without an image produce bare posts. A simple branded image per level or per course type — reused across intakes — is enough, and removes any reason to delay publishing while somebody finds a photograph.
This is the distinction that decides whether a school’s social presence works, and it is the one most often missed.
Prospective students and parents want to know whether you are any good, when courses start, and what it costs. They are reading months before they act, and they compare you with two or three others.
Current students want timetable changes, exam reminders and practice material. They already bought; posts aimed at selling to them are noise.
Sending both streams to the same place at the same volume dilutes both. The table below separates them.
| Feed | Audience | Destination | Volume | Publish when |
|---|---|---|---|---|
| Course intakes | Prospective | Facebook, LinkedIn | 3–6 / month | 8–12 weeks before start |
| Exam dates & deadlines | Both | 2–4 / month | As soon as published by the board | |
| Study tips | Prospective | Pinterest, Facebook | 4–8 / month | Continuously, all year |
| Results | Prospective | seasonal burst | Results day onwards | |
| Teacher profiles | Prospective | Facebook, LinkedIn | 1–2 / month | Before each intake |
| Timetable changes | Current | Facebook only | as needed | Immediately |
The row that earns the most over a year is study tips, which is also the one schools most often skip because it does not sell anything directly.
Open your site and add /feed/ to the address. XML means you have one. Then create a category per content type — Courses, Exams, Tips — and use them consistently. Each category’s feed is its address with /feed/ appended.
Facebook carries most of the value for local schools. Add LinkedIn if you teach business English or professional courses, where the decision-maker is an employer rather than a parent.
Set each pairing separately so intakes and timetable changes behave differently.
Parents read in the evening; adult learners read at lunchtime and after work. A publishing window lets you hit those without anyone being awake for it.
This is the single most valuable habit for a school, and it runs against instinct.
The temptation is to promote an intake when enrolment opens. But the choice of school happens earlier — when a parent first starts looking, or when an adult decides this is the year they finally do it. If your first post about September appears in late August, you are advertising to people who already chose somewhere else in June.
Publish intakes eight to twelve weeks ahead. The page can say places are limited without being a hard sell.
Keep the tips feed running in the gaps. Between intakes there is nothing to sell, which is exactly when a school disappears. A short, genuinely useful piece each week keeps the account alive and reaches people who are still deciding.
Treat exam deadlines as a service, not a promotion. Registration cut-offs get shared by parents to other parents, which is reach you cannot buy.
Results are the most persuasive thing a school publishes and the easiest to get wrong.
Permission first, in writing. For under-eighteens that means a parent or guardian, and the permission should be specific about whether a name or photograph may appear.
Aggregate beats individual for most schools. “Nineteen of twenty-two passed B2 this session” is strong, needs no permissions, and does not put a teenager’s exam result on the internet.
Never publish before results are officially confirmed. Correcting a published result is worse than posting nothing.
Once the policy is settled, a Results category feeds the automation like anything else, and the school accumulates a public record that does more persuading than any advertisement.
Most schools sell a course. The ones that fill fastest sell a smaller first step, and that changes what is worth automating.
A trial lesson, a free level test or a taster session asks far less of a hesitant parent than committing to a term. It is also a dated, publishable item — which means it belongs in a feed like everything else.
Publish level tests as events, not as a service page. A page that says “free level test, Saturday 10 March, four places” is postable and creates a reason to act. A permanent page saying “we offer level tests” never appears in a feed again after the day it was written.
Run a waiting list feed for full courses. When an intake sells out, the useful post is not “sold out” but “next intake opens in May, join the list”. Schools that publish this consistently start each term with enrolments already in hand.
Keep the first step and the full course in separate feeds. Someone who has already booked a trial does not need three more posts about trials; they need the course dates.
The pattern behind all three is the same: anything with a date attached can be published on your own site and will then post itself. Anything written as a permanent page will not. When a school finds that its automation has gone quiet, the cause is almost always that its most persuasive material was written as static pages rather than as dated items.
Schools have a genuine advantage here: enrolment is an explicit, dated action.
Ask on the enrolment form. One field — “how did you hear about us?” — answered by every student, is worth more than any dashboard. After one intake you will know which feed is doing the work.
Tag the links. Add UTM parameters to the addresses your feed emits so your analytics can separate social visits. Watch whether the course pages get opened, not how many likes a post received.
Expect a lag. A tips post published in April may produce an enrolment in September. Judge the tips feed over two intakes, not two weeks, or you will cut the thing that is actually filling your classrooms.
The page has no open-graph image. Use a reusable branded image per course type so publishing is never delayed.
Course pages are being edited and re-published for each new term. Create a new page per intake instead of recycling one, or the feed will treat the edit as a new item.
Both streams are going to the same place. Split the feeds as in the table above.
No per-run limit or publishing window. Set both before you publish a full term’s courses.
Confirm the site published something new, then confirm the feed reflects it. A caching plugin serving a stale feed looks exactly like a broken automation.
Weeks one and two. Create a Courses category and publish your next intake’s courses as individual pages, each with a branded image. Connect the feed to Facebook.
Weeks three and four. Add a Tips category. Four short pieces a month — the explanations your teachers already give twice a week.
Weeks five to eight. Add exam dates as they are announced. This is the feed that gets shared beyond your own followers.
End of term. Read the enrolment form answers. Keep what produced enrolments, tighten what did not, and resist adding more feeds until the existing ones are earning.
By then the school is posting steadily across the whole cycle, including the quiet weeks, with no one writing social posts. For a local business whose customers decide months before they buy, that continuity is the entire point.
No. If your site publishes anything in a dated list — courses, news, blog posts — it almost certainly has a feed already.
No. Automation publishes items appearing in the feed after it starts running, so previous terms are not broadcast.
Use separate categories on the website and point each feed at its own destination, as in the table above.
Aggregate figures need no permissions and work well. Individual results require written permission, and for minors that means a parent or guardian.
Usually yes. A sole tutor has less time for marketing than a school with an office, and the study-tips feed is the cheapest way to be found by people who are still deciding.
Eight to twelve weeks. The decision is made well before enrolment opens.
Study tips and exam information. These are the weeks when a school disappears, and the weeks when future students are quietly comparing options.
Language schools and tutoring centres do not struggle with social media because they have nothing to say. They have term dates, exam deadlines and teachers who explain things for a living. They struggle because the weeks when posting matters most are the weeks everyone is teaching.
Connecting your website’s feeds to your social accounts moves the effort to where it already happens — publishing the timetable, announcing the exam dates, writing down the explanation you gave in class — and lets the posting follow automatically.
Start with course intakes, published eight weeks early, because enrolments are countable. Add study tips next, because they work in the gaps where you have nothing to sell. Add results once your permission policy is written. Done that way, the school is visible through the whole decision cycle rather than only in the fortnight when it is trying to sell.
