← Insights

Shopify blog SEO: what a store blog can and cannot do

Whether a Shopify blog helps SEO, what Google's Article markup actually requires, and how posts should link to your collections.

6 min read

Contents · 5 sections

Does a Shopify blog help SEO?

It can, and the reason is narrower than most advice suggests. Product and collection pages are written to sell, so they rarely answer the question a shopper types before they know what to buy: which material lasts, how sizing works, what the difference between two options is. A blog post is a page whose whole job is one such question. If you answer it better than the pages that rank today, you can appear for a query your catalogue pages never would have matched.

What a blog cannot do is rescue a store whose basics are broken. If your collections have duplicate or thin copy, or your product pages are slow, posts do not fix that. Treat the blog as a second front that works only if the first one is sound. For a fast read on the first one, the audit checklist is the right place to start.

We make no traffic promise here, and you should be suspicious of anyone who does. How a post performs depends on competition for the query, which this article cannot know for your store. What you can do is pick questions where a clear, specific page is missing, and check results in Search Console after a few weeks.

What does Shopify give you for blogs and articles?

Shopify's theme language models a blog as a container and an article as a page inside it. According to the blog object reference, a blog has a handle, a list of its articles, a count of articles that excludes hidden ones, and the tags used across its articles. The same reference notes that the paginate tag controls how many articles show per page, up to a limit of 50.

The article object reference lists what each post carries: a title, an author name, the content, an optional excerpt, a featured image, tags, a publish timestamp, an updated timestamp, and a relative URL. Most of these are things you already fill in when you write a post. Two are worth a deliberate decision:

  • The excerpt. The reference says excerpt_or_content returns the excerpt if one exists and the full content otherwise. If your blog index prints it, a missing excerpt means the index shows the start of the body instead. Write one sentence per post.
  • The featured image. Themes read it for the blog index and for sharing. An image that actually shows what the post is about is more useful than a stock banner, and gives you a place to write meaningful alt text.

To see the URL pattern your posts use, open any live post and read the address bar. The url property is the relative form of that address, and it is what your internal links and sitemap entries should match.

What structured data should a blog post carry?

Google's Article structured data documentation is more relaxed than people expect. It says there is no markup requirement to be eligible for Google News features and that Article markup is there to tell Google more explicitly what the page is about. It also says there are no required properties: you add the ones that apply. The recommended ones are:

  • headline, the title, which Google suggests keeping concise because long titles may be truncated on some devices;
  • image, a crawlable and indexable image that represents the article;
  • datePublished and dateModified, in ISO 8601 format, ideally with timezone information;
  • author, as a Person or Organization with a name and, where possible, a URL that identifies them.

The type must be one of Article, NewsArticle or BlogPosting.

Shopify can produce this for you. Its structured_data filter reference says the filter works on product and article objects, and that an article is output as a schema.org Article. Your theme may already apply it on the article template, so the useful check is simple:

  1. Open a published post and view the page source.
  2. Search for application/ld+json and read the block that mentions Article.
  3. Confirm the headline matches the title on the page, the dates are present, and an author is named.
  4. Paste the URL into Google's Rich Results Test to see what it parses.

If the block is missing, adding {{ article | structured_data }} inside a script tag of type application/ld+json in the article template is a small theme change. If you add fields by hand, keep them to what is visible on the page: an author name in the markup should be the author name a reader can see.

Breadcrumbs are a separate block with their own rules, covered in the breadcrumb schema guide.

This is the part most Shopify blogs get wrong. A post that answers a pre-purchase question has already done the hard work; the next step is a link to the collection or product it points toward. Use a descriptive anchor, such as the collection's name, rather than "click here" or "shop now".

Some rules we apply:

  • Link up the funnel from every post. One or two links to the most relevant collection, placed where the reader would plausibly want to see the range, beat a block of ten at the bottom.
  • Link across the blog sparingly. Related posts are useful; a wall of tags is not.
  • Keep the target stable. If you rename or merge a collection, set the redirect. The 404 and redirects guide covers how.
  • Use one version of each page. Link to the clean canonical address, not a filtered or parameter version. See canonical URLs on Shopify.

New posts also need to be discoverable. The sitemap guide explains what Shopify's sitemap includes and how to submit it. A post with no links from any other page and a place only in the sitemap is a weak signal; link it from the blog index and from a related collection or post.

What should you write about first?

Start from questions, not keywords. Your own inbox, chat transcripts and the questions your support team answers most often are a better source than a keyword tool, because they show what your actual buyers ask. A reasonable first batch:

  1. The comparison between your two most-confused products.
  2. The sizing, fit or compatibility question you answer by email every week.
  3. The care or maintenance question that arrives after purchase.
  4. The "what to look for" question for your main category.
  5. The delivery, returns or customs question that stops people from checking out.

Write each one as the page you would want to land on: the answer in the first paragraph, specifics after it, one link to the relevant collection. Then wait. Check the Search Console queries for those URLs after several weeks and improve the posts that show impressions but few clicks.

If you would rather have someone read your store and tell you which of these will matter for your catalogue, that is what the Store Teardown is for. The services page shows how we build this into themes.

Next step

Own your growth.Start with the teardown.

Read it, then decide whether you want us to fix what it finds.