An independent bookshop has the single best raw material for social media of any small business: a constant stream of genuinely interesting things arriving on the shelves, plus staff who have opinions about them. What it almost never has is someone with a free hour to turn that into posts.
The usual result is a Facebook page that was busy for three weeks in 2023, an Instagram account that gets a photo when someone remembers, and an events page on the shop’s own website that nobody outside the shop has ever seen. The books sell themselves in person and reach nobody online.
This guide covers the fix that costs the least time: letting the shop’s own website do the posting. If your site already publishes new arrivals, staff picks or event listings, it is already producing a machine-readable feed of exactly those items, and that feed can post to your social accounts on its own.
Most bookshop websites, whether built on WordPress, Shopify or a small-shop platform, are already generating more structured content than their owners realise. Each of these is a candidate:
Each of those categories can be a separate feed, and each feed can go to a different place. That separation is the whole trick, and it is covered in detail further down.
An RSS feed is a plain, machine-readable list of the newest items a website has published. Your site almost certainly produces one without being asked. On WordPress it lives at your domain followed by /feed/, and every category has its own — /category/staff-picks/feed/, for example. Shopify produces one for blogs and one for products. Ghost, Squarespace and most small-business platforms do the same.
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 uploaded in advance, nothing is scheduled by hand, and no one has to remember anything. Publishing on your own website becomes the trigger.
The practical effect for a bookshop is that adding a staff pick to the website — something a bookseller might do anyway — is the same action as posting it to Facebook, X, LinkedIn and Pinterest. This is the core idea behind RSS automation generally, and it suits bookshops unusually well because the content already exists.
The social post carries the item’s title and a link back to your site. The network then builds its own preview card from the page’s open-graph tags — the cover image, the title and the description your website already declares for sharing. That means the appearance of your automated posts is controlled by your website, not by the automation.
For a bookshop this is good news and one thing to check. The good news: if your product pages show the book cover, the cover is what appears on social media. The thing to check: pages with no image produce a bare post. Adding a cover image to the page fixes it everywhere at once.
A bookshop’s audiences are not the same on every network, and sending everything everywhere is the fastest way to lose all of them. The table below is a reasonable starting arrangement.
| Feed | Best destinations | Rough volume | Why |
|---|---|---|---|
| Events | Facebook, local groups | 2–6 / month | Facebook is still where local event discovery happens for most age groups that attend bookshop events. |
| Staff picks | Instagram-adjacent channels, X, Pinterest | 4–8 / month | Opinionated, shareable, and the closest thing a shop has to a personality online. |
| New arrivals | Pinterest, Facebook | 8–20 / month | Covers are visual; Pinterest keeps working months later, unlike a timeline post. |
| Signed / pre-order | Facebook, X, email | 1–4 / month | Time-sensitive and scarce — the posts most likely to produce a same-day order. |
| Shop news | Facebook only | 1–2 / month | Useful to regulars, uninteresting to everyone else. |
Notice that no single feed goes to every network. A shop running this arrangement posts perhaps twenty times a month across four networks without anyone writing a single post.
Start with what exists. Open your site and add /feed/ to the end of the address. If you see a page of XML, you have a feed. If your platform hides it, look in the page source for application/rss+xml.
Then get the narrower ones. On WordPress, any category produces a feed by appending /feed/ to its address, which means creating a “Staff Picks” category and using it consistently is all the setup a bookshop needs.
Each social account is connected once. A Facebook Page, an X account, a LinkedIn page and a Pinterest board can all run from the same shop.
This is where the table above becomes real. Each pairing of a feed and a destination is set up separately, so events can go to Facebook while new arrivals go to Pinterest, from the same website.
A bookshop’s audience is not reading social media at 04:00. Scheduling controls let you hold posts and release them during hours your customers are actually awake — and stop six new arrivals from firing within a minute of each other on a delivery day.
Most bookshops receive stock in batches. If twenty titles are added to the website on a Tuesday morning and the automation is unrestricted, twenty posts appear within minutes. On Facebook that reads as a glitch; on X it looks like a compromised account; on a local community page it will get you asked to stop.
Two settings prevent it, and both are worth configuring before the first delivery rather than after. A maximum per run caps how many items go out at once. A publishing window spreads them across the day. Together they turn a batch of twenty into a steady trickle over several days, which is also better for reach — a shop posting three good titles a day for a week outperforms one posting twenty in an hour.
Automation will not turn a bookshop into a national account, and any guide claiming otherwise is selling something. What it reliably does is these three things.
It stops the account going dormant. A page that posts several times a week stays in front of the people who already follow it. A page that goes quiet for a month effectively unfollows itself.
It puts your events in front of people who have not walked past the window. Event listings are the single highest-return feed for most shops, because attendance is a real, countable outcome.
It makes staff picks travel. A shelf card is seen by people already in the shop. The same words on a website, posted automatically, reach the people deciding whether to visit.
What it will not do is replace a human entirely. Replies, local conversation, and the occasional photo of the shop cat are still a person’s job. The automation removes the chore — announcing your own stock and events — and leaves you the part that actually needs you.
The page has no open-graph image. On most platforms the featured or product image becomes the open-graph image automatically, so the usual cause is a page published without one.
Something changed the item’s identity in the feed — usually a re-publish, a changed URL, or a product being deleted and recreated. Editing an existing page does not normally cause a repost; recreating it does.
Check that the website actually published something new, then check that the feed reflects it. A caching plugin serving an old copy of the feed looks exactly like a broken automation from the outside.
No publishing window or per-run limit is set. See the delivery-day section above.
The feed is ordered by publication date, not by event date. Publish event pages when you announce them, not on the day, and the ordering takes care of itself.
Do not start with five feeds. Start with the one that has a measurable outcome: events.
Week one. Create an Events category on the website, publish the next three events as pages, connect the feed to your Facebook Page. Watch one post arrive.
Week two. Add staff picks as a second feed. Ask each bookseller for two sentences per book — the same words that would go on a shelf card.
Week three. Add new arrivals, with a per-run limit and a publishing window, pointed at Pinterest and Facebook.
Week four. Look at what actually happened. Which posts got clicks, which events filled, which titles sold. Then tighten the filters rather than adding more feeds.
By the end of the month the shop is posting several times a week, and the total additional work is writing two sentences about books your staff already have opinions about. That is the whole proposition for a local business with more stock than time.
No. If your site publishes anything in a dated list — blog posts, products, events — it almost certainly has a feed already. WordPress, Shopify, Ghost, Squarespace and most small-shop platforms all produce one by default.
No. Automation publishes items that appear in the feed after it starts running, so connecting a feed does not flood your followers with every book you have ever listed.
Yes, and they should. Use separate categories on the website — events, staff picks, new arrivals — and point each one at the destinations that suit it.
Post that one by hand. Automation is for the repetitive majority; nothing stops you posting manually alongside it, and most shops do.
Fifteen to twenty-five across all networks, weighted towards events and staff picks. Beyond that, engagement per post tends to fall faster than total reach rises.
Yes. Give each branch its own category or its own site section, then point each branch’s feed at that branch’s local page. The arrangement is the same, just repeated.
Usually yes, because the cost is close to zero once configured. A local bookshop’s 400 followers are disproportionately people who live nearby and already buy books, which is a better list than most businesses ever build.
Bookshops fail at social media for a reason that has nothing to do with content and everything to do with time. The stock is interesting, the staff have opinions, the events are genuinely worth attending — and the person who would post about it is serving customers.
Connecting your website’s feeds to your social accounts removes the step that keeps failing. Publish the event on your own site, write the two sentences about the book, and the posting happens on its own, on the schedule you set, to the accounts you chose.
Start with events, because you can count the result. Add staff picks, because they are what makes an independent shop worth following. Add new arrivals last, with a limit, because they are the feed most likely to become noise. Everything else is a matter of tightening filters over time — and by then, the shop is posting more in a week than it used to manage in a quarter.
