Diagram: money pages sit in the permanent site hierarchy as pages, while blog posts form a dated timeline that links up to them — Pages are the permanent structure of your site; posts are the dated blog that links up into it.

Every website has a few pages that carry the business. The page where someone buys. The service page that turns a search into a phone call. The landing page your ads point to. Those are your money pages, and they matter more than the hundreds of other pages around them, because more traffic times a higher conversion rate equals more revenue.

So it’s worth knowing exactly where those pages live on your site and protecting that spot. One of the quietest ways to hurt a money page is to turn it into a blog post. It looks like a small change. It is not.

Let me walk through the difference between a page and a post, which pieces of your site belong as one or the other, and why moving a money page into the blog costs you formatting and search rankings at the same time.

What a money page actually is

A money page is any page built to convert, not just to inform. On most sites that’s a short list: the main offer or product page, the landing pages behind your ads, your core service pages, your location pages if you serve specific areas, and any long-form sales page or VSL (video sales letter).

These pages earn the name because the math runs through them. If a page gets meaningful traffic and converts well, small improvements there are worth more than anything you could do on a page nobody buys from. We treat our own offer and service pages at Local Service Spotlight exactly this way. On a plumber’s site, the “emergency drain cleaning in [city]” page is a money page. Everything else on the site exists to support pages like these, or to bring people to them.

That framing matters for the next decision, because money pages should almost always be pages, in the technical WordPress sense, and rarely posts.

Pages and posts are two different parts of a website

WordPress gives you two main ways to publish: pages and posts. They look almost identical in the editor, which is why they get mixed up, but they play different roles.

Pages are the permanent structure of your site. Home, About, Contact, your services, your offers. They live in a hierarchy, where a page can have a parent and children, which is how you get clean paths like /services/roof-repair/. Pages aren’t tied to a date, they’re not meant to expire, and they usually sit in your main navigation. Think of pages as the rooms of the house.

Posts are the blog. A post is a dated entry on a timeline. Posts flow into your blog feed newest first, get sorted into categories and tags, and roll down and out of sight as newer posts publish above them. Think of posts as the newspaper that lands on the porch each morning: useful, but tied to a moment, and replaced by tomorrow’s edition.

Dennis Yu describes this as the main site hierarchy versus a timeline-based blog, and the distinction holds even if you eventually move off WordPress. Every real content system has some version of permanent structural pages and time-ordered content. The names change. The two jobs don’t.

What deserves to be a page, and what belongs in the blog

Here’s the simple test. If it’s part of your permanent structure, something you’d put in the navigation and expect to still be selling a year from now, it’s a page. If it’s tied to a moment and meant to flow through a feed, it’s a post.

Pages: your money pages, core service and location pages, About, Contact, and your pillar or definitive content, the deep reference articles you want to own a topic.

Posts: blog articles, news, announcements, podcast episodes, event recaps, and case studies or examples that are true for a moment and link up to the page they support.

That last part is the key. In the SEO Tree, the way we think about how every piece of content connects, pages are the trunk and the major branches, and posts are the leaves. A leaf strengthens the branch it hangs from. A case study post about one customer links up to the service page it proves. The post does its job by pointing authority at the page, not by trying to be the page.

So a money page as a post is backwards. You’d be taking something structural and dropping it into the timeline, where it competes with every other post instead of anchoring a branch of your site.

Why moving a money page into a post costs you

Three things break when a page becomes a post, and none of them are obvious the day you do it.

You lose the structure, and the SEO value that comes with it. A page sits in your hierarchy and collects internal links from your navigation and related pages, which is a large part of how search engines decide it matters. A post drops into the blog, gets buried under newer posts, and lives in category and tag archives instead of your site structure. Converting a page to a post loses that SEO value even if you add tags and categories to make up for it. The URL usually changes too, so if the old page had any ranking history or backlinks, those now point at a 404 unless you set up a redirect.

You lose the formatting. Money pages are usually built with a page builder or a custom layout: a hero section, blocks, calls to action, the whole design. Posts render inside your blog’s single-post template, which is built for articles, not landing pages. Move the content across and the layout you designed collapses into a plain article body. The page still exists as words, but the thing that made it convert is gone.

You risk having two pages fight each other. If you convert a page to a post but leave the original page up, or you build a post next to a page that already exists, you now have two URLs targeting the same thing. Google and AI assistants have to guess which one is canonical, your internal links split between them, and neither ranks as well as one strong page would. Having both a page and a post for the same offer is a classic sign of a structure problem, the kind of duplication the SEO Tree exists to prevent.

The trap: preferring how a post looks is not a reason to use one

There are real cases where a post is the right call. Dated content, announcements, episodes, and examples all belong in the blog. If you’re publishing something that’s true for this moment and meant to flow through a feed, use a post.

The trap is everything else. Maybe the blog template looks cleaner to you. Maybe posts show an author byline or an author profile and your pages don’t. Maybe you just prefer how the single-post layout reads. Those are real preferences, and none of them is a reason to change what a page fundamentally is. The structural integrity of your site matters far more than any of them.

So when you feel the pull to convert a money page into a post because of how the post looks or what it happens to show, stop. You’re about to trade something that matters, where the page sits in your site, for something that doesn’t, a surface detail you can get another way.

You can rebuild the look on the page, without changing the type

Here’s the part that dissolves the trap. Anything you liked about the post, you can put on the page. If you want a byline, an author box, a date, or the exact feel of the blog layout, you or an agent can build that onto the page visually. The page keeps its structure, its URL, and its place in your hierarchy, and it still shows whatever you wanted to see.

Most of the time you don’t even need it. A money page rarely needs a visible author to do its job, and the things people reach for a post to get are usually decoration, not function. But if you truly want a certain element on the page, add it to the page. Don’t reach for a post to get it, and don’t convert a page into one to keep it.

The deeper point is bigger than any single detail. You might be sure a page needs some specific thing, and you might even be right that you want it. That still is not a reason to turn the page into a post. Decide page versus post on structure. Solve everything else on the surface.

A quick decision guide

Is this a page where people buy, book, or convert? Make it a page. Always.

Is it timeline content, news, an episode, an announcement, or a specific example? Make it a post, and link it up to the page it supports.

Do you want something a post has, like a byline, an author box, or a certain look? Put it on the page visually. Don’t change the content type to get it.

Do you already have both a page and a post for the same thing? Pick one canonical URL, redirect the other to it with a 301, and consolidate your internal links onto the survivor.

Before you publish anything, know where it sits in your site: which page it belongs to, and whether it links back. If you can’t answer that, you haven’t found its place in the structure yet.

Why this is worth getting right

Money pages are where marketing turns into revenue, so they deserve to be treated as the structural assets they are. Keep them as pages, protect their URLs, build them to convert, and let your posts do the supporting work of pointing traffic and authority up to them. Solve the styling, the formatting, and every other surface question without touching the thing that decides where a page lives.

Get the structure right once and it keeps paying off, on WordPress today and on whatever you build on next. The tools change. A money page is still a money page.

Money Pages vs. Blog Posts: When Something Should Be a Page, Not a Post