# Should your startup have a blog?

Probably not a blog, and probably yes to pages that answer searches. The difference is the shape: a blog is dated posts in reverse order, and most of what a product needs is undated pages that stay accurate for years. This page is about that choice. How often to publish and how many pages to add are separate questions once you have made it.

Updated 2026-09-15 · Source: https://porteur.ai/guides/should-a-startup-have-a-blog

## What a blog is actually for

A blog is a format: dated entries, newest first, usually written to be read once. That format suits some things and suits most product content badly.

| Suits a blog | Suits a page |
| --- | --- |
| A release note, dated and left alone. | How to use the feature it announced. |
| A company decision explained at the time. | The policy that decision created. |
| A study published on a date, cited afterwards. | The method, kept current. |
| A story only true this year. | The guide that is true every year. |
| Your opinion, which readers follow you for. | The answer, which searchers arrive for. |

Most of what a product needs to publish is in the right column: pages that answer a question and get refreshed rather than replaced. Google's freshness systems favour recent content on queries where recency matters, which is news and prices, not "how to import a csv".

## The three ways a startup blog fails

These are not writing problems. They are shape problems, and no amount of effort fixes them from inside the blog.

1. News nobody searches for. "We raised a round", "we are at the conference", "meet our new hire". Real to you, searched by nobody, and it is most of what startup blogs contain.
2. Thin posts written to a schedule. Somebody committed to weekly, and by week six the posts are four hundred words of general advice. That is exactly what Google's scaled content guidance describes.
3. Abandonment. The last post is from fourteen months ago and every visitor can see it. A blog that stops advertises that the company stopped.

> The third failure is the expensive one, because it is visible on a page buyers actually reach. A dead blog linked from your navigation is worse than no blog.

## The test before you write anything

Three questions for each piece you are considering. If it fails the first, do not write it; if it passes the first and fails the others, write it as a page rather than a post.

1. **Does somebody search for this?** Not "is it interesting". Type the question into Google as a buyer would phrase it. If nothing comes back, nobody is looking.
2. **Will it still be true in a year?** If yes, it is a page: no date in the URL, refreshed rather than replaced. If no, it is a post, and that is fine as long as you know it will fade.
3. **Does a page of yours already answer it?** If it does, improve that page instead. A second page on the same search splits the impressions and neither wins.

Almost everything a product wants to publish passes the first two as a page. That is the argument: not "do not write", but "do not write it in a format built for news".

## What to build instead

A library: undated pages grouped by subject, each answering one search, linked from a hub, refreshed on a schedule. Structurally it can live at /guides/ and look nothing like a blog.

| Blog habit | Library habit |
| --- | --- |
| URLs with dates: /2026/09/import-csv | URLs with subjects: /guides/import-csv |
| Ordered by date on an index page | Grouped by subject on a hub page that explains the subject |
| Published and forgotten | Refreshed when the facts change, with the date shown |
| A schedule to fill | A list of questions to answer, ordered by who asks |
| Success is publishing | Success is the page still ranking in a year |

Keep a blog alongside it if you have genuine news or a genuine voice people follow. Release notes, studies and opinions belong there, and they can link to the library where a reader wants the method rather than the story.

## When a blog is the right answer

There are products where the blog is the channel, and they have something specific in common: a voice people follow, or news people wait for.

- A founder who writes well and has an audience that reads them. The blog is distribution for the voice, and the links it earns are real.
- A product where the release notes matter to users, so the changelog is read like a feed.
- A company publishing original data regularly, where each study is an event with a date.
- A category that moves monthly, where a post about this month is genuinely what people search.

Notice what is not on that list: "we heard content marketing works". If the reason to start is that everyone has one, the blog will hit failure two by week six.

## If you already have a blog full of posts

Do not delete it in a weekend. Audit it, decide per post, and act on the data rather than the feeling.

1. **Export twelve months of Performance data by page** Clicks and impressions per URL. Add the internal links and the last update date from a crawl.
2. **Sort into four piles** Ranking and accurate: leave alone. Ranking and stale: refresh. Not ranking but on a real search: rewrite as a page. Not ranking, no search, no links: remove.
3. **Merge the near-duplicates** Three posts on the same subject become one page at the strongest URL, with 301s from the others.
4. **Move the keepers out of the date structure** If the URLs carry dates, decide once whether the migration is worth the redirects. It usually is when the posts still earn clicks.
5. **Leave the news where it is** Release notes and announcements can stay dated. They are doing their job by being dated.

> The point of the audit is not tidiness. It is that pages with nothing to say are pages Google has judged, and removing them is one of the few actions that can help the rest of the site.

## Questions

### Does having a blog help SEO?

Having pages that answer searches helps. The blog format itself does nothing: Google does not reward a posts feed, and it does not favour recent content on queries where recency is irrelevant. Pages that stay accurate beat posts that fade.

### Should a startup blog about company news?

Publish it, but do not expect search traffic from it. Funding, hires and events are searched by almost nobody outside the company. Keep them as a changelog or a news section, and write pages for the questions buyers ask.

### Is it bad to have an abandoned blog?

It is visible, which is the problem. A last post from over a year ago tells every visitor the company stopped. Either remove the date-ordered index and keep the pages that still earn traffic, or publish something.

### Blog or documentation: which first?

Documentation, almost always. It answers real tasks, it proves the product exists, developers search it, and assistants cite it. A blog can wait until you know which questions your buyers repeat.

### Should blog URLs contain dates?

Not for pages you intend to keep. A date in the URL makes an evergreen page look stale and makes refreshing awkward. Use the subject in the slug and show the updated date on the page instead.

## Read next

- [How many pages does a product site need?](https://porteur.ai/guides/how-many-pages-does-a-website-need): The eight pages every product needs, what each page after those must earn, and the point where adding pages starts costing you instead of paying.
- [How often to publish: what actually matters](https://porteur.ai/guides/how-often-should-you-publish): Frequency is not a ranking signal. What a thin page costs, why refreshing counts as publishing, and a rhythm one founder can hold for a year.
- [A content audit for a small site: one table, one decision a row](https://porteur.ai/guides/content-audit): Build a one-table content audit you can finish in a day. See what to keep, refresh, merge, redirect or remove, and what to fix first next quarter.
- [Updating old blog posts: which ones, what to change, what to leave](https://porteur.ai/guides/update-old-blog-posts): Pick the posts worth your hour, make changes that pay, keep the URL, set dates correctly, and know when to merge or retire instead.
- [Topic clusters: the hub, the spokes, and the links that make them one thing](https://porteur.ai/guides/topic-clusters): What a topic cluster is, what makes a hub worth reading rather than a list of links, and the link pattern that holds the whole thing together.
- [Evergreen content](https://porteur.ai/glossary/evergreen-content): Evergreen content is a page on a timeless subject that earns search clicks for years. See how to spot, measure and keep these pages fresh.
- [SEO for documentation: one page per task, the task as the heading](https://porteur.ai/guides/seo-for-documentation): Make your docs the pages buyers and assistants cite: one task per page, clean versions with canonicals, fast HTML, llms.txt, and a dated changelog.

Paste your URL and the free check reads your site and the searches around it in about thirty seconds, then tells you which of your posts still earn clicks and which searches you have no page for. Free check: https://porteur.ai/