Publish and edit blog posts from a Google Sheet

A blog is just a spreadsheet

Strip a blog down and every post is a handful of fields: a title, a URL slug, a publish date, some tags, and the body. That is a spreadsheet row. Yet most blogs drag in a full CMS, a database, and an admin login to manage what is fundamentally a table your writers could edit in their sleep.

PasteSheet turns a Posts tab into a content API. Writers draft in Google Sheets — a tool they already know — flip a status cell to published, and your front end picks it up on the next cache refresh. Slugs map to routes, the body renders as Markdown or HTML, and there is no migration to run when you add a column.

Columns that map to a post

One row per post, one column per field. A typical layout:

• title, slug, and excerpt for the listing and the route.
• published_at to sort newest-first and status to gate drafts.
• tags for filtering and author for bylines.
• body holding Markdown or HTML your renderer turns into the article.

Fetch the published feed

Filter to published rows and sort by date with URL parameters — drafts stay hidden simply by not being marked published:

curl "https://pastesheet.com/your-endpoint/Posts?status=published&sort=-published_at&per_page=10"

{
  "data": [
    {
      "title": "Why we moved our blog to a spreadsheet",
      "slug": "blog-in-a-sheet",
      "excerpt": "No database, no admin panel — just rows.",
      "tags": "engineering, meta",
      "author": "Dana Lee",
      "published_at": "2026-07-09",
      "status": "published"
    }
  ]
}

Read-only, so it is safe to publish

Because the endpoint is read-only by design, it is safe to expose publicly or hand to a teammate: consumers can read and query the data but can never change the sheet. And there is no Google Cloud project, OAuth screen, or service account to set up — you paste a share URL and get a live API.

What it costs

Frequently asked questions

Sources

• Files you can store in Google Drive (size limits) — Google

Related use cases