Web Design

Blog Page Design: How to Lay Out the Blog Index and the Post So People Keep Reading

The results for "blog page design" are galleries: Dribbble shots, template stores and lists of attractive SaaS blogs. They show what blogs look like. They do not give the numbers behind a readable post or the rules that decide how Google reads your dates and page two. This guide does, using the W3C's and Google's own pages read on 11 November 2026, plus the measured layout of the page you are reading.

Blog Page Design: How to Lay Out the Blog Index and the Post So People Keep Reading

Key takeaways

  • A blog has two templates, and they do different jobs. The index helps people find a post; the post page helps them read it and take a next step.
  • Keep lines short. The W3C's strictest readability criterion for text blocks names a width of no more than 80 characters; this page runs at about 75 on a desktop screen.
  • Give text room. The same W3C criterion names line spacing of at least one and a half within paragraphs, and no justified text.
  • Show a visible date, labelled. Google's byline date guide asks for a prominent user-visible date with a label such as "Published" or "Last updated", matching any date in structured data.
  • Paginate with real links. Google's pagination guide says each page needs its own URL and canonical, linked with normal links, and no page numbers after a #.
  • One call to action per post, matched to the topic. A related service or a next read beats a pop-up on every page.

The short answer

Design the blog index for finding and the post for reading. The index needs a featured post, topic filters, clear cards with title, date and a one-line summary, and real page links at the bottom. The post needs a narrow text column, generous line spacing, a visible labelled date, a short summary at the top, headings that work as a table of contents, and one relevant next step at the end.

Who is writing: Amariq designs and builds websites, and this blog is one of them. Where we give numbers for our own layout, we measured them on this page on 11 November 2026. Rules come from the W3C's and Google's own pages read the same day.

What ranks for this search, and what it leaves out

On 11 November 2026, Google (US, English) showed mostly inspiration for "blog page design": Dribbble, Webflow's blog templates, Figma's free blog templates, Land-book, an Awwwards collection, a SaaS Landing Page list of 40 blog pages, Pinterest, Unsection, and an OptimizePress list of 18 blog designs (17 June 2026). Google's AI answer mentioned a narrow reading column of 60 to 70 characters, line height of 1.5 to 1.6, tables of contents, author boxes and calls to action, credited mostly to YouTube videos.

The galleries are useful for taste. What a site owner still needs: which numbers come from a standard rather than habit, how the index and post differ, and what Google says about dates and page two of a blog. Those are below.

Two templates, two jobs

Blog index (the list)Blog post (the article)
Main jobHelp a visitor find something worth readingHelp them read it and take a next step
Above the foldTitle, one line on what the blog covers, featured postTitle, date, summary or key points
Main contentCards or a list, topic filtersOne narrow text column
NavigationTopics, paginationHeadings, table of contents, related posts
Next stepOpen a postOne call to action that fits the topic

Mixing them causes most blog problems: an index that tries to sell, or a post page cluttered with sidebars and banners that pull attention from the text.

The blog index page

Start with a short intro. One sentence on who the blog is for and what it covers. It helps readers and gives the page words of its own beyond titles.

Feature one post. The newest, or the one that matters most to your business. Larger image, title and summary.

Let people filter by topic. Five to eight topics that match your services. Each topic can have its own page, which also helps search engines understand your site's structure.

Design cards for scanning. Each card needs:

  • A clear title, the same as the post's
  • The date
  • A one-line summary
  • The topic
  • An image, if you have a real one; a plain typographic card beats an irrelevant stock photo

Use a list or a grid. Grids suit visual posts and short titles. A list with summaries suits long titles and text-led blogs. Either way, keep six to twelve posts per page, so the first page loads quickly.

Pagination that search engines can follow

Google's pagination guide, read on 11 November 2026, sets out what page two and beyond need:

Google's guidanceWhat it means for your blog
Link pages in order with normal links"Next" and page numbers are real links, not buttons that only run a script
Give each page a unique URL/blog/page/2 or ?page=2, not the same address for every page
Give each page its own canonicalDo not point page 2 and 3 back to page 1
Do not use # fragments for page numbersGoogle ignores what follows a #
rel="next" and rel="prev" are no longer used by GoogleThey do no harm, but they are not what Google reads

Google also says pages in a paginated sequence do not need distinct titles, and suggests linking every page back to the first page of the collection. A "load more" button is fine for people, as long as there are also crawlable links to the same posts.

The blog post page

The reading column

The W3C's success criterion 1.4.8, Visual Presentation, is a Level AAA criterion, the strictest tier. For blocks of text it lists:

  • Width of no more than 80 characters or glyphs (40 for Chinese, Japanese or Korean)
  • Text not justified to both margins
  • Line spacing of at least one and a half within paragraphs
  • Paragraph spacing at least 1.5 times larger than the line spacing
  • Text that can be resized to 200 percent without scrolling sideways to read a line

