Tip 2: Post Regularly

Tip 2: Post Regularly

R
Richard Newton
Google has no ideal publishing frequency.

Google doesn’t reward a publishing schedule

A fiddle-leaf fig grows from a large glazed ceramic pot on a wooden shelf, with other potted plants behind it.

Start with the honest bit. Google has said plainly that it has no preferred publishing frequency. No ranking system checks whether you posted on a Tuesday, and there’s no bonus for hitting three posts a week. A store that pushes out 40 thin posts a month can easily do worse than one that publishes four good ones. A single careful guide to choosing a 25 cm glazed ceramic pot for a fiddle-leaf fig will do more for a houseplant store than ten loose posts about indoor greenery.

Volume on its own can actively hurt. Every weak page is something search engines have to find, crawl and judge, and a library padded with them says something unflattering about the whole site. The full case for that is in the 1,000-article store that ranks for nothing, and the mechanics of frequency and recency in automated publishing are covered in our piece on automated blog posting. Neither argument gets repeated here.

This tip survives the honesty test because the thing worth being regular about is the useful page, shipped on time, week after week. Do that and a store gets benefits that have little to do with an algorithm counting posts, and a lot to do with how shoppers, seasons and small teams behave.

What a steady rhythm of useful pages buys a store

A person is repotting a leafy houseplant with its exposed root ball over a worktable covered in soil and pots.

Coverage that adds up

Each useful page answers a question your site previously ignored. Take a store selling houseplants and pots. One guide on repotting is a page. A year of steady work gives it repotting, drainage, pot sizing, winter watering, low-light plants and pet-safe plants, all linking to each other and to the right collections. That body of work is a different asset from the same number of posts scattered across whatever seemed timely. Grouping it deliberately is the subject of Tip 5 on clustering.

Seasonal lead time

New pages take time to be discovered, indexed and settled in the results. Weeks at the very least, often months. A store that writes its Christmas gift guide in mid-December has, in practice, published it for next year. The same goes for the spring repotting guide written in April, when the people who needed it have already bought their pots somewhere else.

A steady rhythm is what lets you work ahead of demand. When pages go out every week or fortnight, putting the autumn buying guide into the August slot is a scheduling decision. When pages go out in panicked bursts, it never happens.

A learning loop you can use

Publish monthly and you get a dozen data points a year, spread across seasons that behave differently. Publish weekly and within a quarter you can see which kinds of pages pick up impressions, which earn clicks and which sit untouched. Search Console will tell you most of this, provided there’s enough new material for a pattern to show.

A habit the team can keep

Bursts are usually a symptom. Someone clears a fortnight, writes eight posts, then gets pulled back into product launches and nothing ships until spring. A modest, fixed slot survives busy months far better than good intentions do.

Work out a cadence you can actually sustain

A person pours water from a clear pitcher into the reservoir of a self-watering planter beside green plants.

Pick your number backwards, from capacity and from the supply of genuinely useful topics. Advice that says every store should post three times a week skips both.

  1. Count your supply. List the real shopper questions your site doesn’t yet answer well, using the sources in Tip 1: support emails, return reasons, reviews, site search. A focused range might produce 40 solid topics. A broad catalogue might produce hundreds.
  2. Time one page honestly. Research, drafting, checking product facts against the spec sheet, images, internal links, publishing. Time a real one rather than guessing, because most teams underestimate the checking. Testing a self-watering planter properly, for example, means filling its reservoir and timing how long it really lasts.
  3. Divide, then take some off. If you have one day a week for content and a good guide takes half a day, that’s two a week on paper. Plan for one and keep the spare time for refreshes and for the week everything goes wrong.
  4. Check runway against supply. At one page a week, 40 topics is about nine months. That tells you when the next round of question-mining needs to happen.

The number that falls out might be one page a fortnight. That’s fine. Write it down, give it a fixed day, and treat the slot as a commitment the way you would a stock order.

A fortnightly guide that reliably answers a real question beats a burst of a dozen posts in January followed by silence. By June the fortnightly store is still covering ground and still learning, while the burst store is wondering what went wrong.

Refreshes count as publishing

A woman repots a leafy plant into a glazed blue planter beside an empty terracotta pot.

Rhythm doesn’t have to mean new URLs. Updating a sizing guide after a product is recut, adding this season’s colours to a care guide, or merging two thin posts into one strong page are all real improvements to what shoppers find. In a plant shop, that might mean rewriting the care guide for its 20 cm terracotta pot when the supplier switches to a glazed finish that holds water longer.

Once a library passes a few dozen pages, most stores should split their slots between new pages and refreshes. Choosing which pages deserve the attention is a method of its own, set out in our guide to content refresh prioritisation. One warning: changing the date on a page without changing its substance fools nobody, least of all the shopper who notices last year’s prices.

