How to start a blog on WordPress without overbuilding it

One small business owner on r/smallbusiness said they had spent “around $500 without visible progress” on a WordPress site and were still working through tutorials and templates. That is the usual way a first blog fails. WordPress was not too hard for them. They kept adding layers before the site had published anything.

The setup itself is short. You choose a kind of WordPress, publish a post, decide where posts appear, set the URL structure, and check that search engines are allowed in. Each step is below, followed by what usually breaks and how to tell when the problem is no longer a settings problem. If you are building pages around the blog, our guide to adding pages in WordPress covers that side.

Which WordPress do you actually need?

Decide this first, because the two products work differently. WordPress.org’s own documentation describes WordPress as free, open-source software that you install on hosting you choose. WordPress.com is a hosted blogging service run by Automattic. People mix them up all the time. In a 2025 WordPress.org support thread, the poster expected their WordPress.org account to come with a site and a dashboard. It doesn’t. That account is only for the forums and community.

• WordPress.com fits if you mainly want to write. Hosting, updates and SSL are handled for you. The Free plan puts you on a wordpress.com subdomain with no custom domain.
• Self-hosted WordPress fits if you want full control over themes, plugins and code. You pay for hosting and usually a domain, and you are responsible for updates, backups and security, or you pay a managed host to handle them.

Neither choice is permanent. You can move a WordPress site later. For a business, the blog should usually live on the company’s existing domain. Practitioners on r/marketing give the reason: links and search visibility build up on one domain instead of being split across two.

What does it cost to start a WordPress blog?

It can cost nothing, or several hundred dollars in the first year. Published figures vary because each source counts different things. WordPress.com Free costs $0. When we checked its pricing page, the Personal plan was $9 a month billed monthly or $4 a month billed annually. Annual plans include a custom domain for the first year and monthly plans do not. WordPress.com’s own cost article says a .com domain usually costs $13 to $25 a year after the first year.

For self-hosted sites, cheap shared hosting with an auto-installer is enough for a blog if you are willing to learn by fixing your own mistakes. Managed hosting costs more and takes care of backups and updates. Introductory prices are low, and renewal prices are usually higher and harder to find. Before you choose a cheap host, check whether backups and support are included or sold as extras.

How to set up the blog, step by step

You need administrator access to the dashboard. Every step below happens there, and none of it needs code.

1. Publish one real post. Go to Posts → Add New, write it, and click Publish. In the block editor you then confirm with a second Publish button. Save draft does not publish the post. Your posts page stays empty, or can even return a 404, until at least one post is published.
2. Decide where posts appear. Open Settings → Reading. “Your latest posts” puts the post list on the homepage. “A static page” lets you pick one page as the homepage and a different page, often an empty one called “Blog”, as the Posts page. One page cannot do both jobs. Our guide to editing your WordPress homepage explains why only published pages appear in that dropdown.
3. Set permalinks once. Go to Settings → Permalinks, choose Post name and save. WordPress.org’s permalink documentation says these URLs are meant to be permanent. If you change the structure on a site that already has traffic, old links return 404 unless you add redirects.
4. Let search engines in. In Settings → Reading, untick “Discourage search engines from indexing this site”. WordPress’s Reading settings documentation says this option adds a noindex,nofollow directive to the whole site. Many people tick it while building and forget to untick it.
5. Add only the plugins you have a reason for. A backup plugin and one SEO plugin cover most new blogs. If you use a caching plugin, install only one. Popular plugins have millions of installs, but that only tells you a plugin is popular, not that you need it. Our walkthrough on installing a WordPress plugin safely covers the steps.
6. Check the post the way Google sees it. Add the site to Google Search Console, paste the post’s URL into URL Inspection, and read the result.

When you are done, the post loads at a clean URL like yoursite.com/first-post/, it appears on the homepage or Blog page, and URL Inspection reports no noindex. Leave the theme alone until you have published a few posts. Pick a free theme that already looks close to what you want and get on with writing.

Why the blog page ignores the design you gave it

The Posts page is not a normal page. WordPress builds the list of posts, and your theme decides how that list looks. WordPress.org’s Reading settings documentation says the page’s own content and assigned template may be ignored. If you designed that page in a page builder, your layout will not appear and the page will look different from the one you built.

A 2025 WordPress.org support thread called “Adding a blog” was solved this way: the user set the page as the Posts page in Settings → Reading, then changed the look in the theme’s blog or archive settings. In a block theme, that means editing the blog template in the Site Editor, not editing the page.

Why a published post is not showing in Google

Whether a post displays, whether Google finds it, and whether Google indexes it are three separate questions. A post can look perfect and still not be indexable. Check these in order:

• Site-wide noindex: the “Discourage search engines” box is still ticked.
• SEO plugin settings: Yoast and similar plugins can set a whole post type to noindex. Yoast’s help on common XML sitemap errors says a post is left out of its sitemap if it is noindexed, if its canonical URL points somewhere else, or, for the News sitemap only, if it was published more than 48 hours ago.
• robots.txt used instead of noindex: Google’s documentation on blocking indexing with noindex explains that if robots.txt blocks a page, Google cannot read the page’s noindex. Use noindex to keep a page out of search.

Even with everything set correctly, Google’s sitemap overview says a sitemap helps Google find pages but does not guarantee they will be indexed. A recrawl request is also only a request. New sites get indexed slowly, and they get traffic even more slowly. For titles, descriptions and sitemaps in more depth, see how to do SEO on WordPress.

What breaks first on a new blog, and the first fix

The order below is based on how often each problem comes up in support forums and documentation. Nobody has measured it. Each problem shows a message you can recognise.

“There has been a critical error on this website”

The usual cause is a plugin or theme conflict, often right after you added several things at once. WordPress emails the admin address with details, and if debugging is turned on, wp-content/debug.log names the file involved. WordPress.com’s guide to finding a plugin or theme conflict describes the method: deactivate every plugin, turn them back on one at a time, and switch to a default theme if the error remains. Take a backup first. Our guide to fixing plugins that are not working goes through each step.

“Not secure” or a certificate error after connecting a domain

This is almost always a DNS problem, not a theme problem. Point the domain’s DNS at your host first, then wait for the SSL certificate. WordPress.com says certificates usually arrive within minutes but can take up to 24 hours. A CAA DNS record can also stop Let’s Encrypt from issuing a certificate.

“Error establishing a database connection”

The WordPress Advanced Administration Handbook lists three causes: wrong database credentials in wp-config.php, a database server that is down, or a host limit you have hit. Check the database name, user, password and host against what your host gave you. If they match, contact the host and don’t guess.

The homepage works but every post returns 404

The rewrite rules are stale. Open Settings → Permalinks and click Save Changes without changing anything. If posts still 404, the server may not have Apache’s mod_rewrite enabled, which your host has to fix.

“Publishing failed” or “not a valid JSON response”

Copy your text somewhere safe first. Then try another browser, turn off browser extensions, and look for a plugin conflict. WordPress.com’s support pages connect the “not allowed to assign the provided terms” version of this error to duplicate tags or categories.

When to stop and get help

Stop changing settings when the fix needs server access you don’t have: a database error after you have confirmed the credentials, mod_rewrite, or DNS records at a registrar you can’t log into. Those belong to your host. Stop too if you have spent a week on themes and still have no posts. In a 2019 r/Wordpress thread, one person reported about 120 active hours on a basic blog. Most of that time goes into design work that one published post would make unnecessary.

If you would rather describe the work than do it, SiteSelf for publishers drafts, updates and publishes posts on an existing WordPress site through chat, then checks the live page and reports what changed.