The W3C notes that content does not have to use these values; a way for users to get them must exist, and the browser can provide it. Still, they make a sound default for anyone designing a post template.

How this page measures, at a 1920 pixel wide desktop screen on 11 November 2026: the text column is 672 pixels wide, body text is 19 pixels with a 30.4 pixel line height (1.6), and a typical paragraph runs at about 75 characters per line. It sits inside the W3C's 80 characters.

SettingCommon starting pointThis page
Column widthNarrow enough for under 80 characters a line672 px, about 75 characters
Body text sizeLarge enough to read without zoom19 px
Line heightAt least 1.51.6
AlignmentLeft aligned, not justifiedLeft aligned

The top of the post

Readers decide in seconds whether to stay. Give them:

  1. The title, the same as in search results where you can.
  2. A visible date with a label. Google's byline date guide asks for a user-visible date shown prominently, labelled with words such as "Published" or "Last updated". It also asks that visible dates match the dates in structured data, and that you do not use future dates or the date of an event described in the post.
  3. A short summary or key points. Many readers want the answer first.
  4. The author or business behind it. A name and a line on why you know the subject.

Inside the post

  • Headings every few paragraphs that say what the section answers. They double as a table of contents.
  • Tables for comparisons, not long paragraphs of numbers. Make them scroll sideways on phones instead of squashing.
  • Images that explain. Screenshots, diagrams and real photos. Write alt text that says what the image shows.
  • Links in the text to related posts and services, written as words that describe the destination, not "click here".
  • No sidebars fighting the text. Put related posts and the call to action after the content, or between sections at most once.

The end of the post

Close with one next step that fits the topic: a related service, a tool, a consultation or the next post in a series. A post about pricing can end with a quote request; a post about a technique can end with the next read. One clear choice beats a row of five buttons. Our call to action examples show wording that works.

Mobile

Most of the rules hold on phones, with a few changes:

  • The column fills the screen with side padding of about 16 to 24 pixels.
  • Body text stays large; do not shrink it to fit more on screen.
  • Tables scroll sideways inside their own box.
  • A sticky header should be short, so it does not eat the reading space; see our sticky header guide.
  • Test at 390 pixels wide for horizontal scrolling, a common sign of a broken table or a long link.

Speed and accessibility

Blog pages carry many images, which makes them slow if left unchecked. Size images to the column width, use modern formats, and lazy-load images below the first screen. Our speed test guide explains how to measure. Check contrast between text and background, keyboard focus on links, and heading order; our accessibility checklist covers each.

A blog page design checklist

CheckDone?
Index has a one-line intro, a featured post and topic filters
Cards show title, date, summary and topic
Pagination uses real links and unique URLs
Each paginated page has its own canonical
Post text column stays under 80 characters a line
Line height at least 1.5, text left aligned
Visible, labelled date that matches structured data
Summary or key points at the top
Descriptive links to related posts and services
One call to action that fits the topic
No sideways scrolling at 390 px except inside tables

How Amariq can help

We design and build blogs as part of business websites on Webflow, Framer, WordPress, Shopify, Wix, Squarespace or a custom stack, with an index, post template and topic pages your team can update. Each project is priced from its scope, never by the hour, with 40% to start, 30% at design approval and 30% before launch. Once the final payment is made, the design, copy and code belong to you, and your domain, hosting and analytics accounts sit in your name. See our web design service or browse this blog to see the layout in use.

Frequently asked questions

What is the best layout for a blog page?

For the index, a featured post followed by a list or grid of cards with title, date, summary and topic, plus topic filters and real page links. For the post, a single narrow text column with headings, a visible date and one call to action at the end.

How wide should a blog post be?

Narrow enough that lines stay under 80 characters, the limit in the W3C's Visual Presentation criterion. On this site that is a 672 pixel column with 19 pixel text, about 75 characters a line.

Should a blog post show the date?

Yes. Google's byline date guide asks for a prominent, labelled, user-visible date that matches any date in structured data. Readers also use it to judge whether advice is current.

Is infinite scroll bad for a blog?

Not for readers, but search engines need crawlable links to every post. Google's pagination guide says to give each page its own URL and link pages in order with normal links, so add those alongside any "load more" button.

Should a blog have a sidebar?

It is optional. A sidebar can hold topics or a signup, but on most business blogs it competes with the text and disappears on phones anyway. Many sites put related posts and the call to action after the article instead.

How many posts should show on a blog index page?

Enough to scan without a long load, often between six and twelve. Use pagination or a "load more" button with crawlable links for the rest.

Rahat Khondokar, founder of Amariq

Rahat Khondokar

Founder & CEO, Amariq

Rahat designs and builds websites for marketing teams and ecommerce brands, and writes here about the structure, copy and conversion work behind them. More about Amariq. Find him on YouTube, Dribbble and LinkedIn.

Keep reading

Related articles.

All articles