Build a queue, then a calendar

A ceramic plant pot with a visible drainage hole sits on a wooden potting bench beside soil and a hand trowel.

The practical tool is a queue: a ranked list of briefs, each with the decision the page helps a shopper make, the products it leads to and the date it needs to be live by. The calendar is just the queue with dates attached, and the queue should always be longer than the calendar so a slipped week doesn’t leave a gap.

Here’s what the houseplant store’s autumn queue might look like:

  • Live by early September: bringing outdoor plants inside for winter and what to check first, linking to pest treatments and larger pots.
  • Live by mid-September: low-light houseplants for north-facing rooms, linking to the low-light collection.
  • Live by early October: how often to water houseplants in winter, answering last November’s most common chat question.
  • Live by mid-October: pots with and without drainage holes, written because “no drainage” is a recurring return reason.
  • Refresh by early November: the existing gift guide, rebuilt around current stock and prices.

Notice what isn’t on the list. You won’t find a “10 best houseplants” post because a competitor has one, no near-duplicate of the watering guide aimed at “watering schedule for indoor plants”, and no news post about a trade show nobody searches for. Each of those would fill a slot. None would help a shopper decide anything.

Every item that did make it earns its slot by answering something shoppers ask. The order comes from the season and from when demand starts, which is usually earlier than the peak in sales. Keyword volume helps break ties.

Signs your cadence has outrun your usefulness

More is only better while each page stays worth reading. Slow down if you notice any of these:

  • New posts overlap existing ones heavily, aimed at a slightly reworded version of the same query.
  • Nobody on the team would send the latest few posts to a customer who asked the question.
  • A growing share of pages still has no impressions several months after going live.
  • Search Console shows a rising number of new URLs as crawled but not indexed, a sign Google has looked and decided they aren’t worth including. Fix that before adding more URLs to the pile.
  • Product facts in older posts are going stale because every hour goes into new ones.

When the signs appear, pause new pages for a cycle. Merge the overlaps, fix or remove the weak ones, and restart at a pace the checking can keep up with. If a new post on a copper plant mister repeats what the humidity guide already says, fold it into that guide.

Consistency at small-team scale

A woven jute planter hangs from the ceiling among lush indoor plants in a sunlit plant shop.

The hard part for most stores is keeping the slot filled with pages that are genuinely useful, month after month, with one or two people. In a two-person plant shop, it is the difference between a guide to a hanging jute planter going live before spring and one that sits half-written until summer. That’s the problem Sprite is built for. At Whitestep, one person manages three brands; over a three-month period they added 142 pages, a +62% increase in new content, alongside +90,000 non-brand impressions and +13% organic clicks, as set out in the Whitestep case study.


This is Tip 2 in Sprite’s 11-part series on ecommerce content that compounds. Next: Tip 3: Tell Stories.

Frequently asked questions

How many blog posts a month should a Shopify store publish?

No single number is correct, and Google doesn’t use one. Work it out from two limits: how many genuinely useful topics you have queued, and how many pages your team can research, write and fact-check properly in a month. For many small stores that lands somewhere between two and four pages a month to begin with. Keep it steady for a quarter, look at what the pages achieved, and only raise the pace if quality holds and you still have real shopper questions left to answer.

Will publishing more often make Google crawl my store more?

Not in any way worth chasing. How much Google crawls a site depends mainly on its size, its technical health and how much demand there is for its pages. Publishing more low-value URLs gives Google more to wade through without giving it a reason to rank any of them. The reliable way to get new pages found is ordinary housekeeping: keep your XML sitemap current, link each new page from relevant existing pages and collections, and make sure the page answers something people search for.

Do updates to old posts count towards a publishing schedule?

Yes, when the update is substantial. Rewriting a sizing guide after a product is recut, merging two overlapping posts into one stronger page, or rebuilding a gift guide around current stock all improve what shoppers find, and they deserve a slot in the calendar as much as a new URL does. Changing a date, swapping a few words or adding a paragraph of filler does not count. A useful rule is that a refresh should change what a shopper would decide after reading the page.

I’ve published a lot of weak posts. What should I do with them?

Audit before you add anything new. Export your blog URLs with their Search Console impressions and clicks, then sort each post into one of four piles: keep, improve, merge into a stronger page, or remove. Posts that overlap should be merged and redirected to the surviving page. Posts with no search demand and no value to customers can go, with a redirect if anything links to them. Then restart publishing at a pace your team can check properly, so the problem doesn’t rebuild itself.

Sprite builds brand authority through continuous, automated improvement. Quietly. Consistently. And at Scale.

No commitment
30-day free trial
Cancel anytime
Powered bySprite
Your Turn

See What You Could Save

Discover your potential savings in time, cost, and effort with Sprite's automated SEO content platform.